Methane emissions from contrasting production regions within Alberta, Canada: Implications under incoming federal methane regulations
Bibliographic record
Abstract
Aggressive reductions of oil and gas sector methane, a potent greenhouse gas, have been proposed in Canada. Few large-scale measurement studies have been conducted to confirm a baseline. This study used a vehicle-based gas monitoring system to measure fugitive and vented gas emissions across Lloydminster (heavy oil), Peace River (heavy oil/bitumen), and Medicine Hat (conventional gas) developments in Alberta, Canada. Four gases (CO2, CH4, H2S, C2H6), and isotopic δ13CCH4 were recorded in real-time at 1 Hz over a six-week field campaign. We sampled 1,299 well pads, containing 2,670 unique wells and facilities, in triplicate. Geochemical emission signatures of fossil fuel-sourced plumes were identified and attributed to nearby, upwind oil and gas well pads, and a point-source gaussian plume dispersion model was used to quantify emissions rates. Our analysis focused exclusively on well pads where emissions were detected >50% of the time when sampled downwind. Emission occurrences and rates were highest in Lloydminster, where 40.8% of sampled well pads were estimated to be emitting methane-rich gas above our minimum detection limits (m = 9.73 m3d–1). Of the well pads we found to be persistently emitting in Lloydminster, an estimated 40.2% (95% CI: 32.2%–49.4%) emitted above the venting threshold in which emissions mitigation under federal regulations would be required. As a result of measured emissions being larger than those reported in government inventories, this study suggests government estimates of infrastructure affected by incoming regulations may be conservative. Comparing emission intensities with available Canadian-based research suggests good general agreement between studies, regardless of the measurement methodology used for detection and quantification. This study also demonstrates the effectiveness in applying a gaussian dispersion model to continuous mobile-sourced emissions data as a first-order leak detection and repair screening methodology for meeting regulatory compliance.
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.001 | 0.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.002 |
| Science and technology studies | 0.002 | 0.001 |
| Scholarly communication | 0.002 | 0.000 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 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 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".