FIRMS Daily Fire
The Fire Information for Resource Management System (FIRMS) was developed to provide near real-time active fire locations to natural resource managers. This dataset contains the most recent 48 hrs of FIRMS active fire data captured using the Visible Infrared Imaging Radiometer Suite (VIIRS) 375m sensors aboard the joint NASA/NOAA Suomi National Polar-orbiting Partnership (Suomi NPP) and NOAA-20 satellites. Both satellites have an orbit that enables full global coverage every 12 hours. The mid-latitudes (covering the continental U.S. and southern half of Alaska) receive 3-4 looks per day.
Each point represents the centroid of a single ~375m x 375m pixel of satellite imagery for which a measurement
was recorded at a particular time. The
channel brightness temperature properties (
brightness_temp_i5) correspond to
measurements from two of the satellite's five high-resolution image bands (I-bands).
Iggy updates this dataset twice a day, at 1000 and 2200 UTC.
For more information on how this dataset was generated, see https://earthdata.nasa.gov/earth-observation-data/near-real-time/firms/active-fire-data and https://viirsfire.geog.umd.edu/viirs-af-products.
Satellite that captured image
Confidence value (
Indicates daytime fire (true) or nighttime fire (false)
Date and time when image was captured
Actual length of pixel along satellite scan direction, in meters
VIIRS I-4 channel brightness temperature of the fire pixel measured in degrees Kelvin. Note that this measurement can be unreliable in very high-intensity (FRP) fires due to pixel saturation
VIIRS I-5 channel brightness temperature of the fire pixel measured in degrees Kelvin. Note that this measurement can be unreliable in very high-intensity (FRP) fires due to pixel saturation
Actual length of pixel along satellite track direction, in meters
Fire radiative power (FRP) in megawatts. Note that this measurement can be unreliable in very high-intensity fires
API ReferenceView the API Reference
GET when your query carrries the request parameter appended in URL and
POST when the request parameter is in the message body.
Use the query construction wizard below to see how to access this data through Iggy’s API.