berestovskyy wrote:A permalink would help. But in theory Validator reports #47 only if inward connectivity is possible at node B (i.e. there is at least one connected segment, it is drivable and its direction is two-way or one-way directed to the reporting segment)

Woops. Sorry! (posted edited too)
https://www.waze.com/editor/?zoom=6&lat ... 50&env=usa

I forgot it because I didn't have that handy WP+ to use any longer! It had nothing to do with being up at 4am.

Great job with that script of yours

I didn't read the whole 14 pages but I did read the "Complete List of Checks for v0.5.0" and didn't find a couple of stuff I had in mind, so here it is:

Street name starting without upper case
What is the problem?
[EN]The street name starts with a lower case letter.
[FR]Le nom de la rue commence par une miniscule.
How to fix?
[EN]Set the first letter in upper case.
[FR]Passer la première lettre en majuscule.
Wiki instructions: link
Severity: warning
Countries: FR, GF, NC, RE

Another one (maybe too specific?):

'Eglise' should be written 'Église'
What is the problem?
[EN]Wrong spelling => wrong speech in navigation.
[FR]Mauvais orthographe qui provoque une mauvaise prononciation.
How to fix?
[EN]Correct the spelling (É = alt-144).
[FR]Corriger l'orthographe (É = alt-144).
Wiki instructions: link
Severity: warning
Countries: FR, GF, NC, RE

The same could be done to a lot of other words but 'Église' (Church) exists in every city at least once.

Entrance ramps here in France just start with the name of the road they are leading to, without the "to".
And I can't think of any example where a segment could/should start with a lower case.

berestovskyy wrote:31.01.2014 v0.5.8:
- NEW 'Construction zone (only available in the report)'
Default marker: 'CONST ZN'
Marker for Poland: 'REMONT'

For FR, GF, NC, RE, the equivalent is "*TRAVAUX*".

Here is another idea to be discussed (or not ): checking average speed on a segment (don't know if you can get it like the Color Highlights script do) and highlight those with excessive speed regarding the road.

I have URs that appears with weird detours being proposed and the explanation seems to be one or several segments with illogical speeds registered. The cause of this is segments that have been re-used and modified, sometimes generating a false average speed.

Like 150 km/h on a ramp (with the Freeway attached to it being limited to 90), and Waze tells the driver to exit the Freeway just to re-enter on it the next ramp (without any trafic jam or whatever on the Freeway).

Since you won't be able to know what the correct speed should be for each segment, you could do a general check and mark all the segments with, for example, a speed over 150 km/h. Or 130 km/h but excluding Freeways. Or whatever seems logical in your country regarding a type of road.

The type of warning is to be determined (orange or red since it affects the routing).

Wonderful powerful script .. it finds errors that I never thought they could exist. Link to the wiki which may explain why I have to fix them. I fix problems and learn to be a better editor in the same time.

Thanks a lot for this script !!!

Would it be possible to add the recently added speed limits and tunnel indications to the custom template list? I propose the names ${speedAB}, ${speedBA} and ${tunnel}.

If the verified tag is part of the segment, it should be possible for Validator to pick it up and expose it in the custom templates. So that would be an interesting addition for countries that have imported speed limits indeed.

Even though it was slightly off-topic, it was still useful for the topic. So no harm done

EDIT: ah, didn't notice that you accidentally wrote "TB" instead of "Validator". Meh.

I have the same issue as jdelosa. Would it be possible to hide that bubble somehow? They were handy when I first used validator, but by now it is just taking up space and even hiding useful information.