339 results found

1. Move closures history to the Closures tab

   Move the information about the closures history of a segment from the General to the Closures tab. This way the closures information won't interfere with important segment changes history and it will be easy to look the specific information. The "last date" will then be correct for each of them - segment changes and closure changes. Also, being in the Closures tab will allow for more data about the closure to be included (incorporating Script features - URO+ or the new WME History Enhancer).

   https://greasyfork.org/en/scripts/449557-wme-history-enhancer

   39 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   Looking into the suggestion  ·  2 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Ability to snap area places to road
   27 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Need more details  ·  AdminElla (Waze Team) (Admin, Waze) responded

   Thank you for reaching out. We don't have enough details to thoroughly investigate this idea so we will close it now. If this idea is still relevant, please submit it again and include all relevant details.

3. Add closed map suggestions count to profile page

   It'd be great if you could track how many map suggestions you have closed. You can already see your closed UR, PUR, and MP counts on your profile page so it would be great if closed map suggestions could also be added.

   Here is a simple mockup I made of what that could look like: https://i.imgur.com/XajOINK.png

   52 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  General  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Looking into the suggestion  ·  Tam (Waze Team) responded

   Great timing! We’re currently working on being able to track the number of closed map suggestion. Keep an eye out for updates on the WME.

4. Ability to select long stretches of road

   A feature that would allow defining a start and an end point and which would automatically select the road between them would be very helpful. There is somtimes a need to select a length of road in the tens or even hundreds of kilometres. (The alt-click trick doesn't work for such long distances.)

   Two use case examples:

   1) RTC on long stretch of highway

   There have been several highway closures due to winter storms recently. Selecting the entire road to be closed requires lots of panning and selecting individual segments, which is very time-consuming.

   2) Making changes to long stretches of road

   Example: changing the speed limit, road type, name, etc.

   A feature that would allow defining a start and an end point and which would automatically select the road between them would be very helpful. There is somtimes a need to select a length of road in the tens or even hundreds of kilometres. (The alt-click trick doesn't work for such long distances.)

   Two use case examples:

   1) RTC on long stretch of highway

   There have been several highway closures due to winter storms recently. Selecting the entire road to be closed requires lots of panning and selecting individual segments, which is very time-consuming.

   2) Making changes to long stretches… more

   56 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  General  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Looking into the suggestion  ·  Tam (Waze Team) responded

   Great timing! We’re currently working on being able to select long streches of road. Keep an eye out for updates on the WME.

5. Harmonize poor-road nomenclature to "Poor roads"

   Please harmonize the nomenclature Waze uses for roads that may beat up cars or get them dirty.

   Currently, WME allows marking segments as "unpaved", while the companion feature in the app allows the driver to avoid "dirt". But unpaved and dirt are two different things; for example, many would consider a gravel road to be unpaved, but few would call it dirt. Meanwhile, even some paved roads have such poor surface quality that local drivers might wish to avoid them in favor of better alternatives.

   Since the underlying goal is to allow drivers to avoid roads with poor surface quality, why not harmonize the nomenclature to "Poorly surfaced roads" or just "Poor roads"? Using this nomenclature instead of "unpaved" or "dirt" would better match the goal of the feature, and would encourage local editors to apply the feature in ways that make sense for their road environment and Wazing community.

   Failing that, WME and the app should at least use the same terminology anyway.

   Please harmonize the nomenclature Waze uses for roads that may beat up cars or get them dirty.

   Currently, WME allows marking segments as "unpaved", while the companion feature in the app allows the driver to avoid "dirt". But unpaved and dirt are two different things; for example, many would consider a gravel road to be unpaved, but few would call it dirt. Meanwhile, even some paved roads have such poor surface quality that local drivers might wish to avoid them in favor of better alternatives.

   Since the underlying goal is to allow drivers to avoid roads with poor surface quality,… more

   15 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   Looking into the suggestion  ·  1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Replace ':' and '>' by a direction field

   Hi guys,

   The idea would be to replace the ':' or '>' instructions present on segments by a direction field that
   would not display on the segment name but would allow to construct the guidance instructions.

   This would allow to properly manage the direction signs in the city without having this kind a street : "Street Chip: Dale area" and easily managed the directions in roundabouts, etc.

   Thanks for your feedback.

   by Ardillon42
   Link to original suggestion: https://www.waze.com/forum/viewtopic.php?f=1525&t=287620

   17 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   We're working on it  ·  AdminWaze Team (Admin) (Admin, Waze) responded

   Hey!
   Thank you for this suggestion.

   We are currently working on a road shields feature for the WME, and we believe this suggestion will be addressed as part of this development.

   We will update accordingly.

   Hezi

