How much of the Andrews Forest burned in 2023?

HJ Andrews says the Lookout Fire burned about 70% of the forest. That matches the area the fire covered: 68% of the forest lies inside the incident's final perimeter and inside the BAER soil burn severity map, the two footprints that existed when the figure was first given, and 67% inside the later MTBS perimeter. The ground that actually burned is less: 57% at low, moderate or high severity, about a fifth at high severity.

How we did Matches except 0 of 4 exact, 2 within tolerance, 2 explained all studies
HJ Andrews: the Lookout Fire burned "approximately 70%" of the forest · tolerance 2.5 percentage points ('approximately' / 'ca.' a round 70%, the same rule as the old-growth study's 'about 40%') · The published figure is read as the area the fire covered: it was first given on 6 Oct 2023, when only the NIFC perimeter and the BAER map existed, and the two footprints of that date lie within 2.5 points of it. The burned-at-severity share is a different quantity, kept as a contrast. why
  • Inside the NIFC final incident perimeter (the footprint on 6 Oct 2023)70% → 68.2% −1.8 ptswithin tolerance
  • Inside the BAER soil burn severity map (final 3 Oct 2023)70% → 68.1% −1.9 ptswithin tolerance
  • Inside the MTBS fire perimeter (mapped later, 2024)70% → 67.4% −2.6 ptsexplained why
  • Contrast: actually burned (MTBS low to high severity)70% → 57.0% −13.0 ptswording why
67.4%–68.2%of the forest inside the fire's mapped footprint (NIFC, BAER, MTBS); published "approximately 70%"
[17, 30, 5]
57.0%of the forest actually burned at low, moderate or high severity (MTBS), a different measure
[13]
19.2%of the forest burned at high severity (MTBS)
[13]
38 of 38steps 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.3.0, recorded 2026-10-31 15:18 UTC.

Map of the HJ Andrews forest boundary with the 2023 Lookout Fire severity classes inside it, over a hillshade, with streams and two fire perimeters
The HJ Andrews Experimental Forest (black outline), with MTBS's 2023 burn-severity classes where the forest lies inside the MTBS fire perimeter (magenta), drawn as their 30 m cells at 65% opacity over a hillshade of an 8 m USGS 3DEP DEM. Orange: the NIFC final incident perimeter. Blue: streams (HJ Andrews HF013). The straight stepped lines in the shading north-west of the forest are in the 3DEP elevation data itself, where its source surveys meet. Rendered as SVG by gis_render in the recorded run; click to zoom.

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

What was published

A share of the forest burned: "approximately 70%", first given on 6 October 2023, before MTBS mapped the fire (its post-fire image is from 26 August 2024). The statement does not say how "burned" was measured. So this page measures the area the fire covered with each footprint that existed then, the incident's final perimeter (NIFC) and the BAER soil burn severity map, and with the later MTBS perimeter; and, as a contrast, the share that actually burned (MTBS low, moderate or high severity).

Statement by the HJ Andrews Experimental Forest (not a journal paper)HJ Andrews Experimental Forest (Oregon State University and USDA Forest Service). Monthly meeting notice, 6 October 2023: the Lookout Fire "has burned approximately 70%" of the forest "to date". Repeated on the post-fire field trips page 2023–2024: "The Lookout Fire burned over approximately 70% of the H.J. Andrews Experimental Forest."

HJ Andrews monthly meeting notice, 6 Oct 2023 · HJ Andrews post-fire field trips page · HJ Andrews Lookout Fire updates, 2023 · MTBS program

Published method. HJ Andrews gives no method, boundary or source for its 70%. During the fire, on 28 and 29 August 2023, its updates page gave 57% of the forest's 6,400 ha as burned to date; the fire kept spreading after that.

The data and where it came from

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

DataWhereLicence
HJ Andrews Experimental Forest boundary (GI006, boundary83.shp), NAD83 UTM zone 10NHJ Andrews LTER, 175 kB 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)
MTBS fire bundle for the Lookout Fire (perimeter and dNBR6 severity classes, 30 m, USA Contiguous Albers)Re-hosted by the HJ Andrews LTER, 8.3 MB zip, no form or account
https://andrewsforest.oregonstate.edu/sites/default/files/lter/fsdbdata/gis/LF_or4422212214620230806.zip
US federal data, public domain
NIFC WFIGS interagency fire perimeter for the Lookout Fire (incident 2023-ORWIF-230327): the incident's final perimeter, polygon dated 23 Sep 2023, 25,754 ac; GeoJSON in EPSG:5070 from the feature serviceNational Interagency Fire Center, WFIGS Interagency Perimeters feature service (query, f=geojson), 0.3 MB, no form or account
https://services3.arcgis.com/T4QMspbfLg3qTGWY/arcgis/rest/services/WFIGS_Interagency_Perimeters/FeatureServer/0
US federal data, public domain
BAER soil burn severity for the Lookout Fire (item lookout_or4422212214620230806_sbs, final map completed 3 Oct 2023; classes 1 unburned or very low, 2 low, 3 moderate, 4 high; 15 = not mapped), 20 m cells, NAD83 UTM zone 10NUSFS Enterprise Data Warehouse BAER soil burn severity image service, exported on the item's own 20 m grid and extent with no no-data value, uncompressed GeoTIFF, 2.6 MB, no form or account
https://imagery.geoplatform.gov/iipp/rest/services/Fire_Aviation/USFS_EDW_BAER_SoilBurnSeverityClassification/ImageServer
US federal data, public domain
USGS 3DEP elevation, exported as a 8 m DEM (32-bit float GeoTIFF, EPSG:5070) for the forest's window; used only for the map's hillshadeUSGS National Map 3DEP elevation image service (exportImage), no form or account; two exports gave the same sha256
https://elevation.nationalmap.gov/arcgis/rest/services/3DEPElevation/ImageServer
US federal data, public domain
HJ Andrews stream network (HF013, hydro.shp), NAD83 UTM zone 10N; drawn on the map onlyHJ Andrews LTER, zip, no form or account
https://andrewsforest.oregonstate.edu/sites/default/files/lter/data/studies/spatialdata/hf01301.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/hja-open/gi00601/x/boundary83.shp10,5400774de0a9ebd9693…
samples/lookout/x/or4422212214620230806_20230731_20240826_burn_bndy.shp33,64444058cc0c370ce97…
samples/lookout/x/or4422212214620230806_20230731_20240826_dnbr6.tif398,684221e116ff1ab8180…
samples/nifc/lookout_2023_wfigs.geojson317,021d26019924a2a9856…
samples/baer/lookout_sbs_export_raw.tif2,558,0000f0f997a5e3ae9df…
samples/dem3dep/hja_forest_5070_8m.tif12,847,836cebeb84b418543df…
samples/hja-open/hf01301/x/hydro.shp173,308263271acd998f7bd…

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

