Bibliographic record
Abstract
Commodity Flow Survey (CFS) data has played a significant role to help set the context for regional transportation policy and investment decisions in the Portland–Vancouver region. Data from the CFS has been a primary input into the region’s Commodity Flow Forecast (1997) and the update in 2002. The CFS has also provided data that has helped answer business community questions about freight flows and engaged them in policy discussions regarding the Columbia River crossing as part of the Interstate 5 Trade Corridor project. Both directly and indirectly, the CFS has been very helpful in helping us set the context for freight movement and to put freight issues on the regional transportation agenda. CFS data gives us the ability to frame the issues, convey the order of magnitude of freight’s importance, and to identify areas where further data is needed. Ultimately, we would like to be able to use the data at a project level, but the CFS doesn’t provide enough detail. That is to say, we would like to have the data at detail level sufficient to help make the case for a specific investment or to prioritize among competing investments. However, even at current levels of detail, the CFS has been useful. Due in part to CFS data in our Commodity Flow Forecast, we have secured $500,000 in regional funding for a freight data collection project that will provide us with some of the detail we need to make specific investment decisions, such as origin–destination and time of day data. This presentation showed how and why our region has successfully used CFS data, identified where we have found gaps and problems, and suggested alternatives for making CFS data more accessible and more useful at a regional level.
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.010 | 0.049 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.008 | 0.012 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.004 | 0.004 |
| Open science | 0.001 | 0.002 |
| Research integrity | 0.001 | 0.002 |
| Insufficient payload (model declined to judge) | 0.014 | 0.005 |
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".