7. Push questions to communicate with drivers

   A suggestion to enable Push questions (PQ’s) to communicate with drivers in order to solve map problems
   I thought it would be really great if Area managers would be able to send PQ’s to drivers in order to get their help in resolving map problems.
   For example:
   • If I get a UR (in an area with low traffic) suggesting that a right turn isn’t enabled anymore and I want to verify this I might need to wait a long time until someone else will send an additional UR.
   • Or if a road is suspected to be closed and I want to verify it before issuing an RT closure.
   In such cases I would issue a PQ in WME.

   This PQ would be sent to drivers (who marked in the application that they are willing to get such PQ’s):
   • In the area
   • In a route crossing the location
   • In a route not crossing the location but suggesting them a small re-route to check the issue.
   There are many variants on how to realize this suggestion. For example it could be realized by enabling a pre-defined set of questions in WME were you only need to update street names.
   Also in order not to disturb drivers too much they can set in the application how many such PQ’s they are willing to get in one day / route.

   Is this idea something that Waze devs are thinking about?
   Is it on the list of future developments?
   Thanks,

   By: reuvenirony
   Link to original suggestion: https://www.waze.com/forum/viewtopic.php?f=1525&t=220636

   A suggestion to enable Push questions (PQ’s) to communicate with drivers in order to solve map problems
   I thought it would be really great if Area managers would be able to send PQ’s to drivers in order to get their help in resolving map problems.
   For example:
   • If I get a UR (in an area with low traffic) suggesting that a right turn isn’t enabled anymore and I want to verify this I might need to wait a long time until someone else will send an additional UR.
   • Or if a road is suspected to be closed and… more

   8 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   Under consideration  ·  2 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Invalid Railroad Regression Error

   I would put this in Beta Bugs but I know that technically it is not a bug. So I am going to make it a suggestion instead.

   If you have a railroad segment cross a street segment and you decide to junction them.
   (pic 1)
   You get an error when you save telling you that all turns are disallowed.
   (pic 2)

   While technically this is true, you CAN"T allow the turns onto/off the railroad segment (and you shouldn't be allowed to).

   This is a left over error from back when turns could be set on railroad segments and needs to be removed. It causes extra unneeded steps when adding the junction.

   I would put this in Beta Bugs but I know that technically it is not a bug. So I am going to make it a suggestion instead.

   If you have a railroad segment cross a street segment and you decide to junction them.
   (pic 1)
   You get an error when you save telling you that all turns are disallowed.
   (pic 2)

   While technically this is true, you CAN"T allow the turns onto/off the railroad segment (and you shouldn't be allowed to).

   This is a left over error from back when turns could be set on railroad segments and needs to… more

   •  

   •  

   4 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Not a suggestion  ·  AdminWaze Team (Admin) (Admin, Waze) responded

   Hey!

   This seems to be a bug.
   A bug was opened to the relevant teams in the HQ.

   Thanks,
   Hezi

