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.

Give editors the ability to enter Notes onto User Reports without these going to the reporters themselves.

This will allow us to leave messages for other map editors without the reporter being notified, for example, Please leave open - due to a Waze developer investigation, Please leave open for a pending site survey, etc.

It may also give us the ability to for to use for an internal conversation about the report that the reporter doesn't need to know about.

Yes, I know we have Map Comments, but having the ability to do this directly on the report would make it easier.

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.

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 is much busier and slower (or if say the right turn lane out the lot is fast but a left turn is slower than using a different lot exit).

This could be a checkbox on PLR segment settings, or potentially a new road type (with the current one named "Parking Lot Aisle" and the new speed data type taking on the "Parking Lot Road" name).

With the newly implemented Lane guidance we see new problems rising up.
In belgium, beeing densly populated, we somtimes have several entry's or exits of the highway following up on each other very closely.
sometimes even as close as 20-50 meters.

I would like to have a sort of junction box type of tool to combine 2 lange guidance segments.

for example:
2 highway exits within 50 meters. I want the Lane guidance before the first exit to allready show in what lane I have to stay if I have to take the 2nd exit.

It's kind of hard to explain but there are plenty of examples where lane guidances following up shortly on each other form a problem.

For really long straight segments, it can be a bit of a pain to find the little handle to make adjustments to the geometry as it is often entirely off-screen. This is especially noticeable now since we're making small adjustments to segments that formerly had no geonodes at all to bring them into better alignment for Falcon.

So as a suggestion - I was wondering how hard it would be to make a tweak to where there's always at least one "add geonode" handle visible on screen when a segment is selected?

At a minimum it would be helpful to make the "new geonode" handle bigger/easier to see (but still clearly differentiate with the existing geonode handles)

(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.

To branch off the discussion from the WME release topic:

RichardPyne כתב:
I would find GPS points much more useful if they were color coded by age rather than direction. Th arrows provide useful direction, but in areas where traffic patterns are changing due to construction, knowing the age of the trace would be far more useful.

dchary2418 כתב:
It could help if the GPS traces were the same original color, but shaded darker for older data.

Glodenox כתב:
I'd be all for somehow showing the age of the GPS points. Especially the more recent data seems of interest to me. Something like "last 7 days", "last 30 days" or "older" would work great as brackets for colouring, I think.

The issue with that is probably that it would allow you to track certain users in areas with not as many users. With no indication of age, this is a lot harder to do right now. But in theory this could be taken into account by not showing the age when there is little data.