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.
1591 results found
-
Speed limit map error
I would insert the ability to see the speed limit map errors reported by users with the function to be enabled or disabled in the control panel.
This possibility, unfortunately, is only available for those who have access to the WME beta but it can be free for everyone.30 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.
-
Temporary Construction Zone Restriction
Per conversation on the editors discord, it would be nice to have a black and orange dashed line which would indicate construction zones in Waze. This way drivers would get an alert and know to slow down if there are any speed restrictions. In the WME app, users would be able to set these temporary restrictions up to what is allowed per their level. This would be done through restrictions field in the editor. A tab would be added in the restrictions editor to show construction zone information. For a user to set a construction zone on a segment or…
12 votes -
Input Permalink into WME Search box should take you to location
You should be able to paste a Permalink into the WME Search box and be taken to the location instead of having to rely on scripts or pasting in your browser bar and reopening the WME page completely.
6 votes -
Comment Alert
Attach a trigger to comment to create a map update request in the future.
Use for any temporary map change that needs an expiration like a road closure has.3 votes -
Ability to enter non-standard addresses in Map Editor, e.g. "11x/1"
Ability to enter non-standard addresses in Map Editor, e.g. "11x/1" currently it's not possible and those are missed completely from waze, messing up with "11x addresses missing "/1", which might be existed and completely different house, which makes things complicated
3 votes -
change/adapt default average speed assigned to a segment for itinerary calculation
Hello,
Using the script "road speed", I can see what are the average speed used for route calculation on every segment.
I'm working on the map in Rwanda, Africa. Here, the major/minor highway may sometime be unpaved road. On these road, the driving speed never exceed 20-30 kph. However, by default, the speed on these "major highway" segment asigned by waze is 60-80 kph, which induce huge difference in the ETA.
Of course, in cities or in the main roads where there is a lot of wazer traffic, this is automatically adapted thanks to the users. But in less populated…
5 votes -
More Specific Error Messages
Specific error messages are very useful, and we can use more of them.
Here are some recent cases I have run across where it would be helpful to have a more-specific error message
RPP too far from identical HN (zoom out if necessary to highlight the HN location)
RPP too far from recently-deleted HN; try again after HN update. (zoom out to highlight the former HN location)
Improper restricted turn in JB (show and highlight the specific turn arrow which is the problem). Allow the turn and try again (https://www.waze.com/forum/viewtopic.php?f=211&t=276336&p=1922955#p1922761)By: voludu2
Link to original suggestion: https://www.waze.com/forum/viewtopic.php?f=1525&t=27659144 votesHey!
Hey!
Thank you very much for this suggestion.Detailed Error messages are part of the planned idea of the WME dev team these days.
We will keep you updated with any updates
Best,
Hezi -
Allow editors to override default order in which area polygons are rendered.
Often times we find that area places intersect on the map and do not render in a way that makes sense. As an example, under the current scheme, a large water body will be drawn behind a smaller park polygon where these two types of objects are drawn together. To combat this, editors are required to either draw complex coastlines twice, or break up water objects to create smaller polygons that will be drawn on top. We could improve the appearance of the map significantly if we had some control over which objects appear in front of others. This could…
16 votesHey,
We would like to get some examples with permalinks in order to be able to check this suggestions.
Any example will be highly appreciated.
Thank you!
-
Improve ability to add pictures to places
Currently when you're in the app you please "places" and the first thing you must do is take a picture of the new place you wish to add. One feature i'd love is if you had the option to add pictures from your camera roll instead cos sometimes its rather difficult in the moment to add all these things.
Another thing is (maybe I should make a separate post about it) but right now there is no way to add photos through WME on desktop.. It would be really good if we could change that. If you're worried about spam…
7 votes -
Surfacing House Number Errors
A nice feature would be to surface the real error message from house number additions. Sometimes when there is a conflict between segments, you get a generic "there was an error" type message, but the back end call has the full details which you can see through dev tools. For example:
This segment: https://www.waze.com/en-US/editor/?env=usa&lon=-97.48797&lat=30.16312&zoom=6&segments=48240740
Conflicts with: https://www.waze.com/en-US/editor/?env=usa&lon=-94.82458&lat=29.82488&zoom=6&segments=48240740,511847520,511847562,511847579When the city is listed as "none" (No City). When adding "115" to the latter, this resulted in an error (see attached)
However, the backend error that is returned by the web request is (see attached)
There's enough in the error message there…
45 votes -
Harmonize poor-road nomenclature to "Poor roads"
Please harmonize the nomenclature Waze uses for roads that may beat up cars or get them dirty.
Currently, WME allows marking segments as "unpaved", while the companion feature in the app allows the driver to avoid "dirt". But unpaved and dirt are two different things; for example, many would consider a gravel road to be unpaved, but few would call it dirt. Meanwhile, even some paved roads have such poor surface quality that local drivers might wish to avoid them in favor of better alternatives.
Since the underlying goal is to allow drivers to avoid roads with poor surface quality,…
15 votes -
Pot holes
When waze warns of upcoming hole can it say which lane it is in
2 votes -
Help detecting unanswered UR.
WME does not sufficiently highlight unanswered URs, while editors are expected to handle unanswered URs.
URs are coloured according to their age and status (open, closed ok, closed nok).
Opened UR are coloured in yellow, becoming darker , then red, when aging.
The only way to differentiate unanswered from answered URs is the presence of a "speech ballon".
I am a Belgian editor, and we, in Belgium, believe we have invented comic strips and speech balloon, so we like speech balloons.
However, I believe speech balloon are not visible enough, and unanswered URs should have a distinct colour, perhaps blue,…6 votes -
Incluir em "Serviços" de Locais a opção: Aceita PIX
Solicitar a inclusão em Locais -> Mais Infos -> Serviços -> "Aceita PIX"
6 votes -
Simulator to test editions
Sometimes when we make changes to the map, we need to wait for it to update to see if it had the desired effect.
It would be nice to have some type of simulation in the WME and thus be able to avoid various changes until the expected result is obtained.
Because of COVID, many editors have not been able to check if the changes we made had the impact we wanted, so we had to wait for a report that warns us of the error or not.39 votes -
A map problem for a suspected closed venue
Many venues that are closed remain in the WME and become WME garbage. During the years these "garbage venues" are growing in number, and the editors do not pay attention to them.
I suggest that there will be a new map problem that will pop up when a venue was not a destination of any navigation for a year or two. If the MP is closed without deleting the venue, it will reset the time for that venue (as though it was a navigation destination).22 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. -
Types of electronic toll
As you know, if you plan a route through highways containing segments with the option “electronic toll” enabled, a time penalty will be added to the final estimated time of route. (3 minutes for each electronic toll, right?)
Here in Portugal we have 2 different types of electronic toll:
-> Type 1 - You need to reduce speed (Electronic reader) or stop (Manual ticket) to cross the toll.
-> Type 2 - You don’t need to reduce speed or stop to cross the toll.So there should be a time penalty on type 1 but not on type 2, but…
22 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.
-
Events entry for multiple dates but basic information is the same for quicker creation
I spent quite a bit of time entering Events today for concerts that happen on every Friday in the summer. Basically the only information that was different was the dates and the road closures were also the same except for the dates. This would be a great time saver if it could enter all the dates and times in separate sections and created separate Events.
6 votes -
Record node RTCs in the edit history
Segment RTCs are recorded in the segment edit history, allowing editors to easily check along a route to see if a now-expired closure may have been the reason for a routing problem flagged up via a UR.
Now that we have the ability to also mark nodes as open/closed in order to allow/deny routing across a closure, having node closure states recorded in the history is also important, so that we can deal with URs related to routing problems along those cross routes as well.
ideally we'd be able to see in the history for a given segment if either…
13 votes
- Don't see your idea?