Beta intro
Mayor of London

Our feeds

These guidelines include technical information to help you understand how the feeds work and how to use them correctly. They also provide information on data refresh rates and how to brand the data. Using our data is subject to our terms and conditions.

The example feeds listed below are not updated and are for demonstration purposes only. You will need to register to gain access to the live feeds.

General

 
Journey Planner API Beta

This API allows you to make requests to TfL's Journey Planner and receive responses as XML.

You need to register to gain access to the live feeds.

Some ideas

  • Incorporate journey planning in London within a new or existing application
  • Allow planning from/to stations, stops, places of interest, geolocations, addresses or postcodes

Branding

  • Please do not include any TfL branding in your application or give the impression this is an official TfL application
  • Please add the attribution "Powered by the Transport for London Journey Planner API" in the application credits

Content provider
Transport for London

 
Journey Planner timetables

The Journey Planner timetable feed contains up-to-date standard timetables for London Underground, bus, DLR and river services. The timetables are updated every seven days. They do not take account of planned engineering works.

How often we publish a fresh copy of the feed
1440 mins

Maximum time allowed between capturing and displaying the feed
10 mins

Maximum time information can be displayed before being updated
1440 mins

Some ideas

  • Create an application that allows Londoners to plan their journeys

The example feed below is not updated and for demonstration purposes only. You need to register to gain access to the live feeds.

Content provider
TfL Group Customer Services

 
Station locations

Our station location feed is a geo-coded KML feed of most London Underground, DLR and London Overground stations.

How often we publish a fresh copy of the feed
1440 mins

Maximum time allowed between capturing and displaying the feed
10 mins

Maximum time information can be displayed before being updated
4320 mins

Some ideas

  • Add your business location to the map so customers can find you
  • Display places of interest on the map - this helps people find the nearest Tube station

The example feeds below are not updated and for demonstration purposes only. You need to register to gain access to the live feeds.

Branding

  • Use the Tube roundel for Tube stations
  • Use the DLR roundel for DLR stations
  • Use the London Overground roundel for London Overground stations
  • All stations are marked with the famous TfL roundel

Content provider
TfL Digital

 
Station facilities

Our station facilities feed is a geo-coded KML feed of most London Underground, DLR and London Overground stations. It has station facilities and access information for each station. All stations are marked with the famous TfL roundel.

How often we publish a fresh copy of the feed
1440 mins

Maximum time allowed between capturing and displaying the feed
10 mins

Maximum time information can be displayed before being updated
4320 mins

Some ideas

  • Add your business location to the map so customers can find you
  • Display places of interest on the map - this helps people find the nearest Tube station

The example feed below is not updated and for demonstration purposes only. You need to register to gain access to the live feeds.

Content provider
TfL Digital

Tube

 
Tube departure boards, line status and station status

This feed provides access to realtime Tube data, including:

  • A summary train prediction service
  • A detailed train prediction service
  • Station status
  • Line status

Powered by Windows Azure

How often we publish a fresh copy of the feed
30 secs

Maximum time allowed between capturing and displaying the feed
30 secs

Maximum time information can be displayed before being updated
30 secs

Some ideas

  • Create a web or mobile application to allow customers to check live Tube departures from their nearest station

Read the Development Beta SDK for network status and train prediction services:

Service updates

We have created a style guide to show you how we display live travel information and provide guidance on how to reproduce this:

Content provider
London Underground

 
Tube this weekend

The 'Tube this weekend' feed contains information on planned line and station closures for the coming weekend. This allows people to plan their journeys and avoid disruption.

It also has details of planned works affecting station access - such as those involving lifts and escalators.

How often we publish a fresh copy of the feed
720 mins

Maximum time allowed between capturing and displaying the feed
2 mins

Maximum time information can be displayed before being updated
10 mins

Some ideas

  • Add the feed to your staff intranet. It will increase traffic and allow you to promote other travel-related schemes targeted at your employees - for example car pooling and cycle to work schemes
  • If your company is organising weekend events it allows your visitors to plan ahead and take alternative travel routes

The example feeds below are not updated and for demonstration purposes only. You need to register to access the live feeds.

