The HJ Andrews biomass map (TV080), rebuilt from the LiDAR with the published equation

Seven LiDAR tiles run through the published equation, with nothing fitted and on TV080's own 5 m cells, come back at TV080's mean to within 1% (632.5 against 637.4 Mg/ha over 134,255 cells) and match it cell by cell: r = 0.9998, RMSE 12.1 Mg/ha, 99.8% of cells within 10%. What is left is a small, steady shortfall of about 5 Mg/ha.

How we did Close Benchmark 0 of 1 exact, 1 within tolerance all studies
TV080 biomass grid: seven LiDAR tiles rebuilt with the published equation, nothing fitted · tolerance mean within 2% over the same cells
  • Mean aboveground live biomass, 134,255 cells of 5 m637.4 Mg/ha → 632.5 Mg/ha −4.9 Mg/ha (−0.8%)within tolerance
Cell by cell against TV080 (no published figure to match)
  • Correlation r, the same 5 m cells0.9998benchmark
  • RMSE per 5 m cell12.1 Mg/habenchmark
  • Cells within 10% of the published value99.8%benchmark
632.5 Mg/hamean of the reproduced cells; TV080 637.4 over the same 134,255 cells
[181, 182]
r = 0.9998cell-by-cell correlation with TV080 at 5 m, on TV080's own cells
[183]
12.1 Mg/haRMSE per 5 m cell; 99.8% of cells within 10%
[183, 184]
155 of 155steps replay identically in a fresh session

Numbers in brackets, like [14], are step numbers in this study's run.json: the NativeGIS call that returned the figure. NativeGIS 0.4.0, recorded 2026-10-31 21:58 UTC.

Map of the HJ Andrews Experimental Forest coloured by TV080 aboveground live biomass, with seven red squares in a row across the middle marking the LiDAR tiles rebuilt
TV080 aboveground live biomass (Mg/ha, 5 m cells; colours stop at 2,000) over the forest boundary, with the seven LiDAR tiles rebuilt and compared in red. Rendered by gis_render in the recorded run; click to zoom.

The middle tile, bin_079

The same 705 m square three ways: TV080 as published, our rebuild on TV080's own cells, and the difference (red: ours lower; blue: ours higher; colours stop at ±400 Mg/ha). The difference map is almost blank: nine cells in ten are within 12 Mg/ha.

Published (TV080): fire episodes outlined over 2023 high severity
Published (TV080)
Reproduced from the 2008 LiDAR: fire episodes outlined over 2023 high severity
Reproduced from the 2008 LiDAR
Reproduced minus published: fire episodes outlined over 2023 high severity
Reproduced minus published

Click or tap a map to open it full screen, then zoom and pan.

What was published

TV080 is a 5 m grid of aboveground live biomass in Mg/ha over the 2008 HJ Andrews LiDAR area, made with the equation of Seidl et al. (2012). Its metadata records the exact calculation: biomass = 400 × (0.1870714 + 0.02105491 H95 + 0.0001975951 elevation + 0.0001773864 SD²)³, where H95 is the 95th percentile first-return height in a 5 m cell, elevation is the 5 m bare earth, and SD is the standard deviation of H95 in the 7 × 7 cells (35 m) around the cell. The cubed term is biomass in Mg per 25 m² cell; × 400 turns it into Mg per hectare.

Journal paper and the HJ Andrews data set made with its equationSeidl, R., Spies, T.A., Rammer, W., Steel, E.A., Pabst, R.J. and Olsen, K. (2012). Multi-scale drivers of spatial variation in old-growth forest carbon density disentangled with Lidar and an individual-based landscape model. Ecosystems 15: 1321–1335, doi:10.1007/s10021-012-9587-2. Data set: TV080, Aboveground Live Biomass (2008), Andrews Experimental Forest (tv08001), HJ Andrews Forest Science Data Bank.

Seidl et al. 2012 (journal) · Seidl et al. 2012 (Forest Service full text) · TV080 metadata · HJ Andrews data catalogue

Published method. The paper fits the cube root of biomass on 708 field plots, grouped into 41 spatially independent groups, and reports coefficients rounded to three figures (Table 2) with a bootstrapped adjusted R² of 0.768. Old growth, as the paper delineates it (2,191 ha), averages 435.1 Mg C/ha of aboveground live carbon at a carbon content of 50%, which is 870.2 Mg/ha of biomass.

The data and where it came from

All of it is open: downloaded without an account or a form.

