Skip to main content

8284

Details

AADF latest year 2016
Region London
Local authority Tower Hamlets
Road name A1202
Road type Major
Start junction road A1203
End junction road Cable Street
Link length 0.20km (0.12 miles)
Easting & Northing 534160,180760
Latitude & longitude 51.50985,-0.06814

Location

Contents

Average Annual Daily Flow

Average annual daily flow
Year Count method All motor vehicles Cars & taxis LGVs HGVs Pedal cycles Motorcycles Buses & coaches
2016 Estimated using AADF from previous year on this link 8,334 5,689 1,608 375 354 524 139
2015 Estimated using AADF from previous year on this link 8,351 5,809 1,559 364 342 488 131
2014 Estimated using AADF from previous year on this link 8,307 5,724 1,589 377 338 490 128
2013 Estimated using AADF from previous year on this link 8,229 5,640 1,559 420 314 478 131
2012 Estimated using AADF from previous year on this link 8,267 5,678 1,547 399 330 519 124
2011 Estimated using AADF from previous year on this link 8,504 5,870 1,598 372 321 546 118
2010 Estimated using AADF from previous year on this link 8,623 5,954 1,626 371 327 556 116
2009 Estimated using AADF from previous year on this link 8,748 6,051 1,656 363 296 563 115
2008 Estimated using AADF from previous year on this link 8,978 6,219 1,709 358 298 580 112
2007 Manual count 9,092 6,353 1,710 349 290 570 110
2006 Estimated using AADF from previous year on this link 8,784 5,905 1,749 478 273 446 206
2005 Estimated using AADF from previous year on this link 8,435 5,686 1,651 498 210 411 189
2004 Estimated using AADF from previous year on this link 8,539 5,802 1,642 489 163 412 194
2003 Estimated using AADF from previous year on this link 9,026 6,454 1,570 431 154 392 179
2002 Estimated using AADF from previous year on this link 9,148 6,681 1,470 473 132 376 148
2001 Estimated using AADF from previous year on this link 9,715 7,077 1,577 530 129 402 129
2000 Estimated using AADF from previous year on this link 9,805 7,244 1,543 527 114 361 130

Download data

Data disclaimer

Traffic figures at the regional and national level are robust, and are reported as accredited official statistics. However, DfT’s traffic estimates for individual road links and small areas are less robust, as they are not always based on up-to-date counts made at these locations. Where other more up-to-date sources of traffic data are available (e.g. from local highways authorities), this may provide a more accurate estimate of traffic at these locations.

It is the responsibility of the user to decide which data are most appropriate for their purpose, and if DfT road link level traffic estimates are used, to make a note of the limitations in any published material.

Quality flags in data downloads

DfT’s road link level traffic estimates are calculated using a variety of methods, with some methods likely to produce more accurate estimates than others.

The data tables available to download here contain a column - estimation_method – showing the method used to estimate traffic for each location and year. Figures having an estimation method of “Counted” are likely to be more accurate than those marked as “Estimated”, and the latter should be used with caution.

Site details
Manual count point site 8284 details
Average annual daily flow
Number of vehicles that travel past the count point (in both directions) on an average day of the year.
Average annual daily flow by direction
Number of vehicles that travel past the count point on an average day of the year, by direction of travel.
Raw counts
Vehicle counts recorded at this count point.
Data Description Records Download
Site details Manual count point site 8284 details 1
Average annual daily flow Number of vehicles that travel past the count point (in both directions) on an average day of the year. 17
Average annual daily flow by direction Number of vehicles that travel past the count point on an average day of the year, by direction of travel. 34
Raw counts Vehicle counts recorded at this count point. 24

To apply more filters to downloads, or retrieve data split into pages you can use our API.