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.
126 results found
-
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).
131 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…
128 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.
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.
-
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.
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.
-
"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.
111 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).
109 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.
-
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.
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.
-
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.
104 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.
-
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…95 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.
-
Sub-cities
The goal is to have a mechanism for attaching localities or hamlets to a city.
The French wiki presents a number of situations (https://wazeopedia.waze.com/wiki/France/Routes_Nommage).
There is also the management of districts or neighborhoods of large cities that could also benefit from this feature.95 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.
-
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…
91 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 Options object types posted in forum
Currently when an editor uses the Forum Sharing Option to request an unlock, the request ALWAYS says "I would like to be able to edit the following segment(s)." no matter what type of object is selected.
The request should be automatically based on type of object selected
If segment(s) selected, no change
If venue(s) selected, the request should say "I would like to be able to edit the following venue(s)."
If they have any other type of object selected, the request should say "I would like to be able to edit the following [selected object type]."85 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.
-
Segment restriction type that prompts user to confirm access (gates)
Currently we create gates using PR segments. However, this rarely has the intended effect. Those with access (say a gated community) don't get a route through a gate this is most convenient or worse, if all entrances are gated, then restriction is meaningless other than to ensure it's not a through-way.
I'm suggesting a segment restriction type that would generate a pop-up at start-state of a route asking if the user has access to a segment (gate) if that's the shortest route. Ideally, Waze would remember that for that user in the future. This could potentially be used for restricted…
84 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.
81 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.
-
Extra click required for approving a PUR
When approving/rejecting a PUR (new place, new photo, change in details), an extra click is now needed to close the window. Simply clicking approve/reject would close the window, but now you also have to click done to close the window. This wasn't the case until WME v2.109 (released August 2022)
Screen capture (approving a new place): https://www.dropbox.com/s/v5r8lfe1afe7s5j/purnew.gif?dl=0
Screen capture (rejecting a new photo): https://www.dropbox.com/s/j6o4anmu6afxay8/purphoto.gif?dl=080 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 segment selection on mobile
Hello,
Could you improve the segment selection on Mobile and Tablet?
The selection of a segment is already not easy ...
This could be good in addition to being able to easily select several segments, or multi selection, on mobile and tablet.For example, very useful for urgent closure requests made without a permalink and the Team Closure editor is not in front of a PC (and the editor providing the information is on the road at the same time).
Best regards
80 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.
-
Use RTC history to create new RTC on the same segments
It would be very convenient to be able to re-create a RTC based on the RTC history for one or more segments. This would also require being able to choose to select all segments that were included in the original RTC, as well as optionally proposing start / end times.
Two use case examples:
1) Recurring RTCs where the schedule is not known far in advance
For example, there is nightly road construction on a given highway, but this may not repeat every night for various reasons. The actual closure is only published a few hours before, and so requires…
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.
-
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.
-
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).
75 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?