FOI request detail

SCOOT data Ealing

Request ID: FOI-1610-2223
Date published: 02 November 2022

You asked

Could you please provide the SCOOT data for the following location: - junction: Lower Boston to Uxbridge Rd (from 2020 to now) - junction: Hanger Lane to Uxbridge Rd (from 2020 to now).

We answered

TfL Ref: 1610-2223
 
Thank you for your clarified request received by Transport for London (TfL) on 19 October 2022 asking for information about SCOOT data.
Your request has been considered in accordance with the requirements of the Freedom of Information Act and our information access policy.  I can confirm that we hold the information you require. You asked:

Could you please provide the SCOOT data for the following location:
- junction: Lower Boston to Uxbridge Rd (from 2020 to now)
- junction:
Hanger lane (A406) and Uxbridge Rd (from 2020 to now).


Please see attached as requested which contains all of the junctions between Uxbridge Road and Hanger Lane and Uxbridge Road and Lower Boston Road. Please expand the column widths to see the data where necessary.

Please see below for an explanation of what each column refers to within the data:
  • 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 the following data caveat:

SCOOT Flow may differ from other validated traffic counts as the SCOOT system utilises loop occupancy as its 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 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


Sara Thomas
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.