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.
1252 results found
-
House Number (HN) Mode recenters map
When hitting H to enter HN editing mode, the map is recentered and zoomed on the selected segment. There should not be any zoom or centering change if the current zoom level allows for HN editing.
16 votes -
Counter for Chargers at a Charging Station
Please add a counter to charging station tab Chargers. Once you need to scroll (~7+ charging points), it's difficult to assess how many chargers there are. Example: this Tesla Supercharger: https://waze.com/nl/editor?env=row&lat=52.16064&lon=4.54912&zoomLevel=20&venues=2949642.29824096.27841780
Just something like this would suffice: https://i.postimg.cc/90z5LZ8z/afbeelding.png
16 votes -
Allow moving nodes inside Junction Boxes
Junction Boxes currently prevent moving the location of nodes inside them, which means that geometry edits often need JBs to be deleted and recreated.
16 votes -
Edit favorites on the map editor
Enable favorite editing in map editor. This would be an easier way to make include of several favorites or POIs help in planning a trip.
Ideally it would allow planning with historic traffic data (similar to Google Maps) allowing to establish the travel time between them and estimate the arrival time .
Alternatively the Waze can import the saved locations from Google Maps, so it should be possible to link the Waze has Google Maps account.
16 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.
-
New Feature Request - When a photo must be rejected
It would be nice to have a comment window or a multi-choice button list in WME to send to the Wazer who submitted a rejectable photo so that we can tell them why the photo is being rejected:
- This photo shows a person's face
- This photo is too blurry
- This photo shows a license plate
- This photo is not helpful in identifying the place
...and so forth. It would be something more than just "this does not meet our community standards."
16 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.
-
Could you add express lane support.
Could you add express lane support. I would like to be able to edit the map for express lanes and when they are open be directed to take them when I can! Right now waze gets confused when I use the express lanes and tends to direct me on the slow freeway.
15 votes -
Closure layer behaviour on selected segments
When the closure layer is off and you have a segment with closure selected, the active closure is not showing when you switch on the closure layer. You need to unselect and reselect the segment to be able to see it. It would be nice if that can be resolved.
15 votes -
Improve WME editing capability on mobile phones
I can currently add or delete real-time closures in WME in Chrome on my mobile (Galaxy S20). I can't change turn permissions, for instance, as touching the turn arrow to be changed deselects the segment it's part of. Can we get more functionality of WME in Chrome on a mobile phone?
15 votes -
Allow to drag a node of a segment with closure
Dragging of a node is not allowed when the node is of a segment with closure on it, although the ID of the segment that includes the closure does not change. It is suggested to allow it.
As a temporary solution, it is possible to delete the closure, and then drag the node, and then reenter the closure (but still the closure is removed for the time it takes to complete the change).15 votes -
Properly display far lane guidance at exit arrows on Junction Boxes
The current implementation of far lanes does not allow map editors to easily see the end result of their selection. We have to "guess" at what the app will actually display to the user and, many times, we have to actually drive there to experience the lanes.
This feature requests Waze to add the ability to show the combined far lanes at the exit arrow of a Junction Box.
Currently, if we block a turn using the Junction Box, the exit arrow turns red. If we change the voice prompt for an exit arrow (e.g. changing from Waze default to…
15 votes -
TR-panel shouldn't cover the TR-arrows
I've the impression that the behavior of the TR panel is changed. The panel remains longer visible after clicking one of the TR arrows. Nice in certain circumstances. Not so nice if you want to set all TR arrows of a crossing and some of the arrows are covered by the panel.
Suggestion:
Place the panel a bit further away from the crossing, making all TR arrows reachable.
The little triangle pointing to the selected arrow could be lengthened.15 votes -
Display far lanes information when viewing previous build
When viewing previous build (formerly snapshot mode) it's not possible to see what the far lanes information was. Please add this to the data available when viewing the previous build.
15 votes -
Issue tracker, one more filtering option needed
To be able to follow resolving rates it would be great if you could add one more filter, Solved / Not Identified / Both. Going through those one by one to find out percentage of solved issues is quite a job, this would help a lot.
15 votes -
Re-add the City/State to the Issue Tracker tiles
Unlike the previous Issue tracker, the new Issue Tracker no longer displays the general City/State a User Report has been raised. Please re-add this.
15 votes -
Temporary real-time traffic regulations override
Police frequently implement temporary local traffic regulations, such as diverting vehicles through bus lanes or HOV lanes. On Waze, these segments are typically mapped with Time-Based Restrictions (TBRs) to prevent routing through them. However, these areas are usually pre-mapped. I propose creating a new entity within WME that can be toggled in real-time to override existing TBRs, allowing for more accurate routing based on live traffic conditions
15 votes -
WME Feed customise by country
WME Default loading is launching with feed showing KoiFish suggestions that are locked for almost all editors.
Most L1-2 editors cannot add these and cannot hide them either. As a display, it is very confusing for them.
Without taking away any choices in Feed selection, it would be nice if the WME Default Feed could either be selected by country as defined by coordinators or at least remove KoiFish suggestion as default load for all editors.
15 votes -
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,…
15 votes -
Wildlife Collision Hazard Areas
Wildlife, especially deer, are a significant hazard to drivers in many parts of the world. Collisions with deer account for one to two million insurance claims each year in the US alone. While wildlife on the roadway is harder to anticipate than other hazards, authorities do know of specific areas, times of year, and times of day that drivers are at increased risk of collision. Please let us mark these hazard areas (with the times of year and times of day they should be "active" to avoid hazard-alert fatigue) to communicate this risk to drivers. Both drivers and wildlife will…
15 votes -
Add the ability to search segments by ID in the WME
Add the ability to search segments by ID in the WME
14 votes -
Add a comments field to WME when adding a closure
When adding a closure, I think it would come in handy if there was a comments field (or text box) that could be used to let other editors know, what source was used. If there is a problem/question afterwards, other editors know where to ask for additional info.
This field should only be visible to editors, no need to show it in the Waze app itself.
Currenly I use the description field, but that's not so handy.
14 votes
- Don't see your idea?