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.
1622 results found
-
Display the capture date of Satellite imagery
There are solutions to find the capture date, but they are cumbersome and outside of WME.
From discussions with staff, I've been told that the date is present in the data Waze receives from Geo, so please please please surface the capture date of Satellite imagery in WME.
141 votesGreat timing! We’re currently working on the display the capture date of Satellite image. Keep an eye out for updates on the WME.
-
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…
152 votesGreat timing! We’re currently working on it but more from a safety perspective. Keep an eye out for updates on the WME.
-
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…
148 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 client app version in URs User Preferences field
Currently WME shows various useful information in URs, such as usernames (if available), report source, and various other User Preferences. Please also include app version from which the UR was generated.
This would be useful when troubleshooting certain reports, as some features may not be available to such users and also that some very old version of the app include 'Reported map issue' in the description field by default.
This, at the time of writing, also affects automated replies to URs, from Map Team account.
For e.g., see https://www.waze.com/discuss/t/introducing-automatic-replies-for-urs-without-description-enhanced-filtering/397655/122?u=darkestways thread.
107 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.
-
Eliminate Heuristics and auto-generate paths instead.
Heuristics are hidden behind so many elements of the map nowadays. As a result, editors are often expected to read multi-page documentation to understand how to take advantage of them or how to avoid unintended behaviour. In practice, even experienced editors frequently are unaware or uneducated, making this expectation especially unrealistic for new editors.
My suggestion is to eliminate heuristics altogether, and replace them with auto-generated explicit paths/TIOs/etc. Whether it's an H or an # junction, traffic lights, turn instructions, u-turns, etc, everything should be visible and unambiguous in the editor.
Some examples:
1) if a u-turn in an H…103 votesGreat timing! We’re currently working on it. Keep an eye out for updates on the WME.
-
New filter "Older than" should apply for URs with no comments
The new UR filter "last comment time: older than: should apply also to those URs with zero comments (automated comment). This way we could monitor URs with automated comments that have not been answered yet by an editor after x days.
59 votes -
Issue Tracker: Add options to "area" and "last comment by"
When using the issue tracker, to make searches more practical and useful, the following options are missing:
1. When specifying last responder, we need option to mark "Not me" as sometimes another user may add comments to a UR he didn't report. Right now, there is no easy way to select these URs.
So, all options for last comment by should be: Anyone, Reporter, Me, Not me.- The search area should have the option "not in managed areas" as a checkbox or other way. When we scan for URs in a large are in "Specific area" (le a country or…
60 votes -
Add "above number of days filter since reported date" to Issue Tracker
This idea is similar to https://waze.uservoice.com/forums/59225-map-editor-suggestions/suggestions/48574424-add-above-number-of-days-since-last-comment-filt
The main difference is to add "Above number of days since reported date” to the Issue Tracker.
The reason is to find URs that Waze auto-responded to and sufficient time (e.g. 4 days) have passed and there is no response from the reporter. so we can do a follow-up response. Without this filter, we have to keep changing the end date in the area section (above the Update Request (UR) dropdown) of the Issues tab.
50 votes -
Move layer, refresh, and permalink icons when chat is open.
When you have the chat panel open, the layer, refresh, and permalink icons are hidden. That means when working with an editor in chat, the panel has to be closed to grab a link. Then chat has to be opened again to share it.
70 votesGreat timing! We’re currently working on it. Keep an eye out for updates on the WME.
-
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.
135 votesGreat thinking! We’ll share with the team; they’re always interested in new feature ideas.
-
Add "Serial Number" field to Speed Cameras in WME
Currently, when adding or editing a speed camera in the WME, there’s no way to associate it with its official registration or identification. I suggest adding a “Serial Number” field to the speed camera settings.
Having this field would allow editors to input the official serial number of each speed enforcement device, as issued by the government or regulatory agency. This is extremely valuable because:
- It enables verification and validation of the camera against official databases from transportation or metrology authorities.
- It improves accuracy when identifying missing, moved, or deactivated cameras.
- It helps prevent duplicate or outdated hazards, ensuring only…
60 votesGreat timing! We’re currently working on adding a Serial Number field to Speed Cameras in WME. Keep an eye out for updates on the WME.
-
Indonesia ETLE Camera
In Indonesia, all traffic enforcement cameras operate under one unified system: ETLE (Electronic Traffic Law Enforcement) Camera.
To ensure accuracy in WME, provide clarity on which camera type is valid, and avoid confusion among Indonesian editors, we'd like to request a dedicated Indonesia ETLE camera type that reflect the applicable traffic enforcement regulation for Indonesia.
27 votes -
Add type "Boom Barrier" to permanent hazard
https://i.imgur.com/T05sm8V.png
In my country (but I think everywhere) there are a lot of barriers which are placed in different areas like PLR, restricted areas, private areas, .. This barriers are opened for locals or by different type of card/transmitters. It's very convenient when user or taxi driver see this permanent hazard on his road. I think it's not difficult to add this type to current PH structure.
In my country there ate not "toll booth"-es and we use this type (they are the same on the picture) but it's not convenient for people who use another TTS and language in…245 votes -
Let Editors set their preferred date format in WME Settings
Different regions of the world use different date/time formats, and even within some regions individuals may have their own preference for a date format that's most comfortable for them. Rather than have WME use one format for entering and displaying dates, allow the user to configure their preferred format on the WME Settings page, the same as configuring Imperial vs. Metric units. WME should then honor that date format on all date entry and display fields.
Sample date formats to offer could include "dd-mm-yyyy", "mm/dd/yyyy", or my preference for a default the ISO 8601 "yyyy-mm-dd" international standard format. I suggest…
107 votesGreat thinking! We’ll share with the team; they’re always interested in new feature ideas.
-
Absent Segments in Waze
There are people using Waze moving through segments NOT YET drawn.
KoiFish apparently can not trigger a warning for us to create such segments.Examples (enable GPS points to see)
https://waze.com/editor?env=row&lat=-33.69406&lon=-61.94139&zoomLevel=17&segments=365355793
https://waze.com/editor?env=row&lat=-33.53906&lon=-62.15544&zoomLevel=14
Please vote! Thank you!!
32 votes -
Allow snapping of places geometry nodes together
It would be very useful to be able to "snap" geometry nodes of two different places together (just like to when creating an intersection with two segments). This would ease the mapping of adjacent places (e.g.: a mall next to a park, or a river next to a park, that goes all the way to the edge of said river).
55 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 Google POI uploaded photos in Waze Map Editor (WME)'s Google Places tab
Currently, Waze Map Editor (WME) allows editors to view and edit Google Places (POIs) and submit names for approval. This is an incredibly helpful feature for keeping our map aligned and accurate. However, one crucial piece of data is missing: the user-uploaded photos attached to these Google POIs.
We are requesting the ability to view these Google POI photos directly inside WME (for example, in the Google Place details panel when a Google POI is selected or linked).
Why this is needed (The Value)
Better Visual Verification: Names and locations can sometimes be ambiguous. Being able to see photos of…
28 votes -
Add option to make restrictions visible similar to closures
This goes together with a suggestion on the APP side to add an option to display some restricted segments.
Since there is no easy way to add closures based on a schedule, there are times it would be nice to have restrictions that can be scheduled show in the app similar to a closure. That way someone driving without a route will have the visual cue like a closure.
85 votes -
Include Permanent Hazard (PH) changes in segment history
Currently, when a Permanent Hazard (PH) is added or updated in a segment, no record is created in the segment's history.
Ideally, changes to their attributes should be tracked, but for now, recording when they are added or updated would be very helpful.
27 votes -
Add shortcut to the panel
In my opinion, it would be very useful to add shortcuts next to the possible actions in the panel, so that by seeing them often, editors could remember them better and use them more frequently.
You can see an example here https://drive.google.com/file/d/1EDSybQCFW-2n-if12sFXVMXC6Zkef4UV/view?usp=drivesdk42 votes
- Don't see your idea?