Multisensor Data Integration and Fusion in Traffic Operations and Management
Bibliographic record
Abstract
Widespread technological development and deployment have created an abundance of data sources for traffic monitoring. A database that integrates data from all these technologies would maximize coverage of the network, given the available data. Sometimes, however, there are multiple independent measurements of the current traffic conditions for a particular portion of the network. In these cases, a variety of data fusion techniques can be used to achieve better estimates while helping to overcome information overload. This paper discusses several techniques for fusing data from competitive sensor configurations, describes the analytical foundation of these techniques, and interprets how each technique might be used most appropriately. In addition, these data fusion techniques are implemented and compared relative to their ability to accurately and reliably estimate traffic speeds. A real-world case study in Toronto, Ontario, Canada, demonstrates that estimates from data fusion techniques that pull loop detector data and probe vehicle data from an integrated database are more accurate and reliable than estimates based on individual data sources. Consequently, these data fusion–based estimates can be taken with greater certainty and confidence.
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 machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.004 | 0.005 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.002 | 0.004 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.002 | 0.004 |
| Open science | 0.001 | 0.002 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.001 | 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 source (direct Gemma or distilled Codex), 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".