Five centuries of fire, then the Lookout Fire

The HJ Andrews fire-history map records 31 fires between 1532 and 1952. Counting every 30 m cell once, ground whose last recorded fire was in the 1500s burned at high severity in the 2023 Lookout Fire at 8–9%, against 28.5% overall. That holds however the fire-history layer is aligned. An earlier claim that ground with no recorded fire after 1482 burned hottest did not hold, and is withdrawn.

How we did New analysis No published number to match all studies
Fire history (1532–1952) against 2023 high severity
  • High severity on ground last burned in the 1500s9.0%new
  • High severity over the whole area28.5%new
9.0%high severity in 2023 where the last recorded fire was in the 1500s (5,742 cells)
[228]
28.5%high severity over all 47,725 cells
[11]
8.1–8.9%1500s ground, under each of 4 alignments of the fire-history layer (moved north, or re-registered to Teensma's maps)
[445, 670, 895, 1123]
1124 of 1124steps 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 04:52 UTC.

Map of the whole HJ Andrews forest coloured by the century of the last recorded fire, with the 2023 Lookout Fire perimeter outlined in magenta and 2023 high severity shaded
Every 30 m cell of the HJ Andrews forest, coloured by its last recorded fire before 2023: purple, no recorded fire after the 1482 base; dark blue, the 1500s; through to red, 1900–1952. Magenta outline: the 2023 Lookout Fire perimeter. Grey shading inside it: 2023 high severity (MTBS). Black: the forest boundary. The numbers on this page count only the cells inside the 2023 perimeter. Rendered by gis_render in the recorded run.

How many times each cell burned

The number of recorded fires per cell, 1532–1952, over the whole forest, with the 2023 perimeter outlined in magenta and 2023 high severity shaded grey. Most of the high-severity core in the south-east burned five or more times in the record. The numbers count only the cells inside the perimeter.

Recorded fires per cell: fire episodes outlined over 2023 high severity
Recorded fires per cell

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

What was published

A map of the individual fires from 1482 to 1952, reconstructed from tree rings and fire scars and digitised from 31 episode maps. The 258 polygons come from overlaying those maps. 197 are marked fire present (AGE = 0) with the episode's year, and 61 are marked fire absent (AGE = 1, no year). Polygons overlap wherever the same ground burned in several fires. The 1482 polygon is different from the rest: one polygon spanning the whole reconstruction area with a stair-stepped edge, so this page treats it as the record's base and not as a fire. The thesis's own stand statistics, and the later Tepley et al. 2013 analysis, rest on plot data behind the HJ Andrews registration form, so this page re-derives no published number.

Published dataset, analysed in a new way (not a reproduction of a paper's numbers)Teensma, P.D.A. (1987). Fire history and fire regimes of the central western Cascades of Oregon. PhD dissertation, University of Oregon. Digitised as HJ Andrews dataset DF019, "Fire history reconstruction (1482–1952), Andrews Experimental Forest and vicinity" (EDI knb-lter-and.3990.5).

DF019 data (zip) · HJ Andrews data catalogue

The data and where it came from

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

DataWhereLicence
DF019 fire-history polygons, firehistory_region.shp: 258 polygons with EPISODE (year) and AGE (0 = fire present), NAD83 UTM zone 10NHJ Andrews LTER, 1.6 MB zip, no form or account
https://andrewsforest.oregonstate.edu/sites/default/files/lter/data/studies/spatialdata/df01901.zip
HJ Andrews data policy (CC BY, acknowledgement requested)
HJ Andrews boundary (GI006), and the MTBS Lookout Fire perimeter and severity, as in R9HJ Andrews LTER
https://andrewsforest.oregonstate.edu/sites/default/files/lter/data/studies/spatialdata/gi00601.zip
CC BY (boundary); public domain (MTBS)

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/lookout/x/or4422212214620230806_20230731_20240826_dnbr.tif774,9369bc6bed26d918204…
samples/hja-open/df01901/x/firehistory_region.shp2,204,480f1bd94a45b911c1e…

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

Method

  1. Prepare the 2023 side as in R9: the forest boundary in equal-area Albers, its intersection with the fire perimeter, and the MTBS severity classes clipped to it. A 0/1 raster marks high severity (class 4).
  2. Open the fire-history polygons and keep those marked fire present, leaving out the 1482 base polygon. Reproject them to EPSG:5070 and dissolve them by year, which gives one feature for each of the 31 fires.
  3. For each fire, mark the 30 m cells of the 2023 fire area whose centre falls inside it. Then for every cell take the year of its last recorded fire and the number of recorded fires. Ground covered by several fires is counted once, under its latest fire.
  4. Cross-tabulate both per-cell layers with 2023 high severity. Each cell gets the code class × 10 + high, and a reclassify counts the cells per code.
  5. Maps: the last recorded fire and the number of fires for every cell of the forest (the fire history covers all of it), with the 2023 perimeter outlined and 2023 high severity shaded inside it. Only the cells inside the perimeter go into the tables.

The run made 1124 NativeGIS calls: gis_open × 5, gis_process × 413, gis_query × 158, gis_close × 546, gis_render × 2.

The numbers

By the last recorded fire before 2023

Last recorded fireCells (n)Share of the areaBurned at high severity in 2023
No recorded fire after 14822,3645.0%41.1% (972)
1500s5,74212.0%9.0% (516)
1600s1,5433.2%16.5% (254)
1700s4,1178.6%16.0% (658)
1800s32,83068.8%33.5% (11,009)
1900–19521,1292.4%15.6% (176)
Whole area47,725100.0%28.5%

Each 30 m cell is counted once [228].

By the number of recorded fires, 1532–1952

Recorded firesCells (n)Share of the areaBurned at high severity in 2023
None after 14822,3645.0%41.1% (972)
13,9098.2%29.7% (1,160)
26,02012.6%23.5% (1,415)
37,08014.8%15.5% (1,098)
47,57015.9%16.3% (1,236)
5 or more20,78243.5%37.1% (7,704)
Whole area47,725100.0%28.5%

Each 30 m cell is counted once [230].

Method: the 31 fire episodes after 1482 (DF019 polygons marked fire present), reprojected to EPSG:5070 and dissolved by year [15, 17]. For each episode, the zone's cells whose centre falls inside it [21]; then per cell the latest year and the count [224, 226]; each crossed with a 0/1 raster of MTBS high severity [11]. Units: 30 m cells (900 m²). n = 47,725 cells, the HJ Andrews part of the 2023 fire perimeter.

Does the 200 m misregistration change the answer?

The fire-history layer sits about 200 m south of the forest boundary and of the 2018 LiDAR-based watershed. Here the per-cell tables are rebuilt with the layer moved north by each measured offset (gis_process translate, in its own UTM projection, before everything else), and, in the last column, re-registered to Teensma's own 1987 maps (see Compared with the published maps below). Each cell: share burned at high severity in 2023 (cells).

The re-registration is the best-supported alignment: it corrects the north–south stretch rather than moving the whole layer. DF019 is moved to a local origin, then put through georeference [908], which on a vector treats input coordinates as column and row, so it applies a plain affine. Its 342 control points are measured transect pairs (every second one), each a DF019 edge and the same edge on one of Teensma's registered maps. The affine scales north–south by 0.9774 and leaves east–west unchanged. Its RMSE is 43 m and its leave-one-out error 44 m, about the registration error of Teensma's maps themselves, so a single affine describes the distortion as well as the maps can show it. The op reports the fit in pixel terms; here a pixel is a metre.

Last recorded fire, shifted

As publishedmoved 200 m north [445]moved 15 m east, 143 m north (mean offset from the forest boundary) [670]moved 4 m east, 161 m north (mean offset from the LiDAR watershed) [895]Re-registered to Teensma 1987 (best supported) [1123]
No recorded fire after 148241.1% (2,364)29.4% (2,243)32.2% (2,225)30.9% (2,241)31.8% (2,234)
1500s9.0% (5,742)8.1% (4,995)8.7% (5,228)8.4% (5,121)8.9% (5,305)
1600s16.5% (1,543)18.5% (1,526)18.2% (1,561)18.8% (1,567)17.3% (1,545)
1700s16.0% (4,117)12.9% (3,702)13.2% (3,814)13.2% (3,763)13.3% (3,876)
1800s33.5% (32,830)34.0% (33,784)33.9% (33,525)33.9% (33,636)34.0% (33,346)
1900–195215.6% (1,129)18.8% (1,475)18.8% (1,372)18.8% (1,397)18.9% (1,419)

Number of recorded fires, shifted

As publishedmoved 200 m north [447]moved 15 m east, 143 m north (mean offset from the forest boundary) [672]moved 4 m east, 161 m north (mean offset from the LiDAR watershed) [897]Re-registered to Teensma 1987 (best supported) [1125]
None after 148241.1% (2,364)29.4% (2,243)32.2% (2,225)30.9% (2,241)31.8% (2,234)
129.7% (3,909)28.3% (3,827)29.6% (3,839)29.1% (3,828)29.7% (3,754)
223.5% (6,020)27.4% (5,838)26.5% (5,921)26.9% (5,891)25.9% (5,917)
315.5% (7,080)19.2% (6,918)18.0% (6,979)18.3% (6,946)18.6% (6,954)
416.3% (7,570)17.6% (7,489)16.9% (7,566)17.3% (7,552)16.8% (7,521)
5 or more37.1% (20,782)35.5% (21,410)36.0% (21,195)35.8% (21,267)35.9% (21,345)

Compared with the published maps: where the 200 m offset came from

To find where DF019's southward offset entered, Teensma's own 1987 maps and the 2004 HJ Andrews preview of DF019 were placed on the ground with NativeGIS's georeference and measured against DF019 along north–south transects. Teensma's maps were registered only on features that are not fire lines: 2 stream confluences and 4 closed-contour summits. The preview was registered on the HJ Andrews boundary.

Lines compared (north–south)MeanMediannRegistration error (leave-one-out)Reading
Teensma Fig. 2 outline vs HJ Andrews boundary (GI006), south edge−58 m−58 m21243 mnegative: Teensma's line is south of GI006, by about one registration error [34]
Teensma Fig. 2 outline vs DF019 base polygon, south edge+183 m+183 m22343 mpositive: DF019 is south of Teensma [24]
Teensma Fig. 2 outline vs DF019 base polygon, north edge−13 m−13 m19743 mthey agree [24]
Teensma Fig. 13, fire of 1532: burn lines vs DF019's same fire+126 m+138 m5245 mpositive: DF019 south of Teensma; larger where the lines lie further south [60]
Teensma Fig. 32, fire of 1839: burn lines vs DF019's same fire+159 m+171 m4255 mpositive: DF019 south of Teensma; larger where the lines lie further south [85]
Teensma Fig. 34, fire of 1857: burn lines vs DF019's same fire+54 m+59 m15838 mpositive: DF019 south of Teensma; larger where the lines lie further south [110]
2004 preview: DF019 south edges vs GI006−157 m−178 m13170 mDF019 already south of the boundary in 2004 [143]
2004 preview: DF019 then vs DF019 now+83 m+70 m14070 mabout one registration error: not resolved [153]

Method. Teensma 1987 Fig 2 (study area): affine fit on 6 points, RMSE 21 m, leave-one-out 43 m [15]; Teensma 1987 Fig 13 (1532): affine fit on 6 points, RMSE 22 m, leave-one-out 45 m [51]; Teensma 1987 Fig 32 (1839): affine fit on 6 points, RMSE 28 m, leave-one-out 55 m [76]; Teensma 1987 Fig 34 (1857): affine fit on 6 points, RMSE 19 m, leave-one-out 38 m [101]; HJA DF019 preview (2004): similarity fit on 8 points, RMSE 54 m, leave-one-out 70 m [127]. Teensma's scans have about 3% more scale across than down, so an affine fit is used for them. Transects every 50 m pair each digitised line with the nearest DF019 or GI006 edge within 450 m. The pairs are measured with gis_compare (points by key), whose means are printed above. The medians, per-segment means and the trend are plain arithmetic on the same pairs (summary.json). Two contour rings were rejected as controls because their leave-one-out errors were 160 and 207 m. NativeGIS has no line-with-line intersection yet, so the transect crossings were found in the driving script. The run, published-maps-run.json (163 steps), replays identically in a fresh session. It reads the scanned figures, which are not redistributed here.

The figures. P. D. A. Teensma (1987), Fire history and fire regimes of the central western Cascades of Oregon, PhD dissertation, University of Oregon: Figs. 2, 13, 32 and 34 (PDF from HJ Andrews, pub716). The HJ Andrews DF019 catalogue preview, dated 13 December 2004 (image). They were used as analysis inputs only. The maps below draw only our digitised lines and the open layers, not the figures.

What this means for the sensitivity table. Moving all of DF019 north by 200 m fixes the south edge but moves the northern half 150–200 m too far. A north–south scale of about 0.979 about northing 4,903 km would match the published maps. The sensitivity table above now includes that re-registration, fitted to the measured pairs themselves, as its last column.

Teensma 1987 Fig. 2 study-area outline (magenta) registered on streams and summits, over DF019's base polygon (red) and the HJ Andrews boundary GI006 (green). Lines only: the figure itself is not reproduced.
Fig. 2, study area: Teensma 1987 Fig. 2 study-area outline (magenta) registered on streams and summits, over DF019's base polygon (red) and the HJ Andrews boundary GI006 (green). Lines only: the figure itself is not reproduced.
Teensma 1987 Fig. 13 burn lines for 1532 (magenta) against DF019's 1532 fire (red).
Fig. 13, fire of 1532: Teensma 1987 Fig. 13 burn lines for 1532 (magenta) against DF019's 1532 fire (red).
Teensma 1987 Fig. 32 burn lines for 1839 (magenta) against DF019's 1839 fire (red).
Fig. 32, fire of 1839: Teensma 1987 Fig. 32 burn lines for 1839 (magenta) against DF019's 1839 fire (red).
Teensma 1987 Fig. 34 burn lines for 1857 (magenta) against DF019's 1857 fire (red).
Fig. 34, fire of 1857: Teensma 1987 Fig. 34 burn lines for 1857 (magenta) against DF019's 1857 fire (red).
The south edges of the 2004 DF019 preview (magenta), registered on the HJ Andrews boundary, against DF019 today (red) and GI006 (green).
HJA DF019 preview, 2004: The south edges of the 2004 DF019 preview (magenta), registered on the HJ Andrews boundary, against DF019 today (red) and GI006 (green).

What the numbers say, and what they do not

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: 1124/1124 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/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/hja-open/df01901 && curl -fL -o samples/hja-open/df01901/df01901.zip https://andrewsforest.oregonstate.edu/sites/default/files/lter/data/studies/spatialdata/df01901.zip && unzip -o samples/hja-open/df01901/df01901.zip -d samples/hja-open/df01901/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
  2. Download run.json (1,351,952 bytes, sha256 01b4986ac4bfe8de6576f015a5126b4c9691ec7441d11134d778fc1cae7411b4).
  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.