GEOFUEGO

Harmonization Method & validation

Fire calendar About Code (GitHub) DOI

NASA Space Apps Challenge 2026 · Harmonization of MODIS and VIIRS Hot Spots (CONAE) · Team GeoFuego.com.ar

Argentina's hotspot record is two records: MODIS since 2000 and VIIRS since 2012. VIIRS sees about 3 fire pixels where MODIS sees one, and the ratio changes with region, calendar month, satellite overpass time and the kind of heat source. Glued together, the record shows a false jump in 2012; kept apart, a fire manager cannot compare this season with 2008. This page says how the two were made one, how well it works on years the model never saw, and what it cannot know.

In 2012 the satellite changed. The record should not jump with it.

Spliced as recorded
≈ 2.3×
Argentina: VIIRS 2012–14 over MODIS 2009–11. The jump comes from the change of sensor (≈ 3× in many provinces)
Raw MODIS · harmonized
1.48 · 1.41
2003–2011 mean over 2012–2025 mean: raw MODIS (the same sensor on both sides) · harmonized. The lower activity of the VIIRS era is real; the step is not
Harmonized · naive splice
0.98 · 3.12
burned hectares per hotspot after vs before 2012 (MODIS burned area, MCD64A1): harmonized · naive splice. 1 = continuous

The app shows this panel for any selected area (raw MODIS, raw VIIRS, the splice and the harmonized series with its 80 % range).

1 · The unit: VIIRS-equivalent hotspots on a 0.25° grid

Every value is a count of satellite fire detections expressed in VIIRS-equivalent pixels (375 m), per 0.25° cell (≈ 25 × 25 km; 4 193 cells cover Argentina) and calendar month, November 2000 to today. From 2012 the values are observed by VIIRS S-NPP; before 2012 they are estimated from MODIS. Counts are not a number of fires and not burned area: a fire that burns for several days is counted on every satellite pass.

Why pixel counts and not cell-days. A cell-day unit (one count per cell with fire on a day, whatever the pixel size) removes the pixel-size effect by construction, but it saturates: once a cell has fire on a day, more fire inside it does not count, so the largest seasons are flattened. In Corrientes in January–February 2022, the biggest fire season of the record (45 451 VIIRS-equivalent hotspots in the year, 2.4× the median year), most of the province burned at once; a count of cells with fire cannot say by how much. Pixel-equivalent counts keep that intensity, and the challenge asks which years and months had the highest fire activity. The price is the conversion, which is calibrated and carries an interval.

2 · The factor: per cell × calendar month × satellite set, with shrinkage

3 · Fixed heat sources: a separate class, never subtracted silently

Gas flares, refineries, kilns, sawmill boilers and landfills are hot every month and have a different VIIRS/MODIS ratio from vegetation fire. Three rules put them in their own column (the app shows it as “fixed heat sources”):

  1. Persistent: ≥ 9 months in 12 and ≥ 50 % at night.
  2. Intermittent flares: ≥ 4 months in 12, ≥ 70 % at night, median VIIRS FRP < 3 MW.
  3. An input defect, fixed: the FIRMS MODIS “type” flag changes with the archive version (type 2 is 0.4–1.8 % of detections through 2017 and 2.3–4.9 % from 2018, the same fixed sites). Cells with ≥ 3 MODIS type-2 detections in ≥ 2 years of 2018–2025 are fixed sources in all years for both sensors; their pre-2018 “vegetation” detections have 11 % same-day VIIRS co-location (76 % elsewhere), are 97 % daytime, peak in Dec–Feb: hot bare surfaces, not fire. Filtering on the flag alone would leave those sites inside the vegetation record before 2018 and inside the factor.

Result: 1 628 cells of 0.02°, 3.0 % of all hotspots; 56 % of Neuquén's, 28 % of Santa Cruz's and 18 % of Tierra del Fuego's 2012–2025 detections are in the class (flares). 97 % of VIIRS type-2 detections fall inside it.

4 · After Suomi NPP: the series continues on NOAA-20 and NOAA-21

Suomi NPP, the reference satellite of the harmonized record, stopped delivering data on 2 November 2026 (NASA Earthdata: “Suomi NPP is no longer delivering new data”), and MODIS on Terra and Aqua is scheduled to end in 2027. The next sensor seam is not a future problem: it is this month. The record crosses it with a bridge S-NPP ↔ NOAA-20 / NOAA-21 fitted on paired days of the 2023–2025 standard-processing archives: g = 0.979 (NOAA-20) and 0.951 (NOAA-21). Checked against a different pipeline (FIRMS near-real-time production data): 0.982 for NOAA-20; provincial spread 0.93–1.16 (NOAA-20) and 0.89–0.99 (NOAA-21) where the weight is above 0.9.

