For US Street name starts with lowercase letter, the only exception is “to”.
Too short segment should not apply to terminal segments (those connected at only one end). For one-way freeway/highway/ramp type roads, length must be >= 5 m.
Rule Walking Trail elevation = -5 is arbitrary. I did not see where anyone came forward to explain why he cares.
The validation should be Non-drivable segment junctions with drivable road and apply to any segment of a non-drivable type having an endpoint at a junction with a drivable type. Additional validation of Drivable segment has elevation = -5 could turn up an error somewhere.
NEW search tab: search for your edits, recently modified segments or specific city name
(see the details below)
NEW for ALL ‘SLOW: No connection at node A/B’:
a dead-end node is within 5m from another segment
NEW for ALL ‘Too short segment’
(drivable non-dead-end less than 2m long segment)
NEW for AT, CH, DE ‘Incorrect Freeway elevation’
NEW for ALL right-hand traffic countries
‘Unusual B-A drivable roundabout direction’
UPD ‘Construction zone’: TRAVAUX for France, GF, NC, RE
UPD roundabout checks only for drivable segments now
ENABLED for AT, CH, DE ‘Two-way Freeway segment’
‘Incorrect Freeway lock level’
DISABLED for (almost) ALL
‘Walking Trail instead of a Railroad’
‘Unneeded name on one-way Ramp’
New search tab: Updated since - report/highlight segments, updated since a specific date City name - this field supports lists (city1, city2), wildcards () and negation (!)
Examples:
Greater * Area
!Paris, * - will match any city but Paris
r, s* - will match any city starting with letter r or s Plans
I’d like to stabilize Validator, so no new features for some time. I will still enable/disable checks on your request, accept translations, exceptions etc.
Please report bugs, false positives (with permalinks), typos etc.
The issue is that one segment goes one way ant the other is the return way.
There is no mistake on the roads, thus when one segment goes one way ant the other segment goes the other way, there is no error and should not be highlighted.
I hope you can fix this to prevent a false positive highlight.
Don’t know about the Int’l server, but having two one-ways that connect the same two junctions has caused problems in my area. If the origin or destination is on one of the street waze will occasionally start or stop the route on the other. This has been solved by adding a extra junction on one of the segments.
That isn’t an explanation of the error. Of what is this a useful check?
As a matter of editor policy, all non-drivable road types (including railroads, runways, boardwalks, stairs, and walking trails) have elevation set to -5 per established convention. -5 indicates that the segment is not to be attached to the drivable roadways “to prevent false system reporting that think the roads should be connected.”.
note an error, a warning or a SLOW
some country used to set railroad as Walking Trail elevation = -5
and An Important Change in the Client Display is to come (soon? :mrgreen:)
Please note the ‘Walking Trail instead of a Railroad’ at the moment is enabled for the Poland only.
Let me know if the check should be enabled for other countries.
UPD: ‘Railroad used for comments’ enabled for all countries.
Railroads are not currently displayed in the client. That’s why editors in some areas started marking railroads as “walking trails”, so they’d be displayed in the client. But now we are told by staff that railroads will soon be displayed in the client, so all those -5 walking trails should be changed to railroads. Did I leave some of that out?
I don’t know of this convention, other than with railroads. Perhaps it is not so widespread as you think. In my area, pedestrian boardwalks are marked using normal elevation rules.
Road Types (USA) does not mention elevation for non-drivable roads other than (1) it must be different from any road it crosses, and (2) it should be -5 for railroads.
OK, and I don’t doubt that it isn’t guaranteed. But that doesn’t mean it’s the rule. You’re extrapolating a new rule from two existing rules. “Set every undrivable road to a different level than every road it crosses” and “set every railroad to -5” do not combine to mean “set every undrivable road to -5”, because not every undrivable road is a railroad.
Walking trails at elevation -5 to represent railroads, on the other hand, was a rule (in some places), and is now an obsolete rule. Hence the check (which should be limited to some places).
NEW search option to include/exclude certain checks:
Reported as (see below for the details)
ENABLED for CZ ‘Walking Trail instead of a Railroad’
fixed few bugs with new and deleted segments
New search tab: Updated since - highlight/report segments which were modified since a specific date only. City name - this field supports lists (city1, city2), wildcards () and negation (!) Examples:
Greater * Area
!Paris, * - will match any city but Paris
r, s* - will match any city starting with letter r or s New! Reported as - filter for reported issues. This field supports lists, wildcards and negation and matches severities, check titles and check IDs. Examples:
error - to highlight/report just errors
New road - to highlight/report just segments reported as “New roads”
!40, * - do not highlight/report check #40 (Soft turns on drivable road)
!soft turns*, * - do not highlight/report checks starting with ‘soft turns’
36, 37 - to highlight/report just checks #36 and #37 (unneeded node A/B) roundabout - to highlight/report checks with “roundabout” in the title Plans
I’d like to make Validator more stable, so no new features for some time. But I will still enable/disable checks on your request, accept translations, exceptions etc.
Please report bugs, false positives (with permalinks), typos etc.
I’ve found what I consider to a bug: unneeded node reported between two segments where one of the segments has time-based restrictions and the other doesn’t.
If you look here, there’s a pair of segments, and Validator considers the node between them to be unneeded, however the top segment has time-based restrictions (there’s a gate there that’s closed at night) but the lower segment has no such restriction.
If you think this is a real bug, can you disable reporting of unneeded nodes in cases where one segment has time-based restrictions and the other doesn’t? I expect this is a change that should be common to all countries, not just Ireland.