Research, part of a Special Feature on Effects of Roads and Traffic on Wildlife Populations and Landscape Function Cost-Benefit Analyses of Mitigation Measures Aimed at Reducing Collisions with Large Ungulates in the United States and Canada: a Decision Support Tool
Bibliographic record
Abstract
Wildlife-vehicle collisions, especially with deer (Odocoileus spp.), elk (Cervus elaphus), and moose (Alces alces) are numerous and have shown an increasing trend over the last several decades in the United States and Canada. We calculated the costs associated with the average deer-, elk-, and moose-vehicle collision, including vehicle repair costs, human injuries and fatalities, towing, accident attendance and investigation, monetary value to hunters of the animal killed in the collision, and cost of disposal of the animal carcass. In addition, we reviewed the effectiveness and costs of 13 mitigation measures considered effective in reducing collisions with large ungulates. We conducted cost-benefit analyses over a 75-year period using discount rates of 1%, 3%, and 7% to identify the threshold values (in 2007 U.S. dollars) above which individual mitigation measures start generating benefits in excess of costs. These threshold values were translated into the number of deer-, elk-, or moose-vehicle collisions that need to occur per kilometer per year for a mitigation measure to start generating economic benefits in excess of costs. In addition, we calculated the costs associated with large ungulate-vehicle collisions on 10 road sections throughout the United States and Canada and compared these to the threshold values. Finally, we conducted a more detailed cost analysis for one of these road sections to illustrate that even though the average costs for large ungulate-vehicle collisions per kilometer per year may not meet the thresholds of many of the mitigation measures, specific locations on a road section can still exceed thresholds. We believe the cost-benefit model presented in this paper can be a valuable decision support tool for determining mitigation measures to reduce ungulate-vehicle collisions.
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.003 | 0.006 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.002 |
| Bibliometrics | 0.002 | 0.003 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.002 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.016 | 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".