aceImpact of allometric reference selection on management scale aboveground biomass estimation via Sentinel-2 and machine learning
Accurate estimation of aboveground biomass (AGB) is essential for sustainable forest management, carbon accounting, and climate change mitigation. In remote sensing-based biomass mapping, field-derived AGB values are commonly used as reference data; however, these values are strongly influenced by the selected allometric equation. This study evaluates how alternative allometric reference datasets affect Sentinel-2-based AGB estimation at the forest management scale in Pinus brutia stands. Reference AGB values we…
Sentinel-2-based AGB estimation using CART with the Sun et al. (1980) diameter-based allometric reference achieved the closest agreement with forest management plan data at the management-unit scale in Pinus brutia stands.
Sentinel-2 and CART-based operational AGB mapping in Pinus brutia produced total estimates that differed by more than 700,000 Mg across the same 13,687 ha area depending solely on which allometric reference was used, making reference selection a dominant source of uncertainty.
Findings are bounded to Pinus brutia stands and a single 13,687 ha evaluation area using 112 field plots, limiting generalizability to other species or regions.
Evidence
- Peer-reviewedEnvironmental Monitoring and Assessment2026-08-22
How should this claim be treated?
Truvace Impact Record TRV-2026-0861, v1: “Impact of allometric reference selection on management scale aboveground biomass estimation via Sentinel-2 and machine learning.” Truvace, 2026-08-24. /record/TRV-2026-0861 (accessed at citation time). sha256 1102d3154354a9bf…
Calibration history
Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.
Certified into the record
How to verify without trusting this page
Fetch the canonical text of any version from /api/record/TRV-2026-0861 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.