We recommend you use our improved Unified API to access live feeds.

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.

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.

Air quality

The London Air API (from Kings College London) gives up-to-date information on air quality in London over a limited number of locations.

The London Atmospheric Emissions Inventory provides emissions and concentrations estimates across London.

It provides excellent coverage across London (pollutant concentration estimated every 20m) and is a static dataset representing a specific year (and future year estimates). A new version is soon to be released.

General

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

The Journey Planner timetable feed contains up-to-date standard timetables for London Underground, bus, DLR, TfL Rail 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

Our station location feed is a geo-coded KML feed of most London Underground, DLR, TfL Rail 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
  • Use the TfL Rail roundel for TfL Rail stations
  • All stations are marked with the famous TfL roundel

Content provider
TfL Digital

Our station facilities feed is a geo-coded KML feed of most London Underground, DLR, TfL Rail 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

The Common User Format (CUF) is electronic timetable data for each line on the Underground, specifically designed for use in signalling and control systems but also useful for other applications that need to work with timetable data. This data set has richer information about stops and NAPTANS than the timetable data we share in our API.

Download the data set at timetables.data.tfl.gov.uk.

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

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)

Access point MAC addresses and locations for the public WiFi service in our stations are available at place.data.gov.uk. Where an access point is listed as " Root Area", these are points which are in the process of being commissioned and are not yet active. Developers should filter these out if they require only active WIFI points.

Bus, coach and river

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 Bus Services Ltd

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 Bus Services Ltd

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

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.

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

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

This data (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 will be updated every quarter and is available in .xls file format.

This data set includes the geographic boundary of the Greater London Authority road network 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.

Find JSON and Sharp files for Congestion Charge, Low Emission Zone and Ultra Low Emission Zone boundaries on our Roads data page. The ULEZ comes into force on 8 April 2019 and applies 24 hours a day, 7 days a week. The boundary is the same as that for the Congestion Charge. Find out more about ULEZ.

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.

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

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

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

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

Cycling

The latest data for all launched Cycle Superhighways (CS) and the first Quietway route (Quietway 1) is available at cycling.data.tfl.gov.uk in KMZ and shapefile. The data contains Ordnance Survey TOID references, route names and labels to make it easier for you to use this data to display Cycle Superhighway and Quietway routes in your apps.

Some of the routes contain hand-drawn links therefore TOID = NULL. Also the geometry is copied from OSITN and OS Urban Paths datasets which both provide a TOID reference. Routes have been smoothed to remove traffic islands where these were identified in the OSITN nature attribute.

/BikePoint

/Place

/Journey

/AccidentStats

  • Accidents 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.

 Data for all Santander Cycle Hire journeys by week since September 2015 can be found at 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

This data was used to develop the walking Tube map and is available as an xlsx file at 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.

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.

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

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

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.

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

London Underground data 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.

Detailed guidance on the data is available in the Passenger flows and Train loading data descriptions.

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). (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.

Information about the PTAL measure and the way it should be used is available from the Planning with WebCAT page. 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.

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.

Customer volume and flow data

This is a two week sample of customer volume and flow data collected from our automatic fare collection system for the entire TfL rail and bus network in October 2015. The data has been aggregated to 30 minute level, and we have also modified low values for data protection reasons. The data can be found in a zip file  and includes a metadata spreadsheet listing and describing all of the fields.
30 minute entries.csv: this data shows the total number of gateline entries by station, day and 30 minute time interval
30 minute exits.csv: this data shows the total number of gateline exits by station, day and 30 minute time interval
Bus journeys: this data shows the bus boards by stop, route and time of journey
Journey time.txt: this data shows the journeys made between station pairs and the time taken to make the journey

Content providers
London Underground

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

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

This dataset provides a 5% sample of all Oyster card journeys performed in a week during November 2009 on bus, Tube, DLR, TfL Rail 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