Bus routes in London
- 1 Tagging scheme
- 2 Symbol and colour legend
- 3 Route Network
- 4 Daytime buses (including 24 hour buses)
- 5 School buses
- 6 Mobility buses
- 7 Night buses
- 8 Other buses (not operated by Transport for London)
- 9 Citations
Bus routes current
Bus routes are mapped as a hierarchy of:
- Route Network
- Route Masters
- Bus Depots and Routes
- Ways and Stop Positions
Route Network: There is a single Route Network relation that contains all of the London bus routes, ordered by name. The members of the Route Network relation are Route Masters with no role. Members may eventually be Routes with no role (for lines with a single route without any Route Master, such as unidirectional circular lines with no variant), but creating a Route Master (even if there's for now a single Route member) is recommended to allow further variants and also to allow adding its depot.
Route Master: There is one Route Master relation for each London bus route. The members of a Route Master relation are Bus Depots with role "depot" and Routes with no role. Typically, there is one Bus Depot and two Routes for each Route Master. The Bus Depot members specify the bus depots or bus garages that supply buses for the bus route. Note that circular lines that operate in two directions are actually two separate lines with distinct numbers, grouped together as members of the same Route Master (referenced by the lowest line number).
Route: There is one Route relation for each London bus route direction or variant. The members of a Route relation are Ways with role "forward" or "backward" and Stop Positions with role "stop", "stop_entry_only" or "stop_exit_only". The Ways included in the Route are an ordered set between the first bus stop and the last bus stop. Ways to and from any bus stand or bus depot are not included in the Route. The Stop Positions included in the Route are an ordered set from the first Stop Position to the last Stop Position. The first Stop Position of a route normally has a role of "stop_entry_only". The last Stop Position of a route normally has a role of "stop_exit_only". All other Stop Positions normally have a role of "stop".
|Route master|| (route_master)|
member (with no role)
Only use note=*, to warn editors against auto-sorting, if a route uses a way more than once.
members (with no role), and
member (with role depot)
Bus routes legacy
- Bus routes were originally mapped as single Route relations. This caused problems with ordering, because on some routes, buses use the same way with the same bearing, regardless of direction. Editors are encouraged to convert these legacy single Route relations into the current Route Master format.
- Bus stops were originally mapped without associated Stop Positions. These legacy bus stops were associated with Route relations as members. Editors are encouraged to convert these routes to use Stop Positions instead of legacy bus stops wherever possible. Editors are also encouraged to only add Stop Positions as members of Route relations wherever possible. Legacy bus stops should only be added as members of Route relations (with the role of stop_entry_only, stop_exit_only or stop as appropriate) where no corresponding Stop Position exists yet. Bus Stops should be ordered in the direction of the Route (the first Bus Stop should be the start of the line and the last Bus Stop should be its terminus; if the line is not circular, their respective roles should be stop_entry_only and stop_exit_only, otherwise the first and last Bus Stop may be the same and a circular tag may be used on the route instead of duplicating this stop member).
Bus stops current
Bus stops are mapped as a hierarchy of:
- Stop Areas
- Platforms and Stop Positions
- Stop Area
- There is one Stop Area relation for each collection of bus stops in close proximity to each other. The members of a Stop Area relation are Platforms with role "platform" and Stop Positions with role "stop". Typically, there are two Platforms and two Stop Positions in a Stop Area but a Stop Area can contain any number of Platforms and Stop Positions. The determining factor is that the Stop Area, Platforms and Stop Positions normally have a common name.
- There is one Platform node for each bus stop. A Platform identifies the position where the passengers wait for the bus. A Platform is therefore normally positioned alongside a way, adjacent to its corresponding Stop Position.
- Stop Position
- There is one Stop Position node for each bus stop. A Stop Position identifies the position where the bus stops in the road. A Stop Position is therefore normally positioned on a way, adjacent to its corresponding Platform. If a Stop Position is the first stop or the last stop of a bus route then the Stop Position is normally positioned at a split point of a way.
To conserve the length of this article, the table below omits NaPTAN tags.
Use name=* to specify the common name that both the bus stop flag and the iBus system uses. Normally, the name is the same as the name for its parent Stop Area.
members (with role platform) of
Use name=* to specify the common name that both the bus stop flag and the iBus system uses. Normally, the name is the same as the name for the corresponding Platform.
members (with role stop) of
Bus stops legacy
- Since October 2011, TfL's own system of five-digit bus stop codes allowed users to request real-time departure information via mobile telephones. The codes have no relationship to NaPTAN. The five-digit bus stop codes were not referenced originally. Editors are encouraged to tag Platforms with the five-digit bus stop code, using the ref tag.
- Stop Areas were originally referred to as Sites (type=site, site=stop_area). Editors are encouraged to convert these legacy Sites to current Stop Areas (type=public_transport, public_transport=stop_area, public_transport:version=2). Retain any NaPTAN tags during the conversion.
- Platforms were originally referred to as Bus Stops (highway=bus_stop). Editors are encouraged to convert these legacy Bus Stops to current Platforms (public_transport=platform, highway=bus_stop). Retain any NaPTAN tags during the conversion.
- Stop Positions were not mapped originally. Editors are encouraged to map Stop Positions (public_transport=stop_position, bus=yes) to correspond with their Platforms, so that eventually every bus stop will have a Platform / Stop Position combination.
- The NaPTAN tags for Stop Areas and Platforms originally included a naptan:verified=no tag. When Stop Areas and Platforms have been verified, editors are encouraged to change these tags to naptan:verified=yes or preferably delete the naptan:verified tag. A non-existent naptan:verified tag has the same implicit meaning as the naptan:verified=yes tag.
- Editors originally tagged some bus stops with the routes that they served. That is no longer needed as Routes reference Stop Positions directly. Editors are encouraged to delete any bus stop route tags, such as the route_ref tag or similar.
Symbol and colour legend
The status of each map region is indicated by a symbol, which describes the type of feature, and a colour, which indicates the completeness of that feature in a map region.
Routes that use the green.are highlighted in
Meaning of symbols
|The route is mapped as a relation (r)|
|Bus stops have been checked (h)|
Meaning of colours
The numeric identifiers of OpenStreetMap elements may change as the map is edited.|
You may want to use the Overpass API to create more permanent links based on tags.
The relation "London Buses"combines all route masters.
Daytime buses (including 24 hour buses)
Daytime buses are listed in a separate article Daytime buses and individual separate articles:
- Daytime buses 1-99
- Daytime buses 100-199
- Daytime buses 200-299
- Daytime buses 300-399
- Daytime buses 400-499
- Daytime buses 500-599
- Daytime buses 600-699
- Daytime buses A-Z
This table does not contain route 603 or route 607. Bus route 603 and route 607 are categorised as daytime buses and so they appear in the Daytime buses table.
Whitton, Lincoln Avenue
|Checked 20 August 2017.|