Currently, the WME only allows assigning 1 road shield to the primary name.
This has a lot of limitations:

• The PN must be unique inside its state


• If a road has a local name, a Road Shield can only be assigned to the entire road (or the segments must be renamed).

It would be good to be able to assign 1 Road Shields for each alternative name, too (which is even already supported by the data model).

The Client, could then:
- randomly pick one road shield to show for that segment (for streets with multiple RS)
- must also look in ANs for a roadshield, as PNs may not have one.

More details here (WME beta only): https://www.waze.com/forum/viewtopic.php?f=211&t=314572&p=2131205#p2131205

I noticed that Waze doesn't approach bilingual countries just like GMM does.
For example, in GMM, we can write multiple names for the same road in 2 different languages and based on the user's current phone language chosen, the map changes accordingly.
Unfortunately that doesn't happen in Waze, we are stuck in 1 language only, even if we add "Alternative" name.

Here in Kuwait, we use both Arabic and English (Even street signs are written in both Arabic and English) , in Google Maps we are having no problems since most of the roads in the map are written in both Arabic and English. But in Waze, it is way different.

This is causing problems since most of the locals here prefer the map in Arabic, but also there are people who use the map in English.

My suggestion is:
In WME, when selecting a segment, we should have at least 2 fields to name the selected segment, there also has to be a drop-down menu to choose the wanted language.
The user's map should display the correct language based on the user's language settings in his/her phone.

User Reports (URs) come in by the truckload. Despite a message from an investigating editor, only 10% of URs will receive a reply. This represents a significant amount of time by editors, particularly senior editors managing large areas, to the manual handling of individual URs. Since 90% of the URs result in the same process, help us streamline and automated it so we can focus our valuable time on productive investigations and edits that will value add to Waze.

I propose an additional tick box under "Follow conversation" that says along the lines "Auto reminder and mark as not identified."

When ticked:

• and a user replies, the auto remind and close is disactivated


• and a user does not reply, the user is automatically sent a reminder message after 4 days of the last editor reply, and after 7 days, the UR is automatically marked "not identified" and the last editor to reply is credited with the UR closure.

The "Auto reminder and mark as not identified" flag can only be toggled on if a message is sent. The flag can be toggled off however without a message being sent.

Possible visual presentation: https://imgur.com/VMIGTEW

Access to this feature can be controlled by a country level permission, ideally level 3 and above as default.

When adding or editing RPP, if there is a conflict with the HN layer (i.e. too far), then the WME issues an error that prevents you from saving your edit. Thus, you cannot add or update this RPP.

To resolve the issue you need to perform the following steps:
1. Update/Remove the address in HN layer
2. Wait for next (successful) map build
3. Add the RPP

This is an annoying procedure that should and can be avoided.

The issue can be handled in one of the following ways:
1. Verify the RPP against the most updated data either in the edited or production HN layer databases.
2. Allow conflicts. Issue a warning but allow to save (rank depended). The same as forced HNs are allowed. Especially that for navigation, exiting RPPs are used before HNs.

The above suggestions or any other solution that will allow immediate RPP editing would be very welcomed.

I prefer option 1, as it also solve the conflict.

The restrictions tool used to be simpler a few years ago. Today it allows to setup not only time/days restrictions but also permits/passes, number of passengers, toll roads and more. With new options such as "allowed", "toll free" and "prohibited" it became confusing even for higher rank editors sometimes.

I've lost count of how many times I checked editors that made 1-2 edits and that added a 24/24h 7/7d permanent restriction on what should be a simple "private road". Or even setup a freeway pass on a simple street.

This tool has become extremely complex and powerful, especially since routing was changed years ago to treat any segment with a restriction applied to behave as a "Walking Trail", not routing into the segment but stopping at the junction node if the address is on the segment.

Applied restrictions are almost impossible to detect or keep track of. Without scripts or selecting and opening menus, we cannot easily differenciate a useful restriction from a wrong one. The UI also makes it harder to see, compared to a wrong red/green arrow, missing segment or other more obvious errors.

For all of those reasons it should be possible to restrict its usage per level and per country.
I would personally make it available only at L2, as 3000 edits is usually enough time to figure out that segment types exist and what their penalties are vs adding restrictions.

(Copied over from https://www.waze.com/forum/viewtopic.php?f=1525&t=229014)

If you try to delete unneeded junction node, but it can't be deleted due to a conflicting option between then, at the moment you need to inspect each segment to see what the differences are. This is especially frustrating when there may be a hidden speed limit set on a one way segment.

Can a dialog box pop up on deletion of a junction node if there is a conflict to allow the editor to select one of the conflicting settings for the newly joined segment?

OR

Create an error message saying the junction node cannot be deleted because of <a-b speed limit> conflicting, for example.