qwaletee wrote:"If street name begins with EWNS followed by a space followed by a lowercase letter."
The check is called 'Lowercase street name (with exceptions)'. There is a per country list of exceptions.
Sure, I can fit another list of per country words to ignore at the beginning, but IMO it's better to create new more comprehensive check with a list of allowed lowercase words (to, a, the, de, la etc) and report any other lowercase word no matter its position in the street name.
qwaletee wrote:Been wondering... what are the SLOW indicators for.
There is an option "Settings->Enable slow checks".
At the moment any check which analyzes unknown (and unpredictable) number of adjacent segments is marked as "slow".
bz2012 wrote:Validator flags the segment with a 'turn too sharp' at the north end when that end has the restricted turn (yellow) 24/7, but passes it when the turn is forbidden (red).
Well, there is nothing to report if the turn is disabled (red). Scheduled (yellow) turn is an enabled turn internally in WME.
I'm not sure if it's a common practice to restrict a turn 24/7 just to make sure nobody accidentally enables it If so, Validator might skip restricted turns as well as disabled.
irowiki wrote:- NEW for ALL: 'Out of range elevation'
Does this need to be enabled
I posted an example with elevation 20: permalink
irowiki wrote:Would also be nice to have a way to search for all elevation not set to "Ground" in an area where there are no tunnels, bridges or overpasses.
The search for overpasses is very expensive operation and would be extremely slow. If there are 500 segments on the map it will take ~125000 comparisons to check if a segment crosses another one.