931 results found

1. UR feed should include recently edited areas

   After modifying an area, both senior and junior editors should pay close attention to new URs in that area to alert them of possible errors or oversights. To facilitate this, an editor's WME feed should list URs occurring in a localized area where that editor has recently made significant changes, e.g. "Near recent edits".

   There should be some kind of threshold to this behavior, so that making a minor edit in a dense, heavily-Wazed area with many URs does not unleash an onslaught of unrelated URs in one's feed. The threshold may need to depend on the rank and activity of the editor, and/or on what exactly was edited, for example Freeways versus Parking Lot Roads.

   After modifying an area, both senior and junior editors should pay close attention to new URs in that area to alert them of possible errors or oversights. To facilitate this, an editor's WME feed should list URs occurring in a localized area where that editor has recently made significant changes, e.g. "Near recent edits".

   There should be some kind of threshold to this behavior, so that making a minor edit in a dense, heavily-Wazed area with many URs does not unleash an onslaught of unrelated URs in one's feed. The threshold may need to depend on the rank and activity… more

   9 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

2. Improve the format of unlock request titles

   Including the current lock level of the segment allows editors to see at a glance if they are a high enough rank to address the request, and adding the name of the segment helps differentiate between multiple requests from the same editor in the same city. I would recommend this format:
   Level 4 unlock in Winnipeg, Manitoba (Main St)
   If the segment doesn't have a city name, there shouldn't be a comma before the state:
   Level 4 unlock in Manitoba (Hwy 9)
   If the segment doesn't have a street name, the parentheses should be omitted:
   Level 4 unlock in Winnipeg, Manitoba
   Level 4 unlock in Manitoba

   Including the current lock level of the segment allows editors to see at a glance if they are a high enough rank to address the request, and adding the name of the segment helps differentiate between multiple requests from the same editor in the same city. I would recommend this format:
   Level 4 unlock in Winnipeg, Manitoba (Main St)
   If the segment doesn't have a city name, there shouldn't be a comma before the state:
   Level 4 unlock in Manitoba (Hwy 9)
   If the segment doesn't have a street name, the parentheses should be omitted:
   Level 4 unlock in Winnipeg,… more

   9 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  ·  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

3. Real Speed in WME

   It would be nice if one could specify the real speed in WME. The official speed limit is sometimes much higher than the real speed one can drive on certain roads (road condition, etc). Having these too high speeds results in incorrect route calculations. One could say that the algorithm should fix this, but that doesn’t seem to happen and one gets slower routes offered, based on incorrect info. Tools from the competition offer an option to enter real speeds.

   9 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…)
   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

4. Highlight node closures

   It would be good if there can be a marking of closures if they contain junction node closures. If there are multiple closures on segments (daily from 7-15 for 4 weeks, for example), and you want to change the node closures, it's not possible to determine which have it and which don't without going into the closure. If you then go back out, you return to the top of the list of closures, so it's tedious to keep track where you were.

   9 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  ·  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. New "comment" category: traffic cam

   It can help editors a lot to have quick access to traffic cameras or similar government-deployed cameras that are accessible for the public.
   Certain places have mapped them in WME with a Web Comment (point), but it might be useful to have a distinct category for them, so they are easy to spot.
   It can be simply a duplicate of the existing comment category, but with a new symbol.

   9 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  ·  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

