TfL Open Data
Source: data.gov.uk (2017-03-06)

Transport for London - Open Data. <div>
<p><strong>TfL statement:</strong></p>
<p>We've committed to making our open data freely available to third parties and to engaging developers to deliver new products, apps and services for our customers.</p>
<p>Over 11,000 developers have registered for our open data, consisting of our unified API (Application Programming Interface) that powers over 600 travel apps in the UK with over 46% of Londoners using apps powered by our data.</p>
<p>This enables millions of journeys in London each day, giving customers the right information at the right time through their channel of choice.</p>
<h2 id="on-this-page-0">Why are we committing to open data?</h2>
<ul>
<li>Public data - As a public body, our data is publically owned</li>
<li>Reach - Our goal is to ensure any person needing travel information about London can get it wherever and whenever they wish, in any way they wish</li>
<li>Economic benefit - Open data facilitates the development of technology enterprises, small and medium businesses, generating employment and wealth for London and beyond</li>
<li>Innovation - By having thousands of developers working on designing and building applications, services and tools with our data and APIs, we are effectively crowdsourcing innovation</li>
</ul>
<h2 id="on-this-page-1">How is our open data presented?</h2>
<p>Data is presented in three main ways:</p>
<ul>
<li>Static data files - Data files which rarely change</li>
<li>Feeds - Data files refreshed at regular intervals</li>
<li>API (Application Programming Interface) - Enabling a query from an application to receive a bespoke response, depending on the parameters supplied. <a class="external-link" href="https://api.tfl.gov.uk/" target="_parent">Find out more about our unified API</a>.</li>
</ul>
<p>Data is presented as XML wherever possible.</p>
</div>

Transportfor London (/)

Search the site
- Fares (/fares/)
- Help & contacts (/help-and-contact/)
- Maps (/maps_/maps)
- Plan a journey (/plan-a-journey/)
- Status updates (/status-updates/)
Travel information
- Improvements & projects (/travel-information/improvements-and-projects/)
- Safety (/travel-information/safety/)
- Stations, stops & piers (/travel-information/stations-stops-and-piers/)
- Timetables (/travel-information/timetables/)
- Transport accessibility (/transport-accessibility/)
- Visiting London (/travel-information/visiting-london/)
Ways to get around
- Buses (/modes/buses/)
- Coaches (/modes/coaches/)
- Cycling (/modes/cycling/)
- Dial-a-Ride (/modes/dial-a-ride/)
- DLR (/modes/dlr/)
- Driving (/modes/driving/)
- Elizabeth line (/modes/elizabeth-line/)
- IFS Cloud Cable Car (/modes/london-cable-car/)
- London Overground (/modes/london-overground/)
- River (/modes/river/)
- Taxis & minicabs (/modes/taxis-and-minicabs/)
- Trams (/modes/trams/)
- Tube (/modes/tube/)
- Walking (/modes/walking/)
Quick links
- Contactless and Oyster account (/fares/contactless-and-oyster-account)
- Refunds and replacements (/fares/refunds-and-replacements)
- Pay to drive in London (/modes/driving/pay-to-drive-in-london)
- Travel tools (/status-updates/travel-tools)
- Home (/)
- Open data users (/info-for/open-data-users/)
- Our open data
Our open data

A list of available TfL data feeds and guidelines for using them

We recommend you use our improved Unified API (/info-for/open-data-users/unified-api) to access live feeds.

Syndication developer guidelines

PDF 81KB

These guidelines include technical information to help you understand how our open data works and how to use it 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 (/corporate/terms-and-conditions/transport-data-service).

