__MK__tabaqat · StrataEmergency Management
Hazard & Impact-Zone Analyzer

Draw the zone.
See who's inside.

A hazard footprint appears — flood, fire, surge, quake, hazmat. Draw it, buffer it, import it, or tap a live one, and watch who and what is inside recompute in place: people weighted by social vulnerability, hospitals, schools, responders, road-km and structures — on your own infrastructure, no data leaves the building.

Live demo on real California feeds · any peril · no API keys · runs on Strata or ArcGIS
© 2026 Tabaqat · Built on Strata — sovereign geospatial applications.
The question the EOC asks first

"A zone just appeared — who and what is inside it?"

The Planning Section's Situation Unit has to answer it every operational period, and the mitigation planner has to evidence it: under 44 CFR §201.6, a hazard-mitigation plan's risk assessment must identify the hazards and the assets exposed to them. "Who and what is inside the zone" isn't a nice-to-have — it's a compliance deliverable.

Today that answer is assembled by hand, or exported as a static PDF from a desktop tool, or shipped to a vendor cloud to compute. None of those redraws when the boundary moves.

5axes that matter for this job — and no tool on the market holds all five at once

live & interactive · on-prem / no data egress · open-source · hazard-agnostic · authored by describing it, no GIS analyst required.

We studied the field — beyond Esri

Everyone holds one or two axes. The intersection is empty.

Footprint providers

FEMA NFHL · NOAA SLOSH/surge · WFIGS perimeters · USGS PAGER/ShakeMap. They draw or model the hazard — and do zero exposure math on your assets.

Desktop loss engines

Hazus · InaSAFE · Esri Flood-Impact / Target-Hazard. Expert, US-only, batch — they emit a static report, not a live web recompute.

Clouds that ingest your data

Esri GeoEnrichment · First Street · Jupiter · Moody's RMS. Interactive, but credit-metered, demographics-only, and your study area egresses to a vendor.

Redraw the boundary → exposure recomputes across every widget, for any peril, on your own servers. That's the cell nobody occupies.

The signature loop

The map is a drafting table.

  • Set the footprint four ways: ✎ draw a polygon · ◉ buffer a point to a radius · ⬆ import a GeoJSON · 📡 tap a live flood/fire service and adopt it as the zone.
  • Summarize-within runs — buffer / intersect / point-in-polygon — the instant the boundary is set or moved.
  • Everything recomputes in place: the exposure ledger, the by-sector chart, the exposed-assets table and the exception banner — no reload, no re-export.
1gesture — draw or drag the zone — drives the whole board; the recompute is the product, the zone is just the input

The analysis an ArcGIS Pro analyst runs in a batch tool, running live under your cursor.

The Exposure Ledger

People, facilities, lifelines — counted, the moment the zone moves.

  • One live card per target, grouped by CISA sector: hospitals, schools, shelters, fire/EMS/police, structures, road-km — each recomputing on zone edit.
  • People at risk, equity-weighted: an SVI band shows how much of the exposed population sits in higher-vulnerability tracts, and a gauge reads the pop×SVI composite.
  • The exception banner surfaces the worst first — "6 hospitals & a high-SVI population inside the zone" — click it to isolate on map and table.
EXPOSURE LEDGER · recomputes on zone edit
184,320 people · est.
61% in higher-SVI tracts
✚ Hospitals
6
🏫 Schools
23
⛑ Fire/EMS/Police
14
🛣 Road km
42
Honest by construction

It never fakes a number it can't stand behind.

Estimates are labeled

Population from an arbitrary polygon is an areal estimate, marked as such — wire Census ACS + CDC/ATSDR SVI for a census count. We never dress an estimate as a census figure.

Demo vs live is visible

Live facilities carry a live dot; anything without a machine-readable source carries a DEMO tag. The feed bar shows every source's freshness.

Not a loss engine

This finds what's exposed — not dollar or casualty loss. We cite Hazus and the National Risk Index as vocabulary; we don't pretend to be them.

