Opened 12 years ago
Closed 10 years ago
#8194 closed defect (duplicate)
JOSM fails to recognize error
| Reported by: | Owned by: | team | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Core validator | Version: | |
| Keywords: | self_crossing check | Cc: |
Description
I just wanted to point out that JOSM failed to recognize error during validation of boundary relation. It allowed me to pass through validation, even though afterwards, after searching why boundary doesn't appear in nominatim and in OSMInspector, Me and colleague found the error in boundary relation (Y shape on one way which is part of relation - http://i49.tinypic.com/zksd8z.jpg). Hopefully it will not happen to anybody else in the future.
Regards, Alen
Attachments (3)
Change History (9)
by , 12 years ago
comment:1 by , 12 years ago
Confirmed the self-intersecting test does not work on untagged ways or tagged as boundary=*, but does work when tagged as highway=*
comment:2 by , 12 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → needinfo |
The self-intersecting test does not take into account way tags.
Could you please supply a .osm file with this error ? I have run some tests with Y-shaped ways and the warning is correctly raised.
by , 12 years ago
| Attachment: | error_not_raised.osm added |
|---|
No crossing way error raised (same geometry, but different tagging)
comment:3 by , 12 years ago
| Component: | unspecified → Core validator |
|---|---|
| Keywords: | self-intersecting added |
| Owner: | changed from to |
| Status: | needinfo → new |
comment:4 by , 11 years ago
The check is only run on some major tags like highway, railway, waterway. I did try barrier=wall which does nor raise a warning neither.
Think this check should be run on all ways.
comment:5 by , 11 years ago
| Keywords: | self_crossing check added; self-intersecting removed |
|---|
comment:6 by , 10 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
Closed as duplicate of #8220.
error description image