Wildfire perimeter at the event time
Was the event location inside a documented wildfire perimeter, and when was that perimeter observed or published?
The data that answers it
Ranked by fit · best firstNIFC's public WFIGS ArcGIS layer publishes incident perimeter polygons with incident name/key fields, fire discovery, containment and control times, polygon/create/current dates, and supports point-in-polygon spatial queries. These fields pin incident and perimeter timing, but the citation does not define official-versus-indicative status semantics, source geometry lineage, retrieval time, or a stable geometry/product version.
For a buyer-selected forest-fire event and episode, GDACS returns a GWIS-sourced MultiPolygon labelled `Affected Area`, with polygon date, event/episode and source identity, event interval, and modification time. It can determine whether a location lay within the mapped affected area, but is indicative automatic evidence rather than an official incident-command perimeter.
The pay-per-result Actor accepts buyer-supplied coordinates and screens them against the current NIFC WFIGS perimeter layer. Its guarded output supplies `in_perimeter`, WFIGS `fire_unique_id`, `fire_perimeter_date`, perimeter-versus-incident-point source type, upstream `data_last_updated`, `checked_at`, source URL, and per-source completeness status, so a current-event answer can be pinned to incident, mapped-perimeter time, provenance, and query time. It does not query a historical perimeter as of a buyer-selected event time, exposes no stable geometry version, warns that perimeters may lag spread by hours, and is not an official evacuation source.
Related questions
Under Peril event ground truthNeed Wildfire perimeter at the event time 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.