Modify ↓
Opened 18 months ago
Last modified 17 months ago
#7120 new enhancement
Check: Railway end node near other railway
| Reported by: | newsScott@… | Owned by: | team |
|---|---|---|---|
| Priority: | normal | Component: | Core validator |
| Version: | Keywords: | unconnected_way | |
| Cc: |
Description
There allready exists a "Way end node near other highway" check. The same would be very helpful to improve the quality of railway data.
Some false positives may be avoidable if the code would also check for the tag "railway:buffer_stop" in the end node.
Attachments (0)
Change History (3)
comment:1 Changed 18 months ago by anonymous
comment:2 Changed 18 months ago by simon04
- Component changed from Core to Core validator
comment:3 Changed 17 months ago by simon04
- Keywords unconnected_way added
Note: See
TracTickets for help on using
tickets.



i realized that there is allready some support of this. But i think the current implementation needs some changes:
in org/openstreetmap/josm/data/validation/tests/UnconnectedWays.java:
The default distance (mindist) of 10 meters is not useful for checking railways. I my experiments, something like 1-2 meters is best. So should there be a mindist_highway and mindist_railway?
The code finds some false positives: many platforms are still tagged "railway=platform" instead of "public_transport=platform". In member function "visit", ways tagged with railway=platform should not be taken into account:
something like