Post-Installation Geotechnical Issues Associated With Large-Scale HDD Crossings
Bibliographic record
Abstract
Horizontal Directional Drilling (HDD) is increasingly being used as a technique to install pipeline through challenging conditions. With this increased use, several post-installation geotechnical issues have, quite literally, surfaced, often many months or years following the original installation. These issues include sinkhole development around the entry/exit points for the HDD operations and settlement of the surface above the HDD bore path. Both can be attributed to two major factors, those involving unfavourable ground conditions and those involving problematic installation procedures. Several examples of each of these factors are described along with mitigation measures designed to prevent both sinkhole and settlement from occurring following HDD installation. Case histories from two large HDD crossings are subsequently presented which illustrate the potential magnitude of these issues and the steps that are often required for repair; the first from a crossing of the Fraser River outside of Vancouver, Canada, and the second from a crossing of a major river in north-central Argentina. In both of these cases, large sinkholes formed behind the HDD exit points, resulting in property damage and possibly threatening neighboring utilities. Site investigation and design techniques implemented to minimise the potential for sinkhole development and settlement are discussed, and several remediation options used in the cases histories are presented.
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 distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.000 |
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 teacher head, 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".