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.
1478 results found
-
No feedback provided if permalink is unable to select items
Currently there is no feedback given if one or more items are not selected when opening a permalink (i.e segments, places, URs, etc.).
For instance, I have a document with PLs of segments that are always closed during events (such as stadiums). If a segment ID is changed and therefore no longer linked in the PL, I have no way of easily knowing this.
Please consider providing some sort of warning if WME is unable to locate all the linked items.
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 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.
-
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
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.
-
Selection of the period of GPS history
As the editor, I would like to have an impact on the length of the GPS track history.
Sometimes you need a short history to catch events, and sometimes as long as possible to check the traffic density or the correctness of the road.
38 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.
-
Automatic flag on unused places
Many places in the WME are not used for various reasons: The place was closed or moved, the place was created for an event that has passed, the place was wrongly created, the place exists but nobody uses it for routing. During the years, the number of such "garbage" places is growing, and will continue to grow forever.
There must be some way of cleaning these places from the map.
It is suggested that every place (excluding RPP and natural features) that nobody set it as a destination for 15 months, will be automatically flagged, with a reason that the…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.
-
"All Issues" should have an editable area & level restricted (permissional area) filter.
I'm liking the new "All Issues" section but it needs another filter where I can filter out all the stuff I can't edit due to permissions such as areas outside my editable areas and level restricted edits.
I'm currently a L1 and want to move up higher but not having the ability to only see what I can edit, it's time consuming going through them all.
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.
-
Junction box, add ability to demand a pass or mark as private for specific route
Junction box is still evolving so it would be good to add one more feature to it. We have situations where driving through a longer section of road is only permitted with certain conditions but driving to an address in between or to drive across the affected street from different direction is always allowed.
Thinking about a possibility that those conditions could be set as a pass and then apply it only to specific route in junction box. This could probably also be used in a way that you could set a specific route to be private road in routing,…
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.
-
Ability to add more than 4 fields in the Address box
Please give us the ability to create more than 4 address fields. and make it so that editors can set custom number of fields according to their own area.
Right now waze has four boxes for address: Street, City, State, Country.
Not all addresses in the world work quite exactly like this so please
I would like to suggest waze allow users to create custom fields and name them and Country coordinators set the limit of fields in each city and country.
So we can have many fields like:
Street
Sector
Phase
Town
City
District
State
etc.
I tried looking…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.
-
Mark police/traffic issues on OTHER side of road
Today one can only mark police, traffic issues on the same side (direction of travel) of traffic, Provide the option to help others know when police, accident, traffic issues are on the other side of the road to aid the opposite traffic know about it since it is known before they get there.
36 votes -
Add more keyboard shortcut options for drawing Hazards
Right now, we've got a long list of Permanent Hazards available to map, but only two (Speed bump and Speed camera) have assigned keyboard shortcuts.
Having more keyboard shortcuts would be super helpful for productivity. Personally, I think the default shortcut for each hazard could be blank/none, so users can set their own preferred keys for the hazards they use most often.
Link to the forum discussion: https://www.waze.com/discuss/t/new-feature-alert-permanent-hazards-now-available-in-wme-all-environments/350757/36
36 votesGreat timing! We’re currently working on adding more keyboard shortcuts. Keep an eye out for updates on the WME.
-
Show stop points in the House Numbers layer
The House Numbers layer currently displays only the location of the HN, but not the stop point on the related segment. In HN editing mode, when you select the HN, the stop point also becomes visible, with a dotted line from the HN to the stop point. Suggestion is to display the stop point and the dotted line as part of the House Numbers layer, even when not in HN editing mode. (This might either be visible only at a high-enough zoom level, such as 18, or be an option that the user could enable from the layers menu.)
36 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 layer should disable
With the new house number editing flow, once you edit a house number and leave house number editing, the House Number layer remains active. The layer should return to disabled if it was disabled before editing the house number.
36 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 - add filter by Language
Now that the Language setting is attached to URs, it would be very beneficial in terms of efficiency to have the ability to filter by language in the Issue Tracker.
The filter should allow editors to select one or more languages and either include or exclude the selection.
For example:
1. include: English + French + Greek
2. exclude: Greek35 votesGreat timing! We’re currently working on adding filter by language. Keep an eye out for updates on the WME.
-
Switch editor profile ROW/IL/NA
When an editor makes changes and we want to see what was done (usually flagged in the high volume report), senior editors will often check the editor profile. If that editor is from another environment (ROW visitor to NA, etc), and their last edits were in the home environment, we have no way to see what edits were made in our environment.
Please add an ability to change the edit history per environment. This could be a drop down on the environment currently displayed, or adding an environment option to the URL (env=usa).
35 votes -
Allow closure overlapping
Hi,
very often I am notified of an event that needs closure after it started, then I go to select the many segments that must be closed.
When I want to add a proper closure on them, there are already dozen of closure made by drivers and I have to remove all of them one by one before adding mine. That's annoying because it is slow, and sometimes new closure are made by drivers while I am removing them :And overlapping closure are not a real problem because when it is done by waze app it happens often so…
35 votesHey!
Thank you for the suggestion.
In order to check this suggestion, we would like you to share some more examples with us.
We aim to get the understanding of how often this is an issue.Best,
Hezi. -
Event based restrictions
Sometimes for major events and after major emergencies (wildfires, hurricanes, flooding) there are roads that are open to residents but not to the general public.
I would suggest something that can be applied like a real time closure, but acts more like setting the road to private so it allows routing onto the segment but not through the segment.
This may be related to Permanent Hazards instead, but however it is implemented it should not require a tile update.
35 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.
-
Fill place data with linked Google place data if those are blank in WME
I often create a place and link Google place to it first to see/verify the address etc. Feels like very dumb double work when at least the name/city/address is in that linked Google place already, it would be very nice if WME could pull those from that entry when linking it and autofill those IF the corresponding fields are empty in place properties. And of course those must remain editable after that also.
34 votes -
Add Kurdish Sorani Language
Please add Kurdish Sorani language support to Waze to accommodate the millions of users from Kurdistan.
34 votes -
Update current MAP PROBLEMS scanning to disconnected nodes
It is becoming increasingly difficult to identify two segments that are very close to each other but not connected. Sometimes they even sit on top but until you click them, you don't realise that they are not connected.
This leads to many routing issues and is not identified till there is a UR or a chance visual by an editor.
Validator script and Checker.Waze help with this but you have to be at the location editing. It would be really nice if this "disconnected segments with nodes within 5 metres of each other" could be natively searched by Waze scanner…
34 votesGreat timing! We’re currently working on it. Keep an eye out for updates on the WME.
-
Add checkboxes to flag unusable/inaccessible gas stations
Editors occasionally find angry URs from drivers who couldn't use or reach stations listed in their gas-station finder. For example, a substantial fraction of drivers -- the majority? -- cannot use non-gasoline fuel, cardlocked stations, military-only stations, or private stations located inside secure installations. Many cannot use members-only stations, such as Costco in the US.
One way to prevent these misroutings would be to add checkboxes for limited-audience gas stations, for example as follows. The app could then let drivers opt in as desired.
In WME, the list might read:
- Military only
- Members only
- Non-gasoline fuels only…34 votes
- Don't see your idea?