Branding

  • Use the correct colour to represent each Tube line
  • Text: 'Information supplied by Transport for London' (hyperlink)

Bus, Coach and River

 
Live bus and river bus arrivals API (instant)

This API provides realtime bus and river bus arrival information across all TfL bus stops and piers. Instant requests are responded to with the live bus and river bus arrival information valid at that point in time. They provide a snapshot of the data. Instant requests are primarily targeted at use within mobile applications.

How often we publish a fresh copy of the feed
Every 30 seconds

Maximum time allowed between capturing and displaying the feed
5 seconds

Maximum time information can be displayed before being updated
30 seconds

Some ideas

Apps developers can add this data to their travel tools:

  • 'Bus stops or piers near you' location services can be refined using device-optimised applications
  • Develop apps for visually impaired passengers
  • Allow a passenger to view the predicted arrival times (for the next 30 minutes) for a chosen bus route or pier
  • Venue owners could include their bus stop code or pier with their listing details, so customers can easily find nearby bus stops or piers

You need to register to gain access to the live feeds.

Branding

  • Please do not include any TfL branding in your application or give the impression it is an official TfL application
  • Please add the attribution "Data provided by Transport for London"

Content provider
London Buses Ltd

 
Live bus and river bus arrivals API (stream)

This API provides realtime bus and river bus arrival information across all TfL bus stops and piers. Stream requests are responded to with a continuous supply of live bus and river bus arrival information. From a single request the response will continue to be updated over time. These requests are primarily targeted at server-to-server usage.

How often we publish a fresh copy of the feed
Every 30 seconds

Maximum time allowed between capturing and displaying the feed
5 seconds

Maximum time information can be displayed before being updated
30 seconds

Some ideas

Apps developers can add this data to their travel tools:

  • 'Bus stops or piers near you' location services can be refined using device-optimised applications
  • Develop apps for visually impaired passengers
  • Allow a passenger to view the predicted arrival times (for the next 30 minutes) for a chosen bus route or pier
  • Venue owners could include their bus stop code or pier with their listing details, allowing customers to easily find nearby bus stops or piers

You need to register to gain access to the live feeds.

Branding

  • Please do not include any TfL branding in your application or give the impression it is an official TfL application
  • Please add the attribution "Data provided by Transport for London"

Content provider
London Buses Ltd

 
Bus stop locations and routes

This dataset describes the London Buses standard network information.

The network information includes the location of all bus stops in London and the sequence of bus stops that every bus route in London stops at.

As our stops and routes do change on a frequent basis, you will need to come back to us regularly for the updates.

How often we publish a fresh copy of the feed
Weekly

Maximum time allowed between capturing and displaying the feed
1 day

Maximum time information can be displayed before being updated
2 weeks

Some ideas

  • To allow visitors to your website to locate their nearest bus stop and route
  • Develop an application to allow users to plan journeys by bus

The example feeds below are not updated and for demonstration purposes only. You need to register to gain access to the live feeds.

Guidelines

Branding

Use the buses roundel for bus stops.

Content provider
iBus, TfL Surface Transport

 
iBus

The iBus system tracks the movement and performance of buses on all of our contracted routes in London.  

We publish weekly reports which show the actual arrival time of buses on a route at any given bus stop for the selected day. The routes were selected as the first of the New Routemaster (New Bus for London). This data is not syndicated.

 
Coach parking sites/locations

London has a number of coach parking sites that are provided to enable operators to safely park vehicles in areas that will not impede other road users. The file provides geo-coded locations of all coach parking sites along with details such as hours of operation and charging information.

How often we publish a fresh copy of the feed
1440 mins

Maximum time allowed between capturing and displaying the feed
10 mins

Maximum time information can be displayed before being updated
4320 mins

Some ideas

  • This information will benefit coach operators and can be used to provide coach parking information across a variety of digital applications eg an industry-specific Satnav system

The example feeds below are not updated and for demonstration purposes only. You need to register to gain access to the live feeds.

Branding

  • Use relevant icons to distinguish between coach parks, on-street coach meters, coach bays and other coach parking
  • Text: 'Information supplied on (date) by Transport for London' (hyperlink)
  • Image files are included in the data

