Public Transport Validation Results for Netherlands_Gelderland_North
⚠️ Warnings
Relation 336548 dropped platforms: node 6154166505Relation 336548 has parsed only 12/13 platform names
Relation 336997 dropped platforms: node 6154166510
Relation 336997 has parsed only 30/31 platform names
Relation 337080 dropped platforms: node 6154166505
Relation 337080 has parsed only 28/29 platform names
Relation 337081 dropped platforms: node 6154166510
Relation 337081 has parsed only 38/39 platform names
Relation 337084 dropped platforms: node 6154166509
Relation 337084 has parsed only 22/23 platform names
Relation 337133 dropped platforms: node 6154166505
Relation 337133 has parsed only 19/20 platform names
Relation 349830 dropped platforms: node 6154166509
Relation 349830 has parsed only 20/21 platform names
Relation 349831 dropped platforms: node 6154166509
Relation 349831 has parsed only 30/31 platform names
Relation 349892 dropped platforms: node 6154166509
Relation 349892 has parsed only 12/13 platform names
Relation 405729 dropped platforms: node 6154166506
Relation 405729 has parsed only 27/28 platform names
Relation 405731 dropped platforms: node 6154166510
Relation 405731 has parsed only 24/25 platform names
Relation 405733 dropped platforms: node 6154166505
Relation 405733 has parsed only 30/31 platform names
Relation 405942 dropped platforms: node 6154166506
Relation 405942 has parsed only 22/23 platform names
Relation 405943 dropped platforms: node 6154166510
Relation 405943 has parsed only 48/49 platform names
Relation 406539 dropped platforms: node 6154166506
Relation 406539 has parsed only 61/62 platform names
Relation 406604 dropped platforms: node 6154166505
Relation 406604 has parsed only 47/48 platform names
Relation 535908 dropped platforms: node 6154166510
Relation 535908 has parsed only 32/33 platform names
Relation 535913 dropped platforms: node 6154166510
Relation 535913 has parsed only 44/45 platform names
Relation 1645112 dropped platforms: node 6154166510
Relation 1645112 has parsed only 4/5 platform names
Relation 1645113 dropped platforms: node 6154166509
Relation 1645113 has parsed only 16/17 platform names
Relation 1646413 dropped platforms: node 6154166506
Relation 1646413 has parsed only 29/30 platform names
Trajectory of relation 1655144 is not continuous after way 661011736. Selected next edge: way 1274089733
Relation 3046296 dropped platforms: node 12180892834, node 12180892838
Relation 3046296 has parsed only 41/43 platform names
Relation 5667106 dropped platforms: node 6154166505
Relation 5667106 has parsed only 28/29 platform names
Relation 5669256 dropped platforms: node 6154166506
Relation 5669256 has parsed only 31/32 platform names
Relation 5700108 dropped platforms: node 3862968699
Relation 5700108 has parsed only 2/3 platform names
Relation 5833126 dropped platforms: node 3931062992
Relation 5833126 has parsed only 12/13 platform names
Relation 5833127 dropped platforms: node 3931062992
Relation 5833127 has parsed only 13/14 platform names
Relation 5860352 dropped platforms: node 639247727
Relation 5860352 has parsed only 11/12 platform names
Relation 5860354 dropped platforms: node 639247727
Relation 5860354 has parsed only 21/22 platform names
Trajectory of relation 7188637 is not continuous after way 550097839. Selected next edge: way 1000410296
Trajectory of relation 7188637 is not continuous after way 1236158594. Selected next edge: way 577597945
Relation 7188637 dropped platforms: node 2178507105, node 4820005733
Relation 7188637 has parsed only 12/14 platform names
Relation 7201321 dropped platforms: node 3080941086, node 4820005733, node 6342888127
Relation 7201321 has parsed only 5/8 platform names
Relation 7201325 dropped platforms: node 3080941086, node 4820005733
Relation 7201325 has parsed only 8/10 platform names
Relation 7220241 dropped platforms: pt (51.349068700000004, 8.28008425)
Relation 7220241 has parsed only 11/12 platform names
Relation 7220242 dropped platforms: pt (51.349068700000004, 8.28008425)
Relation 7220242 has parsed only 10/11 platform names
Relation 9191299 dropped platforms: node 6185421963
Relation 9191299 has parsed only 14/15 platform names
Relation 10693304 dropped platforms: pt (51.345105610000005, 12.384813459999998)
Relation 10693304 has parsed only 9/10 platform names
Relation 10693305 dropped platforms: pt (51.345105610000005, 12.384813459999998)
Relation 10693305 has parsed only 9/10 platform names
Relation 10693366 dropped platforms: pt (51.345105610000005, 12.384813459999998)
Relation 10693366 has parsed only 6/7 platform names
Relation 10693367 dropped platforms: pt (51.345105610000005, 12.384813459999998)
Relation 10693367 has parsed only 6/7 platform names
Relation 11527860 dropped platforms: node 6154166510
Relation 11527860 has parsed only 48/49 platform names
Relation 12724733 dropped platforms: node 673703169
Relation 12724733 has parsed only 6/7 platform names
Relation 13676641 dropped platforms: node 6185421963
Relation 13676641 has parsed only 6/7 platform names
Finished in 4718.693340063095 seconds
Summary: lines - 299, stops - 3554
ℹ️ Notices
Warning "Trajectory of relation.. is not continuous after way.." happens when:- connected road segment was lost in relation
- ill-formed relation, segment was added into relation for error
Warning "relation.. dropped segments.." happens when not all segments from relation were included into parsed rote. It happens when:
- the gap between segments is more than 500 meters
- reverse segments were lost when road is passed in both directions
Warning "relation.. dropped platforms.." happens when:
- distance from platform to nearest segment is more than 100 meters
- platform can not be projected onto trajectory
- platform is to the left from trajectory while region has right-hand driving rules
- segments were dropped
Warning "relation has not enough platforms" happens when:
- only road segments were added into relation
- no platforms were added for bus-route
- no stop-positions were added for tram-route
- stops/platforms were dropped because road segments were dropped