The Event Geodatabase (GDB) is the NWCG standard for use on all incidents and contains point, line, and polygon representations for typical fire features. 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 data in 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 (Local Event GDB, Mapping Event GDB, Edit Event GDB, etc). It is important to understand that because "Event" is a schema standard, these are all the same geodatabase. Different names designate the different implementation phases of the Event GDB in various workflows. The Event GDB is implemented in the wildland fire enterprise through the National Incident Feature Service (NIFS).
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 data standard can be extended as necessary in a local GDB, but the standard data elements should not be modified.
- Required data elements in the Wildland Fire Event GDB must be fully populated (including the IRWIN ID) at all times during the incident.
- The required data element FeatureAccess must be properly attributed and controls sharing of the incident data. Unless it is considered sensitive the fire polygon will have FeatureAccess = "Public".
- The Event GDB should 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 on a daily basis or more frequently based on incident activity.
- When an internet connection is available the local Event GDB will be loaded into the NIFS.
NWCG resources such as job aids, checklists, training courses, and how-to videos are available to develop the GISS position and to implement GeoOps. A key resource for a GISS is the NWCG GISS Workflow, PMS 936-1, process. The following sections provide the details of GeoOps.
- Event Point NWCG data standard
- Event Line NWCG data standard
- Event Polygon NWCG data standard
- Blank Event Geodatabase, included in GeoOPS folder template (zip)
- NWCG GISS Workflow, PMS 936-1
The GISS is responsible for following the Event GDB standard and the specifications described in this section. The GISS will load the Event GDB into the NIFS after any edits to the local geodatabase. The GISS will work with the Situation Unit Leader (SITL) to ensure all data in the Event GDB accurately represents the incident.