38 results found

1. Internal editor Notes on User Reports

   Give editors the ability to enter Notes onto User Reports without these going to the reporters themselves.

   This will allow us to leave messages for other map editors without the reporter being notified, for example, Please leave open - due to a Waze developer investigation, Please leave open for a pending site survey, etc.

   It may also give us the ability to for to use for an internal conversation about the report that the reporter doesn't need to know about.

   Yes, I know we have Map Comments, but having the ability to do this directly on the report would make it easier.

   Give editors the ability to enter Notes onto User Reports without these going to the reporters themselves.

   This will allow us to leave messages for other map editors without the reporter being notified, for example, Please leave open - due to a Waze developer investigation, Please leave open for a pending site survey, etc.

   It may also give us the ability to for to use for an internal conversation about the report that the reporter doesn't need to know about.

   Yes, I know we have Map Comments, but having the ability to do this directly on the report would make… more

   322 votes

   Vote 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…)
   15 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
   Added to backlog  ·  AdminWaze Team (Admin) (Admin, Waze) responded

   This suggestion has been added to the team's backlog, and is currently waiting for assignment. Will update when we have an established ETA. 

   
   

   Thanks to all who have helped us with further info!

2. Additional camera types, with names and TTS defined by community

   July 2020, Waze has three camera types: speed, red light, dummy. It is clear talking to different community leaders that the requirements for specific cameras vary from country to country. Thus, we are asking for the ability to add new camera types per country, with the ability to input into text to speech (TTS), and on/off toggle alert in the app. These could be provided by form, similar to new gas station brands, etc. by a country's leadership.

   Alternatively, collect a list of camera types from the communities to create a long list, and allow countries to turn them on/off by country.

   Obviously there's a wide range of cameras, and in each jurisdiction some are more important to others. There are also new and emerging camera types, such as dual red light AND speed cameras, and even newly released mobile phone detection cameras which fine users for driving while holding their phone.

   July 2020, Waze has three camera types: speed, red light, dummy. It is clear talking to different community leaders that the requirements for specific cameras vary from country to country. Thus, we are asking for the ability to add new camera types per country, with the ability to input into text to speech (TTS), and on/off toggle alert in the app. These could be provided by form, similar to new gas station brands, etc. by a country's leadership.

   Alternatively, collect a list of camera types from the communities to create a long list, and allow countries to turn them on/off… more

   297 votes

   Vote 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…)
   Added to backlog  ·  10 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

3. Add closures to new segments

   It would be really great if we could add closures to segments just after creating them. Currently that's not possible. In this case, once the segments are built into the map, the closures would be added to them automatically

   Why?

   Sometimes city administrations make few changes in the traffic by creating new roads. The problem is that most of the times (at least where I live) we don't know exactly when those roads will be released. In addition, map build may delay.

   So, as soon as we know a new road will be built, we can create it on WME and add a closure after that. Once the road is released, we can delete the closure.

   by quantumjedi
   Link to original suggestion: https://www.waze.com/forum/viewtopic.php?f=1525&t=296229&start=10

   It would be really great if we could add closures to segments just after creating them. Currently that's not possible. In this case, once the segments are built into the map, the closures would be added to them automatically

   Why?

   Sometimes city administrations make few changes in the traffic by creating new roads. The problem is that most of the times (at least where I live) we don't know exactly when those roads will be released. In addition, map build may delay.

   So, as soon as we know a new road will be built, we can create it on WME… more

   247 votes

   Vote 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…)
   6 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
   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

