Public Transport Validation Results for Russia_Saint Petersburg
⚠️ Warnings
Relation 1784173 dropped platforms: node 1197352825Relation 1784173 has parsed only 66/67 platform names
Relation 1784535 dropped platforms: node 298318596
Relation 1784535 has parsed only 26/27 platform names
Relation 1784538 dropped platforms: node 1197352825
Relation 1784538 has parsed only 28/29 platform names
Relation 1814912 dropped platforms: node 1197352825
Relation 1814912 has parsed only 44/45 platform names
Relation 2015609 dropped platforms: node 2102040725
Relation 2015609 has parsed only 26/27 platform names
Relation 2362048 dropped platforms: node 858269212
Relation 2362048 has parsed only 15/16 platform names
Relation 2584508 has not enough platforms
Relation 2633832 dropped platforms: node 2102040725
Relation 2633832 has parsed only 27/28 platform names
Relation 2666288 has parsed only 19/20 platform names
Relation 2699351 dropped platforms: node 8327599338
Relation 2699351 has parsed only 26/27 platform names
Relation 2699352 dropped platforms: node 8327599338
Relation 2699352 has parsed only 25/26 platform names
Relation 2707226 dropped platforms: node 1197352825
Relation 2707226 has parsed only 40/41 platform names
Relation 2750229 dropped platforms: node 1023604190
Relation 2750235 dropped platforms: node 1023604190
Relation 3210628 has parsed only 55/56 platform names
Relation 3565895 has not enough platforms
Relation 3566304 has parsed only 8/9 platform names
Relation 3572798 dropped platforms: node 8327599338
Relation 3572798 has parsed only 16/17 platform names
Relation 3572799 dropped platforms: node 8327599338
Relation 3572799 has parsed only 15/16 platform names
Relation 3573054 dropped platforms: node 858269212
Relation 3573054 has parsed only 15/16 platform names
Relation 3576169 has parsed only 19/20 platform names
Relation 3576172 has parsed only 14/16 platform names
Relation 3576175 has parsed only 35/37 platform names
Relation 3576182 has parsed only 21/22 platform names
Relation 3576184 has parsed only 16/17 platform names
Relation 3576185 has parsed only 90/92 platform names
Relation 3810853 dropped platforms: node 9174129644
Relation 3810853 has parsed only 2/3 platform names
Relation 3824711 dropped platforms: node 2102040725
Relation 3824711 has parsed only 24/25 platform names
Relation 3824712 dropped platforms: node 2102040725
Relation 3824712 has parsed only 22/23 platform names
Relation 4260141 has parsed only 6/7 platform names
Relation 5401057 dropped platforms: node 2102040725
Relation 5401057 has parsed only 68/70 platform names
Relation 6152071 has parsed only 12/13 platform names
Relation 6152072 has parsed only 10/11 platform names
Relation 6152374 has parsed only 10/11 platform names
Relation 6152375 has parsed only 9/10 platform names
Relation 6167465 has parsed only 36/37 platform names
Relation 6167466 has parsed only 31/32 platform names
Relation 9695201 has parsed only 1/2 platform names
Relation 9695236 dropped platforms: node 12680358776
Relation 9695236 has parsed only 18/20 platform names
Relation 11200779 has parsed only 13/14 platform names
Relation 11200780 has parsed only 7/8 platform names
Relation 13202356 dropped platforms: node 1197352825
Relation 13202356 has parsed only 23/24 platform names
Relation 13223410 has parsed only 1/2 platform names
Relation 13994947 dropped platforms: node 1197352825
Relation 13994947 has parsed only 25/26 platform names
Relation 14220634 dropped platforms: node 2338367049
Relation 14220634 has parsed only 21/22 platform names
Relation 14220978 dropped platforms: node 1116681617
Relation 14220978 has parsed only 13/14 platform names
Relation 14361355 dropped platforms: node 1197352825
Relation 14361355 has parsed only 34/35 platform names
Relation 14453225 dropped platforms: node 9949768615
Relation 14453225 has parsed only 24/26 platform names
Relation 14453226 has parsed only 30/31 platform names
Relation 14583353 has parsed only 36/38 platform names
Relation 14629164 has parsed only 54/56 platform names
Relation 14629165 has parsed only 54/56 platform names
Relation 16055650 has parsed only 26/27 platform names
Relation 16891505 dropped platforms: node 9174129644
Relation 16891505 has parsed only 3/4 platform names
Relation 17251707 has parsed only 94/96 platform names
Relation 19000719 dropped platforms: node 1197352825
Relation 19000719 has parsed only 52/53 platform names
Relation 19333374 dropped platforms: node 1826574079
Relation 19333374 has parsed only 34/35 platform names
Relation 19333392 dropped platforms: node 1826574082
Relation 19333392 has parsed only 35/36 platform names
Trajectory of relation 20620160 is not continuous after way 78279179. Selected next edge: way 1083687978
Trajectory of relation 20620160 is not continuous after way 1343068570. Selected next edge: way 1106376259
Relation 20623861 has not enough platforms
Trajectory of relation 20623930 is not continuous after way 1218182468. Selected next edge: way 431106371
Relation 20623930 has not enough platforms
Finished in 4619.003055095673 seconds
Summary: lines - 1287, stops - 8580
ℹ️ 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