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.
169 results found
-
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.
146 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.
145 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).
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.
-
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…140 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…
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.
-
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…136 votes -
Directly edit water layer
The water layer should be editable.
The water layer import is outdated and frequently lakes and ponds are drawn where roads and houses now exist.
We can add hacks to WME to suppress the display of these water features in the Waze app but this is not ideal.
131 votes -
Allow 3 choices for PURs that report closed places. 1) Ignore; 2) edit place 3) delete place
Currently we can only ignore a PUR that reports a place closed or delete the closed place. We have no other choices available. Often, we need to make changes in operating hours or make other changes but NOT delete the place. If we ignore the PUR, it counts against the reporter. We need a third choice that gives the reporter credit for the report but allows us to keep the place and make appropriate changes to it.
127 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 postal codes/ZIP codes to Waze address editor
When a Waze app user searches for an address added using the Waze Map Editor, it does not show the postal code. But with Google addresses, the postal code is shown. Please add postal codes to the WME.
121 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.
-
Close a place for a fixed period
Sometimes I receive UR for places closed for works (construction site, temporary closure).
It would be nice for editor to be able to close a place for a fixed period, as you can close a road.I had the case on 2 gas stations under construction closed for several months. A "temporarily closed" button or closing dates with automatic reopening would be great!
119 votes -
Show Lane Guidance for all editors
Show Lane Guidance (LG) for all editors regardless of level.
Today there is a limit to handle LG. In my country the limit is set to a higher value than my level. At present we lowlevel-editors cannot see the current LG and therefore we are not able to propose a adjustment of a existing LG nor propose a new.117 votes -
Allow forcing a closure to expire (instead of deleting the closure)
The WME shows now the status of all recently finished and all active closures. A deleted closure will not be visible anymore.
For that reason, we prefer to "finish" closures instead of deleting them.
It would be nice to have an option in the context menu of closures, to make the closure expire, by setting its end moment to now.116 votes -
Polygons in WME should just be a thick border instead of a full fill
To allow for easier interaction with polygons and segments & places inside polygons, change the polygons to be a thick border instead of it being a filled polygon.
With the expansion of features that include many polygons beyond just places (JBs, Permanent Hazards, Natural features, etc), it would make it much easier to work with these shapes.OpenStreetMap does this very well.
114 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.
-
"Hide street name" option
Include a checkbox near the street name for segments, so that when it is selected the name of the street does not appear on the live or client map. This would be useful for segments that have a name that would benefit directions, but could be confusing to see on the map. For example, seeing the name "Main St Frontage Road" on the app, especially when zoomed out enough that the name appears right over "Main St", could easily cause confusion and take longer for the driver to comprehend the map, especially if they are familiar with the area.
114 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.
110 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.
-
Improve House Numbers Editing Interface Clarity
Since the version 2.272, the HN interface has become visually overloaded mainly on cross roads. In the previous version, entering house numbers mode would visually isolate the numbers belonging only to the selected street. This behavior was much more intuitive and provided a cleaner, distraction-free environment for editing.
We suggest restoring this functionality - either by default or as an optional toggle - so that only the house numbers from the selected street are shown during editing. This change would significantly improve clarity, reduce errors, and enhance the overall editing experience.
Thank you for your consideration.
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.
-
Connect an Advertising Pin to its Place on the WME
Very often it happens that advertising pins are not placed in the correct place on the map, which leads to routing errors. It would be very useful to be able to link these Pins to the corresponding Place entered by the editors in the correct place in the WME, so that the routing to these destinations works correctly. (as we already do for the link to Places on Google Maps).
106 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.
-
Automatically send UR reminders and mark as 'not identified' if no reply
User Reports (URs) come in by the truckload. Despite a message from an investigating editor, only 10% of URs will receive a reply. This represents a significant amount of time by editors, particularly senior editors managing large areas, to the manual handling of individual URs. Since 90% of the URs result in the same process, help us streamline and automated it so we can focus our valuable time on productive investigations and edits that will value add to Waze.
I propose an additional tick box under "Follow conversation" that says along the lines "Auto reminder and mark as not identified."
…
106 votes -
Narrow Road Permanent Hazard
This permanent hazard would warn users of an upcoming section of narrower road width that has traffic and/or safety considerations. Potential applications include:
Areas where a two-way road transitions to a single-lane width where opposing traffic must alternate/give way through the narrow section
• Ex. 1: https://waze.com/en-US/editor?env=usa&lat=41.26449&lon=-75.78368&marker=true&zoomLevel=18&segments=502096154
• Ex. 2: https://waze.com/en-US/editor?env=usa&lat=42.10978&lon=-71.24117&marker=true&zoomLevel=18&segments=74434220,22554146
• Ex. 3: https://waze.com/en-US/editor?env=usa&lat=44.33295&lon=-73.28244&marker=true&zoomLevel=19&venues=187892155.1879052625.3735122Two-way roads of limited width where common parallel/street parking cause drivers to have to move in or out of the parking lanes to allow traffic from no parking direction to pass
• Ex. 1: https://waze.com/en-US/editor?env=usa&lat=40.02695&lon=-75.22336&marker=true&zoomLevel=18&segments=41758956,41751608,41747111,41755005
• Ex. 2: https://waze.com/en-US/editor?env=usa&lat=41.88316&lon=-71.35791&marker=true&zoomLevel=17&segments=43507359,43531672
These are strictly permanent hazard warnings…
102 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.
-
Change Forum Sharing Option autofill
When an editor uses the forum sharing options, new editors are consistently adding the wrong lock level to their request.
For example, the current Unlock Request automatically fills in the following information:
Hi Editors,I would like to be able to edit the following segment(s).
Your help would be greatly appreciated.Permalink: https://waze.com/en-US/editor?env=usa&lat=29.63406&lon=-104.27920&zoom=5&segments=516527406
Reason:
Unlock to level:Thank you in advance,
The "reason" and "unlock to level" kind of blend in.My suggestions would be to automatically fill in the current lock level of the selected objects and the rank of the editor making the request for the "unlock to…
99 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.
- Don't see your idea?