4. Improve the GPS points layer

   To branch off the discussion from the WME release topic:

   RichardPyne כתב:
   I would find GPS points much more useful if they were color coded by age rather than direction. Th arrows provide useful direction, but in areas where traffic patterns are changing due to construction, knowing the age of the trace would be far more useful.

   dchary2418 כתב:
   It could help if the GPS traces were the same original color, but shaded darker for older data.

   Glodenox כתב:
   I'd be all for somehow showing the age of the GPS points. Especially the more recent data seems of interest to me. Something like "last 7 days", "last 30 days" or "older" would work great as brackets for colouring, I think.

   The issue with that is probably that it would allow you to track certain users in areas with not as many users. With no indication of age, this is a lot harder to do right now. But in theory this could be taken into account by not showing the age when there is little data.

   To branch off the discussion from the WME release topic:

   RichardPyne כתב:
   I would find GPS points much more useful if they were color coded by age rather than direction. Th arrows provide useful direction, but in areas where traffic patterns are changing due to construction, knowing the age of the trace would be far more useful.

   dchary2418 כתב:
   It could help if the GPS traces were the same original color, but shaded darker for older data.

   Glodenox כתב:
   I'd be all for somehow showing the age of the GPS points. Especially the more recent data seems of interest to… more

   175 votes

   Vote 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…)
   Added to backlog  ·  7 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

5. Copy and Paste Turn Instructions from one turn to another

   Please allow us to Copy into the clipboard (or similar function) all Turn Instructions from one turn, and Paste them into another turn.

   Quite often, I'm having to replicate the same instructions for different turns at the same junction for those coming from different directions, but turning into the same road. It would be a big timesaver if we could copy TIs into other turns without having to repeat the same steps.

   157 votes

   Vote 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…)
   3 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
   Added to backlog  ·  AdminWaze Team (Admin) (Admin, Waze) responded

   Thanks for supporting this suggestion! We've added it to the WME team's backlog, and hope to get to it in the near future. We will follow up here when we have an update, or need more info from the community. 

6. Close the turns

   Now we can only close the segments, but it would be really useful to be able to close only the turns.
   In many cases, for example, when there are road works at an intersection or roundabout, you can turn in one direction but not in another.
   In these cases for the moment, we can not do anything, at most we can insert a restriction on the turns but obviously with all the limitations of the case.
   They are not in real time and are not visible on the map.
   The ability to close nodes recently arrived on the WME does not help in these cases, as the same node could be open in one direction and closed in another.
   I believe it is an absolutely essential function.

   Now we can only close the segments, but it would be really useful to be able to close only the turns.
   In many cases, for example, when there are road works at an intersection or roundabout, you can turn in one direction but not in another.
   In these cases for the moment, we can not do anything, at most we can insert a restriction on the turns but obviously with all the limitations of the case.
   They are not in real time and are not visible on the map.
   The ability to close nodes recently arrived on the WME does… more

   149 votes

   Vote 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…)
   Added to backlog  ·  4 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

7. Improve RPP editing when it conflicts with HN layer

   When adding or editing RPP, if there is a conflict with the HN layer (i.e. too far), then the WME issues an error that prevents you from saving your edit. Thus, you cannot add or update this RPP.

   To resolve the issue you need to perform the following steps:
   1. Update/Remove the address in HN layer
   2. Wait for next (successful) map build
   3. Add the RPP

   This is an annoying procedure that should and can be avoided.

   The issue can be handled in one of the following ways:
   1. Verify the RPP against the most updated data either in the edited or production HN layer databases.
   2. Allow conflicts. Issue a warning but allow to save (rank depended). The same as forced HNs are allowed. Especially that for navigation, exiting RPPs are used before HNs.

   The above suggestions or any other solution that will allow immediate RPP editing would be very welcomed.

   I prefer option 1, as it also solve the conflict.

   When adding or editing RPP, if there is a conflict with the HN layer (i.e. too far), then the WME issues an error that prevents you from saving your edit. Thus, you cannot add or update this RPP.

   To resolve the issue you need to perform the following steps:
   1. Update/Remove the address in HN layer
   2. Wait for next (successful) map build
   3. Add the RPP

   This is an annoying procedure that should and can be avoided.

   The issue can be handled in one of the following ways:
   1. Verify the RPP against the most updated data either in… more

   108 votes

   Vote 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…)
   Added to backlog  ·  0 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

