A Contemporary Approach for Visualizing Temporal and Spatial Urban Freight Movement by Leveraging Mobility Portal Data
Bibliographic record
Abstract
Analyzing and visualizing traffic data in order to better understand congestion trends, safety concerns, goods movement and capacity needs is a pressing need. Broadly speaking, there is a large amount of traffic data available today, including volume, lane occupancy, speed, and travel time, which can be used to manage transportation networks, provide traveler information and produce performance measures. This broadly disseminated data almost always treats all vehicles alike, without discriminating between trucks and passenger cars. Since trucks are critical and growing components of freeway traffic, monitoring and tracking their dynamics can reveal the impacts of freight movement on current freeway operations and over time will uncover trends useful for future planning and management. This study takes advantage of a unique data stream available for the freeway network of Portland, Oregon, USA. In addition to providing continuous vehicle count, speed and lane occupancies at 20-second intervals at more than 500 stations (1,300 individual detectors), the Portland system reports volume bins at 4 length-based classifications. (60 ft). Given that most vehicle classification studies are done over very short time intervals at an extremely limited number of locations, this nonstop data stream enables unprecedented insight into where and when trucks are traveling on Portland's freeways and a wealth of opportunities for performance measurement and diagnosis of their impacts. The objective of this paper is to exploit this new data stream and explore new visualization techniques that depict truck volume, truck percentage and volume-weighted average vehicle speeds along Portland's Interstate 5 corridor, an important north-south freight route between the Canada and Mexico borders. Results confirm the merit in analyzing and tracking truck volumes, proportions, and other dynamics for traffic management, information and modeling. The results of this study and the techniques employed here can be used to better understand and visualize freight movement dynamics on a continuous basis.
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.002 | 0.005 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.008 | 0.010 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.006 | 0.005 |
| Open science | 0.002 | 0.003 |
| Research integrity | 0.001 | 0.002 |
| Insufficient payload (model declined to judge) | 0.005 | 0.001 |
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".