Method

  1. Open the forest boundary (UTM zone 10N), plus the MTBS perimeter and severity raster (USA Contiguous Albers). As in R1, EPSG:5070 is declared for the perimeter.
  2. Reproject the boundary to EPSG:5070. Albers is an equal-area projection, so areas measured in it are true areas.
  3. Intersect the boundary with the MTBS fire perimeter: the part of the forest inside the fire.
  4. Clip the MTBS severity classes to that intersection (cells whose centre is inside), polygonize them, dissolve by class and measure the areas.
  5. Open the NIFC final incident perimeter (served in EPSG:5070) and intersect it with the boundary the same way.
  6. Open the BAER soil burn severity raster (EPSG:26910, 20 m). Count its values, then make one 0/1 raster for "mapped" (classes 1 to 4) and one per class. Their means over the cells whose centre is inside the boundary, in its own UTM projection, are the shares of the forest. Nothing is resampled.
  7. Render the map as SVG: the MTBS severity classes as 30 m cells at 65% opacity over a hillshade of an 8 m USGS 3DEP DEM, with both fire perimeters, the forest boundary and its streams.

The run made 38 NativeGIS calls: gis_open × 7, gis_process × 25, gis_query × 4, gis_render × 2.

Published numbers next to ours

The claim against three footprints of the fire

MeasureArea (ha)Share of the forest
HJ Andrews, 6 Oct 2023: "burned approximately 70%"≈ 70%
The forest (equal-area Albers) [4]6,374100%
Inside the NIFC final incident perimeter (polygon of 23 Sep 2023) [16, 17]4,34868.2%
Inside the BAER soil burn severity map's mapped area (final, 3 Oct 2023) [21, 30]4,33968.1%
Inside the MTBS fire perimeter (post-fire image 26 Aug 2024) [5]4,29467.4%
Contrast, a different measure: actually burned, MTBS low, moderate or high severity [13]3,63657.0%
Contrast: BAER soil burn severity low, moderate or high [30]3,98662.6%
Burned at high severity (MTBS) [13]1,22319.2%