8. Keep previous history for merged/split segments

   Hello!

   I think it would be very helpful if segment history included data from previous "iterations" of that segment, when a segment was created by merge or split.

   Right now, the history starts anew any time there is a new segment ID, but I would imagine it should be fairly trivial to develop a backend mechanism that, any time a segment is split or merged, merges the history of the previous segment ID into the new segment's history.

   This is useful not only diagnostically but also to catch cheaters on the map, who today can split and merge segments at will with no evidence.

   It is very easy to envision how this would work with a segment created by split, as the history of the previous, longer segment can simply be displayed before the "Segment created by split" line, perhaps with the old ID of the previous segment appended.

   For segments created by merge, obviously there are multiple histories to incorporate, but I think it can still be done in a sensible way from a UX / UI standpoint, as follows.

   Right now, the history of a merged segment starts with "Segment created by merge", and the data is lost. In a better implementation, perhaps it looks like this: "Segment created by merge of [segment ID 1] and [segment ID 2]".

   Then, at the time of the merge, the old history of the other two segments are merged into the new segment as well, with the old segment ID appended.

   So, let's say you have segments 123 and 345 from the basemap, each with a few edits before, named "Main St", connected by a node, then you delete the node to merge the segments into segment 54321 (newer segments have much higher IDs!). Right now, the history would be simply,
   Mon May 01 2017 by sketch(6) / Segment created by merge

   Let's say the other segments have history like this:
   123:
   Wed Dec 14 2016 by EladOfTheBerg(2)
   Updated Geometry
   GEOMETRY
   Changed from [this] to [this]
   Thu Jun 23 2016 by WilliamHMacy69(1)
   Updated Primary street name
   PRIMARY STREET NAME
   Changed from Maine Street to Main St

   345:
   Fri Aug 26 2016 by RickyBobby666(3)
   Updated Lock level
   LOCK LEVEL
   Changed from 1 to 3
   Thu Jun 23 2016 by WilliamHMacy69(1)
   Updated Primary street name
   PRIMARY STREET NAME
   Changed from Maine Street to Main St

   In the improved implementation, the history for segment 54321 would read:
   Mon May 01 2017 by sketch(6)
   Segment created by merge of 123 and 345
   Wed Dec 14 2016 by EladOfTheBerg(1) (ID: 123)
   Updated Geometry
   GEOMETRY
   Changed from [this] to [this]
   Fri Aug 26 2016 by RickyBobby666(3) (ID: 345)
   Updated Lock level
   LOCK LEVEL
   Changed from 1 to 3
   Thu Jun 23 2016 by WilliamHMacy69(1) (ID: 123, 345)
   Updated Primary street name
   PRIMARY STREET NAME
   Changed from Maine Street to Main St

   If you really want to get fancy, the "123" and "345" in "Segment created by merge of 123 and 345" could be little hover buttons like with the geometry changes.

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

   Hello!

   I think it would be very helpful if segment history included data from previous "iterations" of that segment, when a segment was created by merge or split.

   Right now, the history starts anew any time there is a new segment ID, but I would imagine it should be fairly trivial to develop a backend mechanism that, any time a segment is split or merged, merges the history of the previous segment ID into the new segment's history.

   This is useful not only diagnostically but also to catch cheaters on the map, who today can split and merge segments at… more

   107 votes

   Vote 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
   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

