Traffic Surveys
Automatic Traffic Count Data Analysis
How to interpret ATC outputs without hiding device limits.
By SWAT Alliance Editorial Team · Updated 25 August 2026
Insight at a glance
A short visual checklist for better study decisions.
Use the article as a starting point, then confirm the project-specific scope, method, review and output with the delivery team.
Question
What decision should this evidence help someone make?
Scope
Which locations, movements, classes and periods matter?
Review
How will completeness and definitions be checked?
Output
What format will make the result easiest to use?
Short answer
Automatic traffic count data analysis checks the device context, interval continuity, direction and class outputs, anomalies and limitations before the record is used for a decision.
Understand the source
Record device type or source description, installation point, lanes, directions, periods, time zone, maintenance or gap notes and the fields actually supplied.
Check the series
Review missing intervals, duplicated records, implausible jumps, direction totals, class totals, clock changes and any aggregation or rounding applied to the raw output.
Interpret within bounds
ATC data describes the selected device, location and period. It should not be presented as a complete explanation of movements, vehicle identity or future demand without supporting evidence.
Frequently asked questions
Can ATC replace a turning movement count?
Not automatically. ATC may record line volumes while a TMC requires path-by-path movement allocation.
Should automatic data be quality reviewed?
Yes. Device outputs still need scope, continuity, anomaly and reconciliation checks.
Go deeper
Traffic Data Validation & Quality Control Methodology
A documented review framework for traffic data before it is delivered or relied upon.
Read the technical method →Related services
Continue reading