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

[dbraughlr]

The results should update dynamically when you change elements. Otherwise, press the χ icon to delete old results.

[dbraughlr]

we can let this issue sleep again.

The issue belongs in another thread - not in this one.

It might be helpful if a moderator would move some of the elevation discussion from this thread to the other.

[dbraughlr]

Any ideas?

String them together using delimiters, e.g. name + '\t' + city + '\n'.

[dbraughlr]

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.

[dbraughlr]

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.

Ignoring the detail that departure angles from too sharp all the way to <135º give a "turn right" instruction, I still think that the point is that a turn should be expected to be allowed to any road between, say 45º and wherever the best continuation is.

In short, a road which merely requires "stay right" still should have its turn enabled- at least this is what I was expecting. So if the road bears hard left, a turn of straight ahead should be expected to be permitted even if 185º.

I think another way if saying this is that any road that can be reached without crossing traffic is the opposing direction, why is the turn not allowed?
(Yes, bypass roads like AGCs are such examples. I'm not asking. I'm just saying that this is the essence of the question that the validation asks.)

[dbraughlr]

I was referring to the angle as measured from the current segment, not in degrees of turn.
So the angles I gave need to be subtracted from 180 to get degrees of right turn, e.g. 180° - 185° = -5° right turn (a turn slightly left of course).

[dbraughlr]

it can delete all segments

What kind of threat is that??

[dbraughlr]

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

As mentioned, we already hashed out this issue regarding #170 and there is a thread on the topic of capitalization. I invite you to contribute to that discussion.

I checked two of your examples from the street view. Clearly, Title case is used. Not only are the words you mentioned capitalized at the beginning of the name, they are capitalized in the middle of a name. I believe that the names you cited should be fixed in Waze to conform to the official spelling.

Conclusion: A street name starting with a lowercase letter is not something that should pass validation.

[dbraughlr]

To get the roundabout instruction to work correctly on this roundabout, I had to not have the segments connect at the same point.

I do not consider traffic circles (e.g., Washington Circle to be roundabouts. They are circular roads controlled by traffic lights. In a real roundabout, traffic does not stop and roads do not cross. However, I do somewhat see how instructions to enter and exit the circle could be useful.

[dbraughlr]

is the scan supposed to pick up on custom checks and put them in the report?

It does for me.