As I was informed by staff today that the speed field in RLCs have no effect on the app behavior at all anymore. Furthermore any effects they did have were a bug. "We recently fixed a bug that was triggering the red light cameras' TTS based on the speed field added there. This behavior shouldn't be based on speed, so I highly suggest you create a suggestion on UserVoice for removing this field."
Therefore i recommend removing the speed field from red light cameras entirely in WME. There is already a separate discussion and work being done on the possibility of having combination speed/red light cams added in the future, this suggestion is for exclusive red light cameras.

When adding Places, especially outdoor places (such as parks, playgrounds, beaches, etc), there are often posted hours saying the Place is open only sunrise to sunset, or conversely that the Place is closed sunset to sunrise. Unfortunately, the existing Place hours interface doesn't allow for these kinds of hours, only HH:mm times. As sunrise and sunset times change constantly, and in some places drastically due to orbital motion of the earth and time changes due to daylight savings times, it is impractical to estimate open/closing times using HH:mm formats.

It would be beneficial to both app users and map editors to allow for the app to determine/reference local sunset/sunrise times (which it already does for dark/light app modes) and use this to mark the venues as open/closed.

Possible mock-up of feature in WME:
https://i.imgur.com/TYAa7vn.png

At the moment, it is no longer possible to add a closure to a segment you have removed or split up, even though this segment is still being used live in the app. If it were possible to add closures in the snapshot mode (recently renamed to "Current live map"), even with a strict time limit, our life would become a lot easier during road works.

At the moment, we need to apply segment restrictions, wait for the map update, remove the closure, make our changes, wait for the map update and then probably add new closures. If we can add closures in the live view, we would just remove the closure, make our changes and add the closure back in the live view. Even easier from a user's standpoint would be allowing us to make changes to closed segments, but I can imagine that would be harder to do.

There are many cases in highways where there is an on-ramp shortly followed by an off-ramp. In those cases, the right lane/s serve for those who get on the HW from the on-ramp, as well as those who get off the HW on the off-ramp.
A wazer that gets on the HW from the on-ramp and has to continue on the HW should get lane guidance to go onto the left lanes when approachng the next junction of the off-ramp, otherwise, he might continue on the right lanes and get off the HW.
A wazer that comes on the HW and approaches the off-ramp, but has to continue on the HW does not have to get lane guidance (it is disturbing to get lane guidance for every off-ramp on the HW).
The suggetion is to allow a conditional lane guidance that will allow to define separate lane guidance according to where the wazer came from (not to be confuzed with another suggestion to deal with lane guidance for a turn that will be taken later on).

Requesting push notifications for events through the editors' community still doesn't work very well and is not rewarding.

Now contributors get a notification if their event was published by Waze staff but they get no notification about the event being reviewed at first. If Waze decided to not send a notification, the contributor doesn't get to know the reason, nor the information that the decision has been made!

When I enter major events I -as a local member- often know that they have a high impact on traffic in the near area.

I suggest adding a tickbox to clearly show that the submitter expects a push notification for the respective event to consider for Waze!

Send the UR closing message to the user when the map really gets updated (contains all changes up to the UR "closing" time).

Some things may get fixed immediately (by adding a closure or updating a place), most things require a map update. That means that we always have to write stuff like "in few days/after the next map update, the problem will be fixed".

Maybe a third button like this:
"Mark as Solved"
"Solve on map update" <-
"Mark as not identified"

When the second button gets clicked a form opens when I can write a message to the user, and you just need a third email template where to put it in and to place the email on a queue, which gets sent when the map update succeeds (you could even put multiple replies in one single email, to avoid spamming the poor users doing a lot of reports).

I realize Waze can show the speed limit on screen and alert when a user goes over the speed limit, but the app does not make any kind of auditory alert when there is a speed limit change (ex: “The speed limit is now 70 MPH”)

Such an alert would be useful because if a driver could know that the speed limit has been, say, raised from 60 to 65, he or she can then drive faster sooner. It might otherwise take 5 or 10 minutes before the driver notices the speed limit was raised - by seeing this on the screen.

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

Please tell us if the reporter has closed their own UR (don't need to know their username).

Quite often a UR is closed by an editor, and it gives their username in the email and closed UR. The problem is we aren't told if this is just some random editor, or the reporter themselves.

It annoys me when an editors closes URs without comment, as it goes against etiquette, but I wouldn't be so bothered if I knew it was the original reporter. If it wasn't the original reporter, then we could follow up with the editor who closed it.

There are many places where Lanes go one or two junctions back (H junctions for example). The editor should allow to define lanes that are not limited to the turns at the end of this segment:
Real example:
We have 3 lanes. The left lane is loaded for 1 KM. In that 1 KM there are 4 junctions ( right turns allowed).

It would be nice to be able to define 1 lane for Left turn, one for going Straight Ahead, and one for Straight Ahead or Right.And be able to do this for all 5 segments.

By: Rill
Link to original suggestion: https://www.waze.com/forum/viewtopic.php?f=1525&t=307279