Content provider
Coaches, TfL Surface Transport

 
Pier locations

Our pier location feed is a geo-coded KML feed of the piers and docks along the River Thames.

How often we publish a fresh copy of the feed
1440 mins

Maximum time allowed between capturing and displaying the feed
10 mins

Maximum time information can be displayed before being updated
4320 mins

Some ideas

  • Add your business location to the map so customers can find you
  • Display places of interest on the map to help people find the nearest pier

The example feeds below are not updated and for demonstration purposes only. You need to register to gain access to the live feeds.

Branding

  • Use the Rivers roundel for piers
  • All locations are marked with the famous TfL roundel

Content provider
River Services, TfL Surface Transport

Roads

 
London digital speed limit map

The speed limit file contains the coordinates (Ordnance Survey Easting's and Northing's) of every speed limit sign within the M25 (inclusive). 

Each record contains a primary limit which shows the speed on the sign plate for traffic approaching the sign.

In some cases there is a secondary limit which shows the speed on the sign plate on the back of the sign for traffic travelling in the other direction.

We update this data approximately every two months.  However, if there are a large number of speed limit changes we may update the file more often. This data is not syndicated.

 
Live Traffic Disruptions - TIMS

This feed was built to replace the Live Traffic Disruptions (LTIS) feed, which was decommissioned on 1 April 2013.

The structure and the content of the new feed has been changed to capture a richer range of information about road disruptions, including improved spatial information, details of closures and more in-depth categorisation of the cause of a disruption.

How often we publish a fresh copy of the feed
5 mins

Maximum time allowed between capturing and displaying the feed
5 mins

Maximum time information can be displayed before being updated
30 mins

The example feeds below are not updated and for demonstration purposes only. You need to register to gain access to the live feeds.

 
Live traffic camera images (CCTV)

Our live traffic camera images feed ('Jam Cams') gives you a bird's eye view of what's happening on London's streets. It provides images from 344 cameras across the Capital, providing an up-to-date view of traffic at key locations.

All images are TfL branded, telling users they're from an official source. The images are date and time stamped and refreshed every three minutes - sometimes more often.

All images have a location description. Individual feeds may be interrupted if there's a system fault or if we're servicing a camera.

Note that images are not captured when a camera is in use for managing traffic, when a camera is being maintained or in the event of a camera or system fault.

If a new camera is added as a Jam Cam, or a camera is removed, it will vanish from the XML feed. As such, it is advised that developers periodically parse this XML, since it may change.

How often we publish a fresh copy of the feed
2 mins

Maximum time allowed between capturing and displaying the feed
2 mins

Maximum time information can be displayed before being updated
15 mins

Some ideas

  • If you operate a freight or delivery service, you may like to keep an eye on traffic conditions and tell your drivers to avoid congested areas
  • Radio stations could add a live camera feed to a traffic news page
  • Organisations with staff intranets could add the traffic camera feed so people can plan their journeys home

The example feeds below are not updated and for demonstration purposes only. You need to register to gain access to the live feed.

Branding

  • No additional branding (all TfL CCTV images already contain TfL branding)
  • You must not crop images

Content provider
TfL Traffic Operations

 
Live roadside message signs

The live roadside message signs XML feed comes direct from TfL's traffic control centre system and contains the location and live message on every sign currently displaying information in London.

We have a network of over 130 roadside message signs, which provide drivers with information about local traffic disruptions. The signs are set by TfL's London Streets Traffic Control Centre.

The feed contains a date and time stamp which should be used to check that the information is up to date and be displayed when publishing the information.

How often we publish a fresh copy of the feed
5 mins

Maximum time allowed between capturing and displaying the feed
5 mins

Maximum time information can be displayed before being updated
30 mins

Some ideas

  • Combine this feed with our traffic camera and live traffic disruptions data feeds to provide a complete picture of traffic along a route or in an area

The example feeds below are not updated and for demonstration purposes only. You need to register to gain access to the live feeds.

Branding

Text: 'Information supplied at (time) on (date) by Transport for London' (hyperlink).

Content provider
TfL Traffic Operations

 
Licensed private hire operators - Findaride