A board that fakes certainty is worse than no board. Provenance travels with every figure into the Impact PDF.

Coexist, benchmark — never copy

Speaks the standards. Owns the live recompute.

CapabilityThe incumbentsThis analyzer
Define the impacted areaDraw once, in a desktop toolDraw · buffer · import · tap-live, any peril
Exposure math on your assetsBatch, exported to a static PDFLive cross-widget recompute in place
Where it runsVendor cloud / licensed desktopYour servers · no data egress
Equity overlay (SVI)A separate viewerWoven into the people count, live
Cost & licencePer-seat / credit-meteredMIT · keyless open basemaps

We consume their footprints (NFHL · SLOSH · WFIGS · PAGER) and their doctrine (44 CFR · CISA sectors · Community Lifelines · Hazus vocabulary) — and own the part they don't: the live, in-place exposure recompute on your own infrastructure.

Proof, not promises

Running on live, verified California data.

Ledger elementLive source (verified 2026-07-21)
Hospitals · schools · shelters inside the zoneCal OES hosted feature services (CORS-open)
Flood & fire footprints (tap-live)Cal OES 100-yr floodplain · CAL FIRE FIRIS perimeters
Road-km inside the zoneCaltrans State Highway Network — clipped live
National footprints & exposureFEMA NFHL · NWS WWA · USGS · Census ACS · CDC SVI · USA Structures

347 services tagged to the hazard/impact spine from a 2,339-service California inventory, plus 13 external feeds — every endpoint verified before it entered the catalog (500-yr flood is layer /5, HCAI's OID is mixed-case, ACS now needs a key, CGS's real layer is the fault-traces service — we found and fixed each). Re-pointing to your state is configuration, not development.

The packet writes itself

One click. The 44 CFR 201 impact packet.

  • An impact-assessment PDF — people exposed (with the SVI weighting), the summarize-within table by CISA sector, road-km — rendered from the live analysis, for the mitigation plan's vulnerability section.
  • Method & provenance printed on it: which counts are live, which population figure is an estimate, which layer is a labeled demo. Accountability travels with the document.
  • Plus per-county atlas, image export, CSV of exposed assets, and a share deep-link for the EOC.
0minutes re-typing exposure into a report — the packet is a projection of the live board, not a parallel document

Hazard Impact Assessment — Flood · California
184,320 people (est.) · 61% higher-SVI · 6 hospitals · 23 schools · 42 road-km
Method: summarize-within · read-only · EPSG:4326

For EM directors, planners & risk desks

Doctrine-native. Sovereign. Deployable now.

  • Speaks the frameworks: 44 CFR 201, CISA 16 sectors, Community Lifelines, Hazus vocabulary — your staff needs no retraining.
  • Peril-agnostic: one exposure surface eats any footprint — flood, fire, surge, quake, hazmat — instead of a tool per hazard.
  • On your servers, behind your SSO; open basemaps, no per-seat map licences; bilingual EN/AR incl. RTL; wall-mode for the EOC floor.
  • Authored by describing it — the GIS admin builds and re-scopes it by command, no ArcGIS Pro analyst in the loop.
∞perils, one surface — draw any footprint and get the same who/what-is-inside answer, on your own infrastructure

Your planner evidences instead of assembles. Your leadership reads exposure, not guesses. Your mitigation plan starts from live analysis.

See it live

Draw the zone.
Watch the ledger recompute.

Open the demo, buffer a point or sketch a footprint, and watch the exposed people, hospitals, schools and road-km snap into place — then press Impact PDF and hand your planner a packet nobody typed.

tabaqat.net → Solutions → Hazard & Impact-Zone Analyzer info@tabaqat.net
© 2026 Tabaqat · Demo: live Cal OES / CAL FIRE / Caltrans feeds · population is a labeled estimate · read-only · Esri®, FEMA® terms used nominatively.
1 / 11