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.
36 results found
-
Disable and restore to default of the issue tracker filters
Please add two important features to the issue tracker:
1. Temporarily disable all filters in the issue tracker (show all URs, PURs etc.), without changing the filters, so that the editor can later on enable the filters in order to have the defined filters without the need to redefine them.
2. Restore the issue tracker to its default state, so that all the previously changed filters will be returned to their default state.
These features will be very useful.41 votes -
POI's moving distance
At the moment moving a POI have a distance limitation (2km I belive?) Sometimes when a business changes phisical place to another place, like 10km away, we need to move the POI like 2km, save, move again, save again...
It makes no sense. Please remove it or allow us to move POIs further.
Thank you.
40 votes -
Add a new UR Issue filter "Last comment by" - "Not Me"
Please add a new UR filter in the "Last comment by" drop-down - called "Not me".
In conjunction with the "Comment by me" filter, this will then allow me to see all URs that I have commented on in the past, but I wasn't the last person to reply. This will include the reporter and other editors.
Currently, if I select Reporter, I cannot see URs that other editors have last commented on. If I select All, I will see them, but also all of my reports that I was the last commenter on.
39 votes -
Automatically select road name text when editing
In the latest version of WME, when you open up the "edit" dialog to adjust a street name, and then click on the text box for "name" or "city", it drops the cursor at the end of the box. It would be nice if the existing text in the box is highlighted so you don't have to manually select the text to clear the box when editing the name of the street or the city name
39 votes -
Add a keyboard shortcut to toggle the Issues Layer
The new issues layer is not linked with a keyboard shortcut to toggle it on/off, at it is the case for other layers like roads, place, closure,....
This would really help, especially for koifish suggestion, so we can quickly toggle on/off the suggestion and see what's under it on the image, or even if there is not a already existing segment hidden by suggestion.
33 votes -
Add checkboxes to flag unusable/inaccessible gas stations
Editors occasionally find angry URs from drivers who couldn't use or reach stations listed in their gas-station finder. For example, a substantial fraction of drivers -- the majority? -- cannot use non-gasoline fuel, cardlocked stations, military-only stations, or private stations located inside secure installations. Many cannot use members-only stations, such as Costco in the US.
One way to prevent these misroutings would be to add checkboxes for limited-audience gas stations, for example as follows. The app could then let drivers opt in as desired.
In WME, the list might read:
- Military only
- Members only
- Non-gasoline fuels only…33 votes -
Segregating effective and suggested closures
WME shows two kinds of closures:
- effective closures, affecting routing and visible on livemap
- suggested closures, non affecting routing and not visible on livemap. Those suggested closures always have a duration equal to a multiple of 24 hours, starting and ending at the same time of day (on different days, obviously), and are usually created by editors having a layer lower than 3. Those suggested closures result from closure reports made from the app.
The WME displays both kind of closures using exact same visuals: it is necessary to open and examine the closure, to determine if it…32 votes -
Add keyboard shortcut for issue resolution buttons
Please add keyboard shortcuts for the Green and Grey buttons ("Not Identified" and "Solved" or their equivalents) options within URs/PURs/MPs.
30 votes -
Do not move my map somewhere else after an edit
Hi,
when editing from the feed (closing MP, UR), after saving WME moves to a random place where it thinks there are other UR I can solve. It is extremely annoying. When editing I save often because of various save bugs, and as soon as I saved it moves somewhere else and I cannot find where I was editing to finish the job.
Same problem when saving, if Waze thinks there is a problem it moves my map to where it thinks the problem is, and if it is a long road, it happens often that the road is offscreen.…24 votesHey!
Thank you very much for this great suggestion.
As we believe this will be solved with a release of related features, we added to our backlog to track and make sure it was solved.Best,
Hezi -
RTC : ability to add them on current tiles
Hi,
the real time closure have a problem :We put them in WME and WME validates them according to their current state in database. But they apply on livemap.
Imagine I have a street that is A->B. Then they decide to reverse it. So it is now saved B->A.
In WME I have B->A
In livemap I still have A->B until tiles update.To avoid routing people A->B, it would be nice to add a closure, but WME refuse since it thinks the road is in opposite direction.
It would be nice if WME could accept it by really…
20 votesHey!
Thank you very much for this great suggestion.
It was added to our backlog to try and see the possibility to implement it.Please note there is no ETA for it yet.
Best,
Hezi -
Show "Hidden" external providers like Yext
Show that this data exists, so that editors will be more likely to merge than to delete.
When new place points are added as part of a large upload from Yext or some other advertising aggregator, many editors will be likely to reject the new-place PURs because an already perfect place already exists.
If they were aware that there was some other important information in the PUR, then they would be much more likely to accept the PUR.
The back end data script reveals the existence of this data in places. But I don't think it makes sense to depend…
13 votesHey!
Thank you very much for this great suggestion.
It was added to our backlog to try and see the possibility to implement it when we will next use external providers.
Please note there is no ETA for it yet.
Best,
Hezi -
WME frontend should show backend errors
Hi,
when saving, if the backend fails, it returns a message. But often they are not localized, and in that case we get a generic
"Please try again later" which is useless because in most case the problem will not solve and the only solution is to cancel all edits.
Here is a list of messages that are not localized and need to be displayed (maybe not exactly in the same form, but at least do not tell the user to try again if it is impossible that it works.Invalid street 0 was set for venue ID -100
Missmatch…11 votesHey!
Thank you very much for this great suggestion.
It was added to our backlog to try and see the possibility to implement it.Please note there is no ETA for it yet.
Best,
Hezi -
Better history for place update
Hey,
in place edit history, it would be nice to have more details on PUR : the only status is accepted or rejected.
Maybe it is not easy to tell what photo was refused or a refused change name, but it would be nice to know what was the updated fields (was it about adding or removing a photo, rename the venue).by kpouer
Link to original suggestion: https://www.waze.com/forum/viewtopic.php?f=1525&t=2840456 votesHey!
Thank you very much for this great suggestion.
It was added to our backlog to try and see the possibility to implement it.Please note there is no ETA for it yet.
Best,
Hezi -
Show RPP PUR's on feed list
There is no privacy issue involved here.
There's simply a pin in the map, among many others, but I can't find them like any others, just because category is "residential"
The privacy issues are solved by the already omitted creator/updater of the place. By not showing them, you are simply making it harder for the PUR be moderated, as we have to scan the map or rely on scripts to do that.
So, plainly: RPP PUR's should be shown in feed list just as any other PUR.
OBS: Previous discussion took place here: https://www.waze.com/forum/viewtopic.php?f=211&t=249211&p=1774596#p1774596
By: biuick84
Link to original suggestion: …3 votesHey!
Thank you very much for this great suggestion.
It was added to our backlog to try and see the possibility to implement it.Please note there is no ETA for it yet.
Best,
Hezi -
New Place Address
I'm not sure if it's a minor-bug or intended, but I ask you to take a look:
Issue regarding Map Editor Beta and Production.
:arrow: When you find a new place waiting for approval, if you click on the red arrow everything runs smooth, but if you feel the need to click on the yellow arrow to check what's that place is about before approving it (sometimes you can't tell just by the name title), notice it isn't possible to change the address... well maybe it's ok at this point before approving it.
(attachment 1)
After you Approve you can't…
0 votesHey!
Thank you very much for this great suggestion.
It was added to our backlog to try and see the possibility to implement it.Please note there is no ETA for it yet.
Best,
Hezi -
Improvements in segment selection for road closures
Sometimes it's necessary to select multiple segments to perform a road closure either for MTE or for a conventional closure. After you have several segments selected, you accidentally select a node and all work is lost (the section disappears). I suggest making a modification that prevents the disappearance of the selection of these segments and notifies the editor that you selected a node and it will not be possible to make the respective closure (before or at the moment of trying to save). Obviously the idea is to give you the opportunity to remove the node from the selection and…
0 votesHey!
Thank you very much for this great suggestion.
It was added to our backlog to try and see the possibility to implement it.Please note there is no ETA for it yet.
Best,
Hezi
- Don't see your idea?