Bibliographic record
Abstract
Wildlife-vehicle collisions (WVCs) pose a significant safety and conservation concern in areas where high-traffic roads are situated adjacent to wildlife habitat. Improving transportation safety, accurately planning highway mitigation, and identifying key habitat linkage areas may all depend on the quality of WVC data collection. Two common approaches to describe the location of WVCs are spatially accurate data derived from global positioning systems (GPS) or vehicle odometer measurements and less accurate road-marker data derived from reference points (e.g., mile-markers or landmarks) along the roadside. In addition, there are two common variable types used to predict WVC locations: (1) field-derived, site-specific measurements and (2) geographic information system (GIS)-derived information. It is unclear whether these different approaches produce similar results when attempting to identify and explain the location of WVCs. Our first objective was to determine and compare the spatial error found in road-marker data (in our case the closest mile-marker) and landmark-referenced data. Our second objective was to evaluate the performance of models explaining high- and low-probability WVC locations, using congruent, spatially accurate (<3-m) and road-marker (<800-m) response variables in combination with field- and GIS-derived explanatory variables. Our WVC data sets were comprised of ungulate collisions and were located along five major roads in the central Canadian Rocky Mountains. We found that spatial error (mean +/- SD) was higher for WVC data referenced to nearby landmarks (516 +/- 808 m) than for data referenced to the closest mile-marker data (401 +/- 219 m). The top-performing model using the spatially accurate WVC locations contained all explanatory variable types, whereas GIS-derived variables were only influential in the best road-marker model and the spatially accurate reduced model. Our study showed that spatial error and sample size, using road-marker data for ungulate species, are important to consider for model output interpretation, which will impact the appropriate scale on which to apply modeling results. Using road-marker references <1.6 km or GPS-derived data locations may represent an optimal compromise between data acquisition costs and analytical performance.
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 distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| 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.000 | 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 teacher head, 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".