6. Notification alert in WME when GPS Traces appears over no segments

   In Waze Map Editor, receive alert when some GPS traces appears over map with no segments.
   Helps to Editors to review or create new segment in map.

   9 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  ·  community  ·  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. Bring back the zoom bar

   With all of the new zoom levels I'm respectfully begging for the return of the zoom bar in order to know what zoom level you are at. Since many map objects only display below a certain zoom level, in vanilla WME, you must guess whether you'll be able to see what you need. Also, the zoom bar allowed for single click zooming, rather than using the scroll wheel or multiple clicks.

   9 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  ·  cartouche  ·  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. add RTC details to segment history in WME

   Currently in WME segment history we can see that a closure was added and when it was added, but It doesn't contain any details about the duration of the closure itself. If a closure is manually deleted by an editor I believe that also shows up in the history, but when a closure expires naturally that is not captured.

   It would be very useful if there was data about the actual closure itself. I'd like to at the very least be able to see when the RTC was scheduled to begin and end. This would help when there are URs about a road not being closed when, for instance, a road crew ends work earlier than it was planned to last.

   Currently in WME segment history we can see that a closure was added and when it was added, but It doesn't contain any details about the duration of the closure itself. If a closure is manually deleted by an editor I believe that also shows up in the history, but when a closure expires naturally that is not captured.

   It would be very useful if there was data about the actual closure itself. I'd like to at the very least be able to see when the RTC was scheduled to begin and end. This would help when there are URs… more

   9 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…)
   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

9. Displaying of node closures on planned closures

   Node closures are great, but they can cause confusion as well. If there are road works with several phases you cannot see if the node closure is on the active closure or on the planned closure.

   Therefore I suggest to make node closures greyed out on planned closures, as you now have with the symbol for segment closures as well. Additionally or alternatively, active node closures can be made red/white instead of black/white.

   9 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  ·  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

10. Add Driveway Road Type

    I'm Suggesting the Addition of a "Driveway" road type that can be added for long driveways for 1 house. Something can be shown for routing to the address using RPPs but not shown on the map as another road.

    9 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  ·  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

