[Script] WME Validator v2020.11.1 (PLACES BETA)

[sketch]

It's been like that in WME for a long time, Jay.

[sketch]

Oh, well, let me restate that — today's WME release replaced the older yellow circle with the current smaller dark blue circle as the representation of a "selected but uneditable node". Streets are shown at zoom 3 for reference but not editable because zoom 3 is typically too far out to edit city streets. So nodes incorporating streets aren't editable because the street it connects to is not editable.

I agree that there's a bug which requires you to reload if you do not deselect such a node before zooming in. If you deselect, zoom in, then reselect, it works. Feel free to report this on the WME release thread, but honesty I'd wait a day or so for the Places discussion to die down

[sketch]

2)a) I would increase the margin of error significantly. For instance, this area, fairly unremarkable right turns, but with angles around 68°.

[sketch]

Wait, I have a problem with the "no right turn" check. Wouldn't it call for erroneous enabling of turns like the right turn from this segment?

2. No right* turn (for any drivable road)
* for the right-hand traffic
Report/highlight the segment if at the node:
a) there is a 90±5° right turn

Why not any segment between 80° and the continuation segment or 180° whichever is less?
Of course, when the continuation segment is <80°, it is the right turn.

The operative angle for determining the difference between turn and stay/exit/continue is 45°. Past that, I'm not really sure what you're saying. Are you suggesting right turns should be enabled for 170° turns?

[sketch]

Ok, how about that:
2. No right* turn (for any drivable road)
* for the right-hand traffic
Report/highlight the segment if at the node:
a) there is an up to 85° right turn
a1) and either this segment OR that right turn segment is longer than 300m (~1000 ft)
b) and that right turn segment is also drivable and non-private
c) and that right turn segment is not marked as closed
d) and the connectivity between those two segments is possible (road directions), but not enabled

Would that new a1) condition be sufficient to detect connectors and other possible exceptions?

a1) seems like it would be sufficient.

What do you mean by "up to 85°"? I would think it should apply for any angle (45º < angle ≤ 90º); i.e., any that would give a "turn right" instruction.

[sketch]

Understood.

Although I will mention that departure angles between 135° and 180° will also give a "turn" instruction, but as angle increases the turn is substantially less likely to be allowed in fact. That's partially covered by the "too sharp turn angle" check, but there should be a neutral area between the two checks where Validator recommends neither enabling nor disabling that particular turn, since the answer in such cases will likely depend on circumstances.

In the meantime, I thought of a circumstance where basic right turns are disallowed. check out Street View on the service road at Aurora and Orion here — to prohibit drivers from cutting through the neighborhood when exiting the Interstate.

Though those segments are actually already highlighted by Validator with a warning...

[sketch]

Got it. So we are pretty much in accord, then. I believe convention is to refer to the angle between your heading before turning and your heading after turning, so, straight and slight right would be perhaps 20°. This is the "45°" referred to all over the place.

[sketch]

check out Street View on the service road at Aurora and Orion here — to prohibit drivers from cutting through the neighborhood when exiting the Interstate.

Wow, very nice and rare example. I just wondering how can we detect such a situation... A turn from a Ramp/Highway to the regular street or lower? Any ideas?

Although the map is perfectly correct, there are few possibilities to suppress the warning in Validator at the moment:
1. Add a 24/7 time based turn restriction from highway to the street.

2. Make an exiting piece of the screet one way.

3. Make the screet private.

I know it's ugly but a tempory solution. So, shall I exclude inward connectivities warnings for the turns from highways/ramps to streets/parking lots/dirts?

No, that exclusion won't work. These turns are technically from a primary street to a street.

I think I previously had a bit of one-way segment at the end; I believe I changed it back because I figured it was now easy enough to see the no-right-turn signs in street view.

[sketch]

Perhaps for locked segments the Validator highlight could be displayed differently. Maybe a few dark or black stripes along the segment? Alternating lighter-darker colors?

[sketch]

On a side note, is there any chance you can allow street names (in the US) that start with "de", "de la", "del", "el" and "la" to not trigger the #170 rule? There are a number of streets in San Diego that start with those and they are 'correct'.

Examples:
https://www.waze.com/editor/?zoom=7&lat ... ts=6953500
https://www.waze.com/editor/?zoom=5&lat ... ts=7077112
https://www.waze.com/editor/?zoom=5&lat ... ts=7013094
https://www.waze.com/editor/?zoom=4&lat ... ts=7077129
https://www.waze.com/editor/?zoom=5&lat ... ts=7094876

Many thanks!
- James

The street signs appear to capitalize the first word (and every word, in fact — using a "small caps" sort of font). I would personally prefer to use title case, as in "Ave de la Garza" or "Calle del Sol" (cf. "Avenue of the Americas").

I would not object to an initial lowercase letter if it were actually represented as such on the street sign. But I've yet to come across any such street signs in reality.

I am not finding the "Udate extensions now" button in Chrome.

Enable Developer Mode.