Skip to main content

Repair Event Layer Files


For a refresher on layer files, please see the GIS Concepts Review document.

Repair Event Layers in the Edit Project

Use the Event layers in the edit map instead of the GISS Edit service directly. While the symbols are now the same, several other settings are saved in the layer files that are not available directly from the service, including caching, advanced labeling, and symbol display order. Critically, each layer is set to not cache any data locally in ArcGIS Pro to ensure the data displayed is always up to date.

  1. Repair the path of the Event Group - All Layers  in the Contents pane of the edit map to the newly created Offline Copy in the \incident_data\edit folder (e.g. GISSEdit_NIFS_2025_A74A6C…).
  2. Remove the GISS Edit Service (National Incident Feature Service 2025) group to avoid confusion. 

    Label point and databases main

  3. Save the Edit Project. Your Contents pane should resemble the following: 

    Re-edit the project contents pane

     

The Event Layer Files that are added to the provided map view of the Pro Project Template aprx can be found in the \tools folder in the GeoOps Incident Directory Structure.

Nearly every map is going to start with the Event Group All Layers YYYY.lyrx file, the primary two types being the Edit Project and Master Projects. The key difference between these two is the database to which the layer file path is repaired.

It is very important to keep these two separate because incident maps should never be created using the Offline Copy and data edits should never be made outside of the Edit Project.

Event Layer File Template Implementation Diagram

Flow chart showing the use of the template layer file used in both the Edit Project and Master Map Projects.

Keeping the Edit Project separate from Master Projects is a crucial component of the GISS Workflow and proper layer file management is essential to this.

A layer file stores symbology, labeling, and Feature Templates and can be used to quickly create projects. Layer files also store files paths and can easily add the wrong data to a project resulting in inaccurate products or wasted time editing the wrong database.

Following best practices will avoid any mishaps, but it is always important to be aware of what data you are working with and how all your databases, maps, projects, local copies, and layer files all fit together.

Event Layer Files in the \tools folder

  • Event Group All Layers 202X.lyrx – All NIFS layers with configured Event Point label classes that can be easily converted to annotation.
  • Event Group BAM Large Symbols 202X.lyrx – Oversized Point and Line symbols use in Briefing Area Map (BAM). Increase or decrease the size as necessary.
  • Event Group IR 202X.lyrx – Print symbology for the IR feature classes.
  • Event Group Repair Status 202X.lyrx – Group layer with Accountable Property, Event Point, and Event Line symbolized based on the RepairStatus field. This layer file should be used in conjunction with the Event Group All 2025 layer file to provide a Repair Status “halo” for features.
  • Event Group Simplified Web Symbols 202X.lyrx – Simplified symbology.
  • Multipage Label Lines 202X.lyrx – ‘Invisible’ Lines with assignment labels (e.g. Div, Branch) used in multipage map projects. Repair to the MultipageLabelLine feature class in the other_incident_data.gdb.
  • Structure Triage 202X.lyrx –Structure Triage symbology based on the guidelines in the Incident Response Pocket Guide page 14+15. Alternate Triage categories for California’s FIRESCOPE are included in the data but not provided as a layer file.

 

Last Modified / Reviewed:

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