9. [Segment Attribute Request] Treat 2 Way as Divided

   I would like to have the ability to draw a single 2-way segment but be able to mark it as divided so it does not say you have arrived until on correct side of road. Sometimes you may have a segment that may not really need to be divided into 2 One-Way segments but if you want routing to offer the correct directions you would have to divide the segments. In my picture below, the red line shows what Waze currently does (it says you have arrived as you pass the house) The green line shows what it should be doing. This can be accomplished by dividing but if there was an attribute that says "divided segment" that Waze would treat the 2-way segment as 2 One-Way segments, then we would not have to add extra "unneeded" segments but still give the correct routing.

   I really think this would go a long way in helping when we have just a short segment that is divided along a longer undivided segment.

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

   I would like to have the ability to draw a single 2-way segment but be able to mark it as divided so it does not say you have arrived until on correct side of road. Sometimes you may have a segment that may not really need to be divided into 2 One-Way segments but if you want routing to offer the correct directions you would have to divide the segments. In my picture below, the red line shows what Waze currently does (it says you have arrived as you pass the house) The green line shows what it should be… more

   •  

   97 votes

   Vote 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…)
   3 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
   Added to backlog  ·  AdminWaze Team (Admin) (Admin, Waze) responded

   Hey,

   This topic may not answered as part of the suggestion up until now, but it has been discussed multiple times across the relevant teams.

   We will keep on updating with any news

   Best,
   Hezi

10. Add manual lock level to Junction Boxes

    Currently, Junction Boxes do not have a controllable lock level. From the look of it, the lock level displayed is the minimum level for the country that can edit a JB. For example, in the UK only L5+ editors can edit JBs, so all JBs show auto(5) in WME.

    With various changes that HQ are making into WME and the app, it seems to me that they expect a massive increase in JBs over time. U-turn prevention, junction modification for Falcon are just some of the things for which the answer often seems to be "use a JB".

    I'm not disagreeing with the increased use of JBs. But some of them in the UK are attached to very complex motorway junctions (https://www.waze.com/editor/?env=row&lon=0.19921&lat=51.87156&zoom=5) which we would definitely want to stay out of reach of junior editors.

    On the other hand, we don't want to prevent junior editors being able to use JBs sensibly in situations where they're needed.

    Without individual lock levels on JBs we don't have much choice. In order to protect complex, important JBs we have to lock junior editors out of JB use entirely.

    By: iainhouse
    link to original suggestion: https://www.waze.com/forum/viewtopic.php?f=1525&t=307738

    Currently, Junction Boxes do not have a controllable lock level. From the look of it, the lock level displayed is the minimum level for the country that can edit a JB. For example, in the UK only L5+ editors can edit JBs, so all JBs show auto(5) in WME.

    With various changes that HQ are making into WME and the app, it seems to me that they expect a massive increase in JBs over time. U-turn prevention, junction modification for Falcon are just some of the things for which the answer often seems to be "use a JB".

    I'm not… more

    94 votes

    Vote 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…)
    Added to backlog  ·  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

11. Subscribe to segment

    It may be nice for us to be able to "subscribe" to a segment ID, not sure if it should be rank locked or not.

    Basically, add a check box on a segments panel to subscribe to changes of the segment.

    When subscribed to a segment, if a change is made to a segment the subscriber gets an email notification that their segment has had changes (and of course provide a PL)

    Among other possible uses, it could be used to get notification if someone makes a change to a segment that is part of the Toll Price feature.

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

    It may be nice for us to be able to "subscribe" to a segment ID, not sure if it should be rank locked or not.

    Basically, add a check box on a segments panel to subscribe to changes of the segment.

    When subscribed to a segment, if a change is made to a segment the subscriber gets an email notification that their segment has had changes (and of course provide a PL)

    Among other possible uses, it could be used to get notification if someone makes a change to a segment that is part of the Toll Price feature.

    by… more

    93 votes

    Vote 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
    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

12. Prompt user to save Lane changes if deselecting segment

    After editing Lanes, it's far too easy to lose the changes by accidentally deselecting the selected segment you are editing if you don't apply the changes beforehand.

    This suggestion is to recognise that changes have been made in Lanes (or road width), and prompt the user to apply or cancel the changes if they deselect the segment they are editing.

    91 votes

    Vote 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…)
    Added to backlog  ·  0 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

