Public Transport Validation Results for Russia_Leningradskaya Oblast_Karelsky
⚠️ Warnings
Relation 1952739 dropped platforms: node 9961037628Relation 1959043 dropped platforms: node 1583073731
Relation 1959043 has parsed only 26/27 platform names
Relation 1959047 dropped platforms: node 1574916436
Relation 1959047 has parsed only 29/30 platform names
Relation 1968364 dropped platforms: node 1574916436
Relation 1968364 has parsed only 16/17 platform names
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 2015609 dropped platforms: node 2102040725
Relation 2015609 has parsed only 26/27 platform names
Relation 2195944 dropped platforms: node 356057596
Relation 2195944 has parsed only 14/15 platform names
Relation 2584508 has not enough platforms
Relation 2625747 has parsed only 37/43 platform names
Relation 2625748 dropped platforms: node 2613970952
Relation 2625748 has parsed only 10/11 platform names
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 3535235 has parsed only 7/8 platform names
Relation 3535236 has parsed only 7/8 platform names
Relation 3546376 has parsed only 6/9 platform names
Relation 3546377 has parsed only 6/8 platform names
Relation 3546882 has parsed only 42/44 platform names
Relation 3546883 has parsed only 43/45 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 3814115 dropped platforms: node 2615344361
Relation 3814115 has parsed only 20/22 platform names
Relation 3814116 has parsed only 22/23 platform names
Relation 3814865 has parsed only 41/42 platform names
Relation 3814866 has parsed only 38/39 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 21/22 platform names
Relation 4121394 has parsed only 7/9 platform names
Relation 4260141 has parsed only 6/7 platform names
Relation 5401057 dropped platforms: node 2102040725
Relation 5401057 has parsed only 66/69 platform names
Relation 5869766 has parsed only 16/18 platform names
Relation 5869767 has parsed only 17/19 platform names
Relation 6101776 dropped platforms: node 2615344361
Relation 6101776 has parsed only 33/35 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 6153342 has parsed only 4/6 platform names
Relation 6167465 has parsed only 36/37 platform names
Relation 6167466 has parsed only 31/32 platform names
Relation 8780087 dropped platforms: node 257414217
Relation 8780087 has parsed only 5/6 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 11133618 dropped platforms: node 6297598488
Relation 11133618 has parsed only 36/41 platform names
Relation 11200712 has parsed only 16/18 platform names
Relation 12405336 has parsed only 13/14 platform names
Relation 12405337 has parsed only 14/15 platform names
Relation 13223410 has parsed only 1/2 platform names
Relation 13234628 has parsed only 12/13 platform names
Relation 13919837 dropped platforms: node 2705661011
Relation 13919837 has parsed only 5/6 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 14532806 has parsed only 6/7 platform names
Relation 14532807 has parsed only 6/7 platform names
Relation 14600034 has parsed only 10/11 platform names
Relation 14600035 has parsed only 10/11 platform names
Relation 14601739 has parsed only 12/14 platform names
Relation 14601740 has parsed only 11/13 platform names
Relation 14601741 has parsed only 11/12 platform names
Relation 14601743 has parsed only 11/12 platform names
Relation 14715399 has parsed only 18/19 platform names
Relation 14715400 has parsed only 17/18 platform names
Relation 14715663 has parsed only 2/3 platform names
Relation 14715664 has parsed only 2/3 platform names
Relation 15261335 has parsed only 26/27 platform names
Relation 15261428 has parsed only 24/25 platform names
Relation 17222766 has parsed only 2/3 platform names
Relation 17222767 has parsed only 4/5 platform names
Relation 18310349 has parsed only 10/11 platform names
Relation 18310350 has parsed only 10/11 platform names
Relation 18661663 dropped platforms: node 9586006265
Relation 18661663 has parsed only 3/4 platform names
Relation 18661664 dropped platforms: node 9586006265
Relation 18661664 has parsed only 3/4 platform names
Relation 18933150 has parsed only 14/15 platform names
Relation 18933151 has parsed only 13/14 platform names
Relation 18933152 has parsed only 13/14 platform names
Relation 18933153 has parsed only 14/15 platform names
Relation 18933157 has parsed only 12/13 platform names
Relation 18933158 has parsed only 12/13 platform names
Relation 19200169 has parsed only 10/11 platform names
Relation 19200170 has parsed only 10/11 platform names
Relation 19359575 has parsed only 43/45 platform names
Relation 19359576 has parsed only 44/46 platform names
Relation 19359578 has parsed only 46/49 platform names
Relation 19359579 has parsed only 45/48 platform names
Relation 19359587 has parsed only 44/46 platform names
Relation 19359588 has parsed only 45/47 platform names
Relation 19415930 has parsed only 16/18 platform names
Relation 19415931 has parsed only 15/17 platform names
Relation 19415932 has parsed only 20/22 platform names
Relation 19415933 has parsed only 20/21 platform names
Relation 19684993 has parsed only 11/12 platform names
Relation 19684994 has parsed only 11/12 platform names
Finished in 1386.7504014968872 seconds
Summary: lines - 418, stops - 2858
ℹ️ 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