The Findaride KML feed contains details of licensed London minicab and other private hire operators. It is based on the same database as the award-winning Cabwise service.

The Findaride feed is not a complete list of licensed operators. For a complete list, please refer to our private hire licence checker.

The feed contains a date and time stamp which should be displayed when publishing the information, and includes:

  • Contact details
  • Operating hours
  • Areas covered
  • Availability of wheelchair-accessible vehicles/offices
  • Number of vehicles
  • Payment options

How often we publish a fresh copy of the feed
1440 mins

Maximum time allowed between capturing and displaying the feed
10 mins

Maximum time information can be displayed before being updated
4320 mins

Some ideas

  • Pub or club owners could add the Findaride feed to their website to help customers get home safely

The example feeds below are not updated and for demonstration purposes only. You need to register to gain access to the live feeds.

Branding

Text: 'Licensed operator information supplied at (time) on (date) by Transport for London' (hyperlink)

Content provider
TfL Taxis and Private Hire

Barclays Cycle Hire

 
Barclays Cycle Hire availability

The Barclays Cycle Hire XML feed contains the name, location, coordinates and maximum number of docking points for all operational Barclays Cycle Hire docking stations. It also contains the number of available bikes (excluding locked or faulty bikes), and number of available docking points.

The feed comes direct from the Service Provider's information database and is updated in three-minute intervals. It contains the same data that is used for the BCH online interactive map.

The Barclays Cycle Hire scheme is available 24 hours a day, seven days a week. There are 6,000 bikes available from over 400 docking stations across central London. At any point, docking stations may be full or empty, working or not working, and bikes may or may not be available to rent.

The feed contains a date and time stamp which should be used to check that the information is up-to-date and be displayed when publishing the information.

How often we publish a fresh copy of the feed
3 mins

Maximum time allowed between capturing and displaying the feed
30 mins

Maximum time information can be displayed before being updated
30 mins

Some ideas

  • Each docking station contains location details (longitude and latitude), so any website offering travel information for customers could display the data, filtered for their geographic area of interest, on a map
  • The information could be used to provide a complete picture of available docking points or bikes along a route or in an area
  • The data could be fed into an online road journey planner or mobile navigation system

The example feed below is not updated and for demonstration purposes only. You need to register to gain access to the live feeds.

Guidelines

Branding

  • Text to display "Barclays Cycle Hire data supplied at (time) on (date) by Transport for London"
  • Use the Barclays Cycle Hire logo (PNG 20KB) to represent the scheme on all applications and services
  • Use the cycle pushpin icon (GIF 8KB) to indicate the location of Barclays Cycle Hire docking stations

Content provider
Cycling, TfL Surface Transport

Oyster

 
Oyster Ticket Stop locations

Our Oyster Ticket Stop locations is a geo-coded KML feed of the 3,700 outlets across London where customers can top up their Oyster card and renew a Travelcard or Bus & Tram Pass.

Each location is marked with the Oyster Ticket Stop logo.

How often we publish a fresh copy of the feed
1440 mins

Maximum time allowed between capturing and displaying the feed
10 mins

Maximum time information can be displayed before being updated
4320 mins

Some ideas

  • Allow visitors to your website or users of your application to locate their nearest Oyster top-up location
  • Incorporate the feed as part of an online travel planning service, or 'how to find us' page

The example feeds below are not updated and for demonstration purposes only. You need to register to gain access to the live feeds.

Branding

Use the Oyster Ticket Stop logo for Oyster Stop locations

Content provider
TfL Fares and Ticketing

Accessibility and toilets

 
Step-free Tube guide and toilet data - Enhanced LRAD

The data contained in this feed provides information about the level of step-free access to platforms and trains that is available at London Underground, London Overground and DLR stations. It also includes the location of toilets available at London Underground, London Overground and DLR stations, including if payment is required. The data can be used to produce guides in varying electronic formats suitable for delivery by mobile applications.

How often we publish a fresh copy of the feed
Quarterly

The example feeds below are not updated and for demonstration purposes only. You need to register to gain access to the live feeds.

 
Bus toilet data

The data contained in this feed contains the locations of the toilets available at London bus stations. The data can be used to produce guides in varying electronic formats suitable for delivery by mobile applications.

