Request ID: FOI-1500-2223 Date published: 17 October 2022
You asked
Hi there, please provide TFL Scoot data - both the congestion % and flow count for the following junctions between 7-10am, from 6th september 2021 to current period if possible.
These roads are all in Lambeth in the Dulwich/Herne Hill/Loughborough Junction/Tulse Hill area
- Croxted Rd Northbound at the junction with Norwood Rd
- Turney Rd Eastbound at the junction with Croxted Rd
- Norwood Rd Northbound at the junction with Dulwich Road/Herne Hill Road
-Milkwood Rd Southbound at the junction with Half Moon Lane/Norwood Road
-Herne Hill Southbound at the junction with Half Moon Lane/Norwood Road
- Dulwich Rd Eastbound at the junction with Norwood Road
- Milkwood Rd Northbound at the junction with Cold Harbour Lane
- Loughbourgh Rd Southbound at the junction with Cold Harbour Lane
- Norwood Rd Northbound at the junction with Tulse Hill gyratory
-Norwood Rd Soutbound at the junction with Tulse Hill gyratory
We answered
Our ref: FOI-1500-2223/GH Thank you for your request received by Transport for London (TfL) on 22 September 2022 asking for TFL Scoot data, and for clarifying your request. Your request has been considered under the requirements of the Freedom of Information Act 2000 and our information access policy. I can confirm that we do hold the information you require.
Please see the attached spreadsheet. Below is an 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 between 7am and 10am across all links approaching the junction
FlowDataCompletenessPercentage – Refers to the availability of data; 100% is a complete dataset.
AverageCongestionPercentage – The average congestion between 7am and 10am across all links approaching the junction
CongestionDataCompletenessPercentage – Refers to the availability of data; 100% is a complete dataset
Please Note:
SCOOT Flow may differ from other validated counts as the SCOOT system utilises loop occupancy as it primary source of data, this is then modelled into a flow count via an average occupancy per vehicle. This is often sensitive to over or under saturation, e.g. when vehicles are sat over the detector for long period of time such as in congestion queuing at the lights. The detectors are often sited at a distance from the junction where this is minimised, but sometime 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 is and we are not able to validate this data
If this is not the information you are looking for, or if you are unable to access it for some reason, please do not hesitate to contact me.
If you are not satisfied with this response please see the attached information sheet for details of your right to appeal.
Yours sincerely
Graham Hurt
FOI Case Officer FOI Case Management Team General Counsel Transport for London
