London public transport tagging scheme
The London public transport tagging scheme has slightly tougher standards to encourage completeness.
To conserve the length of this article, the tables below omit NaPTAN-related tags: they should still be included with the appropriate objects, when known.
The following pages may be useful for finding the current status on London's routes:
- Docklands Light Railway
- Elizabeth line
- London Buses
- London Overground
- London Trams
- London Underground
You may also want to refer to:
- Public transport: Overview of the public transport scheme.
- Proposed features/Public Transport: Detail of the public transport scheme.
Nodes
Bus stop
A bus stop must belong to the relevant stop area relation with the role "platform".
Please continue to use highway=bus_stop with public_transport=platform, because the standard layer does not render the latter yet.
Key | Values | Notes |
---|---|---|
![]() | ||
public_transport | platform | Mandatory. |
highway | bus_stop | Mandatory. This is required to ensure that the bus stop will be rendered. |
bus | yes | Mandatory. |
name | Name | Mandatory. This is the name of the bus stop. It is normally displayed on the bus stop flag.
|
ref | Bus Stop Code | Mandatory if it exists. Ignore this tag if there is no Bus Stop Code. This is a five-digit code. It is normally displayed on a plate or sign, attached to the bus stop. See TfL’s page for information about the bus stop codes.
|
local_ref | Bus Stop ID | Mandatory if it exists. Ignore this tag if there is no Bus Stop ID. This is a one or two character ID. It is normally displayed in a red circle on the top of the bus stop flag.
|
network | Network | Optional. If this is specified then it must match the Network in the parent stop area relation. |
operator | Operator | Optional. If this is specified then it must match the Operator in the parent stop area relation. |
Examples | ![]() ![]() |
Station or tram stop
A station or tram stop must belong to the relevant stop area relation, but it does not require a role.
Key | Values | Notes | ||
---|---|---|---|---|
Multimodal[1] | ![]() ![]() ![]() ![]() ![]() |
![]() | ||
public_transport | station | station | station | Mandatory. |
railway | station | station | tram_stop | Mandatory. |
subway, train, etc.[3] | yes | yes | Not used | Mandatory. These tags refer to the mode of transport that the station or tram stop serves. |
tram | Not used | Not used | yes | |
name | Name | Name | Name | Mandatory. Use the most common name. |
name:<mode>[3] | Mode-specific name | Not used | Not used | |
network | Not used | Network | London Trams | Mandatory. Use semicolons for multiple values. |
network:<mode>[3] | Mode-specific network | Not used | Not used | |
operator | Operator of station | Operator of station | Transport for London | Mandatory. Main operator of station (e.g. Transport for London, Southeastern) |
ref | Not used | Reference | Not used | Optional. Ignore this tag if there are no station codes. |
ref:<mode>[3] | Mode-specific reference | Not used | Not used | |
wheelchair | yes/no/limited | yes/no/limited | yes/no/limited | Optional. This tag describes wheelchair accessibility for the platform: |
addr:housename | Building name | Building name | Building name | Optional. Ignore these tags if there is no address. |
addr:housenumber | Street number | Street number | Street number | |
addr:street | Street | Street | Street | |
addr:postcode | Postcode | Postcode | Postcode | |
Examples | 6414163635![]() |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
![]() ![]() |
Station entrance
A station entrance must belong to the relevant stop area relation, but it does not require a role.
Key | Values | Notes |
---|---|---|
![]() ![]() ![]() ![]() ![]() | ||
railway | subway_entrance | Mandatory. |
bicycle | dismount | Optional. TfL rail services allow folded bicycles at all times. For unfolded bicycles:
|
bicycle:conditional | Two possible values, see notes | |
oneway | yes | Optional. Ignore this tag if it does not apply. |
ref | Exit number or letter | Optional. Ignore this tag if it does not apply. |
wheelchair | yes/no | Optional.
|
Examples | ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Stop position
A stop position must belong to the relevant stop area relation with the role "stop".
Key | Values | Notes | ||
---|---|---|---|---|
![]() ![]() ![]() ![]() ![]() |
![]() |
![]() | ||
public_transport | stop_position | stop_position | stop_position | Mandatory. |
railway | stop | tram_stop | Not used | Mandatory. |
subway, train, etc.[3] | yes | Not used | Not used | Mandatory. These tags describe the modes of transport that serve this stop position. |
tram | Not used | yes | Not used | |
bus | Not used | Not used | yes | |
name | Name and platform number or letter | Name and platform number or letter | Name | Mandatory. Use the most appropriate name for the given mode.
|
ref | Platform number or letter | Platform number or letter | Not used | Mandatory.
|
local_ref | Not used | Not used | Bus Stop ID | Mandatory if it exists. Ignore this tag if there is no Bus Stop ID. This is a one or two character ID. It is normally displayed in a red circle on the top of the bus stop flag.
|
Examples | ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
![]() ![]() |
![]() ![]() |
Ways
Bus station
A bus station must belong to the relevant stop area relation, but it does not require a role.
Key | Values | Notes |
---|---|---|
![]() | ||
public_transport | station | Mandatory. |
amenity | bus_station | Mandatory. |
name | Name | Mandatory. |
network | London Buses | Mandatory. |
operator | Transport for London | Mandatory. |
addr:housename | Building name | Optional. Ignore these tags if there is no address. |
addr:housenumber | Street number | |
addr:street | Street | |
addr:postcode | Postcode | |
Examples | ![]() ![]() |
Bus station building or bus stop building
A bus station building or bus stop building must belong to the relevant stop area relation, but it does not require a role.
Key | Values | Notes |
---|---|---|
![]() | ||
building | transportation roof |
Mandatory. Choose one of the suggested values that accurately describes the feature. |
Examples | ![]() ![]() |
Rail platform
A rail platform must belong to the relevant stop area relation with the role "platform". For bus stops, see section Bus stop.
Please continue to use railway=platform with public_transport=platform, because the standard layer does not render the latter yet.
Key | Values | Notes |
---|---|---|
![]() ![]() ![]() ![]() ![]() ![]() | ||
public_transport | platform | Mandatory. |
railway | platform | Mandatory. This is required to ensure that the platform will be rendered. |
subway, train, etc.[3] | yes | Mandatory. These tags describe the modes of transport that serve this platform. |
area | yes | Mandatory if the platform is a polygon. |
name | Name and platform number or letter | Mandatory.
|
ref | Platform number or letter | Mandatory.
|
wheelchair | yes/no/limited | Optional. This tag describes wheelchair accessibility for the platform:
|
Examples | ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Station area or tram stop area
A station area or tram stop area must belong to the relevant stop area relation, but it does not require a role. Gradually, station areas or tram stop areas will hold station information by default, unless the station building or tram stop building covers the entire area: the change is to help users understand the extent of the stations, especially when it is either underground or there are two main station buildings (e.g. Willesden Junction).
Key | Values | Notes | ||
---|---|---|---|---|
Multimodal[1] | ![]() ![]() ![]() ![]() ![]() |
![]() | ||
public_transport | station | station | station | Mandatory. |
railway | station | station | tram_stop | Mandatory. |
subway, train, etc.[3] | yes | yes | Not used | Mandatory. These tags refer to the mode of transport that the station or tram stop serves. |
tram | Not used | Not used | yes | |
area | yes | yes | yes | Mandatory. |
name | Name | Name | Name | Mandatory. Use the most common name. |
name:<mode>[3] | Mode-specific name | Not used | Not used | |
network | Not used | Network | London Trams | Mandatory. Use semicolons for multiple values. |
network:<mode>[3] | Mode-specific network | Not used | Not used | |
operator | Operator of station | Operator of station | Transport for London | Mandatory. Main operator of station (e.g. Transport for London, Southeastern) |
ref | Not used | Reference | Not used | Optional. Ignore this tag if there are no station codes. |
ref:<mode>[3] | Mode-specific reference | Not used | Not used | |
wheelchair | yes/no/limited | yes/no/limited | yes/no/limited | Optional. This tag describes wheelchair accessibility for the platform: |
addr:housename | Building name | Building name | Building name | Optional. Ignore these tags if there is no address. |
addr:housenumber | Street number | Street number | Street number | |
addr:street | Street | Street | Street | |
addr:postcode | Postcode | Postcode | Postcode | |
Examples | |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
![]() |
Station building or tram stop building
A station building or tram stop building must belong to the relevant stop area relation, but it does not require a role.
By default, the main station building (if there is one) should not hold station information: the exception is where they cover the entire station area, such as at Pudding Mill Lane. See above for more information on the change.
Key | Values | Notes |
---|---|---|
![]() ![]() ![]() ![]() ![]() ![]() | ||
building | transportation roof |
Mandatory. Choose one of the suggested values that accurately describes the feature. |
Examples | ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Relations
Stop area
The page Tag:public_transport=stop_area states that the public_transport=stop_area tag is used as part of a relation to identify all of the features associated with a public transport interchange or part of one. A stop area for a simple bus stop with buses in both directions would consist of two waiting areas or shelters (tagged using public_transport=platform and highway=bus_stop) and two stop positions (tagged using public_transport=stop_position). More complex stop areas may include multiple platforms and stop positions and many associated elements. For larger interchanges it is often appropriate to organise stop areas into a hierarchy.
Key | Values | Notes | ||
---|---|---|---|---|
Multimodal[1] | ![]() ![]() ![]() ![]() ![]() |
![]() ![]() | ||
type | public_transport | public_transport | public_transport | Mandatory. |
public_transport | stop_area | stop_area | stop_area | Mandatory. |
public_transport:version | 2 | 2 | 2 | Mandatory. |
name | Name | Name | Name | Mandatory. Use the most common name. |
name:<mode>[3] | Mode-specific name | Not used | Not used | |
network | Network | Network | Network | Mandatory. Use semicolons for multiple values. |
network:<mode>[3] | Mode-specific network | Not used | Not used | |
operator | Operator | Operator | Operator | Mandatory. Main operator of station (e.g. Transport for London, Southeastern). |
ref | Not used | Reference | Not used | Optional. Ignore this tag if there are no station codes. |
ref:<mode>[3] | Mode-specific reference | Not used | Not used | |
Examples | 9746604![]() |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
![]() ![]() ![]() ![]() |
Networks
Docklands Light Railway
Route network
There is a single Route Network relation that lists all of the routes. The members of the Route Network relation are Route Masters with no role. The Route Masters are ordered by name.
Key | Values | Notes |
---|---|---|
![]() | ||
type | network | Mandatory. |
brand | Transport for London | Mandatory. |
light_rail | yes | Mandatory. |
name | Docklands Light Railway | Mandatory. |
network | Docklands Light Railway | Mandatory. |
operator | KeolisAmey Docklands Ltd | Mandatory. |
short_name | DLR | Mandatory. |
Examples | ![]() ![]() |
The relation is a good starting point for exploring the network. |
Route master
Docklands Light Railway routes have a route_master relation structure that consists of individual route relations for each direction or variant.
In most cases, such routes will have one route_master and two routes.
Key | Values | Notes |
---|---|---|
![]() | ||
type | route_master | Mandatory. |
route_master | light_rail | Mandatory. |
name | DLR: Route Name | Mandatory. This is a descriptive route name.
|
network | Network | Mandatory. This must match the Network in the parent route network relation. |
ref | Route Reference | Mandatory. This is the route reference.
|
wheelchair | yes/no | Mandatory. This describes wheelchair accessibility for the trains on the route. |
brand | Brand | Optional. If this is specified then it must match the Brand in the parent route network relation. |
operator | Operator | Optional. If this is specified then it must match the Operator in the parent route network relation. |
Examples | ![]() ![]() |
Route
Routes must belong to the relevant route master, but it does not usually require a role. Routes consist of platforms, stop positions and appropriately ordered ways.
For the platforms, use the role "platform_entry_only" for the first platform, "platform_exit_only" for the last platform, and "platform" for all other platforms.
For the stop positions, use the role "stop_entry_only" for the first stop position, "stop_exit_only" for the last stop position, and "stop" for all other stop positions.
The ways do not require a role.
Key | Values | Notes |
---|---|---|
![]() | ||
type | route | Mandatory. |
route | light_rail | Mandatory. |
public_transport:version | 2 | Mandatory. |
from | First Station Name | Mandatory. This is the name of the first station on the route.
|
name | DLR: Route Name | Mandatory. This is a descriptive route name.
|
network | Network | Mandatory. This must match the Network in the parent route master relation. |
ref | Route Reference | Mandatory. This must match the Route Reference in the parent route master relation. |
to | Last Station Name | Mandatory. This is the name of the last station on the route.
|
brand | Brand | Optional. If this is specified then it must match the Brand in the parent route master relation. |
operator | Operator | Optional. If this is specified then it must match the Operator in the parent route master relation. |
wheelchair | yes/no | Optional. If this is specified then it must match the wheelchair tag in the parent route master relation. |
Examples | ![]() ![]() ![]() ![]() |
Elizabeth line
Route network
There is a single Route Network relation that lists all of the routes. The members of the Route Network relation are Route Masters with no role. The Route Masters are ordered by name.
Key | Values | Notes |
---|---|---|
![]() | ||
type | network | Mandatory. |
brand | Transport for London | Mandatory. |
name | Elizabeth line | Mandatory. |
network | National Rail | Mandatory. |
operator | MTR Elizabeth line | Mandatory. |
train | yes | Mandatory. |
Examples | ![]() ![]() |
The relation is a good starting point for exploring the network. |
Route master
Elizabeth line routes have a route_master relation structure that consists of individual route relations for each direction or variant.
In most cases, such routes will have one route_master and two routes.
Key | Values | Notes |
---|---|---|
![]() | ||
type | route_master | Mandatory. |
route_master | train | Mandatory. |
name | Elizabeth line: Route Name | Mandatory. This is a descriptive route name.
|
network | Network | Mandatory. This must match the Network in the parent route network relation. |
ref | Route Reference | Mandatory. This is the route reference.
|
wheelchair | yes/no | Mandatory. This describes wheelchair accessibility for the trains on the route. |
brand | Brand | Optional. If this is specified then it must match the Brand in the parent route network relation. |
operator | Operator | Optional. If this is specified then it must match the Operator in the parent route network relation. |
Examples | ![]() ![]() |
Route
Routes must belong to the relevant route master, but it does not usually require a role. Routes consist of platforms, stop positions and appropriately ordered ways.
For the platforms, use the role "platform_entry_only" for the first platform, "platform_exit_only" for the last platform, and "platform" for all other platforms.
For the stop positions, use the role "stop_entry_only" for the first stop position, "stop_exit_only" for the last stop position, and "stop" for all other stop positions.
The ways do not require a role.
Key | Values | Notes |
---|---|---|
![]() | ||
type | route | Mandatory. |
route | train | Mandatory. |
public_transport:version | 2 | Mandatory. |
from | First Station Name | Mandatory. This is the name of the first station on the route.
|
name | Elizabeth line: Route Name | Mandatory. This is a descriptive route name.
|
network | Network | Mandatory. This must match the Network in the parent route master relation. |
ref | Route Reference | Mandatory. This must match the Route Reference in the parent route master relation. |
to | Last Station Name | Mandatory. This is the name of the last station on the route.
|
brand | Brand | Optional. If this is specified then it must match the Brand in the parent route master relation. |
operator | Operator | Optional. If this is specified then it must match the Operator in the parent route master relation. |
wheelchair | yes/no | Optional. If this is specified then it must match the wheelchair tag in the parent route master relation. |
Examples | ![]() ![]() ![]() ![]() |
London Buses
Route network
There is a single Route Network relation that lists all of the routes. The members of the Route Network relation are Route Masters with no role. The Route Masters are ordered by name.
Key | Values | Notes |
---|---|---|
![]() | ||
type | network | Mandatory. |
brand | Transport for London | Mandatory. |
bus | yes | Mandatory. |
name | London Buses | Mandatory. |
network | London Buses | Mandatory. London Buses is a subsidiary of Transport for London that manages London's bus network. |
operator | London Buses | Mandatory. |
Examples | ![]() ![]() |
The relation is a good starting point for exploring the network. |
Route master
London bus routes have a route_master relation structure that consists of individual route relations for each direction or variant, and the depot that provides the buses.
In most cases, a bus route will have one route_master, two routes, and one depot.
The route master relation name uses the ‘London Buses route n’ format to reflect Transport for London's tone of language: firstly, TfL refers to routes as route n (e.g. route 39 or route 6).[4] Secondly, TfL discourages using ‘Buses’ alone when referring to London Buses.[5]
Key | Values | Notes |
---|---|---|
![]() | ||
type | route_master | Mandatory. |
route_master | bus | Mandatory. |
name | London Buses route Route Number | Mandatory. This is a descriptive route name.
|
network | Network | Mandatory. This must match the Network in the parent route network relation. |
operator | Route Operator | Mandatory. This is the name of the bus route operator.
|
ref | Route Number | Mandatory. This is the route number.
|
wheelchair | yes/no | Mandatory. This describes wheelchair accessibility for the buses on the route. |
brand | Brand | Optional. If this is specified then it must match the Brand in the parent route network relation. |
Examples | ![]() ![]() |
Route
Routes must belong to the relevant route master, but it does not usually require a role. Routes consist of bus stops, stop positions and appropriately ordered ways.
For the bus stops, use the role "platform_entry_only" for the first bus stop, "platform_exit_only" for the last bus stop, and "platform" for all other bus stops.
For the stop positions, use the role "stop_entry_only" for the first stop position, "stop_exit_only" for the last stop position, and "stop" for all other stop positions.
The ways do not require a role. JOSM can handle the ordering of ways in route relations better than Potlatch, but if a route uses the same way more than once, then you will have to order them manually and add a note (as described) to advise other editors of the circumstances.
The ways included in a route should only be between the first bus stop and the last bus stop. The route should not include the ways that represent any bus travel between the end bus stops and a bus stand or depot. This is because, including these 'not in service' extensions to the normal route, would create ambiguity about where a bus route starts and finishes. It has been suggested that these 'not in service' extensions should be included and tagged differently, so that renderers can show this information appropriately. Until a convention is agreed for this, these 'not in service' extensions should not be mapped.
Key | Values | Notes |
---|---|---|
![]() | ||
type | route | Mandatory. |
route | bus | Mandatory. |
public_transport:version | 2 | Mandatory. |
from | First Bus Stop Name | Mandatory. This is the name of the first bus stop on the route.
|
name | London Buses route Route Number → Destination | Mandatory. This is a descriptive route name.
|
network | Network | Mandatory. This must match the Network in the parent route master relation. |
note | Intricate relation - do not auto-sort. | Mandatory if a route uses a way more than once. Only use this tag if a route uses a way more than once (example ![]() ![]() |
ref | Route Number | Mandatory. This must match the Route Number in the parent route master relation. |
to | Last Bus Stop Name | Mandatory. This is the name of the last bus stop on the route.
|
brand | Brand | Optional. If this is specified then it must match the Brand in the parent route master relation. |
operator | Route Operator | Optional. If this is specified then it must match the Route Operator in the parent route master relation. |
wheelchair | yes/no | Optional. If this is specified then it must match the wheelchair tag in the parent route master relation. |
Examples | ![]() ![]() ![]() ![]() |
London Overground
Route network
There is a single Route Network relation that lists all of the routes. The members of the Route Network relation are Route Masters with no role. The Route Masters are ordered by name.
Key | Values | Notes |
---|---|---|
![]() | ||
type | network | Mandatory. |
brand | Transport for London | Mandatory. |
name | London Overground | Mandatory. |
network | National Rail | Mandatory. |
operator | Arriva Rail London | Mandatory. |
short_name | Overground | Mandatory. |
train | yes | Mandatory. |
Examples | ![]() ![]() |
The relation is a good starting point for exploring the network. |
Route master
London Overground routes have a route_master relation structure that consists of individual route relations for each direction or variant.
In most cases, such routes will have one route_master and two routes.
Key | Values | Notes |
---|---|---|
![]() | ||
type | route_master | Mandatory. |
route_master | train | Mandatory. |
name | Overground: Route Name | Mandatory. This is a descriptive route name.
|
network | Network | Mandatory. This must match the Network in the parent route network relation. |
ref | Route Reference | Mandatory. This is the route reference.
|
wheelchair | yes/no | Mandatory. This describes wheelchair accessibility for the trains on the route. |
brand | Brand | Optional. If this is specified then it must match the Brand in the parent route network relation. |
operator | Operator | Optional. If this is specified then it must match the Operator in the parent route network relation. |
Examples | ![]() ![]() |
Route
Routes must belong to the relevant route master, but it does not usually require a role. Routes consist of platforms, stop positions and appropriately ordered ways.
For the platforms, use the role "platform_entry_only" for the first platform, "platform_exit_only" for the last platform, and "platform" for all other platforms.
For the stop positions, use the role "stop_entry_only" for the first stop position, "stop_exit_only" for the last stop position, and "stop" for all other stop positions.
The ways do not require a role.
Key | Values | Notes |
---|---|---|
![]() | ||
type | route | Mandatory. |
route | train | Mandatory. |
public_transport:version | 2 | Mandatory. |
from | First Station Name | Mandatory. This is the name of the first station on the route.
|
name | Overground: Route Name | Mandatory. This is a descriptive route name.
|
network | Network | Mandatory. This must match the Network in the parent route master relation. |
ref | Route Reference | Mandatory. This must match the Route Reference in the parent route master relation. |
to | Last Station Name | Mandatory. This is the name of the last station on the route.
|
brand | Brand | Optional. If this is specified then it must match the Brand in the parent route master relation. |
operator | Operator | Optional. If this is specified then it must match the Operator in the parent route master relation. |
wheelchair | yes/no | Optional. If this is specified then it must match the wheelchair tag in the parent route master relation. |
Examples | ![]() ![]() ![]() ![]() |
London Trams
Route network
There is a single Route Network relation that lists all of the routes. The members of the Route Network relation are Route Masters with no role. The Route Masters are ordered by route number.
Key | Values | Notes |
---|---|---|
![]() | ||
type | network | Mandatory. |
brand | Transport for London | Mandatory. |
name | London Trams | Mandatory. |
network | London Trams | Mandatory. London Trams is the arm of Transport for London that manages London's tram network. |
operator | Tram Operations Ltd | Mandatory. |
tram | yes | Mandatory. |
Examples | ![]() ![]() |
The relation is a good starting point for exploring the network. |
Route master
London Trams routes have a route_master relation structure that consists of individual route relations for each direction or variant.
In most cases, such routes will have one route_master and two routes.
Key | Values | Notes |
---|---|---|
![]() | ||
type | route_master | Mandatory. |
route_master | tram | Mandatory. |
name | London Trams: Route Name | Mandatory. This is a descriptive route name.
|
network | Network | Mandatory. This must match the Network in the parent route network relation. |
ref | Route Reference | Mandatory. This is the route reference. Currently the route reference is the original route number (1-4), although route numbers are no longer displayed on the destination dot matrix displays of the trams.
|
wheelchair | yes/no | Mandatory. This describes wheelchair accessibility for the trams on the route. |
brand | Brand | Optional. If this is specified then it must match the Brand in the parent route network relation. |
operator | Operator | Optional. If this is specified then it must match the Operator in the parent route network relation. |
Examples | ![]() ![]() |
Route
Routes must belong to the relevant route master, but it does not usually require a role. Routes consist of tram stop platforms, stop positions and appropriately ordered ways.
For the tram stop platforms, use the role "platform_entry_only" for the first tram stop platform, "platform_exit_only" for the last tram stop platform, and "platform" for all other tram stop platforms.
For the stop positions, use the role "stop_entry_only" for the first stop position, "stop_exit_only" for the last stop position, and "stop" for all other stop positions.
The ways do not require a role.
Key | Values | Notes |
---|---|---|
![]() | ||
type | route | Mandatory. |
route | tram | Mandatory. |
public_transport:version | 2 | Mandatory. |
from | First Tram Stop Name | Mandatory. This is the name of the first tram stop on the route.
|
name | London Trams: Route Name | Mandatory. This is a descriptive route name.
|
network | Network | Mandatory. This must match the Network in the parent route master relation. |
ref | Route Reference | Mandatory. This must match the Route Reference in the parent route master relation. |
to | Last Tram Stop Name | Mandatory. This is the name of the last tram stop on the route.
|
brand | Brand | Optional. If this is specified then it must match the Brand in the parent route master relation. |
operator | Operator | Optional. If this is specified then it must match the Operator in the parent route master relation. |
wheelchair | yes/no | Optional. If this is specified then it must match the wheelchair tag in the parent route master relation. |
Examples | ![]() ![]() ![]() ![]() |
London Underground
Route network
There is a single Route Network relation that lists all of the routes. The members of the Route Network relation are Route Masters with no role. The Route Masters are ordered by name.
Key | Values | Notes |
---|---|---|
![]() | ||
type | network | Mandatory. |
brand | Transport for London | Mandatory. |
name | London Underground | Mandatory. |
network | London Underground | Mandatory. London Underground is a subsidiary of Transport for London that manages London's underground rail network. |
operator | London Underground | Mandatory. |
subway | yes | Mandatory. |
Examples | ![]() ![]() |
The relation is a good starting point for exploring the network. |
Route master
London Underground routes have a route_master relation structure that consists of individual route relations for each direction or variant.
In most cases, such routes will have one route_master and two routes.
Key | Values | Notes |
---|---|---|
![]() | ||
type | route_master | Mandatory. |
route_master | subway | Mandatory. |
name | Route Name | Mandatory. This is a descriptive route name.
|
network | Network | Mandatory. This must match the Network in the parent route network relation. |
ref | Route Reference | Mandatory. This is the route reference.
|
wheelchair | yes/no | Mandatory. This describes wheelchair accessibility for the trains on the route. |
brand | Brand | Optional. If this is specified then it must match the Brand in the parent route network relation. |
operator | Operator | Optional. If this is specified then it must match the Operator in the parent route network relation. |
Examples | ![]() ![]() |
Route
Routes must belong to the relevant route master, but it does not usually require a role. Routes consist of platforms, stop positions and appropriately ordered ways.
For the platforms, use the role "platform_entry_only" for the first platform, "platform_exit_only" for the last platform, and "platform" for all other platforms.
For the stop positions, use the role "stop_entry_only" for the first stop position, "stop_exit_only" for the last stop position, and "stop" for all other stop positions.
The ways do not require a role.
Key | Values | Notes |
---|---|---|
![]() | ||
type | route | Mandatory. |
route | subway | Mandatory. |
public_transport:version | 2 | Mandatory. |
from | First Station Name | Mandatory. This is the name of the first station on the route.
|
name | Route Name | Mandatory. This is a descriptive route name.
|
network | Network | Mandatory. This must match the Network in the parent route master relation. |
ref | Route Reference | Mandatory. This must match the Route Reference in the parent route master relation. |
to | Last Station Name | Mandatory. This is the name of the last station on the route.
|
brand | Brand | Optional. If this is specified then it must match the Brand in the parent route master relation. |
operator | Operator | Optional. If this is specified then it must match the Operator in the parent route master relation. |
wheelchair | yes/no | Optional. If this is specified then it must match the wheelchair tag in the parent route master relation. |
Examples | ![]() ![]() ![]() ![]() |
Further tags
Network, operator and brand
The following values for network are recommended:
Docklands Light Railway London Buses London Cable Car London River Services London Trams London Underground National Rail
London Trams was previously Tramlink and Croydon Tramlink.
London Overground and Elizabeth line are brand names for the concession in the National Rail network, tendered by TfL and currently operated by Arriva Rail London and MTR Elizabeth line respectively.
The use of network=TfL or network="Transport for London" is not recommended. Instead, for rails/stations/routes operated by Transport for London, use:
operator="Transport for London"
Where services are branded "Transport for London" (such as Docklands Light Railway, Elizabeth line, London Overground, London Trams and London Underground), use:
brand="Transport for London"
see Key:brand.
Get stuck in and help improve London public transport on OpenStreetMap
- London public transport tagging scheme/Map Challenges
- London public transport tagging scheme/Examples - some examples that query OSM data using the public transport scheme. Helpful to see what's been implemented already.
Notes
- ↑ 1.0 1.1 1.2 Example of multi-modal stations: stations between Queen's Park and Harrow & Wealdstone (Overground and Underground).
- ↑ 2.0 2.1 Except at Wimbledon, which is inside a multimodal station.
- ↑ 3.00 3.01 3.02 3.03 3.04 3.05 3.06 3.07 3.08 3.09 3.10 3.11 3.12 The correct values for each mode are as follows: aerialway for London Cable Car; bus for London Buses; light_rail for Docklands Light Railway; subway for London Underground; train for Elizabeth line, London Overground and National Rail; tram for London Trams.
- ↑ Oxford Street closed eastbound, p.2 (accessed 23 August 2014).
- ↑ TfL’s editorial style guide, p.37 (accessed 23 August 2014).