Skip to main content

Directory Structure

Purpose

There is a required directory structure minimum for GIS data and related documents created and used on incidents managed under the Incident Command System (ICS). The standard directory structure is clear and repeatable; it promotes efficient use and storage of GIS data and ensures a smooth transition between GIS Specialists (GISS) by making it easy to locate data or products. This structure may be used both by incident GIS Specialists and by GIS professionals at the home unit of the incident. The intention is to allow some scalability for variation of incident situation, such as in number of GISS​ personnel, hardware use/availability, software used, available data, and even physical location, while still meeting the needs of those with whom the GISS cooperates.

Specifications

  • Folder names must not contain spaces, special characters, or periods.
  • The underscore “_” is the only allowable character for delimiting name elements.
  • Capital letters may be used to make names easier to understand.
    • First letter of proper names (e.g., Jones)
    • First letter to delimit multiple words (e.g., ClearCreek, IntenseHeat), often called CamelCase
    • All letters that stand for something (e.g., GPS)
  • The format for dates is eight digits in year, month, day order (yyyymmdd).
  • The format for time is four digits in a 24-hour format (hhmm).
  • The incident directory structure may be stored in any location, but it is recommended to be as close to the drive root as possible.
  • According to agency needs, files for multiple incidents may be stored under an optional root folder named: \[yyyy]_incidents.

Folder Structure

[yyyy_Incidents] (e.g., 2025_Incidents)

[yyyy_incident_name] (e.g., 2025_Maple)

base_data: base data not created on the incident, does not require daily backup

basemaps: topo maps, tile packages, scanned maps

elevation: digital elevation model and hill shade data

logos: agency logos, typically in non-geospatial raster format

orthoimagery: ortho-corrected imagery

vector: vector data file types

documents: spreadsheets, text documents, unit log, digital photos used on maps

incident_data: data created on or for the incident

[subject_directory]: optional/additional folder e.g., repair

backups: date and time stamped backup incident geodatabases from incident geodatabase for recovery purposes

edit: contains Offline Copy (mobile geodatabase) used for editing to avoid edit locks with Master Incident Geodatabase. If using OneDrive to sync the folder structure, Do Not store the Offline Copy in the folder. It should be stored on your computer C:drive.

exports: date and time stamped incident geospatial data export files

final: final date and time stamped incident geospatial data export files for use by the hosting agency or other local organizations

gps: GIS data from field GPS downloads

ir: spatial data created by IRINs

layer files: layer files storing feature templates or incident symbology

Feature Template Layer File.lyrx (one for each GISS)

modified_base_data: base data edited for the incident, e.g., roads, ownership, and structures

Master Incident Geodatabase: the most current Event geodatabase used as the source for all incident maps. This geodatabase should not be edited

Other Incident Geodatabase: an additional geodatabase that contains incident-specific feature classes, such as Temporary Flight Restrictions (TFRs) and grid indices

Annotation Geodatabase(s): one or more geodatabases for storing annotation

Progression Geodatabase: geodatabase for storing progression data

products: GIS map (e.g., .jpg, .pdf) and other product files produced on the incident

[yyyymmdd]: all map products for the intended date of use, not the date of creation

final: copies of all final map products for the incident

projects: GIS product source documents (e.g., aprx)

backups: backup project files (.aprx) copied from master map document files

Edit Project: aprx, for editing data, one for each GISS. Do not save the Edit Project in a OneDrive synced folder. If using OneDrive to sync incident files, save the Edit Project to a logical place on your local C: drive.

Master Project: aprx, for map production

Restricted: all data and products that contain sensitive, restricted, or controlled-unclassified information

Tools: extensions, tools, or other job aids used on the incident

Event Layer Files: preconfigured .lyrx files for the Event schema

Blank Event GDB: empty file geodatabase in the Event schema

Pro default toolbox: ArcGIS Pro required toolbox

The following is an image of the directory structure on a computer, showing folders and databases:

Click on image to enlarge

Image

References

Responsibilities

