Our open data

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.

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

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

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

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

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

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 this is an official TfL application
• Please add the attribution "Data provided by Transport for London"

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:

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.

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

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

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.

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.

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.

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 under the folder /BridgesRestrictions.

The data contains the following variables:

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

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 was updated in July 2017 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 Shape files for Congestion Charge (ZIP 34KB), Low Emission Zone (ZIP 456KB) and Ultra Low Emission Zone (ZIP 224KB) boundaries on our Roads data page.

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

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.

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.

London's Cycling Infrastructure Database (CID) covers all of Greater London and includes the following 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. Find out more about this data on our Digital Blog.

These London-wide maps are available on our open data page and make the Strategic Cycling Analysis 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, please use these maps instead of the old-style London Cycle Network maps which do not match the ambitions of the Mayor's Transport Strategy and Cycling Action Plan.

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

The latest data for cycle routes in London 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.

/BikePoint

• All cycle hire stations (live availability is not returned to make this response more cacheable)
• Search cycle hire by docking station name (with live availability returned for matches)
• The details including availability at a given bike station, using the BikePoint's unique id

/Place

• Cycle parking (Place resource with PlaceType "CyclePark")
• Search by geographical area (with live availability returned for matches)
• Search for nearest within a given distance of a point (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: all the way/leave at station/take on transport/cycle hire (/Journey)
• Cycle routes graded as easy/moderate/fast (/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

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.

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.

• Station topology files (GTFS)
• Station topology files (detailed)
• Live lift disruption feed

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.

The data underlying TfL's Network Demand Dashboard report has been made available for exporting, this can be found in the "Network Demand/" folder.

Please note the following:

• 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 1st Jan 2023 to date has been compiled into a single file (one for each Journey & Station Footfall) which gets refreshed with data till 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 landing page.

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.

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.

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

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

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

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

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

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

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

The Borough Local Implementation Plan transport targets datapack 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.

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 of the locations in each borough where charges are apply, with GIS files in TAB and ESRI format.

The draft London Plan cycle parking calculator 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.
 

The Pedestrian Comfort Level calculator accompanies our Pedestrian Comfort Guidance 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.

The Active Travel Zone GIS layers can be used in Healthy Streets Transport Assessments especially the step by step Active Travel Zone assessment:

• 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. Includes Street Types scores from our 2012 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
  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