OSM Inspector/Views/Public Transport - Routes

From OpenStreetMap Wiki
Jump to: navigation, search

The Public Transport - Routes view in OSM Inspector shows routes which claim to be routes according to the version 2 of the Public Transport tagging schema.

From 2017-10-09 on, this view is based on the schema version 2 (previously the abandoned proposal by user Oxomoa).

Overview

This view shows routes and validation results of all route relations with public_transport:version=2 and route=train/tram/subway/bus/trolleybus/ferry/aerialway.

The OSM data processing of this view is done by osmi_pubtrans3.

Limitations

The validation engine begin used does only check for a few important errors.


Data sources

All data in this view is derived from OSM data.

Layers

PTv2 route relations

Valid Routes shows route relations which pass all critical validation tests. There are a few tests which route relations are allowed to fail, e.g. tagging of stop positions/platforms.

Invalid Routes shows route relations which fail at least one critical validation test. See below for a list of all checks.

PTv2 route relations errors

Errorneous ways shows member ways of route relations which cause a test to fail or which are next to a gap in the route.

Errorneous nodes shows member nodes of route relations which cause a test to fail or which are an open end in the route (near a gap).

Validation Tests

The railways over railway test checks if a route for a tram, train or subway uses an unsuitable way for that type of vehicle, e.g. a train route running over a railway=construction or way without railway=*.

The road vehicle over road test checks if a route for a bus or trolleybus but uses an unsuitable way for that type of vehicle, e.g. a bus route running over a highway=construction or way without a valid value of highway=*.

The gap and order test checks if a route has gaps or is not ordered properly. The highway/railway members of PTv2 routes must be ordered. The code which does the check does not differ between gaps and wrongly ordered members. If a route is ordered randomly, the code will report lots of "gaps".

The route has way members test checks if a route contains of more than just a collection of stops and platforms.

The general structure test checks if the overall structure of the member list is ok. A route must begin with an ordered list of stops and platforms. The order of stops and platforms is not checked but there must be no highway/railway member before any stop/platform in the list and no stop/platform after a highway/railway member.

The role and type test checks if the roles and types (node/way/relation) of the members is ok.

  • Nodes must have only one of the following roles: stop, stop_entry_only, stop_exit_only, platform, platform_entry_only, platform_exit_only
  • Ways must have only one of the following roles: platform, platform_entry_only, platform_exit_only, empty role
  • Relations must have only one of the following roles: platform, platform_entry_only, platform_exit_only

The platform proper tags test' checks if a platform which is used by a route relation of type X (route=X has the tag X=yes. For example, all platforms of train routes must have train=yes.

Discussion

See also