Public Transport Validation Results for Russia_Saint Petersburg
⚠️ Warnings
Relation 1778311 dropped platforms: node 5834495781Relation 1778311 has parsed only 18/19 platform names
Relation 1784535 dropped platforms: node 298318596
Relation 1784535 has parsed only 26/27 platform names
Trajectory of relation 1883819 is not continuous after way 1077972129. Selected next edge: way 309915514
Trajectory of relation 1927392 is not continuous after way 1242526071. Selected next edge: way 1391549671
Relation 1983160 dropped platforms: node 6037422222
Relation 1983160 has parsed only 46/49 platform names
Relation 1983161 has parsed only 43/45 platform names
Relation 2362048 dropped platforms: node 858269212
Relation 2362048 has parsed only 15/16 platform names
Relation 2584508 has not enough platforms
Relation 2666288 has parsed only 19/20 platform names
Relation 2699351 dropped platforms: node 8327599338
Relation 2699351 has parsed only 25/26 platform names
Relation 2699352 dropped platforms: node 8327599338
Relation 2699352 has parsed only 25/26 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 3576175 has parsed only 46/48 platform names
Relation 3576182 has parsed only 21/22 platform names
Relation 3576185 has parsed only 88/90 platform names
Relation 3810853 dropped platforms: node 9174129644
Relation 3810853 has parsed only 2/3 platform names
Relation 4260141 has parsed only 6/7 platform names
Relation 6152071 has parsed only 8/13 platform names
Relation 6152072 has parsed only 6/10 platform names
Relation 6152374 has parsed only 6/11 platform names
Relation 6152375 has parsed only 5/9 platform names
Relation 6167465 has parsed only 36/37 platform names
Relation 6167466 has parsed only 31/32 platform names
Relation 7930174 dropped platforms: node 11832443084, pt (54.51928153333333, 30.372400222222225)
Relation 7930174 has parsed only 2/6 platform names
Relation 7932272 dropped platforms: node 11832443084, pt (54.51928153333333, 30.372400222222225)
Relation 7932272 has parsed only 2/6 platform names
Trajectory of relation 8432365 is not continuous after way 1364780022. Selected next edge: way 1370506889
Relation 8780087 dropped platforms: node 257414217
Relation 8780087 has parsed only 4/5 platform names
Relation 8808901 dropped platforms: node 1266490569
Relation 8808901 has parsed only 3/4 platform names
Trajectory of relation 8808913 is not continuous after way 1364780022. Selected next edge: way 1370506889
Trajectory of relation 8808945 is not continuous after way 1364780022. Selected next edge: way 1370506889
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 13223410 has parsed only 1/2 platform names
Relation 14220634 dropped platforms: node 2338367049
Relation 14220634 has parsed only 20/21 platform names
Relation 14220978 dropped platforms: node 1116681617
Relation 14220978 has parsed only 13/14 platform names
Relation 14453225 dropped platforms: node 9949768615
Relation 14453225 has parsed only 25/27 platform names
Relation 14453226 has parsed only 31/32 platform names
Relation 14583353 has parsed only 45/47 platform names
Relation 14763574 has parsed only 30/31 platform names
Relation 16055650 has parsed only 29/30 platform names
Relation 16141144 has parsed only 14/15 platform names
Relation 16141145 has parsed only 14/16 platform names
Relation 16166453 has parsed only 13/15 platform names
Relation 16166454 has parsed only 12/14 platform names
Relation 16891505 dropped platforms: node 9174129644
Relation 16891505 has parsed only 3/4 platform names
Relation 17130404 dropped platforms: node 11571144813
Relation 17130404 has parsed only 8/9 platform names
Trajectory of relation 17223260 is not continuous after way 1364780022. Selected next edge: way 1370506889
Relation 17251707 has parsed only 94/96 platform names
Relation 18431214 has parsed only 17/18 platform names
Relation 18431215 has parsed only 18/19 platform names
Finished in 2824.318942308426 seconds
Summary: lines - 1259, stops - 8291
ℹ️ 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