Environmental Permitting of British Columbia Oil and Gas Commission Regulated Pipelines: Lessons From the Trenches
Bibliographic record
Abstract
There are many projects proposed to transport oil and gas resources to British Columbia’s (BC’s) west coast. BC has multiple major pipeline transmission systems (e.g., Trans Mountain pipeline, Spectra Energy and Pacific Northern Gas), and at least six major oil and gas pipelines are planned for construction over the next decade [1]. Large pipeline projects like these that span hundreds of kilometres can involve multiple jurisdictions (federal, provincial or joint) and require considerable regulatory planning. Once a pipeline project is approved through an environmental assessment (EA) process, it must still undergo rigorous environmental review as part of regulatory permitting. This paper provides an overview of oil and gas environmental regulatory processes in BC, with a focus on the role and process of the BC Oil and Gas Commission (BC OGC) as it pertains to environmental permitting requirements (i.e., legislation and regulation) for pipeline projects. Current regulatory application and review processes have been developed for small projects. This creates several unique considerations for major pipeline project applications. Among these is how best to coordinate the permit applications required for environmental management and protection of the diverse resource features of interest to BC regulatory agencies (e.g., culturally modified trees, riparian management areas, wildlife tree retention areas and old growth management areas). This paper also highlights the need for an integrated multidisciplinary approach and discusses lessons learned related to strategic planning of permit applications. We provide examples of how collaboration among the proponent’s teams and multiple consultant teams is necessary to develop effective regulatory strategies and obtain timely approvals.
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.013 |
| Meta-epidemiology (narrow) | 0.000 | 0.001 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.002 | 0.003 |
| Science and technology studies | 0.016 | 0.010 |
| Scholarly communication | 0.014 | 0.005 |
| Open science | 0.003 | 0.004 |
| Research integrity | 0.005 | 0.008 |
| Insufficient payload (model declined to judge) | 0.007 | 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".