Reference · built on requestCommons signalHazards & public safety

NIFC WFIGS Wildland Fire Open Data

Current US wildland fire perimeters and incident points from IRWIN, served by NIFC as ArcGIS feature services.

Request accessPricing ↗

About

The Wildland Fire Interagency Geospatial Services (WFIGS) group at the National Interagency Fire Center publishes wildland fire geospatial data under the interagency Wildland Fire Data Program, hosted in the NIFC ArcGIS Online organization. The WFIGS Current Interagency Fire Perimeters service carries perimeters for incidents that IRWIN categorizes as Wildfire or Prescribed Fire and that have not been declared contained, controlled or out. A companion service, WFIGS Current Wildland Fire Incident Locations, carries a point for every incident that meets the same criteria, since not every incident has a perimeter.

Through Fibric, an operator queries both services against your sites, routes and shipment lanes and proposes a hold, a notice or a roster check for a person to approve.

This is a reference listing. It documents what Fibric would read from NIFC WFIGS Wildland Fire Open Data and what it could propose, based on the publisher's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Current fire perimeters as polygons from the WFIGS_Interagency_Perimeters_Current FeatureServer, layer 0 (Perimeters), in WGS 84
  • Perimeter attributes with the poly_ prefix: poly_IncidentName, poly_GISAcres, poly_Acres_AutoCalc, poly_MapMethod, poly_PolygonDateTime, poly_IRWINID and poly_Source
  • IRWIN incident attributes with the attr_ prefix: attr_IncidentSize, attr_PercentContained, attr_FireDiscoveryDateTime, attr_ContainmentDateTime, attr_POOState, attr_POOCounty and attr_GACC
  • Incident points from the WFIGS_Incident_Locations_Current FeatureServer, layer 0 (Incidents), with IrwinID, IncidentName, IncidentTypeCategory, InitialLatitude and InitialLongitude
  • Fire behavior, cause, fuel and management fields such as attr_FireBehaviorGeneral, attr_FireCause, attr_PrimaryFuelModel, attr_TotalIncidentPersonnel and attr_IncidentManagementOrg
  • Query responses as JSON, GeoJSON or PBF through the ArcGIS REST Query operation, with a maxRecordCount of 2000 on each layer

Proposed actions

Read-only. This feed informs operators; it changes nothing.

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Hold shipments that would cross a perimeter

    Intersect the day's lanes with the current perimeters and propose a hold on loads that would pass inside a polygon whose attr_PercentContained is still low.

    With Weather Hold

  • Warn sites near a new incident point

    When an incident point from the locations service appears within your radius of a site, draft a notice with attr_IncidentName, attr_POOCounty and the discovery time for a manager to send.

    With Severe Weather Notice

  • Check the roster at a site inside a perimeter

    When a perimeter covers a site, propose an evacuation roster check with the people scheduled there, and leave a record of who confirmed.

    With Evacuation Roster

  • Pause hot work during a nearby wildfire

    Propose that hot-work permits at sites within your set distance of an active perimeter wait until the incident is declared contained.

    With Hot Work Permit

Requirements

  • A list of your sites, routes or lanes as coordinates or polygons to intersect with perimeters and incident points
  • A poller that re-queries the services, since NIFC states the data refresh every 5 minutes and no push or webhook is documented
  • Paging by OBJECTID or resultOffset for responses above the layer's 2000-record maximum
  • Credit to the sources NIFC lists in the item's access information, led by the DOI Office of Wildland Fire IRWIN service and USDA Forest Service
Authentication
None. The feature services are public ArcGIS REST endpoints; no key, token or registration is documented.

Limits

  • Perimeters are not available for every incident; the locations service is the complete set for the same IRWIN criteria
  • Fall-off rules drop stale records: under 10 acres after 3 days without update, 10 to 100 acres after 8, larger after 14
  • Fires that started earlier than December of the previous calendar year are excluded; older perimeters move to the Year to Date and Full History services
  • NIFC states the data are not legal documents, may change over time and carry no warranty as to accuracy, reliability or completeness

Access and pricing

Reference listing. Public feed access is separate from Fibric integration. If you request this feed, your quote covers the build, usage, and support.

Request NIFC WFIGS Wildland Fire Open Data ↗

Questions and answers

How often does NIFC refresh the current perimeters?
NIFC states the data are refreshed every 5 minutes and that changes in the perimeter source may take up to 15 minutes to display. Fall-off rules that remove stale records are enforced hourly.
Which incidents are in the current perimeters service?
Incidents IRWIN categorizes as Wildfire or Prescribed Fire that have not been declared contained, controlled or out, have no completed fire report, are valid and not quarantined in IRWIN, and whose source polygon is set to Public, Approved and visible.
Do I need a key, and what are the terms?
No key is documented; the services are public ArcGIS REST endpoints. NIFC's item terms say the data are not legal documents, may change over time, are no better than their sources and carry no warranty. Users are responsible for appropriate use.
Ask about NIFC WFIGS Wildland Fire Open Data

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This Commons signal listing is developed, published, and supported by Fibric. It reads public data published by National Interagency Fire Center, Wildland Fire Interagency Geospatial Services (services3.arcgis.com, data-nifc.opendata.arcgis.com). Upstream agencies and projects are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy