Map Editor Suggestions
Welcome to the Map Editor's suggestion box!
This is the place to share your ideas for improving the Waze Map editor.
1544 results found
-
Have an option to see the year of the Satellital Image shown in the WME
Always shows the actual year but not the year when was taken that Sat Image. Will be really helpful to know that.
182 votesGreat timing! We’re currently working on displaying the date of the satellite image. Keep an eye out for updates on the WME.
-
Put a Seed on the Production map (from the Editor) to "ask for specific questions" to actual wazers
Could be used for many things.
My idea would be:
a) Wazer, do you see a traffic light in "this" corner?
1. Yes
2. No171 votesThanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
-
External Providers Search Displays Too Little Information
The + Add linked Google place functionality on venues is incredibly difficult to use. When you search, the Waze-prioritized white space leaves almost no room for the search results to actually contain usable data. As it is now, I often have to guess as to which place it might be and often have to repeat the process making editing places very inefficient. Please expand the information displayed here so that this functionality is actually useful to finding and linking Google places. The whole name of a place should appear along with a complete address.
171 votesThank you for submitting this suggestion!
At the moment, when you hover over a place, it shows its complete address. Is this something that solves the original issue you mentioned?
If not, we would love to hear from you on how it can be improved.
Thank you!
-
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…169 votes -
Addition of a road type: Dangerous or Unsafe road
It is suggested to add one more road type: Dangerous or Unsafe road. This type will be used for example when it is a very steep or winding or bumpy road, or a road on the edge of an abyss.
The time it takes to pass the road in such cases is not the only parameter that counts.
It is suggested that the "penalty" for passing such a road will be proportional to its length. For example 1 minute for every 100m.162 votes -
Disable Permanent Hazards on Non-Driveable Roads and Pedestrian Paths
Disable the ability for permanent hazards to be snapped to and/or placed on non-driveable roads (runway and railroad) and pedestrian paths (routable, non-routable, and stairway) in WME. PHs intended for driveable roads at junctions with these road/path types can be accidentally placed on the incorrect non-driveable segment. While easy to check and correct when placing, this could preemptively prevent mistakes.
159 votesThanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
-
Filter GPS tracks by date
Filter GPS tracks by date
159 votesThanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
-
Testing routes in waze map editor
I would like to test a route, from A to B, in the map editor to check if the optimal route is chosen and find the reason why not. It could be easier to find that waze leads astray which happened to me this summer. Waze tried to lead me against a one way street.
156 votesGreat thinking! We’ll share with the team; they’re always interested in new feature ideas.
-
Allow for issue tracker to show results in descending order
Currently the default view of issue tracker results is ascending (newest to oldest.) It would be nice to allow the results to show in reverse (oldest to newest.) Sometimes I want to address the oldest issues first so that there are not so many backlogged.
155 votesThanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
-
Show only active closures
In the layers menu, under closures, there should be an "Only active" option. When this is enabled, only active closures will be shown in the WME. This would make the WME look "cleaner" and uncluttered.
144 votes -
House numbers for villages with no street names
There are many places where there are no street names - it's just "City name - number" as the address.
141 votesThanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
-
Reorder custom turn instruction elements
When editing custom turn instructions, if an element (shield or free text) should be inserted before existing elements, then the existing elements must be deleted. There is no way to create new elements in front of existing elements.
Please add the ability to reorder elements. This way we could create new elements and then move them to the front if needed. This would save many clicks and retyping.
137 votesThanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
-
Bring back the Pedestrian Crossings Permanent Hazard (PH)
With the recent launch of the Traffic Light feature, Waze has significantly improved driver awareness at intersections. However, a critical safety gap remains for unsignalized pedestrian crossings (such as those with warning beacons or RRFBs.
Previously, Waze included a "Pedestrian Crossing" category under Permanent Hazards, but its removal has left editors and drivers without a way to map these specific hazards. Currently, a driver will be alerted to a stop sign or to turn at a red light, but they receive no warning/surfacing for a mid-block crossing where a pedestrian might step into the road unexpectedly.
I am advocating for…
137 votes -
Add selectable traffic light icon options & updated TTS for flashing signals
In order to be more hyperlocal, please add selectable traffic light icon options to WME that would then display in the app at intersections where flashing yellow (warning) lights are erected or those that have flashing red lights (stop). In some areas, red flashing lights exist and do indicate it's a stop but from a TTS and visual perspective, "Turn left|right at the flashing light" is much more hyperlocal than turn at the stop sign, when a stop sign might not actually exist there.
An example of said light: https://beta.waze.com/en-US/editor?env=usa&lat=31.77078&lon=-94.19763&marker=true&zoomLevel=19
Streetview: https://maps.app.goo.gl/biqxPWVDQmM18TTE6Editors could easily provide plenty more examples where…
137 votesThanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
-
Put the House number field before the Street field
In some countries, House number needs to be before Street. Maybe this can be customisable by country? If not, I believe it's more logical to have House number first (smaller to larger).
136 votesThanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
-
Add general destination information to URs
URs have been improved by adding more information in WME 2.206, and it would be nice to continue to add information that doesn't jeopardize the privacy of the reporter.
My idea would be to add information on how the stop point of a user's route was obtained - whether it be a house number, house number interpolation, RPP, Google address, Waze place, Google place, etc. Specifics on the geographic location wouldn't be needed, it would just be very beneficial to know how the stop point was chosen. We get a lot of URs complaining about navigation ending at the wrong…
134 votesThanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
-
Make the UR Issues Tracker a Tracker and not a Filter
Currently the Issues Tracker is not a tracker, but rather a filter because it hides other URs (issues) on the map.
Ad an option not to hide URs on the map and display the default view (default setting in tracker)... so yes, we need to have some default options (that each user can change)... and when this option not to hide URs on the map to display the default view (including URs).
For example:
I always leave everything to see on my map - my default.
When searching for new URs or looking for URs with answers from reporters, I…133 votes -
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 RPPThis 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…132 votesThanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
-
Only send one Email if a UR gets commented and closed
On URs, it would be nice for editors to have a "comment and close" button to send a single email/notification to users, instead of two (an editor has left a comment, and your reported issue has been closed).
Most of the time, the user sends a last message right before closing the UR (something like: thank you, we fixed the map, it will take a few days to reach the app...).
Alternatively, use a queue and automatically merge these two events together if they occur within a specified time frame.
132 votesGreat thinking! We’ll share with the team; they’re always interested in new feature ideas.
-
Allow closure creation in "Current live map/snapshot" mode
At the moment, it is no longer possible to add a closure to a segment you have removed or split up, even though this segment is still being used live in the app. If it were possible to add closures in the snapshot mode (recently renamed to "Current live map"), even with a strict time limit, our life would become a lot easier during road works.
At the moment, we need to apply segment restrictions, wait for the map update, remove the closure, make our changes, wait for the map update and then probably add new closures. If we can…
130 votes
- Don't see your idea?