How often we publish a fresh copy of the feed
Quarterly

The example feed below is not updated and for demonstration purposes only. You need to register to gain access to the live feeds.

Network statistics

 
Rolling Origin & Destination Survey (RODS)

The Rolling O&D survey is an ongoing programme to capture information about journeys on the Tube network.

The 2010 tables are reconciled to the annual counts as well as summary statistics from the Underground Users Survey. The 2010 RODS data is also reconciled to Oyster Origin and Destination flows for stations that have sufficient information.

Please note the data reflects November counts and represents the number of people travelling on a typical (or average) weekday. Therefore, year-on-year RODS fluctuations do not necessarily reflect whole-year annual demand changes. The data is adjusted to remove any abnormal circumstances that may affect demand such as industrial action or long-term closures.

How often we publish a fresh copy of the feed
Annually

Maximum time allowed between capturing and displaying the feed
9 months

Maximum time information can be displayed before being updated
1 year

Some ideas

  • Develop a service to indicate when stations are particularly crowded, to allow users to avoid certain stations at that time.

The example feed below is not updated and for demonstration purposes only. You need to register to gain access to the live feeds.

Content providers
London Underground

 
London Underground passenger counts data

Passenger counts collects information about passenger numbers entering and exiting London Underground stations, largely based on the Underground ticketing system gate data.

Counts data is obtained during the autumn of each year and does not necessarily reflect whole-year annual demand. The data is adjusted to remove the effect of abnormal circumstances that may affect demand such as industrial action.

Notes are given in the notes sheet on each spreadsheet.

How often we publish a fresh copy of the feed
Annually

Some ideas

  • Identify the busiest days and times for individual stations so that passengers can plan their journey to avoid the most congested stations or times.

The example feed below is not updated and for demonstration purposes only. You need to register to gain access to the live feeds.

Notes for 2010 counts

Tables

There are spreadsheets by station and quarter hour, for Weekday, Saturday and Sunday, both for entries and exits. There is also a separate spreadsheet for total annual usage.

Definitions

  • Entries - Number of passengers passing gates or ticket barriers going from the street to the platforms
  • Exits - Number of passengers passing gates or ticket barriers going from the platforms to the street
  • Passenger - Usually an LU passenger, but for most joint stations the count will include flows between the street and NR services

Columns

  • nlc - National location code
  • date - Date of count - see also Source below

Notes

  • N = station closed
  • T = Figures include all passengers on the W&C line (which is closed on Sundays)
  • B = Figures for Bank/Monument now exclude W&C line passengers interchanging with other lines
  • A = previous year's counts adjusted by average change between years by zone
  • 02:00-02:15 - every quarter-hour of the day has a column
  • Total: Total for the whole traffic day
  • Rows: Ordered alphabetically by station name. Bank and Monument are treated as a single station
  • Counts: All numbers quoted are number of passengers for one typical day

Source

Up to 1997 inclusive, all count data was obtained by field workers watching and counting the flow on one day - this is called a manual count. Increasingly since 1998, count data has been obtained from the automatic gates. This is processed through our RELATE computer system and is based on an average over four to five weeks.

Where the date of the count is a single day or a season, eg Aut-10, Spr-10, this implies that the data comes from a manual count. Where the date is given as a month this implies that gate data has been used, eg: Nov-10 the five weeks (two weeks ending 22/09/10 and three weeks ending 26/11/10 - for avoidance of school half-term break and Industrial action on the LU network) for Weekdays

Issue date March-2011

Content provider
London Underground

 
Dial-a-Ride statistics

This quarterly report details usage, by London borough, for the specified quarter, as well as the same quarter of the previous year to allow for comparison.

Dial-a-Ride is a free door-to-door service for disabled and older people who can't use buses, trains or the Tube. Those eligible for membership have a permanent or long-term disability which means they are unable or virtually unable to use mainstream public transport.

There are a number of figures provided:

  • The number of passengers registered to use the service
  • The number of requests made for the service within the period
  • The percentage of requests scheduled (accepted)
  • The percentage of trips cancelled by passengers
  • The percentage of trips cancelled owing to service (operational) reasons
  • The number of completed trips

