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.
1140 results found
-
Filter GPS tracks by date
Filter GPS tracks by date
138 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.
-
Reorder custom turn instruction elements
When editing custom turn instructions, if an element (shield or free text) should be inserted before existing elements, then the existing elements must be deleted. There is no way to create new elements in front of existing elements.
Please add the ability to reorder elements. This way we could create new elements and then move them to the front if needed. This would save many clicks and retyping.
137 votesGreat timing! We’re currently working on reordering custom turn instruction elements. Keep an eye out for updates on the WME.
-
Addition of a road type: Dangerous or Unsafe road
It is suggested to add one more road type: Dangerous or Unsafe road. This type will be used for example when it is a very steep or winding or bumpy road, or a road on the edge of an abyss.
The time it takes to pass the road in such cases is not the only parameter that counts.
It is suggested that the "penalty" for passing such a road will be proportional to its length. For example 1 minute for every 100m.136 votes -
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…127 votesWe plan to work on creating an issue tracker for UR in the near future.
-
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…125 votes -
Testing routes in waze map editor
I would like to test a route, from A to B, in the map editor to check if the optimal route is chosen and find the reason why not. It could be easier to find that waze leads astray which happened to me this summer. Waze tried to lead me against a one way street.
121 votesGreat thinking! We’ll share with the team; they’re always interested in new feature ideas.
-
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…
119 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.
116 votesWe plan to work on this in the near future.
-
Keep previous history for merged/split segments
Hello!
I think it would be very helpful if segment history included data from previous "iterations" of that segment, when a segment was created by merge or split.
Right now, the history starts anew any time there is a new segment ID, but I would imagine it should be fairly trivial to develop a backend mechanism that, any time a segment is split or merged, merges the history of the previous segment ID into the new segment's history.
This is useful not only diagnostically but also to catch cheaters on the map, who today can split and merge segments at…
116 votesHey!
Thank you very much for this great suggestion.
It was added to our backlog to try and see the possibility to implement it.Please note there is no ETA for it yet.
Best,
Hezi -
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).
114 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.
111 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 -
External Providers Search Displays Too Little Information
The + Add linked Google place functionality on venues is incredibly difficult to use. When you search, the Waze-prioritized white space leaves almost no room for the search results to actually contain usable data. As it is now, I often have to guess as to which place it might be and often have to repeat the process making editing places very inefficient. Please expand the information displayed here so that this functionality is actually useful to finding and linking Google places. The whole name of a place should appear along with a complete address.
108 votesThank you for submitting this suggestion!
At the moment, when you hover over a place, it shows its complete address. Is this something that solves the original issue you mentioned?
If not, we would love to hear from you on how it can be improved.
Thank you!
-
Add manual lock level to Junction Boxes
Currently, Junction Boxes do not have a controllable lock level. From the look of it, the lock level displayed is the minimum level for the country that can edit a JB. For example, in the UK only L5+ editors can edit JBs, so all JBs show auto(5) in WME.
With various changes that HQ are making into WME and the app, it seems to me that they expect a massive increase in JBs over time. U-turn prevention, junction modification for Falcon are just some of the things for which the answer often seems to be "use a JB".
I'm not…
108 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.105 votes -
"Sharp" Turn Instruction
Create a "sharp" turn instruction. Similar to "keep" instructions being an angle <44 degrees, a sharp turn instruction could be one greater than 135 degrees but less than 170 (which would be u-turn). Other apps already have this instruction and it would greatly complement lane guidance visuals that use the sharp left/right turn symbol. Alternatively, it could be provided only as a TIO for use only where the community finds appropriate.
105 votesWe are looking into this suggestion's feasability and will update when we have some answers.
-
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…
101 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 Attribute Request] Treat 2 Way as Divided
I would like to have the ability to draw a single 2-way segment but be able to mark it as divided so it does not say you have arrived until on correct side of road. Sometimes you may have a segment that may not really need to be divided into 2 One-Way segments but if you want routing to offer the correct directions you would have to divide the segments. In my picture below, the red line shows what Waze currently does (it says you have arrived as you pass the house) The green line shows what it should be…
100 votesHey,
This topic may not answered as part of the suggestion up until now, but it has been discussed multiple times across the relevant teams.
We will keep on updating with any news
Best,
Hezi -
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.
-
Move GPS layer below segments layer
A way to move the GPS layer below segments layer allowing easier checking segment directions / selecting / adjusting based on GPS layer. Like WME Fix UI Memorial script dues it but native to WME :)
99 votes
- Don't see your idea?