Effects of body size on estimation of mammalian area requirements
Bibliographic record
Abstract
Abstract Accurately quantifying species' area requirements is a prerequisite for effective area‐based conservation. This typically involves collecting tracking data on species of interest and then conducting home‐range analyses. Problematically, autocorrelation in tracking data can result in space needs being severely underestimated. Based on the previous work, we hypothesized the magnitude of underestimation varies with body mass, a relationship that could have serious conservation implications. To evaluate this hypothesis for terrestrial mammals, we estimated home‐range areas with global positioning system (GPS) locations from 757 individuals across 61 globally distributed mammalian species with body masses ranging from 0.4 to 4000 kg. We then applied block cross‐validation to quantify bias in empirical home‐range estimates. Area requirements of mammals <10 kg were underestimated by a mean approximately15%, and species weighing approximately100 kg were underestimated by approximately50% on average. Thus, we found area estimation was subject to autocorrelation‐induced bias that was worse for large species. Combined with the fact that extinction risk increases as body mass increases, the allometric scaling of bias we observed suggests the most threatened species are also likely to be those with the least accurate home‐range estimates. As a correction, we tested whether data thinning or autocorrelation‐informed home‐range estimation minimized the scaling effect of autocorrelation on area estimates. Data thinning required an approximately93% data loss to achieve statistical independence with 95% confidence and was, therefore, not a viable solution. In contrast, autocorrelation‐informed home‐range estimation resulted in consistently accurate estimates irrespective of mass. When relating body mass to home range size, we detected that correcting for autocorrelation resulted in a scaling exponent significantly >1, meaning the scaling of the relationship changed substantially at the upper end of the mass spectrum.
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.010 | 0.038 |
| 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.001 |
| Scholarly communication | 0.000 | 0.001 |
| Open science | 0.000 | 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".