DataWhereLicence
TV080 biomass grid, tv08001.zip: tv08001.e00 (a 5 m integer grid in E00 export form, 2,872 × 2,154 cells, NAD83 UTM zone 10N) with FGDC metadataHJ Andrews LTER, 6.8 MB zip (sha256 9e418923…c564de8b), downloaded without a form
https://andrewsforest.oregonstate.edu/sites/default/files/lter/data/studies/spatialdata/tv08001.zip
Use constraints "no legal constraints", acknowledgement requested (HJ Andrews data policy, CC BY)
The 2008 LiDAR flight the grid was made from (Watershed Sciences, 10–11 August 2008): seven 750 × 750 m tiles, ot_HJ_Andrews_bin_029, 039, 054, 079, 110, 136 and 163, N 4897150–4897900, EPSG:26910OpenTopography OTLAS.082011.26910.1, anonymous bulk download (25 to 37 MB per tile)
https://portal.opentopography.org/lidarDataset?opentopoID=OTLAS.082011.26910.1
Treated as CC BY 4.0 with attribution to HJ Andrews / Watershed Sciences (HJ Andrews catalogue GI010); OpenTopography lists the licence as not provided
The flight's tile index (HJAnd_OR_TileIndex.shp), for the mapOpenTopography, same bulk folder
https://opentopography.s3.sdsc.edu/pc-bulk/HJAnd_OR/HJAnd_OR_TileIndex.zip
As the LiDAR
HJ Andrews Experimental Forest boundary (GI006, boundary83.shp), for the mapHJ Andrews LTER, zip, no form or account
https://andrewsforest.oregonstate.edu/sites/default/files/lter/data/studies/spatialdata/gi00601.zip
HJ Andrews data policy (CC BY, acknowledgement requested)

The input files the run read, pinned by checksum

File (relative to the data folder)Bytessha256
samples/tv080/x/tv08001.e0089,653,180b3b4f0a0a8229d9d…
samples/ot2008/ot_HJ_Andrews_bin_029.laz24,955,073fdfda3f607e0b651…
samples/ot2008/ot_HJ_Andrews_bin_039.laz27,163,0738b14913fcf9010d4…
samples/ot2008/ot_HJ_Andrews_bin_054.laz37,364,217fd78d0fd9171b8da…
samples/ot2008/ot_HJ_Andrews_bin_079.laz30,167,25492a1e0b5a89c15e1…
samples/ot2008/ot_HJ_Andrews_bin_110.laz24,612,702f39e9fab0e97f5dc…
samples/ot2008/ot_HJ_Andrews_bin_136.laz31,573,048b666e41d3daf2ead…
samples/ot2008/ot_HJ_Andrews_bin_163.laz37,342,138561ae324ea96e005…
samples/ot2008idx/x/HJAnd_OR_TileIndex.shp25,8049cdba01734e369e3…
samples/hja-open/gi00601/x/boundary83.shp10,5400774de0a9ebd9693…

Full checksums are in run.json. Replay refuses an input whose checksum differs.

