Human and animal movements combine with snow to increase moose-vehicle collisions in winter
Bibliographic record
Abstract
Abstract Wildlife-vehicle collisions imperil humans, wildlife, and property. Collisions with moose (Alces alces) are especially consequential and there are indications they may increase during severe winters. We tested hypotheses regarding the influence of moose movements and vehicular traffic patterns on collision risk. We first modeled daily snow depth and accumulation across 5.6 million km2 of the North American Arctic-Boreal region. Next, we analyzed the movements and road use of 113 GPS-collared moose in response to snow depth. Finally, we examined the influence of these snow properties on vehicular traffic and 7680 moose-vehicle collisions. As winter progressed and the snowpack deepened in each study area, GPS-collared moose migrated to lower elevations, leading them into areas with shallower snow but higher road densities. This elevational migration corresponded with a higher probability of road-use by moose (by up to ten-fold) in winter than in summer. Corresponding to these patterns, moose-vehicle collisions were 2.4–5.7 times more frequent from December through February (compared to early summer). Collision risk was highest when and where snow depth was less than 120 cm, indicating that migration into areas with shallower snow increased collision risk in those areas. Most (82%) moose-vehicle collisions occurred after dark. This pattern was strongest during winter, when nighttime traffic volumes were eight times higher than summer due to longer nights. Overall, our findings suggest that concurrent seasonal changes in human and wildlife behavior increase the frequency of moose-vehicle collisions during winter. Snow depth influences collisions primarily through its impacts on moose movement, while strong seasonal changes in daylight hours cause an increase in nighttime traffic that further contributes to risk. This information may help predict times and places where risk of moose-vehicle collisions are highest and to develop seasonally dynamic mitigation strategies.
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.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.000 | 0.000 |
| 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".