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.
120 results found
-
ICON Change on RTC for Turns
Currently when you select a segment with an RTC on a turn arrow, you just see the white fence/barricade icon that you see on the node. You then have to hover over the turn arrow, then click on Turn Closures and go to the window that popped up to see if these are active or finished.
I would like to see the icon changed to the the Red Closed symbol when active, like we see on segments when they are actively closed, and then the grey circle we see when they are finished. It would help tremendously in deciding if…
71 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.
-
Incorporate the Top "X" scripts into native WME
Given the recent injection of malicious code into scripts used by the majority of experienced editors
https://www.waze.com/discuss/t/urgent-two-scripts-were-compromised-on-feb-1-please-read-if-you-use-scripts/365499
I strongly urge Waze relook at the Top "X" scripts that were identified several years ago and incorporate them into native WME.These scripts serve several functions
1) Increase navigation precision: JAI (mentioned above) is absolutely needed for experienced editors to determine the angles and thus, the turn announcements when one moves from one segment to the next
2) Speed up editor time: ColorSpeed (also mentioned above) and others, like LaneTools or Road Shield Assistant, provide a quick visual on the overall WME…92 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.
-
House number change history
When selecting a house number the interface no longer shows who last modified the house number. History on the segment doesn't always show what was change (it might show added or deleted, but not moved or edited). Segment history needs to have more detail on what was done.
67 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.
-
WME Client simulator
With each additional functionality on WME (Paths / Far-Lanes / Jubra / Junction box / lanes / ....) gets increasingly difficult to map. This makes it more likely that us map editores will make some kind of mistake or don’t take something into consideration. Having a way to preview the changes before they are live on the map will made both editors and client less frustrated, with a more accurate map.
219 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.
-
Copy button for segment/place address
Very often you have to search info for address while editing maps and it could be made a lot easier by adding a copy button to copy address on properties panel. Or maybe 2 buttons, 1st for just the street name, 2nd for whole address.
51 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.
-
Ensure that permanent hazards and cameras are selected before they can be relocated
As shown in the above video, it's far too easy for a PH or camera to be moved accidentally when panning around the map. Hit a PH while panning, and it can be moved half way across the screen.
Please make it so they have to be selected before they're above to be relocated, just like other map elements.
66 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.
-
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.
-
Include temporary settings like HOV route selection in UR information
Relatively recently we got the ability to see some app settings in user reports. What we can't see are temporary settings like whether or not an HOV route was selected. It would be helpful to surface any information available that does not compromise anonymity.
51 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 residential places to be moved farther from their "parent" street
Currently, it is generally not possible to create a RPP at, or move an existing one to, a location more than (approximately) 550 m from a segment that has the same street name as the RPP. However, in rural areas of the United States, it is not unheard-of for houses to be located much farther than that from the nearest road. Suggestion: increase the allowed distance for RPPs to at least 1,500 m (no objection if this would require a higher editing level to accomplish than the default R1 for creating an RPP).
72 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 Tunnels
New feature in the app and WME to avoid tunnels such as ferries, tolls…
25 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 Permanent Hazards on Non-Driveable Roads and Pedestrian Paths
Disable the ability for permanent hazards to be snapped to and/or placed on non-driveable roads (runway and railroad) and pedestrian paths (routable, non-routable, and stairway) in WME. PHs intended for driveable roads at junctions with these road/path types can be accidentally placed on the incorrect non-driveable segment. While easy to check and correct when placing, this could preemptively prevent mistakes.
130 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.
39 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.
-
Issue Tracker: Stop defaulting to All Issues - remember last saved filter selected
If you don't have a Pinned Save Filter, Waze should remember the last Save Filter selected rather than reverting back to "All Issues".
If I'm working on a Saved Filter, and need to refresh, it's more than likely I want to continue working on that same filter afterwards.
29 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.
37 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 oblique imagery (birds eye view) from GMaps to WME
To allow editors a more comprehensive view of an area and to provide an additional data layer of imagery, use the already-available oblique imagery from GMaps in WME.
Oblique imagery allows for a 360° view of a location so we would need a new icon to allow for cycling around the 4 'quadrants' of the imagery.
78 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.37 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 "above" number of days since last comment filter to Issue Tracker
In the Issue Tracker, we have "Last 30 Days" and "Last 7 Days" options in the "Last comment time". This filters out the URs since the last comments were before 30 or 7 days.
Can we have another filter for "Above <number> of Days" ago?
The number of days on the Last and Above options should be configurable for the user. As such, if I enter 3, I should see all URs with Last Comment that was made more than 3 days ago.
We can use a between-dates filter, but this must be changed daily. If we have the above…
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.
-
Allow for issue tracker to show results in descending order
Currently the default view of issue tracker results is ascending (newest to oldest.) It would be nice to allow the results to show in reverse (oldest to newest.) Sometimes I want to address the oldest issues first so that there are not so many backlogged.
92 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 Permanent hazard: Check-point
In many countries, fixed check-points are installed on the road. It could be done by Police, Customs, Tax services, Weight check... and even borders.
It would be great to have those marqued on the map as permanent Hazard " Check point". It has basically the same effect of a toll booth: You often need to stop there, or a least drive through at a very reduced speed.
This would be a great safety enhancement for both drivers and those manning those check points.
25 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?