01
Frame the context
Use Traffic Survey, Junction Count and Roundabout Survey and local road context to describe the question clearly.
Europe · en-GB
Manual traffic count support for United Kingdom projects
UK traffic-survey briefs may use terms such as junction count, roundabout survey, link count, mid-block count, cycle count and queue survey. The language used in instructions and outputs should match the project team’s convention.
This page describes remote project support and technical context for United Kingdom; it does not state an office location or authority approval.
United Kingdom project lens
Turn local context into a usable traffic-data brief.
A clear United Kingdom study brief connects local terminology and conditions to an agreed method, quality review and practical output.
02
Set the method
Define junction arms, movement coding, survey periods, active-travel movements and class schemes in a written survey specification before collection or video processing.
03
Check the data
Check that survey totals, coding, interval summaries and deliverables align with the approved junction layout and scope.
04
Share the output
Agree the spreadsheet, summary, visuals or supporting files your stakeholders need.
Local terminology and scope
Common terminology includes Traffic Survey, Junction Count and Roundabout Survey. Define junction arms, movement coding, survey periods, active-travel movements and class schemes in a written survey specification before collection or video processing.
Common study and data considerations
A classified junction count and a classified link count answer different questions; identify the junction arms or link count point explicitly.
Where DfT-style categories are relevant, confirm the required treatment of cars/taxis, LGVs, HGVs, motorcycles, buses/coaches and pedal cycles rather than assuming it.
Survey applications
- junction and roundabout assessment
- link and mid-block studies
- pedestrian and cycle counts
- ANPR and video-based studies
Manual video-processing workflow
After the brief and source are reviewed, human analysts apply the approved location, movement, classification and interval rules. The data then passes scope, continuity, consistency and output checks before delivery. Recorded footage uses an approved secure-transfer route rather than the public enquiry form.
Deliverables for United Kingdom project teams
UK outputs may use junction movement tables, classified link counts, queue sheets or active-travel observations in the terminology and template agreed by the project team.
The final interval, movement, lane, class and summary structure follows the approved brief. A client template can be supported after its labels and rules are agreed; private templates and source files are never published.
View synthetic traffic count data examples →Methodology and quality
Check that survey totals, coding, interval summaries and deliverables align with the approved junction layout and scope.
Traffic-data validation and QA/QC →Frequently asked questions
What is needed for a junction count brief?
Provide a junction plan or location reference, approaches, movements, dates, time periods, class requirements and output format.