Reading Fire (2012): agency and satellite boundary comparison

Initial cartographic draft · editorial review pending

The two archived records for Reading Fire (2012) give different ways to locate the event. The NIFC feature stores 28,073 GIS acres; the MTBS record stores 26,861 acres. Their outlines share approximately 10,601 hectares, while their combined mapped extent is 11,626 hectares. The question for this draft is: Where do the agency and satellite boundaries differ?

Where do the agency and satellite boundaries differ?

NIFC incident identifier2012-CALNP-003115
MTBS fire identifierCA4049312045120120723
Ignition-date attribute in MTBS23 July 2012
NIFC GIS_ACRES attribute28,073.2 acres
MTBS ACRES attribute26,861.0 acres
MTBS assessment typeExtended
NIFC source / map methodNPS / Autonomous GPS
Reading Fire 2012: NIFC perimeter in green and MTBS boundary in orange; north up.
Historical boundary comparison in a local equal-area projection. Green and orange encode datasets, not burn-severity classes.

Where the outlines agree and differ

The intersection is 91.2% of the union of the two projected polygons. Approximately 751 hectares lie inside the NIFC outline alone, and 275 hectares lie inside the MTBS outline alone. The NIFC outline spans about 14.7 by 14.5 kilometres in the local map coordinates. These widths and heights describe a bounding rectangle, rather than the route or speed of a fire front.

Reading the two acreage attributes

The MTBS acreage attribute is 1,212.2 acres below the NIFC GIS attribute, a difference of 4.3% relative to NIFC. Those attributes are retained as published by each collection; they are separate from the areas recalculated from the polygons for this overlay. The difference is not an observation of fire growth between two times. For a location-based comparison, examine the two edges as well as the totals. Agreement between these archives does not constitute independent verification of every point along the boundary.

Dates and mapping evidence

The MTBS ignition-date attribute is 23 July 2012. Its mapping record links the following scene identifiers:

  • PRE_ID: 504403220110801
  • POST_ID: 804403220130721

The date attribute and scene identifiers provide a route back to the source records. They do not establish a suppression chronology, a containment date, evacuation timing or the date when a particular location burned. This draft has not reconstructed those operational events.

Review before publication

This is an initial cartographic draft. The name, year, source identifiers and spatial overlap have been cross-checked automatically. Before publication, confirm aliases and complex/component relationships against an incident-specific operational record, assess the suitability of the source boundaries, and complete the narrative review. These two collections can share upstream information. The overlap percentage is a geometric comparison, not an evidence-quality score or a measure of ecological damage.

Sources and reproducibility

Method: WGS84 coordinates reprojected to a Lambert azimuthal equal-area projection centred on the NIFC geometry. NIFC query generalization is at most 0.0005 degrees for the original candidates and 0.0001 degrees for supplemental candidates. Metrics use the returned geometries; display outlines are simplified to 45 metres. Polygon intersection divided by polygon union gives the overlap percentage. Values are approximate and are not burn-severity measurements. Source snapshot: 5 November 2026.


Reading Fire 2012: documentary evidence audit and source-version discrepancies

Tecnobosque Wildfire Black Box · Source review · 6 November 2026. This documentary investigation supplements the NIFC–MTBS cartographic comparison above. It does not change the original geometries, recalculate burned area or assess individual responsibility. Numerical differences below describe published records, not new measurements.

Research question

Can the reported final area of Reading Fire be reconciled unambiguously with agency breakdowns and other published park figures? Not from the documents reviewed here. The discrepancies should remain visible until their definitions and source versions are reconciled.

Evidence timeline: what was reported, and when?

Record dateEvidenceInterpretation limit
23 July 2012The fire started following lightning. The later CAL FIRE incident entry gives 5:09 p.m. as its start/report time; NPS’s contemporary account identifies the lightning event.The reported time need not be the physically exact first ignition instant.
8 August 2012NPS news release reported about 2,000 acres and 5% containment, describing the switch to suppression.A contemporary provisional figure is not the final mapped area.
22 August 2012CAL FIRE’s archived incident reports 100% containment and 28,079 acres; NPS’s history page also uses 28,079 acres.The published total does not imply every hectare within the boundary burned uniformly.
29–30 January 2013NPS announced an interagency retrospective review, released on 29 January.A retrospective conclusion must not be assigned to a decision-maker’s knowledge in August 2012.

Finding RF2012-004: 60-acre discrepancy within the official breakdown

Two NPS publications report a total of 28,079 acres and describe approximately 16,993 acres on NPS land, 11,071 acres on USFS land, and 75 acres on private land.

Reported measureAcres
Official published incident total28,079
NPS component16,993
USFS component11,071
Private-land component75
Sum of reported components28,139
Difference from published total+60 (approximately 24.3 hectares)

Evidence status: arithmetic confirmed; interpretation unresolved. The source descriptions use approximate figures, and their mapping assumptions have not been independently established. Do not silently change the official incident total or assert that 60 additional acres burned.

Finding RF2012-005: 895-acre park/NPS-lands difference

On its fire history page, NPS lists 16,098 acres within Lassen Volcanic National Park in a historical table, but 16,993 acres on NPS land in its narrative: a difference of 895 acres. The phrases “within the park” and “on NPS land” need not mean identical geographic scopes. Different datasets, publication revisions or mapping rules are possible explanations, none demonstrated by the inspected source alone.

Finding RF2012-006: injury counts depend on the publication

The NPS historical summary states that one injury was reported; the retrospective Reading Fire Review abstract describes two firefighter injuries. Both counts should retain their exact source and temporal provenance. This does not, by itself, establish an error or a contradiction in the underlying incident reports.

Black Box evidence claims (proposed identifiers)

ClaimDocumented assertionReview state
RF2012-001Reported start on 23 July 2012; 5:09 p.m. in incident recordAttributed historical record
RF2012-002NPS reported roughly 2,000 acres and 5% containment on 8 AugustDated provisional claim
RF2012-003Final published size 28,079 acres, containment 22 AugustReported official figure
RF2012-004Listed land components add to 28,139 acresArithmetic confirmed; meaning unresolved
RF2012-00516,098 acres within park vs. 16,993 acres on NPS landsDefinitions/versions unresolved
RF2012-006One reported injury in NPS summary vs. two firefighter injuries in retrospective reviewSource/date context unresolved

Reproducibility, caveats and further reading

This audit does not reconstruct raw NIFC or MTBS geometry, compute a new dNBR image, or establish the original reason for a documentary difference. Perimeter comparisons require comparable spatial products and dates: see why perimeters disagree, QGIS comparison protocol, versioned evidence timelines, and NBR and burn severity. The MTBS FAQ explains why a satellite burn scar can differ from an operational incident perimeter.

Primary sources: NPS fire history; NPS restoration report (26 September 2012); NPS operational update (8 August 2012); CAL FIRE incident archive; NPS review announcement (30 January 2013); Wildland Fire Lessons Learned Center.

Editorial provenance: documentary audit integrated 6 November 2026. Original cartographic section and embedded visual evidence retained unchanged. These findings are not emergency-response guidance or a legal attribution.