Dear Mr Dutey

TfL Ref: FOI-1584-1920

Thank you for your email received by Transport for London (TfL) on 23
August 2019.

Your request will be processed in accordance with the requirements of the
Freedom of Information Act and TfL’s information access policy. 

A response will be sent to you by 23 September 2019.

We publish a substantial range of information on our website on subjects
including operational performance, contracts, expenditure, journey data,
governance and our financial performance. This includes data which is
frequently asked for in FOI requests or other public queries. Please check
[1]http://www.tfl.gov.uk/corporate/transpar... to see if this helps you.

We will publish anonymised versions of requests and responses on the
[2]www.tfl.gov.uk website. We will not publish your name and we will send
a copy of the response to you before it is published on our website.

In the meantime, if you would like to discuss this matter further, please
do not hesitate to contact me.

Yours sincerely

Eva Hextall

FOI Case Officer

FOI Case Management Team

General Counsel

Transport for London

show quoted sections

Dear Mr Dutey

TfL Ref: FOI-1584-1920

Thank you for your email received by Transport for London (TfL) on 23
August 2019.

Your request has been considered in accordance with the requirements of
the Freedom of Information Act and our information access policy.  I can
confirm we hold some of the information you require. You asked:

For every street listed further down, please provide:

(1) any road motor traffic counts you hold for the past 15 years

(2) recent motor traffic estimates from the London Strategic Transport
Model.

Any of the above must have been extracted as part of background work
carried out by your organisation in relation to designing a new cycle
route between Dalston and Lea Bridge.

List of streets (all in London Borough of Hackney)

- Mildmay Road

- Crossway

- Boleyn Road

- John Campbell Road

- Sandringham Road

- Abersham Road

- St Marks Rise

- Downs Park Road

- Cecilia Road

- Amhurst Road

- Pembury Road

- Cricketfield Road

- Queensdown Road

- Downs Road

- Powell Road

- Kenninghall Road

Please find the attached traffic counts data we hold for the roads you
have listed, going back 15 years.  I can confirm that the data provided
are Ad-Hoc surveys and that all of the available counts we hold for the
requested list of roads have been provided.  Not all roads have had a
survey commissioned and these surveys could have been commissioned for a
variety of other business requirements.

Please note that in accordance with TfL’s obligations under Data
Protection legislation some personal data has been removed, as required by
section 40(2) of the FOI Act. This is because disclosure of this personal
data would be a breach of the legislation, specifically the first
principle which requires all processing of personal data to be fair and
lawful. It would not be fair to disclose this personal information when
the individuals have no expectation it would be disclosed and TfL has not
satisfied one of the conditions which would make the processing ‘fair’.

This exemption to the right of access to information is an absolute
exemption and not subject to an assessment of whether the public interest
favours use of the exemption.

Referring to your second request for recent motor traffic estimates from
the London Traffic Strategic Transport Model, extracted as part of
background work carried out by TfL in relation to designing a new cycle
route between Dalston and Lea Bridge, we use a system called the
Operational Network Evaluator (ONE).  The ONE Model is a tactical traffic
assignment model built in the VISUM software environment. The model is
built as a simplified representation of the real world at a particular
moment in time. The model as a whole has been built and calibrated to
average November 2014 traffic counts and journey time data.  However, the
detailed area of interest for the new cycle route between Dalston and Lea
Bridge has been reviewed and updated where necessary to ensure network
detail and model accuracy is to an adequate standard for the area of
interest and capable of representing the existing situation on-street. 

This data listed on the attached files titled ‘CFR3_BASE_AM_FLOWS’ and
‘CFR3_BASE_PM_FLOWS’ show figures which are correct as of 3 September 2019
when we base-line reviewed the whole area while undertaking the modelling
and design of the new cycle route, CFR3.       

The data will provide you with traffic flow numbers for the specified
movements identified within the survey which can include junction turning,
movements and link level movements.  Each survey is individual and so will
differ from one another dependent on the requirement when the count was
taken.

The scope and scale of the model is in line with WebTAG (Web-based
Transport Analysis Guidance) and is the Department for Transport’s best
practice guidance and toolkit for Transport modelling. 

It states:

“Within the Area of Detailed Modelling, a relatively high level of detail
will generally be appropriate. Guidelines for Developing Urban Transport
Strategies (Institution of Highways and Transportation 1996) suggests that
“all roads that carry significant volumes of traffic” should be included
and more generally that networks “should be of sufficient extent to
include all realistic choices of route available to drivers”.

Due to the nature of assignment modelling and the assumption that users of
the network have perfect information when deciding on a route, the
inclusion of too many smaller roads will most likely result in an
unrealistic amount of rat-running. For this reason only key strategic road
and through routes are included in such a model, as outlined in WebTAG. 
For this reason, although the majority of roads requested were included in
the ONE Model, it has not been possible to provide modelled flow data for:

-           John Campbell Road

-           Queensdown Road

-           Powell Road

-           Abersham Road

Tactical reassignment models are available for the AM (08:00-09:00) and PM
(17:00-18:00) peak hours, and represent an average peak hour on an average
weekday (see attached). Base model flow data has been provided to the
nearest vehicle, but it is usual when taking data from such a model to
consider banding the flows to account for day-to-day variability of
traffic flows, and the above caveats.

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.

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

Eva Hextall

FOI Case Officer

FOI Case Management Team

General Counsel

Transport for London

show quoted sections