FOI request detail

TFL Scoot data - congestion % and flow data

Request ID: FOI-2370-2223
Date published: 20 January 2023

You asked

Hi there, please provide TFL Scoot data - both the congestion % and flow count for the following junctions between 7-10am. These roads are all in Lambeth in the Dulwich/Herne Hill/Loughborough Junction/Tulse Hill area - Loughbourgh Rd Southbound at the junction with Cold Harbour Lane, Milkwood Road & the A2217. 6th SEpt 2021 to current period. Clarification received 19/01/2023: Hi - thanks so much for following up. Sorry for the badly worded request. Yes please, just one junction thanks: - Loughborough Road Southbound at junction with A2217 between 8-10AM.

We answered

TfL Ref: FOI-2370-2223

Thank you for your request received by Transport for London (TfL) on 20th December 2022 (as clarified on 19th January 2023) asking for Scoot data.
Your request has been considered in accordance with the requirements of the Freedom of Information Act and our information access policy. 

Specifically you asked for data from the junction of Loughborough Road Southbound at junction with A2217 between 8-10AM, for the period from 6th September 2021 to the present.

I can confirm that we hold the information you require which is provided in the attached spreadsheet. Please see the following explanation of what each column refers to within the spreadsheet:
  • SCOOTLinkID – Refers to the SCOOT Link ID
  • LinkDescription – A brief description of the location of the Link typically by road name
  • NodeDescription – A brief description of the Location of the Junction typically by road name
  • Latitude
  • Longitude
  • Date – The date of the data
  • VehicleFlowTotal – The total flow observed within the specified time period across all links approaching the junction
  • FlowDataCompletenessPercentage – Refers to the availability of data; 100% is a complete dataset.
  • AverageCongestionPercentage – The average congestion within the specified time period across all links approaching the junction
  • CongestionDataCompletenessPercentage – Refers to the availability of data; 100% is a complete dataset

Please also note the following:

SCOOT Flow may differ from other validated counts as the SCOOT system utilises “loop occupancy” as it primary source of data, which is then modelled into a flow count via an average occupancy per vehicle. This is often sensitive to over or under saturation - for example, when vehicles are sat over the detector for long periods of time such as in congestion when queuing at the lights. The detectors are often sited at a distance from the junction where this is minimised, but sometimes - especially when junctions are close together - this issue is exaggerated. Therefore SCOOT Flow should be used more to generalise trend of demands and not actual counts.

SCOOT congestion is defined as the number of consecutive congested intervals in a cycle. It is expressed as a proportion of the cycle time. (A congested interval is fully defined as: An interval where any detector on the link has a full interval (detector operated continuously over the four-second interval) and the back of queue is greater than half the maximum or, alternatively, where more than one detector has a full interval.)

The data provided here is given as recorded and we are not able to validate it.

If this is not the information you are looking for, or if you are unable to access it for any reason, please do not hesitate to contact me.

Please see the attached information sheet for details of your right to appeal as well as information on copyright and what to do if you would like to re-use any of the information we have disclosed.

Yours sincerely,

David Wells
FOI Case Officer
FOI Case Management Team
General Counsel
Transport for London


Back to top

Want to make a request?

We'll email you the response within 20 working days.

We'll publish the response online without disclosing any personal information.