Rail Trench Structure Design at Port of Vancouver USA
Bibliographic record
Abstract
Located at the Port of Vancouver USA, the West Vancouver Freight Access Schedule 2 Rail Project 16 will connect the BNSF north/south mainline track with the Port rail system. The current rail entrance blocks the mainline when unit trains enter or leave the Port. This resulted in the need to develop a new entrance, the only feasible alignment being along the north bank of the Columbia River and beneath the existing BNSF Bridge 9.6. A 1,350-foot (411.5 meters) portion of this track will be carried by a partially elevated reinforced concrete structure that will protect the rail from 100-year flood waters and support it along the irregular river bank. This paper describes the constraints that dictated the design features and the resulting configuration of the partially elevated reinforced concrete structure. To resist flooding and provide the required clearance under the existing rail bridge, a watertight, continuous concrete trench was selected as the preferred solution. Closely spaced batter piles support 1,100 feet (335.3 meters) of the trench and provide lateral resistance to seismic loads and buoyancy resistance. Portions of the rail trench structure will be constructed below the U.S. Army Corps of Engineers' ordinary high water mark of the river and will be subjected to in-water work timing restrictions. The river is home to several species listed under the Endangered Species Act, and the Port has undertaken a very low-impact approach to construction of the rail trench: no work will be conducted in the flowing water of the river. This necessitates careful planning and sequencing of the work, taking into account projected river levels and tidal fluctuations. Other challenges include an extremely constricted site with limited access and the need to minimize impacts on adjacent tenants and their operations. When constructed, the rail trench structure will provide a unique facility designed to meet the latest structural, seismic, and environmental requirements and maximize operational efficiency for the Port.
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.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.000 |
| Insufficient payload (model declined to judge) | 0.019 | 0.004 |
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".