Guidelines and Support

Some ideas...

• Incorporate journey planning in London within a new or existing application
• Allow planning from/to stations, stops, places of interest, geo-locations, 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.

Guidelines

Read the guidelines (PDF 845KB)

Content provider

Transport for London

The example feeds below are not updated and are for demonstration purposes only.

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

• TIMS feed technical specification (PDF 464kb)
• TIMS feed sample XML data (XML 582kb)
• TIMS feed sample XML errors (XML 951kb)
• TIMS feed schema (XSD 7.8kb)

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

Live bus and river bus arrivals interface documentation (PDF 350KB)

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

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

Live bus and river bus arrivals interface documentation (PDF 350KB) 

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

The feed contains information on location, power rating, connection type, height restrictions, vehicle type allowed, access hours, fees, and other useful details.

The Charge Point Data Dictionary feed is also available. This data dictionary accompanies the main feed. It is necessary to subscribe to both feeds to enable translation of the database codes. See the example feeds below for more detail.

A user must be a member of Source London to charge at these points. Visit the Source London website more information and to register.

Branding requirements

Please don't:

Some ideas...

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 feeds below are not updated and are for demonstration purposes only.
You need to register to gain access to the live feeds.

• Barclays Cycle Hire (CSV 3KB)

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.

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 feeds below are not updated and are for demonstration purposes only.
You need to register to gain access to the live feeds.

• Barclays Cycle Hire availability (XML 1 KB) (Right click and save to view this demo file.)

Guidelines

• Data Dictionary - Barclays Cycle Hire (PDF 20KB)

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 Cycle Hire docking stations

Content provider

Cycling, TfL Surface Transport

Back to top

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 feeds below are not updated and are for demonstration purposes only.
You need to register to gain access to the live feeds.

• Oyster Card Journey information example (CSV 2KB)

Column descriptions

• downo - a number between 1 and 7, 1 being Sunday, 2 being Monday etc
• daytype - Sun - 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

Some ideas...

• Create an application that allows Londoners to plan their journeys

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

• Journey Planner timetables (ZIP 24.8 MB)

Content provider

TfL Group Customer Services

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.

You can view sample data for the feed below.

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

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 are for demonstration purposes only.
You need to register to gain access to the live feeds.

• Live roadside message signs - Live roadside message signs (XML 32KB)
• Live roadside message signs - Live roadside message signs schema (XSD 3KB)

Branding

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

Content provider

TfL Traffic Operations

Back to top

• 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 are for demonstration purposes only.
You need to register to gain access to the live feeds.

• Coach parking (CSV 3 KB)
• Coach Parking - Theatre information (CSV 6 KB)

Branding

• Use relevant icons distinguish between coach parks, on-street coach meters, coach bays, 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

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.

Some ideas...

• Local Authorities might wish to include the Dial-a-Ride performance figures for their borough on their web-sites.

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

• Dial-a-ride (CSV 4 KB)

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

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 jamcam, 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.

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 feed below is not updated and is for demonstration purposes only.
You need to register to gain access to the live feed.

Live traffic cameras - Live traffic cameras XML (XML, 32KB)
Live traffic cameras - Live traffic cameras schema (TXT, 6KB)

Branding

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

Content provider

TfL Traffic Operations

Back to top

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

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 are for demonstration purposes only.
You need to register to gain access to the live feeds.

• Licensed private hire operators - Findaride XML (XML, 764 KB)
• Licensed private hire operators - Findaride XSD (XSD, 5 KB)
• Licensed private hire operators - Findaride XSLT (XSLT, 6 KB)

Branding

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

Content provider

TfL Taxis and Private Hire

Back to top

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 are for demonstration purposes only.
You need to register to gain access to the live feeds.

• Station locations - Station locations KML (KML, 2 KB)
• Station locations - Station locations XSD (XSD, 1 KB)

Branding

• Use the Tube roundel for Tube stations
• Use the DLR roundel for DLR stations
• Use the London Overground roundel for London Overground stations
• Our 'station location' feed is a geo-coded KML feed of most London Underground, DLR and London Overground stations
• All stations are marked with the famous TfL roundel

Content provider

TfL Digital

Back to top

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 are for demonstration purposes only.
You need to register to gain access to the live feeds.

• Pier locations - Pier locations KML (KML 1 KB)
• Pier locations - Pier locations XSD (XSD 1 KB)

Branding

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

Content provider

River Services, TfL Surface Transport

Back to top

Each location is marked with the Oyster Ticket Stop logo.

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 are for demonstration purposes only.
You need to register to gain access to the live feeds.

• Oyster Ticket Stop locations KML (KML, 1 KB)
• Oyster Ticket Stop locations XSD (XSD, 2 KB)

Branding

Use the Oyster Ticket Stop logo for Oyster Stop locations

Content provider

TfL Fares and Ticketing

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 stop and routes do change on a frequent basis, you will need to come back to us regularly for the updates.

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 are for demonstration purposes only.
You need to register to gain access to the live feeds.

• Bus stops examples (CSV 13KB)
• Bus stops sequences examples (CSV 30KB)

Guidelines

• Syndication developer guidelines - Bus stops and routes (PDF 79KB)

Branding

Use the buses roundel for bus stops.

Content provider

iBus, TfL Surface Transport

Back to top

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 are just for demonstration.
You need to register to access the live feeds.

• Tube this weekend XML (XML 4 KB)
• Tube this weekend XSD (XSD 3 KB)
• Tube this weekend XSLT (XSLT 2 KB)

Branding

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

Back to top

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 - i.e. average waiting time.

Please note it does not consider

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

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

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 feeds below are not updated and are for demonstration purposes only.
You need to register to gain access to the live feeds.

• PTALS 2012 Data Grid Points

Content providers

TfL General Statistics Team

The feed contains a wealth of information about station accessibility features, including provision of induction loops at ticket windows and Help Points, Blue Badge parking spaces within car parks and station toilet provision.

The data does not give an exhaustive overview of the accessibility of Tube stations. Details of step-free access can be found in our Step-free Tube Guide, which is available at www.tfl.gov.uk/accessguides

Some ideas... Businesses/organisations could add details of the accessibility of their local Tube station.

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

• LU Reports 2010/11 (ZIP 1.61MB)

Content providers... London Underground - Accessibility & Inclusion Team, Customer Service Strategy, Strategy & Commercial

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.

Some ideas...

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

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

• RODS Access mode 2010 sample (CSV 6 KB)

Content providers

London Underground

It has station facilities and access information for each station. All stations are marked with the famous TfL roundel.

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

• Station Facilities (XML 18 KB)

Content provider

TfL Digital

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.

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 feeds below are not updated and are for demonstration purposes only.
You need to register to gain access to the live feeds.

• Counts Entries 2010 Weekday sample data (CSV 101 KB)

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

0200-0215 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