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
-
Close places temporary just as you can with roads
As roads can be closed between certain dates it will be great that we can also get this for places. For example when a place is going to close for temporary construction.
49 votes -
Add entry point automatically for RPP and Point Pkace
Would it be possible to add entry points for RPPs and Pont Places automatically by default like for the HN?
Now after inserting the RPP or Point Place on the map, also bringing them closer to the relative segment, often Waze does not take you to the desired arrival point and so to solve the problem we have to manually insert the EPs.
I think it would be useful if it was automatically inserted by default as it already happens for HN, so the editor would immediately understand where the navigation will lead .
We will also fix the problem…49 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.
-
Adding a comment when requesting new aerial images
When L6 editors request up-to-date images for the WME, it would be useful if they could write a comment (for example, for whom they have requested the images) and this comment should also reappear when they get the notification that the new images have been provided.
It could also be helpful to have access to a list or map showing the areas that the new images were requested for so that new images are not requested for the same area by different editors.
48 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.
-
Partners polygon layer
Hello,
Thanks to the Waze for Cities program, we are happy to have more and more partners, either for road management (Connected Citizens) or for event management (Global Event Partners).
For those who do not know the details, you should know that a partner benefits from one or more polygons that characterize their rights area (data flows to or from Waze, closures, MTE).
The community being very involved, and always on the lookout for modifications to be made in WME, or closures to be programmed, it often happens that our closures or our editions conflict with their closures.
It is…48 votes -
Flag Waze segments for addition to Google Maps
If an editor adds roads to Waze and sees they aren't in Google Maps, we have to add them using the Google Maps interface. This does not include access to additional imagery which can make it easier to make the updates.
With the increased data exchange between Waze and Google, it makes sense to have a button to flag sections of the Waze map for incorporation of high priority changes rather than having to map the area twice.
48 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 error for Junction Boxes issues more intuitive
Currently when you try to add something that is not allowed due to a junction box located on the segment somewhere (at times it could be several miles away and not visible), you get a very generic error that just says "Saving Error: Operation not supported"
It would be more useful for the error message to say something along the lines of "Saving Error: Junction box connected to one of the segments being changed"
47 votes -
Allow combining chargers when merging EVCS
When merging EVCS, give users the option to include both sets of chargers. For some reason, some networks (ahem, ChargePoint) sometimes list multiple charger sites in the same parking lot or garage. If we try to merge them, we have to select one or the other set of chargers. Please add an option to include both sets.
47 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.
-
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.
-
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.
-
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.
-
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 -
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 -
Issue Tracker Saved Filter: Should be able to modify/edit an already saved filter
I should be able to modify or edit an already saved search.
When saving a new filter, a dropdown of saved searches should be displayed, and if one is selected, an overwrite warning should appear. This should be alongside a "create new filter" option.
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.
-
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.
- Don't see your idea?