Request ID: FOI-2993-2122 Date published: 19 April 2022
You asked
Hi, under the FOI request can I please request Scoot Volume and traffic and congestion data for all these below sites for dates Jan 1 2019 to today's date March 28 2022.
Can we please have it as excel files for each site broken down by day for flow and congestion separately
Additionally if possible I would like to get ‘Flow’ & ‘Congestion’ data for each location in graph format please.
1. 08/070 Denmark Hill /Champion Park going North/South and East/West
2. 08/102 DOG KENNEL HILL / GROVE LANE / CHAMPION HILL North/South - and East and West separately
3. 08/133 DOG KENNEL HILL / PYTCHLEY ROAD / SAINSBURYS. 2ND OTU 08/633 North/South
4. 08/334 EAST DULWICH GROVE / TOWNLEY ROAD / GREEN DALE East/West, North/South
5. 08/011 DULWICH VILLAGE WAY / EAST DULWICH GROVE / RED POST HILL. East/West and North/South
6. 08/023 DULWICH VILLAGE / TURNEY ROAD / CALTON AVENUE. North/South
7. 08/010 LORDSHIP LANE / BARRY ROAD / WOODWARDE ROAD. North/South and East/West
8. 08/020 LORDSHIP LANE / DULWICH COMMON. North/South and East/West
9. 08/342 A205 DULWICH COMMON BY FRANK DIXON WAY. East/West
10. 08/017 DULWICH COMMON / COLLEGE ROAD East/West
11. 08/214 THURLOW PARK ROAD BY WEST DULWICH STATION. North/South and East/West
12. 08/273 A2214 NUNHEAD LANE / PECKHAM RYE (EAST). East/West
We answered
TfL Ref: FOI-2993-2122
Thank you for your request received by Transport for London (TfL) on 28th March 2022 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:
“Under the FOI request can I please request Scoot Volume and traffic and congestion data for all these below sites for dates Jan 1 2019 to today's date March 28 2022.
Can we please have it as excel files for each site broken down by day for flow and congestion separately Additionally if possible I would like to get ‘Flow’ & ‘Congestion’ data for each location in graph format please. 1. 08/070 Denmark Hill /Champion Park going North/South and East/West 2. 08/102 DOG KENNEL HILL / GROVE LANE / CHAMPION HILL North/South - and East and West separately 3. 08/133 DOG KENNEL HILL / PYTCHLEY ROAD / SAINSBURYS. 2ND OTU 08/633 North/South 4. 08/334 EAST DULWICH GROVE / TOWNLEY ROAD / GREEN DALE East/West, North/South 5. 08/011 DULWICH VILLAGE WAY / EAST DULWICH GROVE / RED POST HILL. East/West and North/South 6. 08/023 DULWICH VILLAGE / TURNEY ROAD / CALTON AVENUE. North/South 7. 08/010 LORDSHIP LANE / BARRY ROAD / WOODWARDE ROAD. North/South and East/West 8. 08/020 LORDSHIP LANE / DULWICH COMMON. North/South and East/West 9. 08/342 A205 DULWICH COMMON BY FRANK DIXON WAY. East/West 10. 08/017 DULWICH COMMON / COLLEGE ROAD East/West 11. 08/214 THURLOW PARK ROAD BY WEST DULWICH STATION. North/South and East/West 12. 08/273 A2214 NUNHEAD LANE / PECKHAM RYE (EAST). East/West” I can confirm that we hold the information you require. This is proivded in the attached spreadsheet (note that there are several worksheets within it). 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
TwentyFourHourVehicleFlowTotal – The total flow observed within a 24 hour period across all links approaching the junction
FlowDataCompletenessPercentage – Refers to the availability of data; 100% is a complete dataset.
AverageCongestionPercentage – The average congestion within a 24 hour 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 data 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 - for example, when vehicles are sat over the detector for long period of time such as when queuing at traffic 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.)
SCOOT congestion is used to operate signals at a junction location and is not indicative of congestion or delay to journey times on the wider road network.
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
