Documented fire occurrence
Where and when did an independently documented fire incident occur?
The data that answers it
Ranked by fit · best firstOpenFEMA provides standing annual All Incidents PDR files and identifies the GeoPackage offerings as geocoded versions. The PDR layout identifies each incident by STATE, FDID, INC_DATE, INC_NO, and EXP_NO and supplies incident date and time, incident type, Census tract, full incident-address components, and wildland latitude and longitude. A buyer can therefore search unrelated-target annual files for independently reported fires by location and time, subject to annual lag and voluntary, incomplete reporting.
The public perimeter service supplies wildfire incident identity, discovery date, dated geometry, and update time.
The open address-and-date API returns incident identifiers and dates, establishing documented fire occurrence within San Francisco.
GDACS's standing public event product returns forest-fire event and episode identity, point geometry, affected country, source, event start/end, and modification time for buyer-selected WF events. It supplies indicative global evidence of where and when a documented forest-fire incident occurred, but is not local fire-department ground truth.
Storm Data admits Wildfire for significant forest, grassland, rangeland, and wildland-urban-interface fires and defines beginning/ending times. Bulk event/location records carry identity, linked location, reporting source, and modification/certification dates. Coverage is limited to qualifying significant wildfires and is not a general structural-fire census.
Related questions
Under Fire incident circumstances, Peril event ground truthNeed Documented fire occurrence answered at scale?
We will test these sources on your own records, show you match and fill rates, then handle the contract, security review, and delivery into your stack.