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.
48 results found
-
Internal editor Notes on User Reports
Give editors the ability to enter Notes onto User Reports without these going to the reporters themselves.
This will allow us to leave messages for other map editors without the reporter being notified, for example, Please leave open - due to a Waze developer investigation, Please leave open for a pending site survey, etc.
It may also give us the ability to for to use for an internal conversation about the report that the reporter doesn't need to know about.
Yes, I know we have Map Comments, but having the ability to do this directly on the report would make…
399 votes -
BUS/Motorcycle Lane
Add the option to mark a lane as a BUS lane.
If we have 3 lanes -> Turn left | Front | BUS
We cannot give exact information to the user, because we can only show 2 lanes, because we cannot display the BUS to not mislead the driver.
In Portugal, motorcycles can ride on the BUS lane, so it also helped motorbike drivers a lot
261 votesHey!
Thank you for this suggestion.
This is not a priority for the team at the moment and we won’t move forward with it.
We encourage you to keep on coming up with great suggestions
Best,
-
A true support for bilingual countries
I noticed that Waze doesn't approach bilingual countries just like GMM does.
For example, in GMM, we can write multiple names for the same road in 2 different languages and based on the user's current phone language chosen, the map changes accordingly.
Unfortunately that doesn't happen in Waze, we are stuck in 1 language only, even if we add "Alternative" name.Here in Kuwait, we use both Arabic and English (Even street signs are written in both Arabic and English) , in Google Maps we are having no problems since most of the roads in the map are written in…
237 votesSince bilingual support is a bigger issue affecting not just the WME, this is a company-wide decision that we will bring to the relevant teams.
-
Place Hours: Sunrise to Sunset
When adding Places, especially outdoor places (such as parks, playgrounds, beaches, etc), there are often posted hours saying the Place is open only sunrise to sunset, or conversely that the Place is closed sunset to sunrise. Unfortunately, the existing Place hours interface doesn't allow for these kinds of hours, only HH:mm times. As sunrise and sunset times change constantly, and in some places drastically due to orbital motion of the earth and time changes due to daylight savings times, it is impractical to estimate open/closing times using HH:mm formats.
It would be beneficial to both app users and map editors…
191 votes -
Manage closures in the Issue Tracker menu
Live closures are one of the most important contributions that editors can make to the Waze map
The functionality of viewing past closures on the map has recently been added, which adds complexity to the view.
This suggestion involves managing closures from the Issue Tracker, allowing you to filter those that have been completed, those that are about to expire, or those within a period of time; or by zones in the same way as the UR, PUR or MP
I guess this sug includes this one: https://waze.uservoice.com/forums/59225-map-editor-suggestions/suggestions/47514620-show-only-active-closures and this one https://waze.uservoice.com/forums/59225-map-editor-suggestions/suggestions/45584869-move-closures-history-to-the-closures-tab164 votes -
Improve RPP editing when it conflicts with HN layer
When adding or editing RPP, if there is a conflict with the HN layer (i.e. too far), then the WME issues an error that prevents you from saving your edit. Thus, you cannot add or update this RPP.
To resolve the issue you need to perform the following steps:
1. Update/Remove the address in HN layer
2. Wait for next (successful) map build
3. Add the RPPThis is an annoying procedure that should and can be avoided.
The issue can be handled in one of the following ways:
1. Verify the RPP against the most updated data either in…126 votes -
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…
125 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.
125 votes -
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).
120 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.
112 votesThis idea currently isn't planned, but we will update if it becomes feasible in the future.
Thanks to all who pushed for this idea!
-
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 votesHey!
Thank you for this great suggestion.
We currently have an internal process in place to address this issue, and therefore won’t be developed as a feature in the WME.
If you encounter any issue with advertised location. Please let your coordinators know about it, and they will inform the SCM, so we will be able to check this.
Best,
Hezi -
"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.
102 votes -
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.
-
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…
88 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.
-
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.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.
-
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 votesThank you for this suggestion.
At the moment this is not a priority, and therefore not planned.
We encourage you to keep on coming up with more great suggestions
-
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.
-
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=077 votes -
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.
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?