FEMA / ICS Wildfire GIS Track

This exercise introduces how GIS supports real incident operations. You will create a workspace representing an active wildfire incident and update it across an operational period using concepts from NIMS (National Incident Management System) and ICS (Incident Command System).

Your role is GIS support to Planning and Operations. Your job is to maintain a clear Common Operating Picture that helps decision makers understand fire spread, resource movement, evacuation areas, and operational structure.

Learning objective
Understand how structured map layers support Incident Command decisions during a changing situation.

Scenario overview

A fast-moving wildfire has been reported in mixed forest terrain. Multiple agencies are responding.

Initial information is incomplete. Conditions are evolving. The Incident Commander requires a workspace that can be updated throughout the operational period.

  • Incident Name: Cedar Ridge Fire
  • Incident Number: CRF-WA-047
  • Operational Period: 0600 – 1800
  • Terrain: forest, light residential interface
  • Weather: dry fuel conditions, moderate wind

Step 1 — Create the incident workspace

Step 1 — Create workspace
Name the workspace: Cedar Ridge Fire
Step 2 — Add description
Include operational period and jurisdiction.
Operational Period
The operational period defines the time window for the current Incident Action Plan (IAP). Maps often change between operational periods.

Step 2 — Add incident facilities

Incident facilities help structure coordination.

  • Incident Command Post (ICP)
  • Staging Area
  • Helispot (optional)
  • Division boundaries
ICS term
Division: geographic subdivision of an incident used to organize resources.

Step 3 — Add current fire perimeter

Add the current fire perimeter as a polygon.

Include timestamp metadata if available.

Why timestamps matter
Incident maps must indicate when information was last updated. Conditions can change quickly.

Step 4 — Add projected spread

Create an additional polygon representing estimated spread direction.

This layer may change frequently.

Planning consideration
Projections help operations anticipate resource needs and evacuation decisions.

Step 5 — Add evacuation areas

Add polygons representing evacuation zones.

  • Evacuation Order
  • Evacuation Warning
Common Operating Picture
Clear evacuation layers help ensure consistent messaging between agencies and the public.

Step 6 — Add routes and strike team movement

Create LineString features representing routes used by strike teams.

  • Access route to Division A
  • Contingency route
  • Dozer line approach
ICS term
Strike Team: set of similar resources operating together under common supervision.

Step 7 — Update the incident

Conditions change during the operational period.

  • Fire perimeter expands east
  • Evacuation zone extended
  • Division boundary adjusted
  • Route becomes unavailable

Update the workspace layers accordingly.

Step 8 — Prepare for briefing

The workspace now supports:

  • Incident Command briefing
  • Planning Section updates
  • Operational awareness
  • Resource coordination

Connection to Atlasemoji concepts

  • Workspace organizes incident data
  • Layers separate operational meaning
  • GeoJSON structures support reuse
  • Manifests allow publishing and sharing

Next steps

Workspace GuideLearn MapsMore guided exercises