The SWAT Approach for Pipeline Watercourse Crossings
Bibliographic record
Abstract
This paper describes a multi-year program to assess pipeline crossings of sensitive watercourses along a major pipeline project. During the Front End Engineering and Design (FEED) phase a sensitive watercourse assessment team (SWAT) was established to provide a biophysical and construction assessment of selected watercourses to be crossed by a proposed pipeline project in western Canada. The SWAT comprised a fisheries biologist, a pipeline watercourse construction specialist and other technical support personnel. The field work included assessing biophysical data, fish habitat values, access to the crossing location, construction issues, site-specific mitigative measures and potential habitat compensation options, as well as providing photo documentation and a conceptual crossing sketch. The advantages of the SWAT assessment at a crossing site were: • It provided an effective and efficient field assessment of the proposed watercourse crossing in the early phase of the project. • It was a multidisciplinary assessment. • It provided a recommendation as to a preferred crossing location at the site. • It provided a recommendation as to preferred crossing method and timing of construction at the site. • The data were site-specific to the preferred crossing location. Three consecutive years of baseline biophysical field data were compiled and site reports generated using a custom designed database. Over 200 sensitive watercourses were identified based on environmental, geotechnical, and constructability factors and were visited by the SWAT team, sometimes more than once, for a total of 271 individual site assessments. Data collected during the FEED phase included site-specific information that can be used for ongoing project discussions, regulatory and community consultations, permitting and Fisheries and Oceans Canada (DFO) authorizations. The SWAT program also provided recommendations for minor or significant shifts in crossing location for 40% of the sites visited, resulting in changes to the pipeline alignment during the route evolution process.
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.004 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.007 | 0.005 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.002 | 0.002 |
| Open science | 0.002 | 0.003 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.016 | 0.006 |
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".