Birch Creek Fire (2013): agency and satellite boundary comparison

Initial cartographic draft · editorial review pending

The two archived records for Birch Creek Fire (2013) give different ways to locate the event. The NIFC feature stores 24,924 GIS acres; the MTBS record stores 24,916 acres. Their outlines share approximately 9,650 hectares, while their combined mapped extent is 10,508 hectares. The question for this draft is: Do similar acreage totals describe the same footprint?

Do similar acreage totals describe the same footprint?

NIFC incident identifier2013-AKUYD-000506
MTBS fire identifierAK6537814429420130703
Ignition-date attribute in MTBS3 July 2013
NIFC GIS_ACRES attribute24,923.5 acres
MTBS ACRES attribute24,916.0 acres
MTBS assessment typeInitial (SS)
NIFC source / map methodAICC / GPS
Birch Creek Fire 2013: 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.8% of the union of the two projected polygons. Approximately 425 hectares lie inside the NIFC outline alone, and 433 hectares lie inside the MTBS outline alone. The NIFC outline spans about 13.0 by 13.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 7.5 acres below the NIFC GIS attribute, a difference of 0.0% 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. Here, close totals conceal a larger spatial mismatch. A location near an edge may be classified differently even when the two acreage figures look interchangeable.

Dates and mapping evidence

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

  • POST_ID: 706701420130916

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.