Opened 15 years ago
Closed 14 years ago
#4321 closed defect (invalid)
Validator: crossing ways check broken
Reported by: | Cobra | Owned by: | team |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | Core validator | Version: | latest |
Keywords: | crossing way barrier | Cc: |
Description
Validator doesn't find any crossing ways. "Crossing ways" is activated in validator preferences, the crossings are obvious.
This can be reproduced anytime with any data - new "fake" ways crossing without a commmon node and no layer/bridge/tunnel tags and existing data needing cleanup.
Version information:
Plugin validator Version: 19304
JOSM Revision: 2784 (latest)
Attachments (2)
Change History (8)
comment:1 by , 15 years ago
Keywords: | r-2010-01-blocker added |
---|
comment:2 by , 15 years ago
Keywords: | r-2010-01-blocker removed |
---|---|
Owner: | changed from | to
Status: | new → needinfo |
comment:3 by , 15 years ago
I am still able to reproduce this. I suspected some config was broken and unchecked "crossing ways" in the settings/validator dialog, closed and reopened it to check it again, but validator still doesn't find this sort of errors.
Attached .osm file are some simple streets, "foo" and "bar" are crossing without a common node (error 1) and one of bar's end nodes was put near foo (error 2). "baz" is overlapping the second "baz" (error 3). Validator doesn't find the first two errors (which are quite common in bad osm data). The third one is found correctly.
versions:
validator: 19335
josm: r3051
by , 15 years ago
Attachment: | validator-test.osm added |
---|
comment:4 by , 15 years ago
Keywords: | crossing way barrier added |
---|---|
Priority: | critical → major |
at least it does not find a barrier crossing a way.
r3144 and o20546
comment:5 by , 15 years ago
Owner: | changed from | to
---|---|
Status: | needinfo → new |
comment:6 by , 14 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
validator is now integrated into core; can't reproduce anymore. closing.
Could not reproduce. Please provide examples.