This is a static file so you will need to come back to us for updates. Please specify the report date period when publishing the data.

How often we publish a fresh copy of the feed
Quarterly

Some ideas

  • Local authorities might wish to include the Dial-a-Ride performance figures for their borough on their websites

The example feed below is not updated and for demonstration purposes only. You need to register to gain access to the live feeds.

Notes

  1. Cancellations are shown as percentages of scheduled requests
  2. Passenger cancellations are where DaR has scheduled the trip but the passenger subsequently cancels, most commonly because of illness
  3. Others/unknown includes visitors to London and a small number of members living just outside the Greater London boundary with "grandparent rights"
  4. In Newham, Dial-a-Ride operates separately under the Door2Door service, a joint scheme with Taxicard

Branding

Text: Dial-a-Ride usage statistics for [date period - eg Q1 2010/11] supplied by Transport for London.

Content provider
London Dial-a-Ride, TfL Surface Transport

 
Barclays Cycle Hire statistics

Details of all Barclays Cycle Hire journeys.

The journey information includes:

  • Journey ID
  • Bike ID
  • Start date
  • Start time
  • End date
  • End time
  • Start docking station
  • Start docking station ID
  • End docking station
  • End docking station ID

Some ideas

  • Create a visualisation of Barclays Cycle Hire usage across London

The example feed below is not updated and for demonstration purposes only. You need to register to gain access to the live feeds.

 
Oyster card journey information

This dataset provides a 5% sample of all Oyster card journeys performed in a week during November 2009 on bus, Tube, DLR and London Overground.

An Oyster card user must touch in at the start, and touch out at the end, of a journey by Tube or rail, in order to validate the journey. On buses and trams, users are required to touch in to validate their journey.

Some ideas

  • Create a visualisation of travel flows between all origin and destination points across the transport network
  • Estimate journey times based on the sample journeys, taking into account the time of day

The example feed below is not updated and for demonstration purposes only. You need to register to gain access to the live feeds.

Column descriptions

  • downo - a number between 1 and 7, 1 being Sunday, 2 being Monday etc
  • daytype - Sun to Sat
  • SubSystem - the mode(s) of the journey. LUL - London Underground, NR - National Rail, LTB - London Buses, DLR- Docklands Light Railway, LRC - London Overground, TRAM - Croydon Tram
  • StartStn - Station the journey started at
  • EndStation - Station the journey ended at
  • EntTime - Entry time of the journey in minutes after midnight
  • EntTimeHHMM - Entry time in HH:MM text format
  • ExTime - Exit time of the journey in minutes after midnight
  • EXTimeHHMM - Exit time in HH:MM text format
  • ZVPPT - zones of Oyster Season ticket, if used
  • JNYTYP - Product types involved in the journey. PPY - Pure PAYG, TKT - Pure Oyster Season, MIXED - Combined PAYG and Oyster Season
  • DailyCapping - it shows as Y when PAYG journey was capped
  • FFare - Full PAYG Fare before any discounts
  • Dfare - PAYG Fare after usage based discounts
  • RouteID - The Route Number of the Bus, if a Bus has been boarded
  • FinalProduct - Combined Product Description used for journey
 
Public Transport Accessibility Levels

Public Transport Accessibility Levels (PTALs) are a detailed and accurate measure of the accessibility of a point to the public transport network, taking into account walk access time and service availability.

The method is essentially a way of measuring the density of the public transport network at any location within Greater London. For more information see the PTALs website.

The measure reflects:

  • Walking time from the point-of-interest to the public transport access points
  • The reliability of the service modes available
  • The number of services available within the catchment
  • The level of service at the public transport access points - ie average waiting time

Please note it does not consider:

  • The speed or utility of accessible services
  • Crowding, including the ability to board services
  • Ease of interchange

The data is provided as a 100-metre grid. It has also been converted into contours.

How often we publish a fresh copy of the feed
Annually

Some ideas

  • Create an application to show the distance and walking time from any place of interest in London to the nearest public transport services

The example feed below is not updated and for demonstration purposes only. You need to register to gain access to the live feeds.

Content providers
TfL General Statistics Team