The example data listed below are not updated and are for demonstration purposes only. You will need to register to gain access to the live feeds (https://api-portal.tfl.gov.uk/).

Air quality

London Air API

The London Air API (http://www.londonair.org.uk/LondonAir/API/) (from Imperial College London) gives up-to-date information on air quality in London over a limited number of locations.

Atmospheric Emissions Inventory

The London Atmospheric Emissions Inventory (https://data.london.gov.uk/air-quality/) details emissions and concentrations estimates across London.

It provides coverage across London (pollutant concentration estimated every 20 metres) and is a static dataset representing a specific year (and future year estimates).

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 (https://api-portal.tfl.gov.uk/).

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
- Do not include any TfL branding in your application or give the impression this is an official TfL application
- Add the attribution "Powered by the Transport for London Journey Planner API" in the application credits
Journey Planner API documentation

PDF 845KB

Content provider Transport for London

Journey Planner timetables

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

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

Maximum time allowed between capturing and displaying the feed 10 minutes

Maximum time information can be displayed before being updated 1440 minutes

Some ideas
- Create an application that allows Londoners to plan their journeys
The example feed below is not updated and is for demonstration purposes only. You need to register to gain access to the live feeds (https://api-portal.tfl.gov.uk/).

Journey Planner timetables

ZIP 24.31MB

Content provider TfL Group Customer Services

Station locations

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

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

Maximum time allowed between capturing and displaying the feed 10 minutes

Maximum time information can be displayed before being updated 4320 minutes

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 (https://api-portal.tfl.gov.uk/).

Station locations KML

KML 2KB

Station locations XSD

XSD 2KB

Branding
- Use the Tube roundel for Tube stations
- Use the DLR roundel for DLR stations
- Use the London Overground roundel for London Overground stations
- Use the Elizabeth line roundel for Elizabeth line 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, Elizabeth line 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 minutes

Maximum time allowed between capturing and displaying the feed 10 minutes

Maximum time information can be displayed before being updated 4320 minutes

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 (https://api-portal.tfl.gov.uk/).

Station facilities

XML 18KB

Content provider TfL Digital

Station and stop topology

Stop Structure is an API that provides data about the topology of a station, stop, pier or other stop point. In other words, it includes data about entrances, concourses, ticket halls and platforms, as well as possible interchanges between these areas.
- Stop Structure API documentation and examples (https://techforum.tfl.gov.uk/t/stop-structure-station-and-stop-topology-api/2796)
You need to register to gain access to the live feeds (https://api-portal.tfl.gov.uk/).

Branding
- Do not include any TfL branding in your application or give the impression this is an official TfL application
- Add the attribution "Data provided by Transport for London"
Tube

Tube departure boards, line status and station status

This feed provides access to live 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 seconds

Maximum time allowed between capturing and displaying the feed 30 seconds

Maximum time information can be displayed before being updated 30 seconds

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:

Development Beta SDK

PDF 382KB

You need to register to gain access to the live feeds (https://api-portal.tfl.gov.uk/).

Branding

Follow the relevant design standards (/info-for/business-and-advertisers/design-standards).

Service updates

Our style guide shows you how we display live travel information and provides guidance on how to reproduce this:

User guide for the presentation of service updates

PDF 85KB

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 minutes

Maximum time allowed between capturing and displaying the feed 2 minutes

Maximum time information can be displayed before being updated 10 minutes

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 (https://api-portal.tfl.gov.uk/).

Tube this weekend XML

XML 5KB

Tube this weekend XSD

XSD 3KB

Tube this weekend XSLT

XSLT 3KB

Branding
- Use the correct colour to represent each Tube line
- Text: 'Information supplied by Transport for London' (hyperlink)
Bus, coach and river

Live bus arrivals API (instant)

This API provides realtime bus arrival information across all TfL bus stops. Instant requests are responded to with the live 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 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
- Venue owners could include their bus stop code with their listing details, so customers can easily find nearby bus stops
Live bus and river bus arrivals interface documentation

PDF 560KB

You need to register to gain access to the live feeds (https://api-portal.tfl.gov.uk/).

Branding
- Do not include any TfL branding in your application or give the impression it is an official TfL application
- Add the attribution "Data provided by Transport for London"
Content provider London Bus Services Ltd

Live bus arrivals API (stream)

This API provides realtime bus arrival information across all TfL bus stops. Stream requests are responded to with a continuous supply of live 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 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
- Venue owners could include their bus stop code with their listing details, allowing customers to easily find nearby bus stops
Live bus and river bus arrivals interface documentation

PDF 560KB

You need to register to gain access to the live feeds (https://api-portal.tfl.gov.uk/).

Branding
- Do not include any TfL branding in your application or give the impression it is an official TfL application
- Add the attribution "Data provided by Transport for London"
Content provider London Bus Services 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 (https://api-portal.tfl.gov.uk/).

Bus stops examples

CSV 13KB

Bus stops sequences examples

CSV 30KB

Guidelines

Syndication developer guidelines - Bus stops and routes

PDF 96KB

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 (/corporate/publications-and-reports/buses-performance-data#on-this-page-5) 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 minutes

Maximum time allowed between capturing and displaying the feed 10 minutes

Maximum time information can be displayed before being updated 4320 minutes

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 (https://api-portal.tfl.gov.uk/).

Coach parking

CSV 3KB

Coach parking - theatre information

CSV 6KB

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 minutes

Maximum time allowed between capturing and displaying the feed 10 minutes

Maximum time information can be displayed before being updated 4320 minutes

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 (https://api-portal.tfl.gov.uk/).

Pier locations KML

KML 1KB

Pier locations XSD

XSD 2KB

Branding
- Use the Rivers roundel for piers
- All locations are marked with the famous TfL roundel
Content provider River Services, TfL Surface Transport

Expired bus schedules

Open a .zip file to view bus schedules up to 2 August 2018. (http://bus.data.tfl.gov.uk/expired-schedules/ExpiredSchedules.zip)

Roads

Bridges, tunnels, road barriers - height restrictions

This data set covers 877 structures within the Greater London boundary / M25 comprising of low bridges, tunnels and road barriers in a .csv file which will be updated annually. It is available in our Roads data bucket (http://roads.data.tfl.gov.uk/) under the folder /BridgesRestrictions.

The data contains the following variables:
- Up to 3.0
- Between 3.1 and 3.5
- Between 3.6 and 4.0
- Between 4.1 and 4.5
- Between 4.6 and 5.1
- Up to 9'10"
- Between 9'10" and 11'6"
- Between 11'9" and 13'0"
- Between 13'3" and 14'9"
- Between 15'0" and 16'6"
- Yes = restriction is located on TLRN
- No = sign is NOT located on TLRN
(TLRN = Transport for London Road Network Area = Red Route road network controlled by TfL)

You can add the data as a layer to any mapping or routing product, for example, to plan routes for freight vehicles which avoid bridges which are too low for the vehicle.

Note: Data last updated in October 2019

Busiest times at Blackwall Tunnel

This data (http://roads.data.tfl.gov.uk/) (available under the Journey Times section) shows journey times from Greenwich to Bow through Blackwall Tunnel on a busy weekday and weekend. The journey times come from calculating the time to travel between two locations in heavy traffic conditions. We use anonymised records from TfL's Automatic Number Plate Recognition cameras to calculate these journey times.

You can use this data to see the busiest times on our network and create products for planning quicker and more reliable journeys. The data was updated in July 2017 and is available in .xls file format.

Geographic boundary of the GLA road network

This data set includes the geographic boundary of the Greater London Authority road network (http://roads.data.tfl.gov.uk) for which Transport for London is the Highway Authority.

Sections 14C of the 1980 Highways Act requires TfL to maintain a record of the roads for which it is the Highway Authority. The dataset(s) published here are TfL's record in map form. The boundaries are for visualisations at scale of 1:1250.

CC, LEZ and ULEZ boundaries

Find JSON and Shape files for Congestion Charge (https://s3-eu-west-1.amazonaws.com/roads.data.tfl.gov.uk/boundaries/CC_Boundary_v8_20190526_tab_shape.zip) (ZIP 34KB), Low Emission Zone (https://s3-eu-west-1.amazonaws.com/roads.data.tfl.gov.uk/boundaries/LEZ_Boundary_20071113_tab_shape.zip) (ZIP 456KB) and Ultra Low Emission Zone (https://s3.eu-west-1.amazonaws.com/roads.data.tfl.gov.uk/Boundaries/ULEZ_Boundary_20230829_Shape+Files.zip) (ZIP 224KB) boundaries on our Roads data page (http://roads.data.tfl.gov.uk/).

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 minutes

Maximum time allowed between capturing and displaying the feed 5 minutes

Maximum time information can be displayed before being updated 30 minutes

The example feeds below are not updated and for demonstration purposes only. You need to register to gain access to the live feeds (https://api-portal.tfl.gov.uk/).

TIMS feed technical specification

PDF 465KB

TIMS feed sample XML data

XML 1KB

TIMS feed sample XML errors

XML 1KB

Post code areas impacted by major road schemes

Our postcode impact data is an extract from our GIS mapping of areas impacted by construction work for the Road Modernisation Plan, including Cycle Superhighways and Better Junctions.

How often we publish a fresh copy of the feed We will update this data file monthly, in line with our latest expectations and calibrated traffic modelling of the impact of construction work.

Some ideas
- Check whether sites you deliver to are impacted, and at what times of day
- Consider retiming your deliveries or trips so they are at quieter times of day
Postcode impact data

XLSX 232KB

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 over 700 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 minutes

Maximum time allowed between capturing and displaying the feed 2 minutes

Maximum time information can be displayed before being updated 15 minutes

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 (https://api-portal.tfl.gov.uk/).

Live traffic cameras

XML 29KB

Live traffic cameras schema

TXT 2KB

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 minutes

Maximum time allowed between capturing and displaying the feed 5 minutes

Maximum time information can be displayed before being updated 30 minutes

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 (https://api-portal.tfl.gov.uk/).

Live roadside message signs

XML 32KB

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

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 minutes

Maximum time allowed between capturing and displaying the feed 10 minutes

Maximum time information can be displayed before being updated 4320 minutes

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 (https://api-portal.tfl.gov.uk/).

Licensed private hire operators - Findaride XML

XML 767KB

Licensed private hire operators - Findaride XSD

XSD 6KB

Branding

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

Content provider TfL Taxis and Private Hire

Cycling

Cycling Infrastructure Database (CID)

London's Cycling Infrastructure Database (CID) covers all of Greater London and includes these assets:
- Cycle lanes and tracks
- Cycle parking
- Signalised crossings for cycles
- Restricted routes - Modal filters and traffic gates which allow cycles to pass but restrict car traffic
- Traffic calming, including the location of all speed humps
- Advanced stop lines - boxes at junctions for people cycling
- Signals - early-release signals at junctions
- Signage - Signed cycle routes and other wayfinding
- Restricted Points - points where people cycling will have to dismount
- Paths through parks and other green spaces that can, and cannot, be cycled on
Access the full data set and schema under CycleInfrastructure/Data and CycleInfrastructure/Documentation (https://cycling.data.tfl.gov.uk/). Find out more about this data on our Digital Blog (https://blog.tfl.gov.uk/2019/08/13/data-drop-cycling-infrastructure-database/).

Strategic Cycling Analysis maps

These London-wide maps are available on our planning data page (http://planning.data.tfl.gov.uk/) and make the Strategic Cycling Analysis (http://content.tfl.gov.uk/strategic-cycling-analysis.pdf) more accessible:
- Current and future cycle network
- Permeable Neighbourhoods
The maps split London into a grid made up of 8km squares, so there are 36 versions of each map above. These files show the grid frame:
- London 8km cycling quadrants Frame (pdf)
- London 8km cycling quadrants Frame (kmz, Google Maps)
NB: If you are using this information for London planning applications, use these maps instead of the old-style London Cycle Network maps which do not match the ambitions of the Mayor's Transport Strategy (/corporate/about-tfl/the-mayors-transport-strategy) and Cycling action plan on that page.

CS3 and CS6 cycle counter statistics

Monthly statistics on the number of cyclists on Superhighways CS3 and CS6 from the counters at Blackfriars Bridge and Victoria Embankment are available at http://cycling.data.tfl.gov.uk

Cycling routes

The latest data for cycle routes in London (http://cycling.data.tfl.gov.uk) is available under the "CycleRoutes/" folder. This dataset includes all open, in-progress and future (post-consultation) cycle routes in London and is available in JSON and KML format.

The cycle routes data contains the following meta-data: route names, labels, status and programme. It is updated regularly to reflect the developing cycling network.

Cycling data in the unified API

/BikePoint
- All cycle hire stations (https://api.tfl.gov.uk/swagger/ui/index.html?url=/swagger/docs/v1#!/BikePoint/BikePoint_GetAll) (live availability is not returned to make this response more cacheable)
- Search cycle hire by docking station name (https://api.tfl.gov.uk/swagger/ui/index.html?url=/swagger/docs/v1#!/BikePoint/BikePoint_Search) (with live availability returned for matches)
- The details including availability at a given bike station (https://api.tfl.gov.uk/swagger/ui/index.html?url=/swagger/docs/v1#!/BikePoint/BikePoint_Get), using the BikePoint's unique id
/Place
- Cycle parking (https://api.tfl.gov.uk/swagger/ui/index.html?url=/swagger/docs/v1#!/Place/Place_GetByType) (Place resource with PlaceType "CyclePark")
- Search by geographical area (https://api.tfl.gov.uk/swagger/ui/index.html?url=/swagger/docs/v1#!/Place/Place_GetByGeoBox) (with live availability returned for matches)
- Search for nearest within a given distance of a point (https://api.tfl.gov.uk/swagger/ui/index.html?url=/swagger/docs/v1#!/Place/Place_GetByGeoPoint) (with live availability returned for matches). To return top n nearest cycle parking places within a given distance of a point, please additionally specify 'numberOfPlacesToReturn' as part of the request.
/Journey
- Cycle preference (https://api.tfl.gov.uk/swagger/ui/index.html?url=/swagger/docs/v1#!/Journey/Journey_JourneyResults): all the way/leave at station/take on transport/cycle hire (/Journey)
- Cycle routes graded (https://api.tfl.gov.uk/swagger/ui/index.html?url=/swagger/docs/v1#!/Journey/Journey_JourneyResults) as easy/moderate/fast (/Journey)
/AccidentStats
- Accidents (https://api.tfl.gov.uk/swagger/ui/index.html?url=/swagger/docs/v1#!/AccidentStats/AccidentStats_Get) involving road users, which can be filtered to those involving cyclists
For a full list of all API data feeds, please visit our unified API (https://api.tfl.gov.uk/).

Cycle Hire trip data

Data for all Santander Cycle Hire journeys by week since September 2015 can be found at cycling.data.tfl.gov.uk (http://cycling.data.tfl.gov.uk/).

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
Walking

Walking times between adjacent stations in Zones 1-3

This data was used to develop the walking Tube map (/modes/walking/) and is available as an xlsx file at walking.data.tfl.gov.uk (http://walking.data.tfl.gov.uk/).

The data defines the time it takes (in minutes) to walk between adjacent Tube, Overground and DLR stations on the same line and between adjacent National Rail stations all within Zones 1-3.

This data could be used to show that walking in London can often be the quickest way to get from A to B.

This data was sourced from Google Maps.

Due to the way in which the data was sourced, there may be some instances where the walking time differs from the time shown in TfL Journey Planner and the Unified API.

Walking times for selected Central London journeys which could be quicker to walk

This data contains a selection of Central London walking journeys (that are not on the same Tube, DLR, London Overground or National Rail line) that could be quicker to walk. The data is available at walking.data.tfl.gov.uk (http://walking.data.tfl.gov.uk/).

The data contains details on the time it takes (in minutes) as well as the number of steps to walk between these destinations. A moderate walking pace has been used for all walking times, and an average of 100 steps per minute has been used to represent the approximate number of steps taken between journeys.

This data could be used to show that walking in London can often be the quickest way to get from A to B, especially when journeys require interchanges.

This data was sourced from Google Maps.

Due to the way in which the data was sourced, there may be some instances where the walking time differs from the time shown in TfL Journey Planner and the Unified API.

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 minutes

Maximum time allowed between capturing and displaying the feed 10 minutes

Maximum time information can be displayed before being updated 4320 minutes

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 (https://api-portal.tfl.gov.uk/).

Oyster Ticket Stop locations KML

KML 1KB

Oyster Ticket Stop locations XSD

XSD 2KB

Branding

Use the Oyster Ticket Stop logo for Oyster Stop locations

Content provider TfL Fares and Ticketing

Accessibility and toilets

Step-free access and toilet data
- Station topology files (GTFS) (https://api.tfl.gov.uk/stationdata/tfl-stationdata-gtfs.zip)
- Station topology files (detailed) (https://api.tfl.gov.uk/stationdata/tfl-stationdata-detailed.zip)
- Live lift disruption feed (https://api.tfl.gov.uk/Disruptions/Lifts/v2)
Step-free access and toilet data guide

PDF 191KB

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 (https://api-portal.tfl.gov.uk/).

Bus stations with public toilets

CSV 1KB

Network statistics

Daily journeys and station footfall

The Network demand data (https://tfl.gov.uk/corporate/publications-and-reports/network-demand-data) underlying TfL's Network Demand Dashboard (https://app.powerbi.com/view?r=eyJrIjoiZDgwZWY4NWMtZTFkMi00YzM2LThiMWQtNzg2ZTc2YjliNzM2IiwidCI6IjFmYmQ2NWJmLTVkZWYtNGVlYS1hNjkyLWEwODljMjU1MzQ2YiIsImMiOjh9) report has been made available for exporting. Note:
- Journey data is available only for bus and Tube journeys, whereas Station footfall data is available for Tube and TfL Rail stations
- Data has been segregated into each year from 2019-2022
- Data from 1 January 2023 to date has been compiled into a single file (one for each Journey and Station footfall) which gets refreshed with data until the last Saturday, once a week
- Since there might be Taps data coming in late to our servers, there might be slight discrepancies between the data in the file and the dashboard - the dashboard is updated more frequently, and hence would be more up-to-date
- With every refresh of the files however, the data for all the rows gets updated with the most up-to-date data. The date and time of refresh has been appended in the file name itself for better transparency
- Our reporting methodology, assumptions and calculations have been documented in the 'Data Guide' linked to Network Demand Dashboard (https://app.powerbi.com/view?r=eyJrIjoiZDgwZWY4NWMtZTFkMi00YzM2LThiMWQtNzg2ZTc2YjliNzM2IiwidCI6IjFmYmQ2NWJmLTVkZWYtNGVlYS1hNjkyLWEwODljMjU1MzQ2YiIsImMiOjh9) landing page.
Busiest times on trains and in stations

London Underground data (http://crowding.data.tfl.gov.uk) for customer volumes and movements in stations and train occupancy for a typical weekday. You can use this data to see the busiest locations and times on our network and create products for planning quicker and more comfortable journeys.

Public Transport Access Level (PTAL)

PTAL is a measure of Public Transport Access Level.

We allow users to download the same PTAL data that is used in our Web-based Connectivity Assessment Toolkit (WebCAT) (/info-for/urban-planning-and-construction/planning-with-webcat/webcat). (Any data that was previously available is superseded by the data provided currently, and should no longer be used.)

The use of this data, either through WebCAT or when downloaded from here, is subject to the WebCAT terms of use (/corporate/terms-and-conditions/webcat).

Information about the PTAL measure and the way it should be used is available from the Planning with WebCAT page (/info-for/urban-planning-and-construction/planning-applications/planning-with-webcat). Download the 'Transport connectivity assessment guide' on that page for additional background, examples and other useful measures of connectivity to complement the work with PTAL.

The PTAL grid

PTAL values are provided for a grid of points at 100 meter intervals, covering the whole of London. The concept of presenting PTAL values for grid points is explained in detail in the guide on the Planning with WebCAT page.

The available PTAL data is provided in three files, one for a recent base year and two others for future scenarios in 2021 and 2031.

Format

Each of the files is in CSV format, containing the following data fields:
- A unique identifier for each grid point
- The X (Easting) coordinate, based on the British National Grid
- The Y (Northing) coordinate, based on the British National Grid
- The Access Index (AI) for the point (a calculated value from which we derive PTAL)
- The Public Transport Access Level (PTAL)
The data can be imported into any standard GIS package using the X and Y coordinates.

TfL detailed annual rail and Tube demand dataset

NUMBAT is TfL's most comprehensive rail demand dataset and provides data on boarders/alighters or demand on trains and in stations. Data is available from 2016 and represents the London Underground, Overground, Elizabeth Line and DLR demand.

NUMBAT is for a typical day (by daytype) in the autumn of each year. Multiple data sources were combined to smooth any gaps and provide further information than otherwise available (such as lineloads). The data is adjusted to remove any abnormal circumstances and key events that may affect demand such as industrial action or short-term closures.

Year-on-year NUMBAT fluctuations do not necessarily reflect whole-year annual demand changes. If you are interested in annualised station entry/exit totals, see Annual Counts instead of NUMBAT - it is available on the same crowding data page.
- Access NUMBAT (http://crowding.data.tfl.gov.uk/)
NUMBAT outputs are all given by 15 minutes throughout the day, representing typical flows by daytype:
- Link Load: Number of passengers on the train between two different consecutive stations on a line e.g. from Lambeth North to Waterloo on the Bakerloo line
- Link frequency (supply): Number of scheduled trains per quarter hour between two consecutive stations
- Station Boarders/Alighters: Number of passengers boarding or alighting at a specific platform in a specific station
- Line Boarders: Total boarders across a rail line, derived from summing station boarders. This gives a better picture than Entry/Exits for the utilisation of a line as it includes interchangers
- Station Flow: Number of passenger movements inside a station between its entrances and its different platforms. This includes boarding/alighting and interchange flows
- Station Entries/Exits: number of passengers entering/exiting the station through its gatelines (see also Annual Counts)
TWT is the average of Tuesday, Wednesday and Thursday, so summing all of NUMBAT 5 day types together is different from a week's passenger counts.

RODS data is available on this site for 1996-2017. Please note this had a different methodology to NUMBAT.

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

TfL Annual Counts (Entry/Exit) for rail and Tube

Annual Counts present an annual picture of station entries and exits, used for trend analysis. Raw data is supplemented where there are gaps (such as ungated stations, or magnetic tickets not being picked up). The data is adjusted to remove any abnormal circumstances and key events that may affect demand such as industrial action or short-term closures.

Annual Counts are for a typical day (by daytype) in the autumn of each year. The outputs are all given by 15 minutes throughout the day, by timeband and are annualised using revenue data.
- Access Annual Counts (http://crowding.data.tfl.gov.uk/)
If you are interested in boarders/alighters or demand on trains and in stations please see NUMBAT - it is available on the same crowding data page.

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

Bus boardings, alightings and loadings - BUSTO

The BUSTO dataset provides an estimate of boardings, alightings and loadings on a typical day on TfL's bus network.

The dataset is published annually and represents the travel demand on the bus network on a typical weekday, Saturday and Sunday. Data is available for all routes except school and mobility routes.

The data (http://crowding.data.tfl.gov.uk/) is available in .csv format can be found in a data bucket under the folder /BUSTO.

Further information about the BUSTO dataset (and how it can be used) is available in the BUSTO User Guide and Data Dictionary (PDF 2.0MB) (https://crowding.data.tfl.gov.uk/BUSTO/BUSTO%20User%20Guide%20and%20Data%20Dictionary%20v1.1.pdf).

Dial-a-Ride statistics

This quarterly report (http://accessibility.data.tfl.gov.uk) 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.

A number of figures are 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. 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
Notes
- Cancellations are shown as percentages of scheduled requests
- Passenger cancellations are where DaR has scheduled the trip but the passenger subsequently cancels, most commonly because of illness
- Others/unknown includes visitors to London and a small number of members living just outside the Greater London boundary with "grandparent rights"
- 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

Planning

For London planning applications, you should also refer to the Rolling Origin & Destination Survey (RODS) data under Network Statistics (https://tfl.gov.uk/info-for/open-data-users/our-open-data#on-this-page-9) and Strategic Cycling Analysis Maps under Cycling (https://tfl.gov.uk/info-for/open-data-users/our-open-data#on-this-page-5).

Borough Local Implementation Plan - transport targets data

The Borough Local Implementation Plan transport targets datapack (http://planning.data.tfl.gov.uk) contains borough level data on the Outcome Indicators for the Mayor's Transport Strategy. These include sustainable mode share, casualty numbers by severity, road transport emissions etc, by borough as well as future trajectories for these to 2041.

The datapack also contains each of the borough's Local Implementation Plan targets for the Mayor's Transport Strategy Outcomes. Its purpose is to monitor progress, at a borough and London-wide level, towards achieving the aims and targets of the strategy.

Lane Rental Scheme

The TfL Lane Rental Scheme (TLRS) was introduced in June 2012. It applies a charge for lane rental to the most traffic-sensitive locations of the Transport for London Road Network (TLRN) at traffic-sensitive times of day. 56% of the TLRN is affected.
- Maps (http://planning.data.tfl.gov.uk/) of the locations in each borough where charges are apply, with GIS files in TAB and ESRI format.
Draft London Plan cycle parking calculator

The draft London Plan cycle parking calculator (http://planning.data.tfl.gov.uk/) enables quick and easy calculation of the amount of cycle parking required for a new development so it complies with the draft new London Plan (https://www.london.gov.uk/what-we-do/planning/london-plan/new-london-plan).

Pedestrian Comfort Level calculator

The Pedestrian Comfort Level calculator (http://planning.data.tfl.gov.uk/) accompanies our Pedestrian Comfort Guidance (http://content.tfl.gov.uk/pedestrian-comfort-guidance-technical-guide.pdf) and instructions for using this spreadsheet are in that document.

Users should retain the example in the spreadsheet, as deleting it de-activates the system's calculator.

Active Travel Zone (ATZ)

The Active Travel Zone GIS layers (http://planning.data.tfl.gov.uk/) can be used in Healthy Streets Transport Assessments (/cdn/static/cms/documents/healthy-streets-ta-format.pdf) especially the step by step Active Travel Zone assessment (/cdn/static/cms/documents/atz-assessment-instructions.pdf):
- Town Centres NOTE: GLA Town Centre Classifications 2015.
- TfL Step-Free Access current programme NOTE: Does not include accessibility improvements linked to other major schemes, e.g. Crossrail. Subject to change based on feasibility and consultation.
- Strategic Cycle Network NOTE: Planned and existing routes. All planned routes subject to further feasibility and consultation.
- Permeable Neighbourhoods NOTE: Created during preparation of our Strategic Cycling Analysis (http://content.tfl.gov.uk/strategic-cycling-analysis.pdf). Includes Street Types scores from our 2012 Roads Task Force (https://tfl.gov.uk/corporate/publications-and-reports/roads-task-force) for some of London's major routes.
- Cycle Parking demand at stations NOTE: Uploaded Feb 2019. Based on TfL Strategic Analysis data. Remember all stations in London experience some cycle parking demand.
- TfL Safer Junctions (/travel-information/improvements-and-projects/our-plan-for-londons-roads) NOTE: Uploaded March 2019. Subject to feasibility, consultation, and further design work.
- TfL Safer Speed programme NOTE: Uploaded March 2019. Subject to feasibility, consultation, and further design work.
- Healthy Streets in progress Local Schemes NOTE: Uploaded March 2019. Subject to feasibility, consultation, and further design work. 'Built' or 'On Site' status subject to change. Please consider extending 'Built' schemes outwards onto surrounding highway using Healthy Streets principles.
Other useful open data for the mapping in ATZ assessments includes:
- Ordnance Survey for Green Spaces, Medical, Educational, and Worship land uses The Medical/Educational/Worship data is in the OS VectorMap® District data Functional Sites shape file (e.g. TQ_FunctionalSite.shp). You will need to download both the TQ and TL tiles.
- Space Syntax for a range of spatial data including permeable street networks
Sign in or register for data feeds

Open data users navigation

Open data policy (/info-for/open-data-users/open-data-policy)

Unified API (/info-for/open-data-users/unified-api)

Our open data (/info-for/open-data-users/our-open-data)

Design & branding (/info-for/open-data-users/design-and-branding)

About TfL
- Help & contacts (/help-and-contact/)
- About TfL (/corporate/about-tfl/)
- Careers (/corporate/careers/)
- Publications & reports (/corporate/publications-and-reports/)
- Safety & security (/corporate/safety-and-security/)
- Social media & email updates (/travel-information/social-media-and-email-updates/)
- Transparency (/corporate/transparency/)
- Gift Shop (https://www.ltmuseumshop.co.uk/)
Information for...
- Boroughs & communities (/info-for/boroughs-and-communities/)
- Bus operators (/info-for/bus-operators/)
- Business & advertisers (/info-for/business-and-advertisers/)
- Coach drivers (/info-for/coach-drivers/)
- Freight & servicing in London (/info-for/deliveries-in-london/)
- Investors (/info-for/investors/)
- Media (/info-for/media/)
- Open data users (/info-for/open-data-users/)
- Schools & young people (/info-for/schools-and-young-people/)
- Suppliers & contractors (/info-for/suppliers-and-contractors/)
- Taxi & private hire (/info-for/taxis-and-private-hire/)
- Urban planning & construction (/info-for/urban-planning-and-construction/)
- Mayor of London (http://www.london.gov.uk/)
- London Assembly (http://www.london.gov.uk/mayor-assembly/london-assembly)
- London and Partners (http://www.londonandpartners.com/)
- Metropolitan Police Service (https://www.met.police.uk/)
- London Fire Brigade (https://www.london-fire.gov.uk/)
- The Mayors Office of Policing and Crime (https://www.london.gov.uk/what-we-do/mayors-office-policing-and-crime-mopac)
Legal information
- Data sources (/corporate/data-sources)
- Privacy & cookies (/corporate/privacy-and-cookies/)
- Terms & conditions (/corporate/terms-and-conditions/)
- Digital accessibility (/corporate/website-accessibility/)
Close Favourites

My Lines

Edit my lines (javascript:void(0);)

Service BoardSorry, service board information could not be retrieved. Service BoardService information is out of date. Please try reloading the page.

View all statuses (/tube-dlr-overground/status/)

My Buses

Edit my buses (javascript:void(0);)

My Roads

Edit my roads (javascript:void(0);)

Service BoardSorry, service board information could not be retrieved. Service BoardService information is out of date. Please try reloading the page.

View all reported incidents (/traffic/status/)

My River Buses

Edit my river buses (javascript:void(0);)

Service BoardSorry, service board information could not be retrieved. Service BoardService information is out of date. Please try reloading the page.

View all statuses (/river/status/)

My IFS Cloud Cable Car

Edit my IFS Cloud Cable Car (javascript:void(0);)

Service BoardSorry, service board information could not be retrieved. Service BoardService information is out of date. Please try reloading the page.

View status (/cable-car/status/)

My Journeys

Edit my journeys (javascript:void(0);)

My Places

Edit my places (javascript:void(0);)

Add favourites for quick access to live status, journeys and places

Lines (javascript:void(0);)

Buses (javascript:void(0);)

Roads (javascript:void(0);)

River Buses (javascript:void(0);)

IFS Cloud Cable Car (javascript:void(0);)

JourneysPlan a journey and favourite it for quick access in the future (/plan-a-journey/)

PlacesChoose postcodes, stations and places for quick journey planning (javascript:void(0);)

Close edit Favourites

Favourite lines

Done updating my favourites

Bakerloo

Central

Circle

District

DLR

Elizabeth line

Hammersmith & City

Jubilee

Liberty

Lioness

Metropolitan

Mildmay

Northern

Piccadilly

Suffragette

Tram

Victoria

Waterloo & City

Weaver

Windrush

Favourite buses

Done updating my favourites

Add new bus

Search

Favourite roads

Done updating my favourites

A1

A10

A12

A13

A2

A20

A21

A23

A24

A3

A316

A4

A40

A41

Blackwall Tunnel

Central London Red Routes

North Circular (A406)

South Circular (A205)

Favourite river buses

Done updating my favourites

RB1

RB2

RB4

RB5

RB6

Woolwich Ferry

Favourite IFS Cloud Cable Car

Done updating my favourites

IFS Cloud Cable Car

Favourite journeys

Done updating my favourites

My places

Done updating my favourites

Add new place

Done updating my favourites

Existing place (javascript:void(0)) Add a Label (javascript:void(0))

Add a label

Search

Add places

Places Choose postcodes, stations and places for quick journey planning (/plan-a-journey/)

FaviconFavourites updatedView (javascript:void(0))