Method

  1. Open the TV080 grid (E00) and the seven LiDAR tiles. The tiles are every second whole tile on one west-to-east row across the forest (N 4897150–4897900, from E 560100 to 569100), chosen by that rule before anything was compared.
  2. Per tile: LiDAR QA, then the ground classification delivered with the flight (gis_lidar_ground mode existing).
  3. Elevation: a 5 m TIN bare-earth grid (gis_lidar_dtm) on TV080's grid lines (align to the TV080 grid). Heights: normalised to a 1 m TIN bare earth.
  4. H95: the 95th percentile of first-return heights in each 5 m cell (gis_lidar_metrics, returns first, R type 7 percentile), on TV080's grid lines too, so each of our cells is the same 5 m square as a TV080 cell.
  5. SD: the population standard deviation of H95 over the 7 × 7 cells around each cell (gis_process focal).
  6. Biomass: the published equation with the published coefficients (gis_process calc). Nothing is fitted.
  7. Cut ours and TV080 to the same cells: every cell at least 20 m inside a tile edge, so the 35 m window never runs off its tile (gis_process calc with an extent on TV080's cell edges). No interpolation: the cells are the same.
  8. Compare with TV080 per tile and over all seven tiles as one surface (gis_compare surface with correlation): mean difference, MAE, RMSE, Pearson r and the least-squares line; the share of cells within 10% of the published value (gis_process calc).
  9. Render the maps: TV080 over the whole forest with the seven tiles outlined, and the middle tile (bin_079) published, reproduced and differenced.

The run made 155 NativeGIS calls: gis_open × 10, gis_lidar_qa × 7, gis_lidar_ground × 7, gis_lidar_dtm × 14, gis_lidar_metrics × 7, gis_close × 56, gis_process × 37, gis_compare × 8, gis_query × 1, gis_render × 8.

Published numbers next to ours

Seven LiDAR tiles against TV080

LiDAR tileWest edge (E, m)Cells comparedMean difference (Mg/ha)MAE (Mg/ha)RMSE (Mg/ha)rLargest 7×7 SD of H95 (m)
bin_029560,10014,969−4.24.47.70.999922.1
bin_039561,60019,881−4.75.214.90.999727.6
bin_054563,10019,881−4.85.39.90.999927.1
bin_079564,60019,881−4.95.511.70.999928.7
bin_110566,10019,881−4.34.68.90.999927.1
bin_136567,60019,881−5.86.515.70.999724.5
bin_163569,10019,881−6.06.613.00.999827.2
All seven134,255−5.05.512.10.9998

Per tile [22, 47, 72, 97, 122, 147, 173], all seven [183]. Difference = reproduced − published, cell for cell: our 5 m cells are TV080's cells (gis_lidar_dtm and gis_lidar_metrics aligned to the TV080 grid). r is Pearson's, from gis_compare. Tile bin_029 reaches past the forest boundary, where TV080 has no cells. Units: Mg of aboveground live biomass per hectare, 5 m cells, NAD83 / UTM zone 10N.

The seven tiles as one surface

Published (TV080)Reproduced
Mean over the 134,255 cells (Mg/ha)637.4632.5
Standard deviation (Mg/ha)598.9595.8
Correlation, cell by cell (r)0.9998
Least-squares line, reproduced on published-1.6 + 0.995 × published
Difference: median, 5th to 95th percentile (Mg/ha)−4.1; −11.9 to −0.9
Cells within 10% of the published value99.8%
Before alignment (previous recording): RMSE, r161 Mg/ha, 0.97

Means and standard deviations [182, 181]; r, the line and the difference percentiles [183]; within 10% [184]. Standard deviations are population moments. The before-alignment row is quoted from the previous recording (commit e6ce80f: our 5 m grid 1 m west and 1 m north of TV080's, sampled bilinearly at TV080's cell centres), not from this run.

Why any numbers differ

Replay it yourself

The run file records every call, its arguments, the checksums of the files it read and the numbers it returned. Replaying it repeats every call in a fresh NativeGIS session and checks that each answer comes out the same.

Verified reproducible on 2026-10-31: 155/155 steps identical. The run file was replayed in a fresh NativeGIS session (0.4.0 (source 3692d6e)) against a folder holding nothing but the public downloads below, fetched with these exact commands.
  1. Make an empty data folder and fetch the inputs into it exactly as below (bash; the folder layout is the one the run file expects):
    cd /path/to/an/empty/folder
    mkdir -p samples/tv080 && curl -fL -o samples/tv080/tv08001.zip https://andrewsforest.oregonstate.edu/sites/default/files/lter/data/studies/spatialdata/tv08001.zip && unzip -o samples/tv080/tv08001.zip -d samples/tv080/x
    mkdir -p samples/ot2008 && curl -fL -o samples/ot2008/ot_HJ_Andrews_bin_029.laz https://opentopography.s3.sdsc.edu/pc-bulk/HJAnd_OR/ot_HJ_Andrews_bin_029.laz
    mkdir -p samples/ot2008 && curl -fL -o samples/ot2008/ot_HJ_Andrews_bin_039.laz https://opentopography.s3.sdsc.edu/pc-bulk/HJAnd_OR/ot_HJ_Andrews_bin_039.laz
    mkdir -p samples/ot2008 && curl -fL -o samples/ot2008/ot_HJ_Andrews_bin_054.laz https://opentopography.s3.sdsc.edu/pc-bulk/HJAnd_OR/ot_HJ_Andrews_bin_054.laz
    mkdir -p samples/ot2008 && curl -fL -o samples/ot2008/ot_HJ_Andrews_bin_079.laz https://opentopography.s3.sdsc.edu/pc-bulk/HJAnd_OR/ot_HJ_Andrews_bin_079.laz
    mkdir -p samples/ot2008 && curl -fL -o samples/ot2008/ot_HJ_Andrews_bin_110.laz https://opentopography.s3.sdsc.edu/pc-bulk/HJAnd_OR/ot_HJ_Andrews_bin_110.laz
    mkdir -p samples/ot2008 && curl -fL -o samples/ot2008/ot_HJ_Andrews_bin_136.laz https://opentopography.s3.sdsc.edu/pc-bulk/HJAnd_OR/ot_HJ_Andrews_bin_136.laz
    mkdir -p samples/ot2008 && curl -fL -o samples/ot2008/ot_HJ_Andrews_bin_163.laz https://opentopography.s3.sdsc.edu/pc-bulk/HJAnd_OR/ot_HJ_Andrews_bin_163.laz
    mkdir -p samples/ot2008idx && curl -fL -o samples/ot2008idx/HJAnd_OR_TileIndex.zip https://opentopography.s3.sdsc.edu/pc-bulk/HJAnd_OR/HJAnd_OR_TileIndex.zip && unzip -o samples/ot2008idx/HJAnd_OR_TileIndex.zip -d samples/ot2008idx/x
    mkdir -p samples/hja-open/gi00601 && curl -fL -o samples/hja-open/gi00601/gi00601.zip https://andrewsforest.oregonstate.edu/sites/default/files/lter/data/studies/spatialdata/gi00601.zip && unzip -o samples/hja-open/gi00601/gi00601.zip -d samples/hja-open/gi00601/x
  2. Download run.json (299,011 bytes, sha256 2e50bfe909f00c22eccab60a921bb6de17109fd6f4fcf2ff3f141285c68300aa).
  3. Ask your assistant to replay it with NativeGIS, or call the tool directly:
gis_replay {"action": "replay",
            "file": "<absolute path to the run.json you downloaded>",
            "inputRoot": "<your data folder>",
            "outputRoot": "<a new, empty folder>"}

Paths in the run file are relative to the data folder (inputRoot), and outputs go under outputRoot, so nothing depends on where the original run lived.

Files

Limits

NativeGIS reproductions · every NativeGIS number on this page is read from the recorded run file it links to.