/fires/hotspots, and a pre-computed 0–100 risk score aggregated from those detections is available through /fires/risk. Both endpoints feed the fire and flood exposure factor used in crop aptitude scoring.
Data source
Fire data comes from NASA FIRMS (Fire Information for Resource Management System) via the Area API. FIRMS aggregates active fire detections from multiple satellites and delivers near-real-time (NRT) records typically within 3 hours of the satellite overpass.Satellite sources
Control which satellite’s data is queried with thesource parameter:
Hotspot fields
Each hotspot in the/fires/hotspots response represents a single satellite fire detection pixel:
Risk score formula
The/fires/risk endpoint computes a single score from 0 to 100 using hotspot density, confidence weighting, and average Fire Radiative Power:
- Density component — hotspot count divided by the search area (π × radius²) in km², scaled by 1000, then multiplied by 20.
- High-confidence component — proportion of hotspots rated
highornominalconfidence, multiplied by 30. - FRP component — average FRP in MW divided by 5, capped at 50.
Risk labels
Temporal window
The FIRMS Area API supports a look-back window of 1 to 5 days. Pass thedays parameter to /fires/hotspots to control the window. Values outside the 1–5 range are automatically clamped. The /fires/risk endpoint always uses the maximum 5-day window to ensure the score reflects recent cumulative fire activity.
Caching
Fire hotspot data is cached for 15 minutes. Because fire conditions are dynamic, the cache window is intentionally short. The_cache field in the response reports whether data came from the cache or a fresh FIRMS fetch:
Sample response
The following is a representative response fromGET /fires/risk?lat=-22.0&lon=-60.0&radius_km=150:
/fires/hotspots entry for one detection:
If no
FIRMS_API_KEY environment variable is set, the API returns an empty hotspot list and a risk score of 0. Register for a free NASA Earthdata API key at earthdata.nasa.gov to enable live data.