A site is captured for engineering design. Six months later, the EIA consultant arrives and wants every layer the engineering capture filtered out — canopy structure, individual tree footprints, vegetation strata, foliage density profiles. The capture happened; the data exists; the deliverables don't include any of it because nobody asked. The fix is either a re-fly with the right brief, or a scope-back-to-source reprocess that's only possible if the operator kept the right archive.
If you've ever commissioned a LiDAR capture for an infrastructure project, then watched the environmental team arrive months later asking for canopy structure analysis, tree counts, vegetation stratification or habitat layers, you've met the cross-discipline scope problem. The engineering deliverable is what was asked for. The environmental deliverable wasn't. Both disciplines wanted information that the same flight could have provided; only the engineering side wrote the brief.
LiDAR is unusually well-suited to environmental assessment work because the cloud contains everything above and below the canopy — bare-earth ground returns, canopy structure, mid-strata vegetation, individual tree footprints, and the spatial relationships between all of them. The engineering team filters most of this out to produce a clean DTM. The arborist or ecologist wants the filtered material back.
This article walks through what arborists and ecologists actually consume from a LiDAR capture, how the brief differs from a pure engineering brief, the specific deliverables that show up in EIA work, and the cross-discipline workflow that lets one capture feed both engineering design and environmental assessment without re-flying.
The single most useful environmental deliverable. The CHM is the difference between the digital surface model (top-of-canopy) and the digital terrain model (bare ground) — a raster of canopy height above the ground, typically at 0.5-1 m resolution.
The CHM tells you:
Arborists use the CHM for tree inventory. Ecologists use it for habitat typing. Bushfire planners use it for fuel-load assessment. Carbon analysts use it for biomass estimation. Almost every EIA workflow starts with the CHM.
A processing step that takes the CHM and identifies individual tree crowns, generating one polygon per tree with attributes for canopy area, height, position, and (sometimes) species class.
Tree-segmentation algorithms work best on well-spaced canopy (open woodland, agroforestry, urban street trees). They struggle in continuous closed-canopy forest where individual crowns merge.
Outputs:
Used by arborists for inventory, by transmission network operators for vegetation management, by local government for tree management plans.
Multi-class classification of LiDAR returns by height above ground:
The strata classification supports habitat structure analysis, fire behaviour modelling, and vegetation management planning. The breakpoints (2 m, 10 m) are configurable per project and per vegetation type.
(See ground classification article for the underlying classification mechanics.)
A statistical derivation of vegetation density at each height interval. For each x,y location, the number of returns at each height stratum tells you how dense the vegetation is at that height.
The deliverable is a 3D voxel grid or per-pixel vertical profile showing foliage density vs height. Used for:
Higher-level derived products combining CHM, strata classification and density profile into ecologically- meaningful classifications:
These layers feed directly into EIA documentation and typically require ecologist or specialist processor input alongside the LiDAR processor.
Despite the focus on vegetation, the bare-earth DTM matters for environmental work too: drainage patterns, fine-scale terrain, micro-habitat features (rock outcrops, depressions, seasonal wetlands). A DTM generated for engineering design at 0.5 m resolution may smooth over features the ecology team cares about at 0.1 m resolution.
Five things that change when an EIA consumer is part of the picture:
Engineering-grade DTM can work with 20-30 ppm² ground returns. Vegetation structure analysis needs much higher total density (often 100+ ppm²) and specifically needs returns through the canopy to populate the vertical profile. Captures spec'd at engineering-grade density alone often don't have the total density to support good environmental derivatives.
(See point density article for density spec by deliverable type.)
Engineering processing sometimes drops intermediate returns to reduce file size. For environmental work, the intermediate returns are exactly where the information is — that's the canopy structure. The deliverable should preserve all returns, not just first/last.
Engineering work is largely indifferent to seasonal timing (within the seasonal-cost calculus). EIA work is not. Spring captures show flowering and emergent canopy; summer captures show full leaf-on; autumn captures show senescence; winter captures show bare deciduous and seasonal die-back of grasses.
For multi-species ecological survey, the right capture timing depends on what's being assessed. Worth a conversation with the ecologist before locking the schedule.
(See seasonal pricing article for the cost implications.)
Habitat assessments often need to include adjacent habitat patches for connectivity analysis, even if those patches aren't in the project area. The captured area should extend further than an engineering-only capture would.
(See edge effects article for the buffer-strategy framework.)
EIA work typically needs to align LiDAR outputs with state vegetation mapping, biodiversity values mapping (BVM), threatened ecological community mapping, or property-specific vegetation maps. The brief should specify which existing datasets the LiDAR is supposed to integrate with, and what the relevant attribute schemas are.
For projects supporting EIA work, a typical deliverable bundle includes the engineering set plus the environmental set:
Engineering set (familiar from prior articles):
Environmental set (additional):
The environmental set typically adds 25-40% to the processing cost over engineering-only delivery, sometimes more if specialist ecological interpretation is included.
Three patterns we see when single captures need to serve both engineering and EIA:
Engineering team commissions the capture first; environmental team arrives later. The first commission was scoped for engineering only; the environmental requirements weren't surfaced. By the time the environmental need appears, the capture is delivered, the operator has moved on, and adding environmental deliverables requires either reprocess (if the archive exists) or re-fly.
Fix: EIA consultation should happen at project inception, not at engineering deliverable handover. The brief should encompass both consumer disciplines from day one.
Some organisations run parallel survey programmes — engineering team uses one operator, environmental team uses another, both fly the same site at different times. The deliverables don't align (different sensors, different processing, different control), and integration requires significant reconciliation work.
Fix: Co-commission a single capture sized for both disciplines. The marginal cost of the environmental deliverables is much smaller than the cost of a second capture.
parameters
The capture happens with engineering-only parameters (density, timing, buffer) and the environmental deliverables that emerge are technically correct but operationally suboptimal — sparse canopy returns, wrong season, no buffer, misaligned with state mapping.
Fix: Include the ecologist/arborist in the capture-parameter conversation. Their input on density, timing and buffer can be incorporated without changing the engineering deliverable.
LiDAR is powerful for environmental assessment but not a complete solution. Three categories where additional methods are needed:
Species identification. LiDAR can identify trees; it generally can't identify species from cloud alone. Coupling LiDAR with multispectral or hyperspectral imagery, or with ground-truthed species surveys, fills this gap.
Below-ground or below-canopy features. Dense canopy with limited ground returns produces sparse DTM under the canopy. Bathymetric features in deep water require specialised bathymetric LiDAR. Sub-canopy threatened species surveys still require ground-based work.
Temporal dynamics. LiDAR is a snapshot. Some EIA work requires multi-season data (breeding behaviour, migration patterns, flowering seasonality) that LiDAR can't capture by itself. Multi-cycle programmes help; ground observation is still needed.
(See hybrid workflows article for when adding imagery is the right call.)
Six-sentence brief addition that captures the EIA deliverable scope:
"Deliverables will support both engineering design and environmental impact assessment. In addition to the engineering deliverables specified above, the operator will provide: canopy height model raster at 0.5 m resolution; individual tree segmentation with per-tree attributes (height, canopy area, position); vegetation strata classification at 2 m / 10 m breakpoints; foliage density vertical profile; and habitat structure layer aligned to attached state vegetation mapping schema. Full-return retention throughout. Capture timing in [season] to align with [specific ecological consideration]."
That paragraph turns a cross-discipline ambiguous brief into something both the engineering team and the environmental team can sign off on.
LiDAR is unusually well-suited to environmental assessment because the cloud contains everything an engineering DTM filters out — canopy structure, strata, density profile, individual trees. The problem is when only the engineering side writes the brief.
What arborists and ecologists actually consume: canopy height model, individual tree segmentation, vegetation strata, foliage density profile, habitat structure layers, bare-ground microtopography.
Five things change when EIA is part of the picture: higher density spec, full return retention, capture timing matters, wider buffer, cross-walk to existing mapping.
EIA-aware deliverable bundle adds 25-40% to processing cost over engineering-only. Much cheaper than a separate capture.
Three common cross-discipline failure modes: sequenced procurement losing scope, separate parallel captures, ecologist not consulted on parameters. All fixable by EIA consultation at project inception.
LiDAR isn't a complete environmental solution — species identification, below-canopy features, and temporal dynamics often need additional methods.
Six-sentence brief addition captures the EIA scope in a way that one capture can serve both disciplines.
If you're scoping a project where the same capture needs to support both an engineering design and an EIA, we'll structure the brief in conversation with both teams rather than running one capture for engineering and a second for environment six months later. The integrated brief is the cheap fix; the sequential procurement is where the cost lives.
The GIS-consumer-team handoff article — first in the three-discipline handoff cluster (GIS, civil design, environmental) that this article completes.
Density requirements for environmental deliverables differ from engineering — useful reference for scoping a capture that serves both disciplines.