11. Project Zone for Large/Difficult Projects

    Sometimes when working on large projects, it is difficult to get the timing with tile updates to make a major project (or even smaller projects) go live at the correct time. Often this is done with adding segment restrictions to new segments, waiting for a TU, then applying an RTC and removing the restriction, so that when it goes live, just the RTC has to be removed. However, this usually only works when what is added is totally new and doesn't require reuse or reconfiguring of previous segments. It is also very difficult during reconfigurations when the project all of a sudden changes over early, or has a last minute delay. If we don't catch it in time, it can require several tile updates to get WME correct, and then wait for it to go live in the app. This is frustrating for editors because it makes deadlines and sudden changes very difficult, and frustrating for drivers getting incorrect instructions.

    My idea is a project mode that allows editors to work on large projects over several days without worrying about breaking routing, messing with current configurations, breaking RTC abilities, etc... all while keeping the behind-the-scenes mess hidden from the drivers using the app. Then, with a push of a button (or a predetermined time), the "project" can be made live in the app. Further details below on potential implementations to prevent concurrency issues while guaranteeing a great experience for editors and drivers.

    1 - How to create a "project": An editor with the required rank (set by regional coordinator) selects the "Project" polygon in WME and then draws a polygon around segments that will be included in the project and gives it a name. I'll refer to this polygon as the project zone from now on. Segments inside the project zone can be any lock level, even higher than the editor that places the project zone. Segment lock restrictions function as normal. Project zones are visible on the map through a "Projects" layer. Any segment that is included in a project zone is flagged as being part of that project, and when selected, it will display which project zone it's a part of. At this point, this segment is locked from editing unless in project mode, similar to the RTC editing lock. A project zone can be expanded to include new segments, but if it's shrunk enough that a segment flagged as included is no longer included, you cannot save. The idea behind this "project zone" is to create a clone of the current status of WME so that changes done do not affect the current tile build.

    2 - Working the project: Just like we can view the previous tile build, there will be an option to view the map as it is now, or view the "project". Any editor of any rank should be able to view the project progress, even if they can't create or modify it. From inside the project mode, you simply edit as normal to the new configuration saving often, not worrying about breaking routing (remember, the current map state is unaffected by this). Once editing is complete, including verifying routing is unbroken, you will "publish" the project to the map. I imagine that every time you save while in construction mode, a check that the edit is allowed and viable is made, but not actually completed. Then, when you publish, the edits are actually published to the map. At this point, even after a tile update, the old configuration is what is used in the app and for routing.

    3 - Making the new configuration live: The previous "publish" button actually will have two options. Publish and keep hidden, or publish immediately. Publishing immediately applies all changes in the project zone to the map, and removes the project zone. It will be live after the next tile update. Publishing and keeping hidden will send all the segments in the next tile update but keep them hidden. How do you ask? Just like RTCs can immediately affect routing and affect the visual appearance, the published but hidden segments are kept invisible on the map and have an RTC applied so that traffic isn't routed on invisible segments. Then, an editor in WME can select the project zone and "switch configuration" on demand or schedule it. Upon switching this configuration, the new configuration goes live instantly in the app by making the new configuration visible without RTCs, and any old segment IDs that were not reused go invisible with RTCs. The project zone remains on the map for 2 weeks or until manually removed by an editor. The editor can switch back to the old configuration instantly if needed, such as with a delay in crossing over.

    4 - In-app experience: Won't be snapped to incorrect segments that have been moved for a new configuration. Won't need to wait days for a configuration to go live in the app, especially in the event of a tile update delay. Able to take advantage of new configuration instantly.

    5 - Benefits to editors: Able to work on big projects in chunks over time. Can start adding or changing something, save to verify that it's a valid change, and continue editing. All without worrying about breaking routing (whereas saving often normally might break routing, or require lots of extra steps). No longer need to cram a large project in between tile updates. No longer needing to hope you're available to make the change on the exact day so that the correct tile update makes it go live, but not too early or too late. You could theoretically work a change weeks in advance. Allows us to still RTC segments from the old configuration while working the project zone.

    6 - Example scenarios:

    6-1: This displaced left turn required lots of steps with time based segment restrictions set to have it open at the correct time. Due to weather, the city announced it was delaying opening it by 2-3 days. This was announced 20 minutes before a tile update that would have set the new configuration in motion. Luckily I was able to catch it and update several time based restrictions. Then, after it was live, I had to go in and clean up turn restrictions and lane guidance that was no longer needed or correct. With a project mode, all the changes would be done well in advance of it going live. Then, set the configuration to change at the correct time. If we spotted it was delayed, simply change the time and date. If we didn't, we could reverse the configuration since the project zone would still be there for up to two weeks after it was changed. https://www.waze.com/en-US/editor/?env=usa&lon=-98.07749&lat=29.72828&zoomLevel=19

    6-2: US-281 is undergoing a major expansion. Editors could work to map new freeways and frontage roads (that are probably a few weeks to a few months from being done) now while keeping the current configuration for the drivers. Then, as soon as it goes live, we can easily switch it. Currently, if we get a heads up it's opening, we'll have to get it all done in one day and hope there are no delays crossing over. If we don't get a heads up, we'll still need to try to cram it into one day so we don't break routing. https://www.waze.com/en-US/editor/?env=usa&lon=-98.44717&lat=29.68590&zoomLevel=14&mapComments=171376937.1714097047.939091

    6-3: Dividing roads. You can save often to verify that you won't receive an error while not worrying about breaking routing. No having to create bowties every few intersections to save. Simply divide as you want, saving with segments halfway complete as you cut and merge, and then once done, publish to map immediately.

    6-4: Any other project that is time consuming where you don't want to complete it in one sitting.

    7 - Closing thoughts: This is obviously a giant ask and would likely be very difficult to include. I've tried to suggest it to where concurrency with other edits won't be an issue because they'll be locked. This is a giant mental work-in-progress, so any improvements to the basic idea are more than welcome.

    Sometimes when working on large projects, it is difficult to get the timing with tile updates to make a major project (or even smaller projects) go live at the correct time. Often this is done with adding segment restrictions to new segments, waiting for a TU, then applying an RTC and removing the restriction, so that when it goes live, just the RTC has to be removed. However, this usually only works when what is added is totally new and doesn't require reuse or reconfiguring of previous segments. It is also very difficult during reconfigurations when the project all of… more

    9 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  ·  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

