Evaluating Annual Average Daily Traffic Calculation Methods with Continuous Truck Traffic Data
Bibliographic record
Abstract
Traffic volume, often measured in relation to annual average daily traffic (AADT), is a fundamental output of traffic monitoring programs. At continuous count sites, unusual events or counter malfunctions periodically cause data loss, which influences AADT accuracy and precision. This paper evaluates five methods used to calculate AADT values from continuous count data, including the use of a simple average, the commonly adopted method developed by AASHTO (the AASHTO method), and methods that incorporate adjustments to the AASHTO method. The evaluation imposes data removal scenarios designed to simulate real-life causes of data loss to quantify the accuracy and precision improvements provided by these adjustments. Truck traffic data are used to reveal issues arising when volumes are low or when they exhibit unusual temporal patterns. Unlike the AASHTO method, which incorporates a weighted average and an hourly base time period, the FHWA method provides the most accurate and precise results in all data removal scenarios, according to the evaluation. Specifically, when up to 15 days of data are randomly removed, application of the FHWA method can be expected to produce errors within approximately é1.4% of the true AADT value, 95% of the time. Results also demonstrate that including a weighted average improves AADT accuracy primarily, whereas the use of hourly rather than daily count data influences precision. If possible, practitioners contemplating the adoption of the FHWA method should assess its relative advantages within their local context.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.009 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.000 | 0.002 |
| Open science | 0.003 | 0.000 |
| Research integrity | 0.000 | 0.002 |
| Insufficient payload (model declined to judge) | 0.000 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one teacher head, not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".