Public Transport Validation Results for Belgium_Limburg

⚠️ Warnings
Relation 2538796 dropped platforms: node 11195868340
Relation 2538796 has parsed only 15/16 platform names
Relation 2798672 dropped platforms: node 2183110565
Relation 2798672 has parsed only 41/42 platform names
Relation 2808007 dropped platforms: node 11195868340
Relation 2808007 has parsed only 32/33 platform names
Relation 2808018 dropped platforms: node 11195868340
Relation 2808018 has parsed only 41/42 platform names
Relation 3275132 dropped platforms: node 11195868340
Relation 3275132 has parsed only 34/35 platform names
Relation 3275133 dropped platforms: node 11195868340
Relation 3275133 has parsed only 27/28 platform names
Relation 3283166 dropped platforms: node 2503195600
Relation 3283166 has parsed only 19/20 platform names
Relation 3410378 dropped platforms: node 2476999481, node 2503195565
Relation 3410378 has parsed only 44/46 platform names
Relation 4254050 dropped platforms: node 3054753095
Relation 4254050 has parsed only 51/52 platform names
Relation 4254053 dropped platforms: node 1133624382
Relation 4254053 has parsed only 54/55 platform names
Relation 4272274 dropped platforms: node 2186703218
Relation 4272274 has parsed only 40/41 platform names
Relation 5308103 dropped platforms: node 11195868340
Relation 5308103 has parsed only 37/38 platform names
Relation 5357380 dropped platforms: node 2510066296, node 2510066350, node 2510066431, node 2510066443, node 2510066446, node 2510066450, node 2510066454, node 2510066462, node 2510066463, node 2510066466, node 2510066468, node 2510066470, node 3066040966, node 3066040974, node 3066040978, node 3066040983
Relation 5357380 has parsed only 21/37 platform names
Relation 7172831 dropped platforms: node 11195868340
Relation 7172831 has parsed only 52/53 platform names
Relation 7190393 dropped platforms: node 5148926872
Relation 7190393 has parsed only 9/11 platform names
Relation 7190394 has parsed only 10/11 platform names
Relation 10387455 dropped platforms: node 5006848506
Relation 10387455 has parsed only 21/22 platform names
Relation 16945141 dropped platforms: node 11195868340
Relation 16945141 has parsed only 42/43 platform names
Relation 17094528 dropped platforms: node 2186703145
Relation 17094528 has parsed only 23/24 platform names
Relation 17292923 dropped platforms: node 2499202366
Relation 17292923 has parsed only 28/29 platform names
Relation 17853491 dropped platforms: node 11195868340
Relation 17853491 has parsed only 60/61 platform names
Relation 17853492 dropped platforms: node 2419921282
Relation 17853492 has parsed only 59/60 platform names
Relation 17855614 dropped platforms: node 11195868340
Relation 17855614 has parsed only 38/39 platform names
Relation 17855615 dropped platforms: node 2506485513
Relation 17855615 has parsed only 37/38 platform names
Relation 17863961 dropped platforms: node 2499202366
Relation 17863961 has parsed only 46/47 platform names
Relation 17870147 dropped platforms: node 2500500309
Relation 18112811 dropped platforms: node 2499202366
Relation 18112811 has parsed only 23/24 platform names
Relation 18186798 dropped platforms: node 2183110565
Relation 18186798 has parsed only 54/55 platform names
Relation 18310128 dropped platforms: node 2183110565, node 2965811748, node 2965811750, node 2965811751, node 2965811752, node 2965811753, node 2965811756, node 2965811757, node 2965811760
Relation 18310128 has parsed only 41/50 platform names
Relation 18522293 dropped platforms: node 2341028358
Relation 18522293 has parsed only 30/31 platform names
Relation 18522400 dropped platforms: node 2341028358, node 2527300720
Relation 18522400 has parsed only 27/29 platform names
Relation 18585206 dropped platforms: node 11195868340
Relation 18585206 has parsed only 29/30 platform names
Relation 18585207 dropped platforms: node 11195868340
Relation 18585207 has parsed only 29/30 platform names
Relation 18588464 dropped platforms: node 11195868340
Relation 18588464 has parsed only 35/36 platform names
Relation 18632921 dropped platforms: node 2189499240
Relation 18632921 has parsed only 51/52 platform names
Relation 18633048 dropped platforms: node 2183110565
Relation 18633048 has parsed only 62/63 platform names
Relation 18633049 dropped platforms: node 2183110565
Relation 18633049 has parsed only 63/64 platform names
Relation 18633051 dropped platforms: node 2189499240
Relation 18633051 has parsed only 62/63 platform names
Relation 18633404 dropped platforms: node 2183110565
Relation 18633404 has parsed only 64/65 platform names
Relation 18690331 dropped platforms: node 11195868340
Relation 18690331 has parsed only 39/40 platform names
Relation 18695664 dropped platforms: node 2521747041
Relation 18695664 has parsed only 40/41 platform names
Relation 18695665 dropped platforms: node 2521747041
Relation 18695665 has parsed only 40/41 platform names
Relation 18777978 dropped platforms: node 2499202366
Relation 18777978 has parsed only 34/35 platform names
Relation 18931645 dropped platforms: node 11195868340
Relation 18931645 has parsed only 52/53 platform names
Relation 18965307 dropped platforms: node 2183110565
Relation 18965307 has parsed only 7/8 platform names
Relation 18976084 dropped platforms: node 2183110565
Relation 18976084 has parsed only 35/36 platform names
Relation 18976114 dropped platforms: node 2183110565
Relation 18976114 has parsed only 37/38 platform names
Relation 18976168 dropped platforms: node 2183110565
Relation 18976168 has parsed only 20/21 platform names
Relation 18989554 dropped platforms: node 11195868340
Relation 18989554 has parsed only 32/33 platform names
Relation 18989832 dropped platforms: node 11195868340
Relation 18989832 has parsed only 32/33 platform names
Relation 18989913 dropped platforms: node 11195868340
Relation 18989913 has parsed only 41/42 platform names
Relation 19008266 dropped platforms: node 2503195600
Relation 19008266 has parsed only 20/21 platform names
Relation 19008291 dropped platforms: node 2503195626
Relation 19008291 has parsed only 28/29 platform names
Relation 19008292 dropped platforms: node 2503195627
Relation 19008292 has parsed only 31/32 platform names
Relation 19022130 dropped platforms: node 2499202366
Relation 19022130 has parsed only 26/27 platform names
Finished in 17056.955290079117 seconds
Summary: lines - 567, stops - 5658
ℹ️ 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