Method: the forest boundary reprojected to EPSG:5070 (Albers equal-area) and intersected with the MTBS perimeter and with the NIFC WFIGS perimeter (25,754 ac in its own attribute) [4, 5, 17]. BAER: 20 m cells of the soil burn severity raster whose centre is inside the boundary, in the raster's own EPSG:26910, counted with one 0/1 raster per class [21, 30]; hectares are the share times the boundary's own area. MTBS severity from dNBR6 cells whose centre falls inside the forest-and-perimeter intersection, polygonized, dissolved by class and measured [6, 8, 9, 11, 13]. Units: m² shown as hectares. n = 159,233 BAER cells (400 m²) and 47,725 MTBS cells (900 m²). The boundary file's own area attribute (UTM) is 6,369 ha [14].

BAER soil burn severity inside the forest

BAER classCellsShare of the forest
Unburned or very low8,8425.6%
Low82,45751.8%
Moderate14,2619.0%
High2,9211.8%
Not mapped (value 15)50,75231.9%
Cells with their centre inside the forest159,233100%

The export holds 270,329 mapped cells and 2,167,251 cells of value 15 (not mapped), and no other value [19]. BAER counts "unburned or very low" inside its mapped area, so even its mapped footprint is not all burned ground.

MTBS severity inside the forest

MTBS classhaCellsShare of the forest
Unburned to low6597,32110.3%
Low1,43415,93122.5%
Moderate98010,88615.4%
High1,22313,58519.2%
Increased greenness020.0%

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: 38/38 steps identical. The run file was replayed in a fresh NativeGIS session (0.4.0 (source ed23d55)) 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/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
    mkdir -p samples/lookout && curl -fL -o samples/lookout/LF_or4422212214620230806.zip https://andrewsforest.oregonstate.edu/sites/default/files/lter/fsdbdata/gis/LF_or4422212214620230806.zip && unzip -o samples/lookout/LF_or4422212214620230806.zip -d samples/lookout/x
    mkdir -p samples/dem3dep && curl -fL -o samples/dem3dep/hja_forest_5070_8m.tif 'https://elevation.nationalmap.gov/arcgis/rest/services/3DEPElevation/ImageServer/exportImage?bbox=-2066500,2636500,-2052500,2650600&bboxSR=5070&imageSR=5070&size=1750,1763&format=tiff&pixelType=F32&noData=-9999&interpolation=RSP_BilinearInterpolation&compression=None&f=image'
    mkdir -p samples/hja-open/hf01301 && curl -fL -o samples/hja-open/hf01301/hf01301.zip https://andrewsforest.oregonstate.edu/sites/default/files/lter/data/studies/spatialdata/hf01301.zip && unzip -o samples/hja-open/hf01301/hf01301.zip -d samples/hja-open/hf01301/x
    mkdir -p samples/nifc && curl -fL -o samples/nifc/lookout_2023_wfigs.geojson 'https://services3.arcgis.com/T4QMspbfLg3qTGWY/arcgis/rest/services/WFIGS_Interagency_Perimeters/FeatureServer/0/query?where=attr_UniqueFireIdentifier%3D%272023-ORWIF-230327%27&outFields=OBJECTID,poly_IncidentName,attr_UniqueFireIdentifier,poly_GISAcres,poly_PolygonDateTime&outSR=5070&f=geojson'
    mkdir -p samples/baer && curl -fL -o samples/baer/lookout_sbs_export_raw.tif 'https://imagery.geoplatform.gov/iipp/rest/services/Fire_Aviation/USFS_EDW_BAER_SoilBurnSeverityClassification/ImageServer/exportImage?bbox=555218.49909751082,4877231.7363584125,585918.49909751082,4908991.7363584125&bboxSR=26910&imageSR=26910&size=1535,1588&format=tiff&compression=None&pixelType=U8&interpolation=RSP_NearestNeighbor&mosaicRule=%7B%22mosaicMethod%22%3A%22esriMosaicLockRaster%22%2C%22lockRasterIds%22%3A%5B3639%5D%7D&f=image'
  2. Download run.json (77,068 bytes, sha256 8252843251b03ee865be83ab515ed7371c38c4c0dbaf655d631647c183e4300d).
  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.