Evacuation Route Planning

Multi-zone evacuation plan creation backed by offline GraphHopper routing and live DuckDB hazard data. Define origin zones, calculate routes to shelters automatically, and detect conflicts with active fire perimeters and flood stage gauges — entirely offline.

Offline-First Evacuation Planning

Tactical AI DuckDB's Evacuation Planner Service wraps the GraphHopper offline routing engine to calculate evacuation routes from population zones to shelters or reception centers. All routing computation happens on-device using pre-loaded OSM road network data — no internet connection required at the moment of crisis.

🚗 Wildfire Evacuation Planning

As a fast-moving wildfire threatens three communities, an emergency manager creates an evacuation plan in ATAK. Each community is added as a zone with the nearest shelter as the destination. Routes are auto-calculated via GraphHopper. The hazard check immediately flags Zone B's route as conflicting with the growing fire perimeter, prompting the planner to route that zone to an alternate shelter.

Multi-Zone Plan Architecture

Evacuation plans consist of one or more zones, each with an origin, destination, route profile, and priority order. Plans are stored in two DuckDB tables: evacuation_plans (plan-level metadata and status) and evacuation_zones (per-zone routes and hazard flags).

Zone Configuration

Automatic Hazard Conflict Detection

Every zone route is automatically checked against live hazard data in DuckDB. If active fire perimeter centroids or flood-stage gauges fall within the route bounding box, the zone is flagged with hazard_conflict = true. Conflicted zones are surfaced prominently in the hazard check report.

Hazard Type Data Source Conflict Threshold
Wildfire Perimeter nifc_fire_perimeters Centroid within 0.1° of route bounding box
Flood Stage Alert usgs_gauge_readings FLOOD or MAJOR_FLOOD gauge within 0.05° of route

Plan Status Lifecycle

Plans move through a DRAFT → ACTIVE → ARCHIVED lifecycle. Only ACTIVE plans are included in NIEM IEPD export packages and ICS 209 evacuation order elements.

AI Agent Tool: evacuation_plan

The full evacuation planning workflow is accessible through natural language via the evacuation_plan agent tool. The AI can create a plan, add all zones with auto-calculated routes, activate it, and perform a hazard check in a single conversational session.

Agent Tool Actions

GraphHopper Offline Routing OSM Road Network DuckDB Spatial Hazard Conflict Detection AI Agent Tool NIEM Export Public Safety
← All Features Next: NIEM/LEXS Data Exchange →