01
Frame the context
Use Traffic Count, Turning Movement Count and Intersection Count and local road context to describe the question clearly.
North America · en-US
Manual traffic count support for United States projects
US traffic-data briefs often distinguish intersection and turning movements, link or mid-block volumes, pedestrian and bicycle activity, queue observations, parking and origin-destination evidence. The requested decision should determine the survey design.
This page describes remote project support and technical context for United States; it does not state an office location or authority approval.
United States project lens
Turn local context into a usable traffic-data brief.
A clear United States study brief connects local terminology and conditions to an agreed method, quality review and practical output.
02
Set the method
Define each approach, movement, direction, class and interval in the survey plan. Align the data structure to the engineering analysis or modelling workflow that will use it.
03
Check the data
Review the agreed periods, movement matrix, classifications and directional totals before delivery; note any approved project exceptions clearly.
04
Share the output
Agree the spreadsheet, summary, visuals or supporting files your stakeholders need.
Local terminology and scope
Common terminology includes Traffic Count, Turning Movement Count and Intersection Count. Define each approach, movement, direction, class and interval in the survey plan. Align the data structure to the engineering analysis or modelling workflow that will use it.
Common study and data considerations
Turning movement counts commonly retain approach, left/through/right movement and interval context; pedestrian and bicycle movements can be included where scoped.
Use FHWA vehicle classes only when the US project specification asks for that framework and the source can support the required distinctions.
Survey applications
- intersection and signal studies
- corridor and link analysis
- parking and access planning
- origin-destination and route 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 States project teams
US deliverables may use turning-movement matrices, directional link tables, queues or project-defined vehicle classes; the agency or client template controls the final structure.
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
Review the agreed periods, movement matrix, classifications and directional totals before delivery; note any approved project exceptions clearly.
Traffic-data validation and QA/QC →Frequently asked questions
Can a study include bicycle and pedestrian movements?
Yes. Specify crossing locations, directions, time periods and whether movements must be separated from vehicle data.