9. RTC : ability to add them on current tiles

   Hi,
   the real time closure have a problem :

   We put them in WME and WME validates them according to their current state in database. But they apply on livemap.

   Imagine I have a street that is A->B. Then they decide to reverse it. So it is now saved B->A.

   In WME I have B->A
   In livemap I still have A->B until tiles update.

   To avoid routing people A->B, it would be nice to add a closure, but WME refuse since it thinks the road is in opposite direction.

   It would be nice if WME could accept it by really try to add closure in real time server instead of doing a check according to WME database that is too news.

   It is similar to https://www.waze.com/forum/viewtopic.ph ... e#p1790951

   It's not enough, if you change a segment then need to add a closure, even if the tile build is the next day, it's still one day with routing errors.

   For example the road under map comment was inverted, look at the UR that happened in 6 hours.
   (photo attached)

   by kpouer
   Link to original suggestion: https://www.waze.com/forum/viewtopic.php?f=1525&t=266974

   Hi,
   the real time closure have a problem :

   We put them in WME and WME validates them according to their current state in database. But they apply on livemap.

   Imagine I have a street that is A->B. Then they decide to reverse it. So it is now saved B->A.

   In WME I have B->A
   In livemap I still have A->B until tiles update.

   To avoid routing people A->B, it would be nice to add a closure, but WME refuse since it thinks the road is in opposite direction.

   It would be nice if WME could accept it by really… more

   20 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Added to backlog  ·  AdminWaze Team (Admin) (Admin, Waze) responded

   Hey!

   Thank you very much for this great suggestion.
   It was added to our backlog to try and see the possibility to implement it.

   Please note there is no ETA for it yet.

   Best,
   Hezi

