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

When a Map Comment (MC) has been entered and is nearing its expiration (2 weeks in advance or 1 week in advance), notify and/or place a note in the Feed of the expiring MC.

This would allow the editor to verify if the MC is still needed, extend it, and/or reconnect road segments where a long-term project may have warranted segment disconnects instead of long-term RTCs.

If roads were disconnected and the project is nearing completion, this would allow the editor to reconnect the segments and then add RTCs so routing could occur immediately upon the completion of the project instead of waiting on a tile update.

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

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 it seems it is a check added by WME that lead only to bad ergonomy.

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

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.
So to summarize :

NEVER MOVE THE MAP AUTOMATICALLY.

by kpouer
Link to original suggestion: https://www.waze.com/forum/viewtopic.php?f=1525&t=243357

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.

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

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

The WME URL field for Places is limited to 100 characters. I'm not really sure why!

Most URLs will fit in this area, true. But some hotels have URLs longer than this. When I try to add one to a Place, it is truncated, so the URL does not work in Waze.

A hotel in my area has this URL:

https://hamptoninn3.hilton.com/en/hotel ... index.html

WME truncates it to this when pasting into URL box:

https://hamptoninn3.hilton.com/en/hotel ... ood-clearv

To compare them:

CODE: SELECT ALL
https://hamptoninn3.hilton.com/en/hotels/louisiana/hampton-inn-and-suites-new-orleans-elmwood-clearview-parkway-area-MSYELHX/index.html

https://hamptoninn3.hilton.com/en/hotels/louisiana/hampton-inn-and-suites-new-orleans-elmwood-clearv

For a hotel in particular, websites can be difficult for searching for a particular location, and the localized names (and therefore the URLs) are really long. So, having the local URL can be very helpful to an app user. Extending the length limit will make this possible. Thanks!

by sketch
Link to original suggestion: https://www.waze.com/forum/viewtopic.php?f=1525&t=277350

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 try to add closure in real time server instead of doing a check according to WME database that is too news.

It is similar to https://www.waze.com/forum/viewtopic.ph ... e#p1790951

It's not enough, if you change a segment then need to add a closure, even if the tile build is the next day, it's still one day with routing errors.

For example the road under map comment was inverted, look at the UR that happened in 6 hours.
(photo attached)

by kpouer
Link to original suggestion: https://www.waze.com/forum/viewtopic.php?f=1525&t=266974