12. Point per House Number

    Get 1 edit point per HN placed or per 2 HN moved. This brings more drive to do HNs.

    9 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  ·  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. Multiple entry points

    Waze should re-enable its multiple entry points feature (eg one side of building or another).

    Instead of using the first entry point, Waze users should be directed to the one that’s marked as the main point in the editor.

    9 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  ·  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

14. Don't display a connection node where there isn't any connection

    If one segment touches another segment somewhere in the middle it should be visible if there are two or three segments. Think of a T-crossing. At the spot where the segments meet a dot is displayed, which suggest there is a connection, but sometimes there isn't any: instead of 3 segments there are only 2. Better only display this dot when there is really a connection.

    9 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  ·  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. Change the wording in the automatic email when an editor comments on a UR

    When a user reports a map problem in the app, then an editor responds to it in the Waze Map Editor, the reporter gets an automatic email that says:

    "An editor from the Waze mapping community wants to solve the problem, but needs some more information.", followed by the editor's comment.

    The problem with this wording: This is not always true. If we can identify the cause of the report without needing clarification, then often we may simply use the comment box to thank the reporter for their report. Thus, the comment box isn't always used to ask for more information.

    Possible solution: I would like to suggest a more "neutral" wording to the automatic email, such as: "An editor from the Waze mapping community has replied to your report.", followed by the editor's comment.

    That covers everything from a follow-up question to a simple thanking for the report, so I think this wording (or something similar to it) would be better.

    When a user reports a map problem in the app, then an editor responds to it in the Waze Map Editor, the reporter gets an automatic email that says:

    "An editor from the Waze mapping community wants to solve the problem, but needs some more information.", followed by the editor's comment.

    The problem with this wording: This is not always true. If we can identify the cause of the report without needing clarification, then often we may simply use the comment box to thank the reporter for their report. Thus, the comment box isn't always used to ask for more… more

    9 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  ·  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. Address announcement

    When you arrive at your destination have the app say “you have arrived at 12 thirteen st” or something similar. I use Waze through another scheduling app and I always have to check the other app to see what the street number is that I’m actually navigating to

    9 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  ·  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. External providers: Also suggest places marked as permanently closed (with a proper mark)

    WME uses Google Maps as the external provider in Israel and doesn't suggest places marked in Google as permanently closed. Meanwhile, showing that the place is marked as closed in Google would hint that the place needs additional checking and possibly should be removed from the Waze map.

    9 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  ·  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. Tell the editor why they can't edit Far Lanes

    If you're below the required editor level to edit Far Lanes, then the Far Lanes interface is visible to you when editing Lane Guidance, but it's dimmed out - and there's no explanation why. For example, in Australia, Far Lanes requires Level 4 or higher - but nowhere in the Waze Map Editor does it mention this. For the user editing, the Far Lanes interface just appears greyed out for them for no apparent reason.

    All that needs to be added is some kind of message that says "You need to be a higher level to edit Far Lanes" whenever the Far Lanes interface appears - perhaps just above where the Far Lanes configuration shows.

    If you're below the required editor level to edit Far Lanes, then the Far Lanes interface is visible to you when editing Lane Guidance, but it's dimmed out - and there's no explanation why. For example, in Australia, Far Lanes requires Level 4 or higher - but nowhere in the Waze Map Editor does it mention this. For the user editing, the Far Lanes interface just appears greyed out for them for no apparent reason.

    All that needs to be added is some kind of message that says "You need to be a higher level to edit Far Lanes" whenever… more

    9 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  ·  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

19. Add possibility to add Hump alert on the road

    Add possibility to add Hump alert on the road warning the wazer that there is a hump with voice sound instead of beep.

    9 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

20. Average speed calculation in average speed zone

    The idea is that once you enter a speed enforcement zone there will be an aditional box that displays the average speed driven inside the enforcement. This allows you to gauge how much you can speed up after stopping or going slow for awhile.

    9 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  ·  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