Automated snow avalanche release area delineation in data-sparse, remote, and forested regions
Bibliographic record
Abstract
Potential avalanche release area (PRA) modeling is critical for generating automated avalanche terrain maps which provide low-cost, large-scale spatial representations of snow avalanche hazard for both infrastructure planning and recreational applications. Current methods are not applicable in mountainous terrain where high-resolution (≤5 m) elevation models are unavailable and do not include an efficient method to account for avalanche release in forested terrain. This research focuses on expanding an existing PRA model to better incorporate forested terrain using satellite imagery and presents a novel approach for validating the model using local expertise, thereby broadening its application to numerous mountain ranges worldwide. The study area of this research is a remote portion of the Columbia Mountains in southeastern British Columbia, Canada, which has no pre-existing high-resolution spatial datasets. Our research documents an open-source workflow to generate high-resolution digital elevation models (DEMs) and forest land cover datasets using optical satellite data processing. We validate the PRA model by collecting a polygon dataset of observed potential release areas from local guides, using a method which accounts for the uncertainty in human recollection and variability in avalanche release. The validation dataset allows us to perform a quantitative analysis of the PRA model accuracy and optimize the PRA model input parameters to the snowpack and terrain characteristics of our study area. Compared to the original PRA model our implementation of forested terrain and local optimization improved the percentage of validation polygons accurately modeled by 11.7 percentage points and reduced the number of validation polygons that were underestimated by 14.8 percentage points. Our methods demonstrate substantial improvement in the performance of the PRA model in forested terrain and provide means to generate the requisite input datasets and validation data to apply and evaluate the PRA model in vastly more mountainous regions worldwide than was previously possible.
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.000 | 0.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 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".