[Script] WME Color Highlights - 2.33 Sept 2020

[AlanOfTheBerg]

The script already adjusts the width or opacity of the highlight according to lock level I thought?

[AlanOfTheBerg]

Lastly: RevCons? SelfCons? Can someone tell me what these terms mean?

Have a look at http://world.waze.com/forum/viewtopic.php?f=265&t=42562. I posted an explanation earlier today.

Even better: the documentation in the Glossary.

[AlanOfTheBerg]

I'd still love to see WMECH stop highlighting selfcon. It seems like an "error" when there really isn't.

[AlanOfTheBerg]

I'd still love to see WMECH stop highlighting selfcon. It seems like an "error" when there really isn't.

I have to disagree with this one. Selfcons allow the client to act in an unacceptable way.

Selfcon is the way Waze is defining uturn on a 2-way segment. I'm suggesting that when u-turn functionality is released into the production editor, that this feature be removed from WMECH as too many people will think it is something to fix, when it isn't always needing a "fix."

[AlanOfTheBerg]

First of all, we need to be told. This is the first I've heard that this behaviour might be deliberate. Of course, it might have been discussed in the champs forum, or I might have just had my head up my ass (happens frequently ) and I missed it.

It's in beta test, and like all things there, they aren't announced right away but are slowly leaked. @WazeMapping tweeted it too.

1. Agree. This is the way it is going to be, and why I posted my request for wmech to be updated (maybe I should have put it in the beta forum only...)

2. Yes.

3. Agree, but not sure this is any different than other turns. Once set by an editor (locked, not a soft turn), they shouldn't be auto-updated.

4. The app should update near the same time the routing server is updated. Right now, there is no u-turn instruction, so both need updates to handle it gracefully.

[AlanOfTheBerg]

Presumably a good portion of the house numbers on the older streets are set / were imported with the help of the geocoding sources. Undoubtedly they need to be tweaked - prompted by UR's.

Why, they aren't currently used by Waze search?

It's been posted about already: the search engine and app functionality aren't built yet. It's in process.

[AlanOfTheBerg]

Assuming that u-turns can also be "soft" or "hard", I think the only realistic solution is for Waze to run a cleanup and change every soft-allowed u-turn back to soft-restricted and then stop soft-allowing them. That will preserve all the hard u-turns presumably set by editors..

Please remember that ALL turns at the end of a junction are either locked or not. You cannot have a "soft" u-turn and others locked (hard) at that segment end. If the turns are locked, so is the u-turn. If the turns are unlocked, so is the u-turn. It's an all-or-nothing proposition.

[AlanOfTheBerg]

When the uturn feature was enabled in the editor, there was no change to the data anywhere. Any selfcons which existed before would now show as an allowed uturn, whether locked or unlocked.

[AlanOfTheBerg]

The single question mark possible at each end of a selected segment denotes that the turns from that end of the segment are unlocked. It is not, as noted above and many other places, specific to any turn. It's all or nothing.

It is not "on" the uturn or any other turn. It is for all turns.

[AlanOfTheBerg]

Please keep selfcon highlighting. The statistical correlations are pretty clear in my mind. That may be because whenever I see strange problems I look for them, but I usually find them. Thanks.

Just remember that if you remove it, you may likely be removing a uturn that an editor enabled on purpose and that's the same as restricting a valid turn.