FOI request detail

SCOOT Data for South East London

Request ID: FOI-0577-2122
Date published: 05 July 2021

You asked

Follow-up to 0451-2122: I was hoping to clarify, is this from N09/141 b, or c (or potentially both?), I think there might be two monitoring points - one one on Norwood? Or is this just specifically at that junction? Also, I appreciate I might have to submit a different FOI for this but thought it might be worth asking anyway, would it be possible to have the same data for both N09/141b and N09/141c, and, if possible please the data filtered just to show 7-10am on those two roads, as far back as it goes please?

We answered

TfL Ref: FOI-0577-2122

Thank you for your email of 22nd June 2021 asking for SCOOT data in south east London.

Your request has been considered in accordance with the requirements of the Freedom of Information Act and our information access policy. 

Specifically you asked, in a follow-up to case ref 0451-2122:

“Would it be possible to have the same data for both N09/141b and N09/141c, and, if possible please the data filtered just to show 7-10am on those two roads, as far back as it goes please?”

I can confirm that we hold the information you require, which is provided in the attached spreadsheet. Please see the following explanation as to 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
  • VehicleFlowTotal7amTo10am – The total flow observed between 7am and 10am on each link approaching the junction
  • FlowDataCompletenessPercentage – Refers to the availability of data; 100% is a complete dataset.
  • AverageCongestionPercentage – The average congestion between 7am and 10am on each link approaching the junction
  • CongestionDataCompletenessPercentage – Refers to the availability of data; 100% is a complete dataset

Please note further that 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, 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 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 this data

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

 

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.