Skip to main content

40828

Details

AADF latest year 2018
Region Scotland
Local authority South Lanarkshire
Road name A71
Road type Major
Start junction road A726
End junction road B7078
Link length 8.30km (5.16 miles)
Easting & Northing 273100,645400
Latitude & longitude 55.68543,-4.01998

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
2018 Manual count 9,235 6,975 1,594 594 4 20 52
2017 Estimated using AADF from previous year on this link 11,178 8,120 2,045 923 0 37 54
2016 Estimated using AADF from previous year on this link 11,054 8,129 1,933 899 0 38 55
2015 Estimated using AADF from previous year on this link 10,783 8,030 1,790 870 0 38 56
2014 Estimated using AADF from previous year on this link 10,747 8,126 1,672 855 0 39 55
2013 Estimated using AADF from previous year on this link 10,495 8,014 1,555 834 0 38 53
2012 Estimated using AADF from previous year on this link 10,541 8,164 1,449 832 0 38 58
2011 Estimated using AADF from previous year on this link 10,712 8,400 1,381 831 0 41 59
2010 Estimated using AADF from previous year on this link 10,589 8,375 1,306 814 0 37 57
2009 Manual count 10,718 8,537 1,269 815 0 42 55
2008 Estimated using AADF from previous year on this link 9,816 7,333 1,464 893 5 42 84
2007 Estimated using AADF from previous year on this link 10,125 7,614 1,464 929 5 42 76
2006 Estimated using AADF from previous year on this link 10,124 7,818 1,327 867 5 42 70
2005 Estimated using AADF from previous year on this link 9,846 7,604 1,265 853 5 50 74
2004 Manual count 9,835 7,612 1,205 891 5 53 74
2003 Estimated using AADF from previous year on this link 9,271 7,055 1,356 733 0 53 74
2002 Estimated using AADF from previous year on this link 9,057 6,992 1,204 746 0 43 72
2001 Manual count 8,865 6,909 1,116 730 0 43 67
2000 Estimated using AADF from previous year on this link 8,492 6,531 1,115 747 2 22 77

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 40828 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 40828 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. 19
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. 38
Raw counts Vehicle counts recorded at this count point. 96

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