13. Issue Tracker Option ~ Add ability to have Map Area and Managed Area at same time

    We need the ability to have the "Map area" option selected along with either the "Managed area" or "Specific location" option selected.

    Why you may ask?

    This just happened to me.

    I keep my settings as "Managed area" or "Specific location" so that I can work URs, PURs, etc anywhere any my managed area or State without being at a specific map area

    Someone contacts me by chat for assistance in a location that is not in my managed area or specific location (whichever I have set) and I help them out. Reporter is a happy camper.

    Since I don't have "Map area" selected, I don't see that the reporter had already submitted 2 URs. Another editor that finds those URs and sends me a message to find out if I am going to close the URs since I resolved them.

    In order for me to see the URs, I had to go into my settings and switch to Map area, then I could resolve them.

    I should be able to have my setting show me URs, PURs, etc in my Map area at all times (should be top of the list) and my normal URs, PURs, etc based on my Managed area setting below them.

    Let me know if you have questions.

    We need the ability to have the "Map area" option selected along with either the "Managed area" or "Specific location" option selected.

    Why you may ask?

    This just happened to me.

    I keep my settings as "Managed area" or "Specific location" so that I can work URs, PURs, etc anywhere any my managed area or State without being at a specific map area

    Someone contacts me by chat for assistance in a location that is not in my managed area or specific location (whichever I have set) and I help them out. Reporter is a happy camper.

    Since I don't… more

    91 votes

    Vote 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…)
    Added to backlog  ·  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

14. Setting to have vertical menu item selected when opening

    I often times use scripts or change settings before making my first edit. It would be useful to have the option to have WME open with a specific element of the vertical menu selected. That may be any of the options available, but Feed/Issue Tracker and Scripts would be my most likely to use first.

    80 votes

    Vote 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…)
    Added to backlog  ·  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

15. Editing fuel types for each Gaz station in WME

    It would be nice if the types of fuel at Gas stations could be created, selected and sorted for each specific Gas station when editing directly in the WME.
    The main thing is that for each Gas station it was possible to create its own set of fuel types.
    For example:
    for one - Gas, 92, 95, Diesel
    for the other - 92, 95, 98, Diesel
    etc.

    Because all Gas stations are Different!!!

    79 votes

    Vote 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…)
    Added to backlog  ·  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

16. Keep start/end times when duplicating a closure

    When duplicating a closure and changing the date, the duplicated end time changes to match the start time. I suggest that when duplicating the times do not change unless the editor clicks those fields.

    Forum post: https://www.waze.com/forum/viewtopic.php?p=2354616#p2354616

    78 votes

    Vote 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…)
    Added to backlog  ·  3 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

17. Do not allow user selection on buttons

    Buttons in WME (UR, PUR, etc.) should not allow the user to select the text. There is no functional use for editors to be able to select this text and attempting to click can result in the text being selected instead of registering a click on the button

    CSS:
    user-select: none;

    75 votes

    Vote 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…)
    Added to backlog  ·  0 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

18. Select segments included in permalink regardless of zoom level

    When handling unlock requests for larger areas, or when doing extensive highway closures, we often deal with permalinks that cover a broad area.
    To combat the problem currently, we have to break up the PLs, or use a script to select segments as we pan around.
    It would be exceptionally helpful and a great time saver if WME would load and select segments that are specified in a PL regardless of the zoom level.

    74 votes

    Vote 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…)
    Added to backlog  ·  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

19. Route of Last Resort RTC

    Ability to create an RTC (or TBSR) that will permit routing on the segment as a last resort (effectively make it a PR from a penalty perspective).

    This would be very helpful for soft construction closures that are marked "local traffic only"

    70 votes

    Vote 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…)
    4 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
    Added to backlog  ·  AdminWaze Team (Admin) (Admin, Waze) responded

    Thanks to all who submitted and voted on this suggestion! It has been added to our backlog.

20. Lines on sections of roads with roundabouts!

    We urgently need to implement the ability to add lanes on sections of roads with roundabouts!
    There are many sections of roads with roundabouts that use multi-lane and different traffic lanes.
    This functionality is severely lacking.

    70 votes

    Vote 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…)
    Added to backlog  ·  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