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.
11 results found
-
Automatically clear the street city field when its value is "None"
Currently, when opening the street name editing panel, the input fields get populated with the string "None" (localized), which requires editor to delete the text manually before setting a new name.
When the street has a "none" street or city name, these fields should be empty (or, at most, with a "none" placeholder that disappears when clicked).
If the user does not change them, consider them as being "none".
168 votes -
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.
106 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!
-
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!
-
Make Map Comments selectable even when behind Area Places
Please allow editors to select Map Comments that located amidst Area Places.
At present, at least in vanilla WME, neither Map Comment points nor areas are selectable if they are amidst an Area Place. The Places layer has to be turned off (or the obstructing place moved or removed) for the Map Comment to be accessible.
Map Comments are among the most useful things for novice editors to view, but such editors may not be aware of the workarounds required to view Map Comments that are amidst Area Places.
69 votesIf we change the order, does it make sense that a place under the map comment won’t be selectable?
-
Parking Lot Roads - Differentiate Aisles & Roads
It would be nice to have a way of setting PLRs to be able to use speed data (versus a set speed) while having the same penalty settings (i.e., the road has no penalty between the two PLR settings). This would be useful in large parking lots area such as sporting venues and malls, where set speed is fine for aisles and minor roads but speed data would be useful for finding the fastest entrance/exit on it's higher volume roads. With the set PLR speed, you are almost always getting the shortest route of PLRs, even if that lot exit…
53 votesHey !
Can you please share some more details and examples for this issue which you would like to address in this suggestion?
This will help us to better understand what will be the best solution.Thank you
-
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…
36 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. -
27 votes
Thank you for reaching out. We don't have enough details to thoroughly investigate this idea so we will close it now. If this idea is still relevant, please submit it again and include all relevant details.
-
Remove RS update location on https://www.waze.com/fr/user/editor/*
Since RS are in wme, on the editor page those edition are link to 0,0 position.
Would it be possible to improve the visualization of these editions because it affects the readability of the map?20 votesPlease provide more information, including screenshots to illustrate the issue.
-
Setting "Repeat every year" on an existing restriction
Now that we have the "Repeat every year" checkbox for restrictions, it'd be useful if we could tick this for existing restrictions to turn them into repeating ones, without the need to then also edit the start/end dates to avoid the "Start date can not be in the past" error.
e.g. a segment has an existing restriction set for 5th September 2019 to 20th October 2019, and the restriction is one that ought to be set as recurring.
The preferred workflow would be for the editor to simply tick the "Repeat every year" checkbox and save, without any other changes…
19 votesHey!
Thank you for this suggestion.
We want to kindly ask you to share with us cases in which you believe this development can be at your assistance.This will help us to get a decision about this suggestion.
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…
13 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!
-
Address localization
lease allow localization of address field just as it is done in search results, so it would be possible to have "%{street} %{housenumber}" instead of "%{housenumber} %{street}" for some languages.
by matsalka
Link to original suggestion: https://www.waze.com/forum/viewtopic.php?f=1525&t=2810560 votesHey!
Thank you for this suggestion, We will be happy to hear more on what will be the added value of this suggestion, if the info is presented in the correct way today already.
Thanks,
Hezi
- Don't see your idea?