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.
75 results found
-
Accept and reject individual suggestions in PUR
Problem summary:
The workflow for place update requests (PUR) is clunky and confusing. We can reject or approve only - yet two or three of the five suggestions might be useful while the others not. After clicking on a PUR for the first time, it is also unclear what is new, changed or deleted.
User story:
I clicked on a PUR pending changes for an existing venue and this is what was displayed:
https://i.imgur.com/CWTE6Jl.png
- It is not apparent what the proposed changes are. I do not know if everything listed is new, changed (e.g. typo fixed) or a proposed deletion.
- …
332 votes -
Allow Junction Boxes and Paths to exist together
When editing, there are many times that you need to restrict a turn that would require the use of a Junction Box (JB) to accomplish. The issue is that if a different route, that does not fit in the JB, needs to have Paths set up, we have to choose one or the other.
We need the ability to set Paths through a JB
208 votesGreat timing! We’re currently working on allowing Junction Boxes and Paths to exist together. Keep an eye out for updates on the WME.
-
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 votesThanks all! We're researching this further and will come back with follow up questions shortly.
-
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-tab161 votesThanks for submitting a suggestion! Closures will likely not be part of the Issue Tracker but we are looking into other solutions.
-
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 -
"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.
108 votesWe are looking into this suggestion's feasability and will update when we have some answers.
-
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 -
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!
101 votes -
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 -
Incorporate Place Interface Enhancements Script RPP Editing Options
The Place Interface Enhancements ("PIE") Script provided an easy way to add RPP's by offering to auto-populate the 'street name' field with values from the nearest street. Optionally, one could have it ignore the checking for the street name from nearby PLRs and PRs:
(Options):
- Use street name from closest segment
- Use city name from closest segment
- When the primary is "No city" look for an alt city
- Ignore PLRs & unnamed PR when using closest segment's name and cityThe script stopped working after an update to WME earlier this year. It would be an…
96 votes -
Automatic UR handling
An update request (UR) without any text can be automatically handled:
1. There will be an automatic system response to the UR that will invite the user to add more details to his request in the WME (include a link) or in the forum (include a link to the local community forum). The user will get an e-mail as fr any other manual response.- Every such UR that has no more responses (other than the automatic one) will be closed as "not identified" after 7 days.
That automatic handling will save a lot of time wasted by area managers. A…
92 votes -
Move Previous Build Button
The small bar with tile build information moves and sometimes covers elements as different parts of WME are accessed. With the exception of my phone in landscape orientation, there seems to be an excessive amount of extra space on the tile bar. My suggestion is to move it to the tile bar on the left, near the settings button.
90 votes -
Show Entry Point Name changes in POI history and PUR
I noticed that Changes to the name of Entry Points of places won't show up in the POI history, it simply says "Updated Entry Points".
This also affects PURs, since you don't know what the Wazer/Editor is suggesting until you accept it.
I reckon those requests mostly get declined since there's no visible change.My suggestion is to add those name changes to the history and PURs.
87 votesWe are looking to feasability for this suggestion and will update when we have some answers.
-
Save all native WME client settings on server side
Base WME client settings are only saved to the local machine, as every time you log in somewhere on a new workstation, you have to go restore your preferences such as Environment, Language, Imperial/Metric, Compact Mode, Transparent Arrows, etc.
However, with the implementation of Issue Tracker, saved filter settings are immediately accessible upon a new login, proving that WME user settings can be saved at the server end.
Please save all native WME settings on the server side so that they are already in place when an existing editor logs in on a new workstation for the first time.
84 votesGreat timing! We're currently working on making your preferences accessible when logging in on a different device. Keep an eye out for updates on the WME.
-
Allow closure creation in "Current live map/snapshot" mode
At the moment, it is no longer possible to add a closure to a segment you have removed or split up, even though this segment is still being used live in the app. If it were possible to add closures in the snapshot mode (recently renamed to "Current live map"), even with a strict time limit, our life would become a lot easier during road works.
At the moment, we need to apply segment restrictions, wait for the map update, remove the closure, make our changes, wait for the map update and then probably add new closures. If we can…
77 votes -
School Zones Speed limit 40km 2:30-4pm weekdays
We need to know the school zones and change the speed limit around these times near school which the time is 2:30-4:00 pm Monday to Friday only around school zones this feature should be added in so people like my self don’t get confused with the on screen speedometer
74 votesThanks for the suggestion! We're currently looking into ways to incorporate this idea into a feature. We'll keep you posted as this develops!
-
Expand character limit for the name of an MTE
Currently the character limit for the name of an MTE is 25. Common MTE names often come very close or exceed 25 characters, such as "Electric Ave Bridge Replacement" (31 characters). It would be helpful to have the character count increased, possibly by another 10-20 or more.
73 votesGreat timing! We’re currently working on expanding the character limit for the name of an MTE. Keep an eye out for updates on the WME.
-
Add map comments to the "All issues" section
It would be great to have all map comments in one place, and the all issues sections seems perfect for this. Include some filters like comment type (point, area), comment expiration date, comment creator (me, other), etc.
73 votesGreat timing! We’re currently working on it. Keep an eye out for updates on the WME.
-
Show only active closures
In the layers menu, under closures, there should be an "Only active" option. When this is enabled, only active closures will be shown in the WME. This would make the WME look "cleaner" and uncluttered.
72 votes -
Draw City Boundaries More Accurately
Currently City Boundary layers are not drawn precisely, which can result in the wrong city name being displayed to users in the app. I continue to get URs on this regularly in my area.
This issue seems to be seen commonly when cities are divided by an undulating river. Users should not be shown that they are in a city that they are not in. The system to "draw" the city layer should rely on more data points to draw a more accurate city layer. I will attach screenshots to show this more clearly.https://www.waze.com/en-US/editor?env=usa&lon=-122.59338&lat=49.19848&zoom=2
https://imgur.com/V9kFFp4
Incorrect city "Maple Ridge"…69 votes
- Don't see your idea?