Lone Pine Fire (2016): agency and satellite boundary comparison

Initial cartographic draft · editorial review pending

The two archived records for Lone Pine Fire (2016) give different ways to locate the event. The NIFC feature stores 9,212 GIS acres; the MTBS record stores 9,006 acres. Their outlines share approximately 3,621 hectares, while their combined mapped extent is 3,754 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 identifier2016-IDIFD-000000
MTBS fire identifierID4302711220820160806
Ignition-date attribute in MTBS6 August 2016
NIFC GIS_ACRES attribute9,212.0 acres
MTBS ACRES attribute9,006.0 acres
MTBS assessment typeInitial
NIFC source / map methodBLM / GPS-Flight
Lone Pine Fire 2016: 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 96.5% of the union of the two projected polygons. Approximately 108 hectares lie inside the NIFC outline alone, and 25 hectares lie inside the MTBS outline alone. The NIFC outline spans about 15.2 by 5.3 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 206.0 acres below the NIFC GIS attribute, a difference of 2.2% 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 6 August 2016. Its mapping record links the following scene identifiers:

  • PRE_ID: 803903020160726
  • POST_ID: 803903020160827

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.