The GISS communicates the directory structure to other GIS Specialists, including the hosting unit GIS staff and regional GIS staff. On an incident, the Situation Unit Leader​ (SITL) (or, in the absence of a SITL, the Planning Section Chief (PSC) or Type 3/Type 4 Incident Commander) ensures that individuals working in the Situation Unit follow NWCG standards, including directory structure conventions. NWCG standards represent a national interagency standard and should not be overridden at the incident level.

 

Last Modified / Reviewed:

NWCG Latest Announcements

NEW! Incident Performance and Training Modernization Story Map Now Available

Date: Aug 26, 2025
Questions? Please contact:
National Wildfire Coordinating Group

NWCG is excited to announce the launch of the Incident Performance and Training Modernization (IPTM) Story Map, a new interactive resource that showcases how NWCG is transforming wildland fire training and qualifications through a performance-based system.

Since its launch in 2023, IPTM has made major strides in updating how we manage incident positions:

  • 36 incident positions now have new Incident Position Standards and Next Generation Position Task Books available for field use
  • 6 more incident positions are nearing completion
  • 111 total incident positions are being analyzed through the IPTM initiative

The Story Map guides you through the IPTM process, highlights key accomplishments, and outlines what’s ahead. Whether you are a trainer or a trainee, this tool offers valuable insight into the modernization effort shaping the future of wildland fire training and qualifications.

This effort would not be possible without the contributions of NWCG staff, NWCG committees, and hundreds of subject matter experts across the wildland fire community.

References:

IPTM Story Map

Incident Performance and Training Modernization Webpage

NEW! S-290, Intermediate Wildland Fire Behavior (Blended) Available Now

Date: Aug 15, 2025
Questions? Please contact:
Fire Behavior Subcommittee

NWCG is excited to announce that the S-290, Intermediate Wildland Fire Behavior (Blended) training is now available on the Wildland Fire Learning Portal. S-290 (Blended) training combines online training and instructor-led training components that support individuals working towards any Single Resource Boss or Fire Effects Monitor incident qualifications.

This second course in the series collectively serves to develop fire behavior prediction knowledge and skills, and provides more detailed information on fuels, weather, and topography that affect wildland fire behavior for safety purposes.

Students are required to finish the prerequisite S-190, Introduction to Wildland Fire Behavior, before enrolling in S-290, Intermediate Wildland Fire Behavior (Blended).

References:

S-290, Intermediate Wildland Fire Behavior (Blended)

S-190, Introduction to Wildland Fire Behavior

Wildland Fire Learning Portal

NEW! S-271, Helicopter Crewmember (Blended) Now Available

Date: Aug 14, 2025
Questions? Please contact:
Interagency Helicopter Operations Subcommittee

The S-271, Helicopter Crewmember (Blended) is now available. Developed through the Incident Performance and Training Modernization (IPTM) effort, this training supports individuals working towards Helicopter Crewmember (HECM) incident qualifications. 

S-271, Helicopter Crewmember (Blended) training combines online training and instructor-led training components. This course is designed to provide students with the knowledge and skills necessary to perform the duties of the HECM position, as described in the NWCG Incident Position Standards for Helicopter Crewmember, PMS 350-22.

Any changes to qualification pathways will take effect with the next update of the NWCG Standards for Wildland Fire Position Qualifications, PMS 310-1, scheduled for January 2026.

References:

S-271, Helicopter Crewmember (Blended)

NWCG Helicopter Crewmember (HECM) Position Page

Wildland Fire Learning Portal

Incident Position Standards and Next Generation Position Task Books Now Available for FBAN and LTAN

Date: Aug 13, 2025
Questions? Please contact:
Fire Behavior Subcommittee

NWCG is excited to announce that Incident Position Standards and Next Generation Position Task Books are now available for Fire Behavior Analyst (FBAN) and Long Term Fire Analyst (LTAN).

The Performance Support Packages for these positions were developed as part of the Incident Performance and Training Modernization (IPTM) effort. These resources support trainees, qualified personnel, and evaluators in their respective roles.

Any changes to qualification pathways will take effect with the next update of the NWCG Standards for Wildland Fire Position Qualifications, PMS 310-1, scheduled for January 2026.

References:

NWCG Fire Behavior Analyst Position Page

NWCG Long Term Fire Analyst Page