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.
83 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…
478 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.
-
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
332 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.
-
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…
258 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 type "Boom Barrier" to permanent hazard
https://i.imgur.com/T05sm8V.png
In my country (but I think everywhere) there are a lot of barriers which are placed in different areas like PLR, restricted areas, private areas, .. This barriers are opened for locals or by different type of card/transmitters. It's very convenient when user or taxi driver see this permanent hazard on his road. I think it's not difficult to add this type to current PH structure.
In my country there ate not "toll booth"-es and we use this type (they are the same on the picture) but it's not convenient for people who use another TTS and language in…238 votes -
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…
225 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.
208 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.
-
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-tab184 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 the GPS points layer
To branch off the discussion from the WME release topic:
RichardPyne כתב:
I would find GPS points much more useful if they were color coded by age rather than direction. Th arrows provide useful direction, but in areas where traffic patterns are changing due to construction, knowing the age of the trace would be far more useful.dchary2418 כתב:
It could help if the GPS traces were the same original color, but shaded darker for older data.Glodenox כתב:
I'd be all for somehow showing the age of the GPS points. Especially the more recent data seems of interest to…169 votes -
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.
159 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.
155 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 numbers for villages with no street names
There are many places where there are no street names - it's just "City name - number" as the address.
141 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 selectable traffic light icon options & updated TTS for flashing signals
In order to be more hyperlocal, please add selectable traffic light icon options to WME that would then display in the app at intersections where flashing yellow (warning) lights are erected or those that have flashing red lights (stop). In some areas, red flashing lights exist and do indicate it's a stop but from a TTS and visual perspective, "Turn left|right at the flashing light" is much more hyperlocal than turn at the stop sign, when a stop sign might not actually exist there.
An example of said light: https://beta.waze.com/en-US/editor?env=usa&lat=31.77078&lon=-94.19763&marker=true&zoomLevel=19
Streetview: https://maps.app.goo.gl/biqxPWVDQmM18TTE6Editors could easily provide plenty more examples where…
137 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.
-
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).
136 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…
134 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 UR Issues Tracker a Tracker and not a Filter
Currently the Issues Tracker is not a tracker, but rather a filter because it hides other URs (issues) on the map.
Ad an option not to hide URs on the map and display the default view (default setting in tracker)... so yes, we need to have some default options (that each user can change)... and when this option not to hide URs on the map to display the default view (including URs).
For example:
I always leave everything to see on my map - my default.
When searching for new URs or looking for URs with answers from reporters, I…133 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…132 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.
127 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.
-
Directly edit water layer
The water layer should be editable.
The water layer import is outdated and frequently lakes and ponds are drawn where roads and houses now exist.
We can add hacks to WME to suppress the display of these water features in the Waze app but this is not ideal.
125 votes -
Close a place for a fixed period
Sometimes I receive UR for places closed for works (construction site, temporary closure).
It would be nice for editor to be able to close a place for a fixed period, as you can close a road.I had the case on 2 gas stations under construction closed for several months. A "temporarily closed" button or closing dates with automatic reopening would be great!
116 votes -
Allow forcing a closure to expire (instead of deleting the closure)
The WME shows now the status of all recently finished and all active closures. A deleted closure will not be visible anymore.
For that reason, we prefer to "finish" closures instead of deleting them.
It would be nice to have an option in the context menu of closures, to make the closure expire, by setting its end moment to now.113 votes
- Don't see your idea?