A Staged Approach for Managing Terrain and Geohazards on New Pipeline Projects
Bibliographic record
Abstract
Pipeline route selection and design is an iterative process by which one or more potential pipeline corridors are systematically narrowed from the general path of about 10 km in width to a highly specified 30 m to 50 m wide corridor. The process usually spans several years, and is frequently becoming increasingly complicated, requiring a multi-disciplinary technical and managerial approach that considers the political and regulatory process, environmental impact and permitting, project and industry economics, access, constructability, land acquisition, and terrain. Specialist technical contributions to the pipeline routing process include pipeline hydraulics, pipeline and facility construction, terrain/geohazards, and environment/archaeology. Problematic terrain and geohazards are two of several issues that need to be managed through the feasibility and design of a new pipeline project. As the project advances through Front End Engineering and Design (FEED) from feasibility to final engineering design and as the corridor narrows from kilometers to tens of meters in width, the level of detail required in ongoing terrain and geohazard investigations should increase to optimize the design process and match the increased detail being provided by other specialists. An idealized Four-Stage framework for managing geohazards and problematic terrain during pipeline routing and design is outlined in the paper. This framework has been founded on several international resources listed in the references and has, by necessity, been developed, tested, and refined by the authors over the last ten years on several large and small diameter pipeline projects in North and South America. Each of the 4 Stages is described and contains guidelines on project study scale, a target corridor width, the engineering design level, cost accuracy, and geohazard related engineering tasks and deliverables. This staged approach is provided as a road map to help guide all project participants including owners, project managers, engineers, scientists, and regulators to understand how geohazards and problematic terrain are managed through the pipeline routing and design 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.008 | 0.007 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.004 | 0.002 |
| Science and technology studies | 0.005 | 0.003 |
| Scholarly communication | 0.008 | 0.004 |
| Open science | 0.004 | 0.006 |
| Research integrity | 0.002 | 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".