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.
Infrastructure
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 |
---|---|---|
Element | ||
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. Usually London Buses . If this is specified then it must be a subset of 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. |
route_ref | Routes serving the stop | Optional. Separated by ; Useful for local surveying without mapping the whole of the bus route at once.
|
Examples | 469787952 469787952 |
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 |
---|---|---|
Element | ||
public_transport | platform | Mandatory. |
railway | platform | Mandatory. This is required to ensure that the platform will be rendered. |
subway, train, etc.[1] | 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 | 170170622 170170622 796886903 796886903 170130361 170130361 203310408 203310408 158003540 158003540 418025655 418025655 |
Station
A station must belong to the relevant stop area relation, but it does not require a role.
Key | Values | Notes | |||
---|---|---|---|---|---|
Multimodal[2] | [3] | ||||
Element | |||||
public_transport | station | station | station | station | Mandatory. |
railway | station | station | tram_stop | Not used | Mandatory. |
amenity | Not used | Not used | Not used | bus_station | Mandatory. |
subway, train, etc.[1] | yes | yes | yes | yes | Mandatory. These tags refer to the mode of transport that the station or tram stop serves. |
name | Name | Name | Name | Name | Mandatory. Use the most common name. |
name:<mode>[1] | Mode-specific name | Not used | Not used | Not used | |
network | Network | Network | London Trams | London Buses | Mandatory. Use semicolons for multiple values. |
operator | Operator of station | Operator of station | Transport for London | Transport for London | Mandatory. Main operator of station (e.g. Transport for London, Southeastern) |
ref | Not used | Reference | Not used | Not used | Optional. Ignore this tag if there are no station codes. |
ref:<mode>[1] | Mode-specific reference | Not used | Not used | Not used | |
wheelchair | yes/no/limited | 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 | Building name | Optional. Ignore these tags if there is no address. |
addr:housenumber | Street number | Street number | Street number | Street number | |
addr:street | Street | Street | Street | Street | |
addr:postcode | Postcode | Postcode | Postcode | Postcode | |
Examples | 6414163635 6414163635 | 6143744010 6143744010 9754369244 9754369244 2446751285 2446751285 1651498764 1651498764 5871218007 5871218007 |
2864283848 2864283848 | 282348817 282348817 |
Station entrance
A station entrance must belong to the relevant stop area relation, but it does not require a role.
Key | Values | Notes |
---|---|---|
Element | ||
railway | subway_entrance | Mandatory. |
bicycle | dismount | Optional. TfL rail services allow folded bicycles at all times. For unfolded bicycles:
Use other values as appropriate if National Rail services have different restrictions. |
bicycle:conditional | Two possible values, see notes | |
name | Exit name signposted at the exit, not the station name. | Optional. Ignore this tag if it does not apply. |
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 | 2204808429 2204808429 2162923164 2162923164 2883647835 2883647835 2968832806 2968832806 |
Stop position
A stop position must belong to the relevant stop area relation with the role "stop".
Key | Values | Notes | ||
---|---|---|---|---|
Element | ||||
public_transport | stop_position | stop_position | stop_position | Mandatory. |
railway | stop | tram_stop | Not used | Mandatory. |
subway, train, etc.[1] | 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 | 1752783277 1752783277 9760735058 9760735058 1812313946 1812313946 1735704089 1735704089 4184900020 4184900020 |
60306534 60306534 |
4710628833 4710628833 |
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 |
---|---|---|
Element | ||
building | transportation roof |
Mandatory. Choose one of the suggested values that accurately describes the feature. |
Examples | 170221186 170221186 347263800 347263800 170130345 170130345 112605950 112605950 140162487 140162487 508440662 508440662 170706695 170706695 |
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. Stop positions and platforms should be placed in the same area if they generally have the same access - if a part of a station can be operated independently it should belong to a separate stop area (for example, the Underground and Elizabeth line stations of Bond Street are clearly separable into two stop areas, while all of Central line, Elizabeth line and National Rail services at Stratford are in the same stop area).
For larger interchanges it is often appropriate to organise stop areas into public_transport=stop_area_groups.
Key | Values | Notes | ||
---|---|---|---|---|
Multimodal[2] | ||||
Element | ||||
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>[1] | Mode-specific name | Not used | Not used | |
network | Network | Network | Network | Mandatory. Use semicolons for multiple values. |
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>[1] | Mode-specific reference | Not used | Not used | |
Examples | 9746604 9746604 |
3662093 3662093 14180345 14180345 2663308 2663308 3757862 3757862 3781969 3781969 |
3749672 3749672 204021 204021 |
Members
Role | Refers to | Comment | Presence |
---|---|---|---|
stop | public_transport=stop_position | Position(s), where the vehicle stops. | Recommended, if applicable. |
platform | public_transport=platform | The platform(s). | Recommended, if applicable. |
<empty> | railway=platform_edge | The platform edges of island platform(s). | Recommended, if applicable. |
<empty> | public_transport=station | The station building/area. | Recommended, if it belongs to the stop area. |
<empty> | railway=subway_entrance | The station entrance/exit point(s). | Recommended, if applicable. |
<empty> | amenity=* | Examples: shelter, bench, bicycle_parking, taxi. | Recommended, if applicable. |
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 | 7225140 7225140 | 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 | 7772561 7772561 |
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 | 7772555 7772555 7772556 7772556 |
London Overground & 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 | network | Mandatory. |
brand | Transport for London | Transport for London | Mandatory. |
name | London Overground | Elizabeth line | Mandatory. |
network | National Rail | National Rail | Mandatory. |
operator | Arriva Rail London | MTR Elizabeth line | Mandatory. |
train | yes | yes | Mandatory. |
Examples | 7225139 7225139 | 9789693 9789693 | The relation is a good starting point for exploring the network. |
Route master
TfL train routes have a route_master relation structure that consists of individual route relations for each direction or variant.
There are 6 route masters in total for the Overground: Liberty line, Lioness line, Mildmay line, Suffragette line, Weaver line, Windrush line.
Key | Values | Notes | |
---|---|---|---|
type | route_master | route_master | Mandatory. |
route_master | train | train | Mandatory. |
name | Route Name | Elizabeth line: Route Name | Mandatory. This is a descriptive route name.
|
network | Network | Network | Mandatory. This must match the Network in the parent route network relation. |
ref | Route Reference | Route Reference | Mandatory. This is the route reference.
|
wheelchair | yes/no | Mandatory. This describes wheelchair accessibility for the trains on the route. | |
brand | Brand | Brand | Optional. If this is specified then it must match the Brand in the parent route network relation. |
operator | Operator | Operator | Optional. If this is specified then it must match the Operator in the parent route network relation. |
Examples | 112649 112649 | 5793626 5793626 |
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 | route | Mandatory. |
route | train | train | Mandatory. |
public_transport:version | 2 | 2 | Mandatory. |
from | First Station Name | First Station Name | Mandatory. This is the name of the first station on the route.
|
name | Elizabeth line: Route Name | Elizabeth line: Route Name | Mandatory. This is a descriptive route name.
|
network | Network | Network | Mandatory. This must match the Network in the parent route master relation. |
ref | Route Reference | Route Reference | Mandatory. This must match the Route Reference in the parent route master relation. |
to | Last Station Name | Last Station Name | Mandatory. This is the name of the last station on the route.
|
brand | Brand | Brand | Optional. If this is specified then it must match the Brand in the parent route master relation. |
operator | Operator | Operator | Optional. If this is specified then it must match the Operator in the parent route master relation. |
wheelchair | yes/no | yes/no | Optional. If this is specified then it must match the wheelchair tag in the parent route master relation. |
Examples | 6413187 6413187 6413186 6413186 |
5642190 5642190 5793620 5793620 |
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 | 5732270 5732270 | 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 | 3511600 3511600 |
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 8885761 8885761). |
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 | 3511639 3511639 963114 963114 |
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 | 9680851 9680851 | 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 | 9680853 9680853 |
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 | 8057977 8057977 142807 142807 |
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 | 7225135 7225135 | 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 | 7673326 7673326 |
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 | 7673325 7673325 102773 102773 |
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 1.3 1.4 1.5 1.6 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; bus for London Buses.
- ↑ 2.0 2.1 Example of multi-modal stations: stations between Queen's Park and Harrow & Wealdstone (Overground and Underground).
- ↑ Except at Wimbledon, which is inside a multimodal station.
- ↑ Oxford Street closed eastbound, p.2 (accessed 23 August 2014).
- ↑ TfL’s editorial style guide, p.37 (accessed 23 August 2014).