Skip to main content

Directory Structure and File Naming

GeoOps Incident Directory Structure

At the heart of all GISS work is the NWCG Standards for Geospatial Operations (GeoOps), PMS 936, Incident Directory Structure.

The Current Incident Directory Structure download contains all the essential folders, templates, and tools. It should be the default starting point for every incident.

The incident folder should be placed at or as close to the drive root as possible. This reduces clicks necessary to access items within, as well as keeps the file path as short as possible.

Eg C:\2020_Incidents\2020_ExampleFire\

Current Incident Directory Structure (zip file)

Implementing the Incident Directory Structure can be as simple as extracting and saving the YYYY_[template] folder to your computer and rename it for the incident. A GISS can extract and begin populating the directory structure even prior to arriving at the incident. The current Event GDB and Layer files are already present in the template file structure under \tools.>

Configure the Pro Project Template

There are some additional steps required to prepare the Pro Project Template to work within the structure.

Prepare the Incident Directory Structure for use with ArcGIS Pro [Draft] [Move these steps to on-page] - BAD LINK, What does the note mean?

Complexes

When assigned to a Complex, only a single Incident Directory Structure should be used, not separate structures for each fire.

This is the name you would use for the IncidentName attribute.

The complex name and ID should be used in all file names.

Eg. 20180805_1430_Mendocino_Cpx_CAMEU_008674_gps_ranch_flin_llw84.shp sit_river_archE_port_20180819_2130_Mendocino_Cpx_CAMEU_008674_0820day.pdf Is this right?

File Naming

The GeoOps file naming and directory structure are designed to serve as metadata. The file and folder names include incident-specific identification information which facilitates archival and use by the hosting agency, GACCs, etc.

File names must be complete and stand on their own outside of the file structure. File names must be concise, use clear text, and avoid ambiguous terms.

The general format for file naming is: {date and time}_{incident information}_{other information}; however, this will vary depending on the file in question. It is strongly recommended that all GISS use the GeoOps File Namer for consistency and accuracy on all file names.

Job Aid

GeoOps File Namer (.xls spreadsheet)

Using and Customizing the GSTOP File-Namer

 

 

NWCG Latest Announcements

2025 Week of Remembrance

Date: June 27, 2025
Questions?  Please contact:
6 Minutes for Safety Subcommittee

As we approach the 2025 Week of Remembrance (WOR), June 30–July 6, we dedicate this time to reflect on the past incidents from 2015 and honor the fallen through learning. Since its inception in 2014, WOR has honored wildland firefighters who made the ultimate sacrifice while encouraging critical discussions that reinforce lessons learned.

Throughout the week, we encourage thoughtful and generative conversations—whether in briefing rooms or at tailgates—that promote a culture of continuous learning and safety.

References:

2025 Week of Remembrance: Letter to Leadership

Wildland Fire Lessons Learned Center

ETC Equipment Bulletin: 25-003 Flame-Resistant Shirt Survey

Date: June 12, 2025
Questions?  Please contact:
Equipment Technology Committee

The U.S. Forest Service National Technology and Development Program (NTDP) is seeking input on the Forest Service-designed flame-resistant (FR) shirt, currently available through the National Interagency Support Cache system and FedMall.

NTDP is conducting a product review to improve future FR shirt designs. As part of this effort, a short survey is now open for federal employees who have worn any of three recent FR shirt models. Feedback will guide design improvements to better meet the needs of wildland firefighters.

To comply with the Paperwork Reduction Act, responses are limited to federal employees. The survey is open through September 12, 2025. 

References:

NWCG Alerts

ETC Equipment Bulletin: 25-003

NEW! S-130, Firefighter Training (Blended) Now Available

Date: June 10, 2025
If you have questions, please visit our FAQ page. 
If your question is not answered there, you can 
submit your question using our Contact Us form. 
 

The S-130, Firefighter Training (Blended), equips new wildland firefighters with essential skills through a mix of online learning and hands-on training. The course features a required online component and an instructor-led exercise, reinforcing online concepts with practical performance-based training.

The course builds competencies in wildland fire operations, safety, and equipment use, applicable across various operational environments. Both the online component and instructor-led field exercise must be completed to receive a certificate of completion. Students are required to finish the prerequisite S-190, Introduction to Wildland Fire Behavior, before enrolling in S-130, Firefighter Training (Blended).

References:

S-130, Firefighter Training (Blended)

S-190, Introduction to Wildland Fire Behavior

Wildland Fire Learning Portal

EMC Memo 25-001: Interim Rapid Extraction Module (REMS) Training and Qualification Requirements

Date: June 3, 2025
Questions?  Please contact:
Emergency Medical Committee

The Emergency Medical Committee has issued interim guidance for Rapid Extraction Module Support (REMS) teams. Until further notice, Type I and II REMS teams must designate a team leader qualified at Firefighter Type 1 Squad Boss (FFT1) or higher. This temporary change replaces the Single Resource Boss (SRB) requirement, which is currently not feasible due to administrative barriers.

This memorandum does not include any other changes to the NWCG Standards for Rapid Extraction Module Support, PMS 552. This interim change takes effect immediately and will remain in place until further notice.

References:

EMC Memo 25-001: Interim Rapid Extraction Module (REMS) Training and Qualification Requirements

NWCG Standards for Rapid Extraction Module Support, PMS 552