10. Invisible RTC's and visible TBR's

    Add the ability to control the visibility of TBR and RTC in the client (and define it in WME).
    They say they often use the wrong type, just to match the required visibility.

    1 vote

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    Looking into the suggestion  ·  1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Improvement for lanes

    I am attaching a suggestion here to allow adding lanes in node that refer to a "far turn". Implementing this suggestion will solve all the problems of setting lanes (including extreme complicated junctions, H and # junctions) without the need for any heuristics! It will work at any junctions even if it is extremely complex with many auxiliary segments.

    In the WME:
    When defining lanes to a segment, turns are automatically displayed for the end of the segment with the segment names to which they refer.
    My suggestion is to add an option for adding to lanes a "far turns". When you want to add a lanes for a "far turns", you will get an option to select the "far turn" and it will be added to the turns list for the lanes setting. You can define one or more "far turns".
    The idea will look like this (attachment 1)
    In the app:
    The lanes will display as defined in the WME for that node (the number of lanes and the arrows).
    When there are lanes at the node with "far turn", the arrows will be highlighted if the route passes in the "far turn".

    An example of this type of solution is required:
    The node:
    https://www.waze.com/editor/?env=il&lon ... ts=1172278
    The "far turn":
    https://www.waze.com/editor/?env=il&lon ... des=800851
    The lanes arrows:
    (Attachment 2)

    At this node, the arrows in the 2 left lanes (as seen in the attached photo) is for the next turn ("far turn").
    The left-most lane should only show left and the lane next to it should show straight and left. Currently, the WME does not allow lanes to be defined correctly at that node. The proposal demonstrates how the lanes should be edited for this node.

    by zeze13
    Link to the original suggestion: https://www.waze.com/forum/viewtopic.php?f=1525&t=301202

    I am attaching a suggestion here to allow adding lanes in node that refer to a "far turn". Implementing this suggestion will solve all the problems of setting lanes (including extreme complicated junctions, H and # junctions) without the need for any heuristics! It will work at any junctions even if it is extremely complex with many auxiliary segments.

    In the WME:
    When defining lanes to a segment, turns are automatically displayed for the end of the segment with the segment names to which they refer.
    My suggestion is to add an option for adding to lanes a "far turns".… more

    •  

    •  

    5 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    Under consideration  ·  0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Metric system on new connections

    Hi,
    Can you add that the metric system is automatically set up according to the country to which we are connected?
    Because there are a lot of L1 in France who change the speed limits of entire districts / cities and put 50 mph ... instead of 50 km/h ... (a difference of 30 km/h ...)

    Take care and thanks for all :)

    By: InstantT
    Link to original suggestion: https://www.waze.com/forum/viewtopic.php?f=1525&t=304262

    8 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    Looking into the suggestion  ·  1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Junction Box Modal dialog does not appear in practice mode

    In practice mode, the modal dialog used to choose the routes through the Junction Box does not appear.

    It does appear when logged in.

    This is inconsistent. All the features of Junction Box should be visible in practice mode so editors can learn about junction box without risk of accidentally making changes.

    by voludu2
    Link to original suggestion: https://www.waze.com/forum/viewtopic.php?f=1525&t=291029

    4 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Not a suggestion  ·  AdminWaze Team (Admin) (Admin, Waze) responded

    Hey!

    This seems. like a bug, and not a suggestion. Therefore, a bug was opened to the relevant teams in the HQ.

    Best,
    Hezi

14. Improve Segment History Reporting of Turns

    Description: Currently when editors make most changes to a turn between two segments the segment history simply shows "Turn onto X road updated". It would be much more helpful if we could easily tell what was changed about that turn. Was is a turn instruction override (TIO)? A difficult turn? Time-based restrictions? There was a change in a value associated with the data model of that segment, so it's very much possible to have the segment history be more specific.

    In this image there are three entries for turn updates to the same turn, but other than the TIO there is no way to know what exactly was done. If there's been a tile update then we only have the option to email a community manager to pull the change info for us. It'd be much quicker and more helpful to be able to get this info at a glance.

    Current behavior: All changes to turn attributes are saved to segment history in a generic format.

    Desired behavior: Changes to turn attributes are displayed in segment history with descriptive wording. ie - "Turn onto X road turn instruction override added/deleted", "Turn onto X road difficult turn added/deleted", etc.

    By: SkiDooGuy
    Link to original suggestion:https://www.waze.com/forum/viewtopic.php?f=1525&t=306811

    Description: Currently when editors make most changes to a turn between two segments the segment history simply shows "Turn onto X road updated". It would be much more helpful if we could easily tell what was changed about that turn. Was is a turn instruction override (TIO)? A difficult turn? Time-based restrictions? There was a change in a value associated with the data model of that segment, so it's very much possible to have the segment history be more specific.

    In this image there are three entries for turn updates to the same turn, but other than the TIO there… more

    •  

    10 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    Looking into the suggestion  ·  1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Show "Hidden" external providers like Yext

    Show that this data exists, so that editors will be more likely to merge than to delete.

    When new place points are added as part of a large upload from Yext or some other advertising aggregator, many editors will be likely to reject the new-place PURs because an already perfect place already exists.

    If they were aware that there was some other important information in the PUR, then they would be much more likely to accept the PUR.

    The back end data script reveals the existence of this data in places. But I don't think it makes sense to depend on all editors running this script all the time. The fact that this data exists should be clearly visible to all editors.

    by voludu2
    Link to original suggestion: https://www.waze.com/forum/viewtopic.php?f=1525&t=275087

    Show that this data exists, so that editors will be more likely to merge than to delete.

    When new place points are added as part of a large upload from Yext or some other advertising aggregator, many editors will be likely to reject the new-place PURs because an already perfect place already exists.

    If they were aware that there was some other important information in the PUR, then they would be much more likely to accept the PUR.

    The back end data script reveals the existence of this data in places. But I don't think it makes sense to depend… more

    •  

    13 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Added to backlog  ·  AdminWaze Team (Admin) (Admin, Waze) responded

    Hey!

    Thank you very much for this great suggestion.

    It was added to our backlog to try and see the possibility to implement it when we will next use external providers.

    Please note there is no ETA for it yet.

    Best,
    Hezi

16. Better history for place update

    Hey,

    in place edit history, it would be nice to have more details on PUR : the only status is accepted or rejected.
    Maybe it is not easy to tell what photo was refused or a refused change name, but it would be nice to know what was the updated fields (was it about adding or removing a photo, rename the venue).

    by kpouer
    Link to original suggestion: https://www.waze.com/forum/viewtopic.php?f=1525&t=284045

    •  

    6 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Added to backlog  ·  AdminWaze Team (Admin) (Admin, Waze) responded

    Hey!

    Thank you very much for this great suggestion.
    It was added to our backlog to try and see the possibility to implement it.

    Please note there is no ETA for it yet.

    Best,
    Hezi

17. Selecting a search result shouldn't reset the zoom level

    When using the WME search box to find a road, it would be really nice if WME could leave the current zoom level well alone rather than always resetting it to level 3.

    Even if it just defaulted back to level 4 that'd be an improvement, but jumping back out to 3 means we then always have to zoom back in at least one step if we want to be able to select a street segment. And even at L4, anyone looking to do some work on point places would then need to zoom in one step more before they show up... So really, not altering the zoom level at all would be the best choice IMO.

    by Twister-UK
    Link to original suggestion: https://www.waze.com/forum/viewtopic.php?f=1525&t=276683

    When using the WME search box to find a road, it would be really nice if WME could leave the current zoom level well alone rather than always resetting it to level 3.

    Even if it just defaulted back to level 4 that'd be an improvement, but jumping back out to 3 means we then always have to zoom back in at least one step if we want to be able to select a street segment. And even at L4, anyone looking to do some work on point places would then need to zoom in one step more before they… more

    0 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    Looking into the suggestion  ·  0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Implement reCAPTCHA v3

    With the recent release of version 3 of reCAPTCHA (the thing you may get to see when you log in and the system suspects you may be a bot instead of a user), it would be a great idea to upgrade to the latest version. We've had several users who have had to fill in the CAPTCHA protection every time for some weird reason (I suspect someone in their neighbourhood is to blame), which could be alleviated with the new system. The system now gives you a score between 0 and 1 to gauge how trustworthy the request is. That also means you can alter how strict the system will be.

    The only downside of this means that you'll need to figure out what you'll do with people/bots with low scores. The reCAPTCHA v3 manual suggests requiring two-factor authentication or e-mail validation from such users, which would indeed help against wrong passwords, but probably won't protect the Waze map from scrapers (I suspect that is also part of the reason why the captcha was implemented).

    Either way, I think it would be a good idea to already add some v3 calls in the background without adjusting any behaviour, just to get an idea of what scores the system generates.

    By: Glodenox
    Link to original suggestion: https://www.waze.com/forum/viewtopic.php?f=1525&t=270181

    With the recent release of version 3 of reCAPTCHA (the thing you may get to see when you log in and the system suspects you may be a bot instead of a user), it would be a great idea to upgrade to the latest version. We've had several users who have had to fill in the CAPTCHA protection every time for some weird reason (I suspect someone in their neighbourhood is to blame), which could be alleviated with the new system. The system now gives you a score between 0 and 1 to gauge how trustworthy the request is. That… more

    0 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    Under consideration  ·  0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. New Place Address

    I'm not sure if it's a minor-bug or intended, but I ask you to take a look:

    Issue regarding Map Editor Beta and Production.

    :arrow: When you find a new place waiting for approval, if you click on the red arrow everything runs smooth, but if you feel the need to click on the yellow arrow to check what's that place is about before approving it (sometimes you can't tell just by the name title), notice it isn't possible to change the address... well maybe it's ok at this point before approving it.

    (attachment 1)

    • After you Approve you can't still change it.
      (attachment 2)

    • You need to click on the map background to remove selection and the click on the place again and now you can change the address. In my opinion this extra step is unnecessary.
      (attachment 3)

    by KarderGomes
    Link to original suggestion: https://www.waze.com/forum/viewtopic.php?f=1525&t=301965#p2064955

    I'm not sure if it's a minor-bug or intended, but I ask you to take a look:

    Issue regarding Map Editor Beta and Production.

    :arrow: When you find a new place waiting for approval, if you click on the red arrow everything runs smooth, but if you feel the need to click on the yellow arrow to check what's that place is about before approving it (sometimes you can't tell just by the name title), notice it isn't possible to change the address... well maybe it's ok at this point before approving it.

    (attachment 1)

    • After you Approve you can't… more

    •  

    •  

    •  

    0 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Added to backlog  ·  AdminWaze Team (Admin) (Admin, Waze) responded

    Hey!

    Thank you very much for this great suggestion.
    It was added to our backlog to try and see the possibility to implement it.

    Please note there is no ETA for it yet.

    Best,
    Hezi