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.
1541 results found
-
Remove unpaived attribute from Off-road / Not maintained segments
An Off-road / Not maintained segment is unpaived by definition and should not have the unpaived attribute. We encountered navigation problems to destinations on such segments because of this attribute, so in Israel we don't allow to set this attribute. New editors are not aware of this problem, and think that they should set it to unpaived, and we have to explain it to them.
Please remove this attribute in this type of segments in the WME, and it will save a lot of effort.42 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.
-
Disable segment geometry changes in House Number mode
When in the "Edit House Numbers" mode, the Editor allows changes to segment geometry, but then generates an error when saving the changes. It is very easy to unknowingly edit segment geometry when trying to move a house number stop point. When this occurs, any HNs edited after that geometry change need reverted.
Please disable segment geometry changes when in HN mode.
42 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.
-
Recategorizing UR's when solving
Add a feature to WME to recategorize the Solved UR's when closing those. This would give Waze a true insight of what reports are really needed and vice versa, what are rare and could actually just be within General Error category etc. Based on my research of all Solved UR's in Finland for last 3 months only about 50% were in right category.
In my opinion this would help to reduce and refocus UR categories to better match with reality which in turn helps users when they are reporting meaning less UR's with wrong category -> Better data and better…
42 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 new layer with Road Signs (generated from Street View)
Use AI models to identify Road Signs from existing Street View images, and surface them in WME as a new layer.
Road sign examples:
- Speed limits
- Stop/Give way
- No entry
- Prohibited turns
- Sharp bends
- Lanes mergingIdeally this new layer should come with sub-layers and allow editors to show/hide on demand (similar to how Hazards currently appear in WME). Sub-layers could be groups - for example:
- Warnings
- Speed limits
- Orders
- Instructions42 votes -
MTE: exclude segments
It'd be great if there would be an option to exclude certain segments from MTEs.
Either have the MTE snap to a certain elevation level (e.g. exclude underground highway tunnels, or elevated highways,) or exclude certain road categories, such as currently done in Permanent Hazards.41 votes -
Easier way for cutting a segment
There are a lot of occasions where the properties of a road (eg speed) changes within the same segment. Currently the only way to cut segments is to add a road with a junction on the spot where one wants to split the original segment and immediately remove the added road.
This is rather cumbersome/overkill and could lead into incorrect data.
Other map reporting tools have a segment split option within a simple right hand mouse click and it would be nice if a more simple way would be available in WME too.41 votes -
Additional Imagery requests feedback
With the great feature of Additional Imagery, we can make requests for updates using "The Button".
If the imagery update meets our needs, we should be able to confirm that it did (like a thumbs up for alerts in the app).
If we get an alert that imagery has been updated, but the imagery is not sufficient (not new enough, clouded over, etc), we have to submit a new request. Instead of submitting a new request, there should be an option to reopen the original request to get newer/clearer imagery.
As is, there is no easy way to provide feedback…
41 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 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=drivesdk40 votes -
Allow hyphenated house numbers in RPPs
In my AM in Iowa there are several neighborhoods that have hyphenated house numbers. Here's an example: https://beta.waze.com/editor?env=usa&lat=42.40782&lon=-91.76381&zoom=6 Since they are on a private road RPPs should be used but can't be because hyphens are not permitted.
40 votes -
Improve/change the error message
Improve/change the error message when low level editors tries to delete the house number on streets with higher locks. Now we got "Error saving, try later" message. It gives, to editor, no idea of what the problem is, and the user may thinks that's a WME bug. By changing this message, it will give to editor and mentor/higher levels editor's more information to understand where the problem lies.
40 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.
-
Roads with permits for residents only
Very often there are streets that can only be used by residents.
It would be useful to be able to set the segments on the WME "residents only".
This way only those who add their home address on those streets in to the app will be able to use them.
It is different from editing a road as private, because it would only allow access to residents, whereas now if you search for a destination on a private road everyone can access it.40 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.
-
Flagging matches with permanently closed venues
With the "Enhanced Matching" between Waze and Google venues going live, some Waze venues are matched with 'Permanently closed' place from Google Maps.
While these are accurate matches, we won't know these places are permanently closed until an editor interacts with the place or a user reports it to us.
My suggestion is to flag such matches to be reviewed by editors. A PUR or something like that.
40 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.
-
Ability to add more than 4 fields in the Address box
Please give us the ability to create more than 4 address fields. and make it so that editors can set custom number of fields according to their own area.
Right now waze has four boxes for address: Street, City, State, Country.
Not all addresses in the world work quite exactly like this so please
I would like to suggest waze allow users to create custom fields and name them and Country coordinators set the limit of fields in each city and country.
So we can have many fields like:
Street
Sector
Phase
Town
City
District
State
etc.
I tried looking…40 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.
-
Conditional lane guidance
There are many cases in highways where there is an on-ramp shortly followed by an off-ramp. In those cases, the right lane/s serve for those who get on the HW from the on-ramp, as well as those who get off the HW on the off-ramp.
A wazer that gets on the HW from the on-ramp and has to continue on the HW should get lane guidance to go onto the left lanes when approachng the next junction of the off-ramp, otherwise, he might continue on the right lanes and get off the HW.
A wazer that comes on the HW…39 votes -
Move closures history to the Closures tab
Move the information about the closures history of a segment from the General to the Closures tab. This way the closures information won't interfere with important segment changes history and it will be easy to look the specific information. The "last date" will then be correct for each of them - segment changes and closure changes. Also, being in the Closures tab will allow for more data about the closure to be included (incorporating Script features - URO+ or the new WME History Enhancer).
https://greasyfork.org/en/scripts/449557-wme-history-enhancer
39 votes -
Map Suggestions need hotkey
Map Suggestions are a layer in WME. If you want to see under the suggestion, you have to disable the layer. The only way to do that is via the Layer menu. There is no option for setting a hotkey.
39 votesGreat timing! We’re currently working on adding a hotkey for map suggestion. Keep an eye out for updates on the WME.
-
Off road / Unmaintained road should not have the unpaved option
The "Off-road / Unmaintained road" type is almost always unpaved, and in cases where it is paved, it is not to be treated as paved. Thus the "Unpaved" attribute of such a segment is not needed. Moreover, it may sometimes cause an unwanted route when there are some segments that have the unpaved attribute whereas some don't have that attribute.
I suggest removing that attribute from that type of segment.39 votesGreat timing! We’re currently working on it. Keep an eye out for updates on the WME.
-
Add more keyboard shortcut options for drawing Hazards
Right now, we've got a long list of Permanent Hazards available to map, but only two (Speed bump and Speed camera) have assigned keyboard shortcuts.
Having more keyboard shortcuts would be super helpful for productivity. Personally, I think the default shortcut for each hazard could be blank/none, so users can set their own preferred keys for the hazards they use most often.
Link to the forum discussion: https://www.waze.com/discuss/t/new-feature-alert-permanent-hazards-now-available-in-wme-all-environments/350757/36
39 votesGreat timing! We’re currently working on adding more keyboard shortcuts. Keep an eye out for updates on the WME.
-
keyboard shortcut for adding POI
A significant workflow inefficiency within the Waze Map Editor (WME) currently stems from the lack of keyboard shortcuts for adding Points of Interest (POIs). Users are required to rely solely on mouse interaction – hovering over the POI menu and clicking the desired category – every single time they need to add a new point.
This becomes particularly tedious for editors who frequently utilize specific categories. For instance, I personally rely heavily on the 'OTHER' POI category. This isn't for standard points, but rather as a necessary workaround to map complex Residential Place Points (RPPs) or House Numbers (HNs) that…39 votesGreat timing! We’re currently working on the keyboard shortcut for adding a POI. Keep an eye out for updates on the WME.
-
Simulator to test editions
Sometimes when we make changes to the map, we need to wait for it to update to see if it had the desired effect.
It would be nice to have some type of simulation in the WME and thus be able to avoid various changes until the expected result is obtained.
Because of COVID, many editors have not been able to check if the changes we made had the impact we wanted, so we had to wait for a report that warns us of the error or not.39 votes
- Don't see your idea?