London public transport tagging scheme

Introduction

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. Example: Watts Grove
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. Example: 77291
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. Example: BL
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	469787952 469787952

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
public_transport	station	station	station	Mandatory.
railway	station	station	tram_stop	Mandatory.
subway, train, etc.	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>	Mode-specific name	Not used	Not used
network	Not used	Network	London Trams	Mandatory. Use semicolons for multiple values.
network:<mode>	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>	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: yes: There is full step-free access. limited: There is limited step-free access (including the possibility to change from platform to platform). no: There is no step-free access… at all.
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 6414163635	6143744010 6143744010 9754369244 9754369244 2446751285 2446751285 1651498764 1651498764 5871218007 5871218007	2864283848 2864283848

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: no @ (Mo-Fr 07:30-09:30,16:00-19:00 AND folded=no) means they are allowed outside peak hours. no @ (folded=no) means that they are disallowed.
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. yes: Step-free entry or exit. no: No step-free entry or exit.
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
public_transport	stop_position	stop_position	stop_position	Mandatory.
railway	stop	tram_stop	Not used	Mandatory.
subway, train, etc.	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. Example: Crossharbour Platform 1
ref	Platform number or letter	Platform number or letter	Not used	Mandatory. Example: 1
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. Example: BL
Examples	1752783277 1752783277 9760735058 9760735058 1812313946 1812313946 1735704089 1735704089 4184900020 4184900020	60306534 60306534	4710628833 4710628833

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	282348817 282348817

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	170706695 170706695

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.	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. Example: Crossharbour Platform 1
ref	Platform number or letter	Mandatory. Example: 1
wheelchair	yes/no/limited	Optional. This tag describes wheelchair accessibility for the platform: yes: The difference (from train to platform) is level, and it is possible to change to at least one platform. limited: The difference has a noticeable step or gap, but it is possible to change to at least one platform. no: You cannot change to at least one platform, no matter if difference is level or not.
Examples	170170622 170170622 796886903 796886903 170130361 170130361 203310408 203310408 158003540 158003540 418025655 418025655

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
public_transport	station	station	station	Mandatory.
railway	station	station	tram_stop	Mandatory.
subway, train, etc.	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>	Mode-specific name	Not used	Not used
network	Not used	Network	London Trams	Mandatory. Use semicolons for multiple values.
network:<mode>	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>	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: yes: There is full step-free access. limited: There is limited step-free access (including the possibility to change from platform to platform). no: There is no step-free access… at all.
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		542927492 542927492 350983791 350983791 350225610 350225610 693282624 693282624 369690415 369690415

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	170221186 170221186 347263800 347263800 170130345 170130345 112605950 112605950 140162487 140162487 508440662 508440662

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
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>	Mode-specific name	Not used	Not used
network	Network	Network	Network	Mandatory. Use semicolons for multiple values.
network:<mode>	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>	Mode-specific reference	Not used	Not used
Examples	9746604 9746604	3662093 3662093 14180345 14180345 2663308 2663308 3757862 3757862 3781969 3781969	3749672 3749672 204021 204021

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. Example: DLR: Bank - Lewisham
network	Network	Mandatory. This must match the Network in the parent route network relation.
ref	Route Reference	Mandatory. This is the route reference. Example: B-L
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. Example: Bank
name	DLR: Route Name	Mandatory. This is a descriptive route name. Example: DLR: Bank → Lewisham
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. Example: Lewisham
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

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	9789693 9789693	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. Example: Elizabeth line: Liverpool Street - Shenfield
network	Network	Mandatory. This must match the Network in the parent route network relation.
ref	Route Reference	Mandatory. This is the route reference. Example: XR
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	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	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. Example: Liverpool Street
name	Elizabeth line: Route Name	Mandatory. This is a descriptive route name. Example: Elizabeth line: Liverpool Street → Shenfield
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. Example: Shenfield
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	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). Secondly, TfL discourages using ‘Buses’ alone when referring to London Buses.

Key	Values	Notes
type	route_master	Mandatory.
route_master	bus	Mandatory.
name	London Buses route Route Number	Mandatory. This is a descriptive route name. Example: London Buses route 30
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. Example: Metroline
ref	Route Number	Mandatory. This is the route number. Example: 30
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. Example: Hackney Wick
name	London Buses route Route Number → Destination	Mandatory. This is a descriptive route name. Example: London Buses route 30 → Marble Arch
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. Example: Marble Arch Station
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 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	7225139 7225139	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. Example: Overground: Richmond - Stratford
network	Network	Mandatory. This must match the Network in the parent route network relation.
ref	Route Reference	Mandatory. This is the route reference. Example: NLL
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	112649 112649

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. Example: Richmond
name	Overground: Route Name	Mandatory. This is a descriptive route name. Example: Overground: Richmond → Stratford
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. Example: Stratford
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	6413187 6413187 6413186 6413186

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. Example: London Trams: Wimbledon - Beckenham Junction
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. Example: 2
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. Example: Wimbledon
name	London Trams: Route Name	Mandatory. This is a descriptive route name. Example: London Trams: Wimbledon → Beckenham Junction
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. Example: Beckenham Junction
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. Example: Jubilee line
network	Network	Mandatory. This must match the Network in the parent route network relation.
ref	Route Reference	Mandatory. This is the route reference. Example: Jubilee
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. Example: Stanmore
name	Route Name	Mandatory. This is a descriptive route name. Example: Jubilee line: Stanmore → Stratford
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. Example: Stratford
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.