Skip to main content

PMS 936-1

NWCG Geographic Information System Specialist (GISS) Workflow, PMS 936-1

The NWCG Geographic Information System Specialist (GISS) Workflow, PMS 936-1, is supplemental to the NWCG Standards for Geospatial Operations (GeoOps), PMS 936.

The NWCG GISS Workflow, PMS 936-1, is developed and maintained by the NWCG Geospatial Subcommittee (GSC) under the direction of the Data Management Committee (DMC), an entity of NWCG. While previous versions may contain current or useful information, they are obsolete. The user of this information is responsible for confirming they have the most up-to-date version. NWCG is the sole source for the publication.

Comments, questions, and recommendations shall be submitted to the appropriate agency member assigned to the GSC. View the complete roster.

NWCG GISS Workflow Diagram

Image
GIS Workflow, explained below

Figure 1. GIS Workflow
(click image to open larger)

The NWCG GISS Workflow provides three levels of detail, which are scalable to the user. The graphic shows the basic order of operations, followed by an outline of the major steps and essential process details, and finally, the links in the outline and the navigation pane lead the user to detailed process instructions and documentation (see Figure 1).

Definitions:

Offline Copy

The Mobile Geodatabase (GDB) is created when the user runs the Download Map function. This is a copy of the National Incident Feature Services (NIFS) data that can be edited and synchronized. Sync works both ways and an Offline Copy can be synced multiple times; the Offline Copy should always be synchronized before an edit session (to pull down new data) and after an edit session (to push up new edits).

Note that this is not the same GDB used for map creation.

Master Incident GDB

The most current GDB named per GeoOps standards ({year}_{incident name}_{unit ID + local incident ID}) and placed in the incident_data folder to be used as the source for all incident maps. This GDB should not be edited.

Pro Project Template

The ArcGIS Pro project (.aprx) file included in the GeoOps Folder structure under projects. ‘Save As’ should be used on this template to create the Edit Project and all Master Projects. Implementation instructions can be found in the tools folder in the Prepare and Configure the Event GDB document.

Edit Project

The ArcGIS Pro project (.aprx) used for creating and editing the Offline Copy. Editing should not be done in any project used for map creation. This project stores the configured Feature Templates.

Master Project

The current ArcGIS Pro project (.aprx) for each map project. Master Projects can contain multiple layouts for the same map view, but each should be for only a single project type (e.g., All division maps in one project or multiple sizes of the PIO map in one project). Daily backups should be made of each Master Project.

Data Preparation – Do Once

  1. Gather incident information – Name, Unique Fire ID (Unit ID + Local Incident Number), IRWINID, etc.
  2. Implement the GeoOps Incident Directory Structure. Download the zip folder, extract the YYYY_Template folder, and rename for incident.
  3. Populate the base_data folder with data relevant to the fire area.
  4. Configure the Pro Project Template.
    1. Rename project databases.
    2. Rename map view with incident name and set local projected coordinate system.
    3. Repair path of Dynamic Text Update table to other_incident_gdb.
  5. Save as on the Pro Project Template to create the Edit Project. Name per GeoOps standards {map type} = “edit”.
    1. Ensure you are signed into the NIFC AGOL as your active portal.
    2. Optionally, add a vector tile layer basemap to map.
    3. Create an Offline Copy.
      1. Add the National Incident Feature Service (NIFS).
      2. Zoom to incident area of interest (AOI).
      3. Select Download Map to create an Offline Copy. Optionally, download a vtpk of the vector tile layer simultaneously.
    4. Repair path of Event Layers to Offline Copy and remove duplicate service from map.
    5. Configure Feature Templates.
    6. Save a group layer file for Event Features in the incident_data/edit folder and include your name.
  6. Create and Share Web Maps for mobile data collection and information sharing.

Edit Incident Data – Repeat as Necessary

  1. Edit the NIFS (Offline Copy).
    1. Secure information through the Situation Unit Leader (SITL) to create/edit incident data.
    2. Process/Convert/Import incoming data and store per GeoOps file structure.
    3. Open the Edit Project and sync Offline Copy. Edit incident data (only edit your incident).
      1. Edit the EventPolygon first. Calculate Geometries and populate attributes.
      2. Edit the PerimeterLine features to match the Wildfire Daily Fire Perimeter. Calculate Geometries and populate attributes.
      3. Edit the EventLine, EventPoint, and Accountable Property features in a logical order. Calculate Geometries and populate attributes.
      4. Edit the LabelPoint features to create assignment labels, if needed.
    4. Manage suppression repair data.
    5. Update Metadata in the DynamicTextUpdate table.
    6. Save data edits, sync Offline Copy, and save Edit Project.
    7. Export the latest fire perimeter to a progression GDB for use in progression maps.
    8. Calculate containment, ownership acres, etc.

