Skip to main content

PMS 936-1

Configure Feature Templates

Configuring the Feature Templates in the Edit Project is a crucial step towards ensuring all data is properly attributed. Many fields can be set to defaults that will populate automatically in most cases, saving time, and improving consistency.

The standardized attributes of the Event Schema serve as Feature-Level Metadata. Wildland fire is rapidly becoming an enterprise environment with distributed data and aggregated services. GIS data must be identifiable down to each feature in such a system so that users know crucial information such as currency and source.

Utilizing the Feature Templates is the best practice for automatically populating attribute with default values for several reasons:

  1. The Event Schema should not be modified, including database defaults.
  2. There may be multiple editors on an incident.
  3. Feature Templates will not transfer with the GDB when sharing or transitioning.

Esri Feature Template Documentation

Feature Templates should be configured in the Edit Project before making any edits.

  1. Configure Feature Templates
    1. Open the Manage Templates pane. This can be done from the Create Features pane or by clicking the dialog box launcher under the Features group on the Edit tab.​

      Select manage templates.
       
    2. Starting with Label Point, select all the features in the list and click Properties. ​
       
      Image
    3. Set the values for IncidentName and IRWINID and any other defaults you wish to apply to your edits.

      In the properties window select Attributes.
       

    4. Repeat steps b-c for all the other layers.

Note: See the GISS Workflow for more information on Obtaining IRWIN IDs for Incidents and Complexes.
 

  1. Once the Feature Templates for each of the Event feature classes are configured, save a layer file as a backup. A layer file will store both the symbology and more importantly, all the incident specific template settings just configured.
    1. Right-click the Event Group - All Layers in the Contents pane and select Save as a Layer File under Sharing.
      Save the file to the incident_data\edit​ folder following the GeoOps naming convention {year}_{incident name}_{unit ID+local incident ID}_{your name}.lyrx
       
      Image
      This layer file can be used to build a new Edit Project should you need to for any reason.

Note: ​In order to utilize all the settings saved in the layer file, add it to the map through the Add Data button. If the data has moved or you wish to apply it to a different feature class, you can repair/change the data source.

 

Page Last Modified / Reviewed:

NWCG Latest Announcements

The Next Generation Position Task Book and Incident Position Standards are now available for Safety Officer, Field (SOFF)

Date: July 26, 2024
Contact: Risk Management Committee 

NWCG is excited to announce that the NWCG Incident Position Standards for Safety Officer, Field, PMS 350-81 and NWCG Position Task Book for Safety Officer, Field (SOFF), PMS 311-81 are now available.

The Safety Officer, Field (SOFF) is responsible for monitoring operations on an incident from a risk management perspective to provide for the welfare of incident resources and the public. The new Incident Position Standards and Next Generation Position Task Book are developed through the Incident Performance and Training Modernization (IPTM) effort.

References:

NWCG Safety Officer, Field (SOFF) Position

NWCG Incident Position Standards for Safety Officer, Field, PMS 350-81

NWCG Position Task Book for Safety Officer, Field (SOFF), PMS 311-81

Updated NWCG Standards for Electronic Documentation (eDoc), PMS 277

Date: July 25, 2024
Contact: Incident Planning Subcommittee 

The Incident Planning Subcommittee has updated the NWCG Standards for Electronic Documentation (eDoc), PMS 277.

The NWCG Standards for Electronic Documentation (eDoc) establishes the standards for collection and retention of records on wildland fires. This July 2024 update will provide incident management teams the most current standards required to maintain incident records and submit them to host units at the close of an incident.

References:

NWCG Standards for Electronic Documentation (eDoc), PMS 277

eDoc Box Directory (zip file)

NWCG Off-Highway Vehicle Typing Standard Request for Comment

Date: July 24, 2024
Contact: Mobile Fire Equipment Subcommittee 

The Mobile Fire Equipment Subcommittee has released Equipment Bulletin 24-002 NWCG Off-Highway Vehicle (OHV) Typing Standard - Request for Comment. This bulletin outlines the proposed NWCG OHV typing standard, as well as the business need for establishing the standard. Comments on the proposed standard will be accepted through August 15th using the comment form linked below.

References:

ETC-EB-2024-02: NWCG Off-Highway Vehicle (OHV) Typing Standard - Request for Comment

NWCG Off-Highway Vehicle (OHV) Typing Standard Comment Form

NWCG Standards for Airtanker Operations, PMS 514 - DRAFT

Date: July 18, 2024
Contact: National Interagency Aviation Committee 

A draft version of the new NWCG Standards for Airtanker Operations, PMS 514, is now available. The NWCG Standards for Airtanker Operations establishes the standards for dispatching, utilizing, and coordinating airtankers on wildland fires. As this is the first edition of these standards, the National Interagency Aviation Committee (NIAC) requests review and input into the 2025 final publication.

Please review and provide feedback by September 1st, 2024 for consideration. Feedback can be provided utilizing the NWCG Publication Review Form.

References:

NWCG Standards for Airtanker Operations, PMS 514 - DRAFT

NWCG Publications Review Form