FOI request detail

Traffic count & congestion data SE21

Request ID: FOI-1720-2122
Date published: 26 November 2021

You asked

Hi please provide traffic count & congestion %, or similar data sets for the following junctions. Please provide as much history as you have available. -rosendale road Se21 northbound & south circular a205 -rosendale road Se21 southbound & south circular a205 -turney Road Se21 eastbound/northbound & Croxted road -turney road Se21 westbound/southbound & Croxted road

We answered

Our ref: FOI-1720-2122/GH

Thank you for your request received by Transport for London (TfL) on 3 November 2021 asking for information about traffic count & congestion data SE21.

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 documents. The excel file is SCOOT data which provides flows and congestion data, and the zip folder contains all adhoc surveys from the junctions which will provide alternate flow data.

Daily flows and Congestion for all links on the two junctions below.

-rosendale road Se21 northbound & south circular a205 (N09/050)
-rosendale road Se21 southbound & south circular a205
-turney Road Se21 eastbound/northbound & Croxted road (N09/028)
-turney road Se21 westbound/southbound & Croxted road

Please see 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 Note:

SCOOT Flow may differ flow 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
 

Attachments

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.