In the app, the current year is a preliminary near-real-time layer: per day, the mean over the satellites operating that day, converted to S-NPP-equivalent through the bridge; every month carries the count of days with 3, 2, 1 or 0 satellites, and a month with fewer than three is marked as a lower bound. The same method ties the next sensor to VIIRS when it comes. The app's 2012 panel includes a yearly table with raw counts per satellite, 2023–2025, where the three VIIRS satellites can be compared directly.

5 · Clouds and satellite outages: measured and flagged, not corrected

6 · Validation: every number out of sample

TestResult
Leave-one-year-out 2012–2023, fire-season error, Terra + Aquacountry 3.2 % · province 9.8 % · single cell 30 % (one national factor: 8.9 / 15.0 / 34 %)
Split windows (extrapolation in time): fit 2012–17 → test 2018–23, and the reversecountry predicted / observed 0.965 and 0.992; the ratio drifts ≈ 3 % between halves (≈ 9 % before the type-flag fix)
Ablation ladder, province errorscalar 15.0 → country × month 13.1 → + region 12.8 → + province 12.8 → + cell 9.8 %
Forward test on years never used for the factors nor for the interval2024: predicted / observed 1.044 · 2025: 1.024 (country)
Backward test inside the MODIS era, 2003–2011: Terra-only vs Terra + Aqua reconstructionscountry 0.94–1.04 per year
80 % interval, coverage on 2024 · 2025 (years never used)single cells 80 % / 77 % · random areas of 2–9 / 10–49 / 50–199 cells 81 / 80 / 77 % (2024) and 77 / 74 / 73 % (2025) · provinces 76 % / 73 % · country 10 and 11 of 12 months
Continuity across 2012 vs MODIS burned area (MCD64A1): burned ha per hotspot after / before0.98 harmonized · 3.12 naive splice (not independent: MCD64A1 uses MODIS active fires)
S-NPP ↔ NOAA bridge vs production near-real-time data (different pipeline)0.982 vs 0.979 (NOAA-20)

Tested and not adopted (negative results, kept)

The method and the app were reviewed in five rounds by SI systems (Claude, Anthropic) in isolated sessions; every proposal was measured before being adopted or rejected. The reviews and the audit with every number are in the repository (docs/).

7 · What it cannot know (declared limits)

Version history

Version 1.1.0 (16 November 2026), coverage correction. The NASA FIRMS country archive for Argentina does not include the Islas Malvinas, part of the province of Tierra del Fuego, Antártida e Islas del Atlántico Sur (Ley 23.775; Instituto Geográfico Nacional); FIRMS distributes them in a separate archive. v1.1.0 adds them (43 grid cells already assigned to the province by the IGN polygon; detections in 38) with the frozen v1.0.0 province factor (own weight 0, the rule for any cell without own paired data). No factor, band or validation figure is refitted; every value outside the islands is identical to v1.0.0; national totals change by at most 0.3 %. Tierra del Fuego now counts more cells, so its interval uses the next size class. 28 detections fall on islets the simplified IGN polygon does not cover, the same rule as on the mainland coast. FIRMS publishes no archive for the Islas Georgias del Sur and Sandwich del Sur (only volcanic anomalies would be expected there); the Antártida Argentina lies outside the grid and has no vegetation fires. Version submitted for judging: v1.0.0 (git tag v1.0.0, DOI 10.5281/zenodo.24220107).

8 · Reproduce it

Every number in the app and on this page is computed by the open scripts of the repository from NASA FIRMS data. Three levels, from no network to everything:

  1. From the versioned intermediates, no network, no credentials, about one minute: factors → leave-one-year-out → interval bins → harmonized product, byte for byte (sha256 of the outputs in the README). Validation from the same inputs: npm run validate.
  2. From the raw hotspot archives (≈ 600 MB of FIRMS CSVs + 60 MB of ERA5, published in the Zenodo record): npm run build, about 75 seconds, regenerates everything above.
  3. From the sources: npm run fetch needs a free FIRMS MAP_KEY and a free Copernicus CDS key.
node scripts/04_factors.mjs && node scripts/05_loyo.mjs && node scripts/05c_aoi_error.mjs \
  && node scripts/05g_size_bins.mjs && node scripts/06_harmonize.mjs

Data