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.
1266 results found
-
Editing fuel types for each Gaz station in WME
It would be nice if the types of fuel at Gas stations could be created, selected and sorted for each specific Gas station when editing directly in the WME.
The main thing is that for each Gas station it was possible to create its own set of fuel types.
For example:
for one - Gas, 92, 95, Diesel
for the other - 92, 95, 98, Diesel
etc.Because all Gas stations are Different!!!
92 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.
-
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.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.
-
Update UR editor reply email
Below is the email Waze currently sends when an editor replies to a UR reporter:
From: Waze Map Editor no-reply@waze.com
Subject: A comment on a map issue you reportedHi <Reporter Username>,
You received a comment on the map issue you reported, from <Date> on <Road Name>, <City> - “<UR Description>”. An editor from the Waze mapping community wants to solve the problem, but needs some more information.
<Editor Username> on <Date/Time>:
<Editor Message>
You can reply using the Waze mobile app, or <URL to UR> in the Waze map editor.
Want to join the map editing community? Here’s how…
92 votesWe plan to work on updating UR editor reply email in the near future.
-
Incorporate the Top "X" scripts into native WME
Given the recent injection of malicious code into scripts used by the majority of experienced editors
https://www.waze.com/discuss/t/urgent-two-scripts-were-compromised-on-feb-1-please-read-if-you-use-scripts/365499
I strongly urge Waze relook at the Top "X" scripts that were identified several years ago and incorporate them into native WME.These scripts serve several functions
1) Increase navigation precision: JAI (mentioned above) is absolutely needed for experienced editors to determine the angles and thus, the turn announcements when one moves from one segment to the next
2) Speed up editor time: ColorSpeed (also mentioned above) and others, like LaneTools or Road Shield Assistant, provide a quick visual on the overall WME…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.
-
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.
90 votesWe are looking to feasability for this suggestion and will update when we have some answers.
-
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 -
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.
-
Sunrise/sunset vs absolute times for restrictions
Some roads have driving restrictions based on the local sunrise/sunset times, which are difficult to map even somewhat accurately as a series of consecutive restrictions with absolute start/end times.
Being able to set a single year-round restriction using a "sunrise" or "sunset" option to set the start/end times, and leaving it up to the routing server to determine what the actual start/end times are for each restriction based on the current date and coordinates of the restricted segments, could therefore be useful.
by Twister-UK
Link to the original suggestion: https://www.waze.com/forum/viewtopic.php?f=1525&t=30015385 votesHey,
We have looked at this suggestion, and in order to make some decisions about it, would like to kindly ask you to provide us with more data about it.
Please share some examples for when and where this restrictions apply? (use cases)
And any country you know relevant for it.
Thanks!
-
Two-Way Traffic Ahead Permanent Hazard
This permanent hazard would warn users that the road they are travelling on transitions from one-way to two-way traffic. This would not be used for sections of road where traffic gives way to oncoming traffic temporarily (see the suggestion for Narrow Road Permanent Hazard), but instead for roads that are one-way only for a distance and suddenly transition to two-way, as to warn the user that there will be oncoming traffic.
• Ex 1: Drivers heading south on the one-way must be in the right lane to continue onto the two-way road, where traffic from the opposing two-way direction does…
83 votes -
Segment restriction type that prompts user to confirm access (gates)
Currently we create gates using PR segments. However, this rarely has the intended effect. Those with access (say a gated community) don't get a route through a gate this is most convenient or worse, if all entrances are gated, then restriction is meaningless other than to ensure it's not a through-way.
I'm suggesting a segment restriction type that would generate a pop-up at start-state of a route asking if the user has access to a segment (gate) if that's the shortest route. Ideally, Waze would remember that for that user in the future. This could potentially be used for restricted…
81 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
-
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=080 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"…79 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.
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.
-
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.
-
House number editing no longer shows reason for HN error
With the recently released change to how we edit house numbers, we no longer see information of why there is a problem (wrong side, already exists, etc). This functionality needs to be added back, or the actual error needs to be added to the error message, so we understand what the issue is.
Details were provided in this beta post.
https://www.waze.com/discuss/t/a-faster-way-to-add-house-numbers-in-wme-for-segments/358469/2077 votes -
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.
76 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.
76 votesGreat timing! We’re currently working on it. Keep an eye out for updates on the WME.
- Don't see your idea?