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.
120 results found
-
Allow combining chargers when merging EVCS
When merging EVCS, give users the option to include both sets of chargers. For some reason, some networks (ahem, ChargePoint) sometimes list multiple charger sites in the same parking lot or garage. If we try to merge them, we have to select one or the other set of chargers. Please add an option to include both sets.
47 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.
-
Polygons in WME should just be a thick border instead of a full fill
To allow for easier interaction with polygons and segments & places inside polygons, change the polygons to be a thick border instead of it being a filled polygon.
With the expansion of features that include many polygons beyond just places (JBs, Permanent Hazards, Natural features, etc), it would make it much easier to work with these shapes.OpenStreetMap does this very well.
106 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.
-
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.
-
Filter GPS tracks by date
Filter GPS tracks by date
144 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.
-
Enable merging residential places
Today we cannot directly merge two residential places (or merge a residential place into a public one). There is a workaround: convert residential places to public ones, save them, merge, then convert back to residential if needed. Why not allow merging the direct way?
56 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.
-
Parking lot type (motorcycles-only, cars-only, both)
It's very common, at least in Colombia, parking lots only for motorcycles and it's really dissapointing to arrive at a parking lot suggested by Waze, and realize that it's a motorcycle-only parking lot and you're driving a car.
Please add a new property in WME to choose the type of parking lot: motorcycles-only, cars-only, or both, and add a new feature in app to filter by parking lot type.54 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.
-
Recategorizing UR's when solving
Add a feature to WME to recategorize the Solved UR's when closing those. This would give Waze a true insight of what reports are really needed and vice versa, what are rare and could actually just be within General Error category etc. Based on my research of all Solved UR's in Finland for last 3 months only about 50% were in right category.
In my opinion this would help to reduce and refocus UR categories to better match with reality which in turn helps users when they are reporting meaning less UR's with wrong category -> Better data and better…
42 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/change the error message
Improve/change the error message when low level editors tries to delete the house number on streets with higher locks. Now we got "Error saving, try later" message. It gives, to editor, no idea of what the problem is, and the user may thinks that's a WME bug. By changing this message, it will give to editor and mentor/higher levels editor's more information to understand where the problem lies.
40 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…
125 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-tab166 votes -
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.
130 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.
-
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.
-
Event edit mode in WME
During Event Mode you only can select segments and you will not be able to edit them. Only RTCs are possible.
You also can select one previous entered event (MTE) --> this MTE will be preselected for RTCs during event mode. Also the name of the RTC will be the same the whole time.
Benefits: You only have to selects the segments, enter date & time and therefore save a lot of time. You also won't be able accidentally to move segments, nodes or POIs.
Also GPS, my area, POI, issue ans script layer will be deselected automatically (as an…50 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.
-
Street Parking
We have parking lot roads that cover most parking situations, but there's not a great mechanism for handling street parking on public streets where it doesn't make sense to mark a road as a parking lot road. Examples: Many residential neighborhoods, many downtown areas.
Suggestion is to add a flag to all driveable road types except freeway and PLR/PR to indicate "street parking is allowed", along with pricing information similar to how we handle parking lot areas. This could be part of the next phase of the parking project.
27 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 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.
-
More informative options for the GPS layer colours (colour by speed or age)
Currently, the arrows on the GPS layer are coloured by direction. It would be useful for editors to be able to choose between that and at least two other options: colour by speed, to help editors understand historical traffic patterns and troubleshoot routing decisions; and colour by age, to help editors spot roads that may have been recently realigned or closed.
52 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 votes -
Make RPPs a bright pink
Change the colour of the RPP from a camouflaged dusky pink (same shade used to literally camouflage reconnaissance Spitfires in WWII) to a bright pink like #fa0584 to make it more visible in urban backgrounds.
30 votes -
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
- Don't see your idea?