Forestry Structure and Biomass Analysis
Purpose
Forestry Structure and Biomass Analysis estimates forest structure classes, canopy-height metrics, stand units, confidence, and a terrain-adaptive biomass proxy from LiDAR. Outputs are suitable for carbon accounting, resource management, and inventory planning.
Typical Questions This Tool Helps Answer
- What are the estimated carbon stocks and dominant canopy-height metrics across this forest inventory area?
- Which stand units have sufficient LiDAR point density to support high-confidence biomass estimation versus where are results provisional?
- How does forest structure vary spatially across the landscape and are the patterns consistent with reported stand age and disturbance history?
Background
Forest-structure and biomass inference from LiDAR is based on vertical return distribution, canopy height metrics, and terrain-normalized geometry. A common conceptual relation is:
$$B(x) = f\left(H_{p95}(x), \text{cover}(x), \sigma_z(x), \text{density}(x)\right)$$
Where $B$ is biomass proxy, $H_{p95}$ is high-percentile canopy height, and remaining terms describe cover and structural variability.
Structural Signal Components
- Height distribution metrics capture stand vertical development.
- Point-density support drives confidence and output robustness.
- Terrain-adaptive biomass scaling helps reduce underestimation in heterogeneous stands.
Because LiDAR sampling is discrete, metric reliability depends on point density, occlusion, scan geometry, and normalization quality.
Methodological Considerations
- Verify ground normalization quality before interpreting canopy-height derivatives.
- Use density/confidence diagnostics to bound where biomass interpretation is decision-grade.
- Match metric scale to management question (stand-level planning versus fine-scale habitat mapping).
Practical Interpretation Pitfalls
Frequent errors include treating low-density areas as true low biomass, mixing acquisitions with incompatible pulse geometry, and using a single structural metric as a complete ecological condition signal.
Inputs
| Parameter | Type | Required | Description |
|---|---|---|---|
| input | LiDAR (LAS/LAZ or typed lidar object) | Yes | Primary LiDAR source. |
Parameters
- profile (optional):
fast,balanced,strict; defaultbalanced. - resolution (optional): output raster resolution; default
2.0. - stand_block_cells (optional): stand aggregation block size; default
12, minimum2. - biomass_cap (optional): max biomass proxy value; default
25.0. - terrain_adaptation (optional):
off,moderate,strong; defaultmoderate. - output_prefix (optional): output naming prefix; default
forest_structure.
Outputs
Output artifact keys below are runtime outputs, not input parameters.
| Artifact | Runtime Output Key | Type | Description |
|---|---|---|---|
| Canopy height metrics raster | canopy_height_metrics | Raster | Canopy-height metrics layer. |
| Vertical structure class raster | vertical_structure_class | Raster | Structure class map (1-4). |
| Stand structure units vector | stand_structure_units | Vector (GPKG) | Stand polygons with summarized structural attributes. |
| Biomass proxy raster | biomass_proxy | Raster | Biomass proxy map for planning analytics. |
| Confidence raster | confidence | Raster | Confidence map based on LiDAR support quality. |
| Summary contract | summary | JSON | Run contract with metrics, interpretation, and output inventory. |
| Optional report | html_report | HTML | Optional stakeholder-friendly report. |
Summary contract also includes:
output_semanticsconfidence_contractinterpretation_warnings
Runtime note:
- This workflow is Pro-only and requires
include_pro=Truewith a valid Pro/Enterprise runtime.
Example
import whitebox_workflows as wbw
env = wbw.WbEnvironment(include_pro=True, tier="pro")
lidar = wbw.Lidar("survey_classified.laz")
env.forestry_structure_and_biomass_intelligence(
input=lidar,
profile="balanced",
resolution=2.0,
stand_block_cells=12,
biomass_cap=25.0,
terrain_adaptation="moderate",
output_prefix="outputs/forest_structure"
)
-
What is the biomass proxy and dominant canopy-height metric distribution across this forest inventory area, and which stand units show the strongest structure signal?
-
Which stands show structural complexity consistent with mature habitat conditions versus simplified plantation-like structure?
-
Where do canopy-gap and understory-density indicators suggest priority locations for thinning, regeneration support, or biodiversity interventions?
-
Chave, J., et al. (2014). "Improved Allometric Models to Estimate the Aboveground Biomass of Tropical Trees." J. Ecol. 102(3), 726–736.
Parameter Interaction Notes
Results are sensitive to profile, terrain adaptation, and stand block size.
- Strict profile tends to classify fewer cells into the tallest structure classes.
- Strong terrain adaptation can raise biomass proxy in high-relief stands.
- Larger stand blocks provide smoother but less local detail.
QA and Acceptance Criteria
Use a staged acceptance approach for Forestry Structure and Biomass Analysis:
- Confirm LiDAR input quality and expected coverage.
- Confirm all outputs are generated with the selected prefix.
- Validate stand summaries against known forest compartments.
- Review confidence map before operational targeting.
Recommended acceptance checks:
- Summary workflow id is correct.
- Class distributions are plausible for forest condition.
- Stand-unit attributes are populated and usable.
Advanced Operational Guidance
For production deployment of Forestry Structure and Biomass Analysis:
- Keep profile/settings fixed within annual reporting cycles.
- Use confidence and complexity outputs to prioritize field validation.
- Archive summary contracts for program governance and audit trails.
Implementation Patterns
Common implementation patterns with Forestry Structure and Biomass Analysis:
- Baseline stand intelligence run.
- Terrain-sensitivity comparison run.
- Executive reporting run with coarser stand aggregation.
Related Tools
Use Forestry Structure and Biomass Analysis together with upstream conditioning and downstream validation tools in the same bundle to ensure end-to-end consistency and stronger decision confidence.
When To Use This Workflow
Use this workflow when teams need integrated forest structure and biomass-proxy outputs from LiDAR without stitching multiple intermediate tools manually.
Results Delivery Checklist
- Include raster outputs, stand vector layer, summary JSON, and report HTML.
- Document profile, terrain adaptation, and resolution settings.
- Flag low-confidence zones before tactical decisions.
- Provide stand-level interpretation notes for non-technical stakeholders.
- Archive run metadata for repeatability.
Common Questions
Q: Is biomass proxy equivalent to formal biomass certification?
A: No. It is a planning and prioritization proxy, not a formal certification output by itself.
Q: Why did class maps change after switching from balanced to strict?
A: Profile changes adaptive thresholds and therefore alters class assignment behavior.
Q: Why do some areas have good biomass proxy but lower confidence?
A: Biomass and confidence are separate diagnostics; low point-density support can reduce confidence even with strong biomass proxy signals.
Q: What does stand complexity represent?
A: It is a normalized stand-level indicator derived from mean height, biomass proxy, and height variability.
Q: Why are small stand patches disappearing with larger stand blocks?
A: Larger block aggregation smooths local variability and merges fine-grained patterns.
Q: How should we use the confidence layer operationally?
A: Prioritize high-confidence zones for immediate decisions and route low-confidence zones for validation.
Q: Can we compare outputs from different resolutions?
A: Yes, but comparisons should account for resolution-driven differences in structure detail and aggregation.
Q: What causes many nodata cells in outputs?
A: Gaps in LiDAR support or invalid cells during intermediate gridding steps can propagate nodata.
Q: Which output is best for stand-level planning meetings?
A: stand_structure_units paired with biomass_proxy and confidence usually provides the best decision context.
Q: How often should this be rerun?
A: Typically after major LiDAR updates or when management planning cycles require refreshed stand intelligence.