Public Transport Validation Results for Russia_Omsk Oblast
⚠️ Warnings
Relation 2909863 has parsed only 32/34 platform namesRelation 2909863 has node 11436651842 as platform while node itself is not platform
Relation 2909863 has node 11463146040 as platform while node itself is not platform
Relation 4252676 dropped platforms: node 2795673815
Relation 4252676 has parsed only 45/46 platform names
Relation 4504619 has parsed only 29/32 platform names
Relation 4504619 has node 11436651841 as platform while node itself is not platform
Relation 4504619 has node 11436633920 as platform while node itself is not platform
Relation 4504619 has node 11368014063 as platform while node itself is not platform
Relation 4635728 dropped platforms: node 2794807687
Relation 4635728 has parsed only 49/50 platform names
Trajectory of relation 8797303 is not continuous after way 1365617971. Selected next edge: way 1336919716
Relation 8797303 has parsed only 40/41 platform names
Relation 8812667 dropped platforms: node 3177720655
Relation 8812667 has parsed only 50/51 platform names
Relation 8822958 dropped platforms: node 5991287476
Relation 8822958 has parsed only 50/51 platform names
Relation 8830105 dropped platforms: node 5991287476
Relation 8830105 has parsed only 41/42 platform names
Relation 8836058 dropped platforms: node 1190556639
Relation 8836058 has parsed only 47/48 platform names
Trajectory of relation 8858282 is not continuous after way 608535838. Next edge was not found!
Relation 8858282 dropped segments: way 1240954682, way 1240954683, way 1337239851, way 1337239854, way 628395554, way 72183881, way 72183944
Relation 8858282 dropped platforms: node 5158681450
Relation 8858282 has parsed only 46/47 platform names
Trajectory of relation 8858283 is not continuous after way 95916693. Next edge was not found!
Relation 8858283 dropped segments: way 1240954682, way 1240954683, way 1337239851, way 1337239854, way 628395554, way 72183881, way 72183944
Relation 8858283 dropped platforms: node 5158681451
Relation 8858283 has parsed only 43/44 platform names
Relation 8858775 has parsed only 27/28 platform names
Relation 8858776 has parsed only 29/30 platform names
Relation 8858784 dropped platforms: node 2794807687
Relation 8858784 has parsed only 30/31 platform names
Relation 16175683 dropped platforms: node 11099445152, node 2794230335, node 2794232043, node 2794233673
Relation 16175683 has parsed only 71/72 platform names
Trajectory of relation 18320544 is not continuous after way 58784807. Selected next edge: way 309693127
Trajectory of relation 18324208 is not continuous after way 58784807. Selected next edge: way 309693127
Trajectory of relation 19025334 is not continuous after way 230328750. Selected next edge: way 263153263
Trajectory of relation 19025688 is not continuous after way 263153263. Selected next edge: way 230328750
Finished in 11840.14202785492 seconds
Summary: lines - 250, stops - 1561
ℹ️ 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