Skip to main content

Event Geodatabase

NWCG Committee Realignment Website Updates: Content will continue to be updated over the coming days as we work through final reviews and adjustments, and all publications and products are currently under revision.

Purpose

“Event” is the NWCG GIS operational data standard for use on all incidents and contains point, line, and polygon representations for typical fire features. Commonly referred to as ‘The Event GDB,’ it was approved by the NWCG's Geospatial Subcommittee in the spring of 2017 along with the NWCG Wildland Fire Event Point, Event Line, and Event Polygon Data Standards. The Event GDB is used in all phases of a wildfire incident including initial attack, extended fire management activities, and rehabilitation and repair.

A standardized incident geodatabase schema is critical to the interoperability and efficiency of personnel and tools on a wildland fire incident. A consistent schema permits the development of tools and workflows to speed data management and mapping. A standard schema also allows incident data to be aggregated at the Geographic Area Coordination Center (GACC) and national level to provide a picture of the wildland fire situation.

The Event GDB is referenced several ways based on application (Offline Copy, Master Incident GDB, etc.). It is important to understand that because "Event" is a schema standard, the data in each of these is interchangeable. Different names designate the different implementation phases of the Event GDB in various workflows. The Event GDB is primarily implemented in the wildland fire enterprise environment through the National Incident Feature Service (NIFS).

Specifications

The Geographic Information System Specialist (GISS)​ will adhere to the following:

  • GISS and any other incident personnel working with incident spatial information must use the NWCG Approved Wildland Fire Event GDB standard for data storage and exchange.
  • The Event schema should not be modified.
  • Required data elements in the Wildland Fire Event GDB must be fully populated during the incident. The Event attributes serve as feature-level metadata for each record.
  • The Event GDB will be stored in the correct location in the Incident Directory Structure and follow File Naming conventions for GDB name.
  • The Event GDB will be backed up to provide a snapshot of the incident data daily or more frequently based on incident activity.
  • The required data elements FeatureAccess, FeatureStatus, and IsVisible are used by external systems to control the sharing of the incident data. Unless considered sensitive, the fire polygon will have FeatureAccess = Public, FeaturesStatus = Approved, and IsVisible = Yes (these are the default values for Event Polygon).
  • PolygonDateTime, LineDateTime, and PointDateTime data elements must be entered in UTC in ArcGIS Pro.

References

Responsibilities

The GISS is responsible for following the Event GDB standard and the specifications described in this section of GeoOps. The GISS will sync Event data to the NIFS after editing the Offline Copy. The GISS will work with the Situation Unit Leader (SITL) to ensure all data in the Event GDB accurately represents the incident.

 

Last Modified / Reviewed:

NWCG Latest Announcements

LMC Equipment Bulletin 26-001: Aquatic Invasive Species – Seasonal Reminder for Mussels

Date:  July 30, 2026
Questions? 
Please contact: Equipment and Technology Subcommittee

The Logistics and Equipment Management Committee (LMC) issued Equipment Bulletin 26-001: Aquatic Invasive Species - Seasonal Reminder for Mussels, reminding the wildland fire community that aquatic mussels continue to be a problem. Mussels rapidly colonize hard and soft surfaces, including aquatic plants and fire equipment, clogging pipes, fouling motors, disrupting water systems, and impacting native species.

To help prevent their spread, fire personnel must follow the decontamination procedures outlined in the NWCG Guide to Preventing Aquatic Invasive Species Transport by Wildland Fire Operations, PMS 444. Additionally, report any sightings immediately to your Lead Resource Advisor and include clear, close-up photos (with a pen or your hand for size reference) and location details.”

Read the complete LMC Equipment Bulletin 26-001, to learn more. 

References:

NWCG Alerts

LMC Equipment Bulletin 26-001: Aquatic Invasive Species - Seasonal Reminder for Mussels

NWCG Guide to Preventing Aquatic Invasive Species Transport by Wildland Fire Operations, PMS 444

Intermediate Faller (FAL2) Position Task Book Update

Date:  July 24, 2026
Questions? 
Please contact: Tree Felling Subcommittee

NWCG Operations Management Committee (OMC) has issued an update to the NWCG Position Task Book for Intermediate Faller (FAL2), PMS 311-91. To ensure clarity for both trainees and evaluators, the updated FAL2 Position Task Book (PTB) explicitly states who is authorized to sign off on your tasks:

“Evaluators must be qualified as a FAL2, or an Advanced Faller (FAL1).”

If you are currently working out of a previously published version of the FAL2 PTB, you do not need to restart. However, OMC highly encourages you to take the following step to prevent any confusion in the field:

  • Print and replace the updated evaluator information page (page 2) in your current physical PTB.

References:

Intermediate Faller (FAL2) Position Page

RMC Memo 26-01: Transition Plan for Implementing Updates to Intermediate Faller (FAL2) Position Qualifications

NWCG Position Task Book for Intermediate Faller (FAL2), PMS 311-91

Equipment Advisory 26-001: Potential Front Driveline Joint Failure on 2018 and Earlier Ram Pickups

Date:  July 10, 2026
Questions? 
Please contact: Equipment and Technology Subcommittee

The Logistics/Equipment Management Committee (LMC) has released Equipment Advisory 26-001: Potential Front Driveline Joint Failure on 2018 and Earlier Ram Pickups. This advisory highlights multiple U.S. Forest Service regions reporting front driveline joint failure incidents.

This advisory recommends firefighters and fire managers to: 

  • Follow all Ram-issued inspection, maintenance, and service guidance for front driveline joints. 
  • Consider installing a driveline loop. 
  • Coordinate with fleet managers and service providers to determine the most appropriate driveline loop kit for each pickup.

For further details, please refer to the complete advisory.

References:

Equipment Advisory 26-001: Potential Front Driveline Joint Failure on 2018 and Earlier Ram Pickups

Technical Service Bulletin: 03-002-21

NEW! NWCG Standard Operating Procedures, PMS 900

Date:  July 9, 2026
Questions? 
Please contact: NWCG Staff

NWCG is excited to announce the publication of the NWCG Standard Operating Procedures, PMS 900.

The new publication establishes general, consistent, and uniform standards for conducting business with the National Wildfire Coordinating Group.

References:

NWCG Standard Operating Procedures, PMS 900