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.
1656 results found
-
Surfacing House Number Errors
A nice feature would be to surface the real error message from house number additions. Sometimes when there is a conflict between segments, you get a generic "there was an error" type message, but the back end call has the full details which you can see through dev tools. For example:
This segment: https://www.waze.com/en-US/editor/?env=usa&lon=-97.48797&lat=30.16312&zoom=6&segments=48240740
Conflicts with: https://www.waze.com/en-US/editor/?env=usa&lon=-94.82458&lat=29.82488&zoom=6&segments=48240740,511847520,511847562,511847579When the city is listed as "none" (No City). When adding "115" to the latter, this resulted in an error (see attached)
However, the backend error that is returned by the web request is (see attached)
There's enough in the error message there…
45 votes -
Change the wording in the automatic email when an editor comments on a UR
When a user reports a map problem in the app, then an editor responds to it in the Waze Map Editor, the reporter gets an automatic email that says:
"An editor from the Waze mapping community wants to solve the problem, but needs some more information.", followed by the editor's comment.
The problem with this wording: This is not always true. If we can identify the cause of the report without needing clarification, then often we may simply use the comment box to thank the reporter for their report. Thus, the comment box isn't always used to ask for more…
45 votes -
Receive reminder when closure will expire soon
The ability when adding a closure to select a checkbox to receive a reminder notification a couple days before expiry would be really useful. Sometimes when adding closures we do not know when the road will reopen, so the closure is set for a week or a month. So it would be great to know when these closures are about to expire so we can check and extend the closure if needed.
45 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.
-
More Specific Error Messages
Specific error messages are very useful, and we can use more of them.
Here are some recent cases I have run across where it would be helpful to have a more-specific error message
RPP too far from identical HN (zoom out if necessary to highlight the HN location)
RPP too far from recently-deleted HN; try again after HN update. (zoom out to highlight the former HN location)
Improper restricted turn in JB (show and highlight the specific turn arrow which is the problem). Allow the turn and try again (https://www.waze.com/forum/viewtopic.php?f=211&t=276336&p=1922955#p1922761)By: voludu2
Link to original suggestion: https://www.waze.com/forum/viewtopic.php?f=1525&t=27659144 votesHey!
Hey!
Thank you very much for this suggestion.Detailed Error messages are part of the planned idea of the WME dev team these days.
We will keep you updated with any updates
Best,
Hezi -
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.44 votes -
All 1-way roads should automatically be A→B
There's no need for 1-way roads to be either A→B or B→A.
They should only be able to be A→B.This will solve a lot of issues us editors encounter, for example when adding road closures.
I saw another suggestion here to apply A→B closure also on B→A segments, but it would be much better to just get rid of B→A segments.Let me know if there are any questions.
44 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…
44 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.
-
Allow for polygons in major traffic events to be bigger than 20km
Waze Map Editor doesn't allow a polygon bigger than 20km to be used for a Major Traffic Event.
Example: Attempting to create an MTE for Twin Cities Marathon that only targets a 0.06mi buffer around the route itself, so it only alerts affected drivers.
43 votes -
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.
43 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=drivesdk42 votes -
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.42 votesGreat timing! We’re currently working on it. Keep an eye out for updates on the WME.
-
Disable and restore to default of the issue tracker filters
Please add two important features to the issue tracker:
1. Temporarily disable all filters in the issue tracker (show all URs, PURs etc.), without changing the filters, so that the editor can later on enable the filters in order to have the defined filters without the need to redefine them.
2. Restore the issue tracker to its default state, so that all the previously changed filters will be returned to their default state.
These features will be very useful.42 votes -
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.
-
Avoid specific street or area
Add the option in the settings to avoid specific areas, the functionality already exist as you already have the features of avoiding toll roads, dangerous zones, and complex intersections, so just add the functionality to avoid custom areas, for example a specific street or city i dont want to pass through
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 -
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…41 votes -
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
41 votesGreat timing! We’re currently working on adding more keyboard shortcuts. Keep an eye out for updates on the WME.
- Don't see your idea?