Update the Master Incident GDB – Done After Every Edit Cycle

  1. Back up Offline Copy.
    1. Determine the path and name of the Offline Copy.
    2. Convert the Offline Copy (mobile GDB) to a backup GDB (file GDB).  Save into the daily backup folder under incident_data\backups and name following GeoOps.
  2. Create or Replace Master Incident GDB.
    1. If Master Incident GDB already exists, delete from \incident_data.
    2. Copy the backup GDB to the \incident data folder and rename it following GeoOps to become the new Master Incident GDB.

Create Incident Maps and Digital Products – Repeat as Necessary

  1. Create or Update Incident Map(s).
    1. Use an existing Master Project or open the Pro Project Template and Save As to create a new Master Project per the GeoOps.
    2. Repair path of Event layer file(s) to point to the Master Incident GDB.
    3. Add base maps and ancillary datasets to map.
    4. Create a layout or make a copy of a provided layout template for the desired map product.
    5. Apply definition queries to display only the Event Features appropriate for the intended map audience.
    6. Use dynamic labeling where applicable and create annotation as necessary.
    7. Ensure all essential map elements are present and correct (STANDL SGD).
    8. Export Geospatial PDF map per GeoOps standards.
  2. Create and share public web products.

Back Up and Sharing – Repeat as Necessary

  1. Back up incident data.
  2. Share digital map products by posting to the NIFC FTP site or designated SharePoint folder nightly. Use QR codes if desired.

**** If additional NIFS edits are needed the Master Incident GDB should not be edited. Only the Offline Copy should be edited.****

The National Wildfire Coordinating Group (NWCG) provides national leadership to enable interoperable wildland fire operations among federal, state, Tribal, territorial, and local partners. NWCG operations standards are interagency by design; they are developed with the intent of universal adoption by the member agencies. However, the decision to adopt and utilize them is made independently by the individual member agencies and communicated through their respective directives systems.

 

Last Modified / Reviewed:

Print PDF

NWCG Latest Announcements

Updated NWCG Standards for Fire Unmanned Aircraft Systems Operations, PMS 515

Date: April 23, 2025
Questions?  Please contact:
Interagency Fire Unmanned Aircraft Systems Subcommittee

The NWCG Standards for Fire Unmanned Aircraft Systems Operations, PMS 515 standardizes processes and procedures for the interagency use of Unmanned Aircraft Systems (UAS), including pilot inspections and approvals. This updated publication provides the aviation community with standards to ensure UAS are used safely, effectively, and efficiently in support of fire management goals and objectives.

References:

NWCG Standards for Fire Unmanned Aircraft Systems Operations, PMS 515

NWCG National Interagency Aviation Committee

ETC Bulletin 25-001: Retrofitted Hot/Cold Beverage Kits - 2025 Field Season

Date: April 16, 2025
Questions?  Please contact:
Equipment Technology Committee

Due to spout failures and the associated risk of burn injuries, manufacturers have retrofitted the Hot/Cold Beverage Kits using a heat-shrinking band to secure the black spout at the insertion site. The updated kits feature a fluorescent label on each full kit assembly for easy identification. Catering units are encouraged to confirm the clear heat-shrinking bands are intact around each spout before filling.

ETC Bulletin 24-001 regarding Hot/Cold Beverage Kits has been archived and replaced by ETC Bulletin 25-001 for the 2025 season.

References:

NWCG Alerts

ETC-EB-25-001 Retrofitted Hot/Cold Beverage Kits

NWCG Standards for Wildland Fire Chainsaw Operations, PMS 212, and Next Generation Position Task Book for Basic Faller Are Now Available

Date: April 14, 2025
Questions?  Please contact:
Hazard Tree and Tree Felling Subcommittee

The updated NWCG Standards for Wildland Fire Chainsaw Operations, PMS 212, and NWCG Position Task Book for Basic Faller (FAL3), PMS 311-19 are now available.

The NWCG Standards for Wildland Fire Chainsaw Operations, PMS 212 includes position standards designed to be used in conjunction with the Next Generation Position Task Book (Next Gen PTB). The Next Gen PTB for Basic Faller (FAL3) includes an evaluation guide with suggested rating elements to consider when assessing trainees.

References:

NWCG Standards For Wildland Fire Chainsaw Operations, PMS 212

NWCG Position Task Book for Basic Faller (FAL3), PMS 311-119

NWCG Basic Faller (FAL3)

RMC Memo 25-01: Summary of Updates to Safety Officer Positions

Date: April 9, 2025
Questions?  Please contact:
RMC Member Eric Fransted

The Risk Management Committee (RMC) serves as the position steward for all Safety Officer incident positions and continues to improve position standards, training, and naming conventions. The implementation of Complex Incident Management (CIM) required changes to position titles. RMC collaborated with the NWCG Incident Position Standards Committee (IPSC) to propose and implement these updates. 

References:

RMC Memo 25-01: Summary of Updates to Safety Officer Positions 

NWCG Position Catalog