Skip to content
Developer Docs

Storm intelligence

Last updated View as MarkdownAgent index

Storm intelligence connects eight capabilities within Platform and data. Forecast supports preparation, Alert brings warning context, Radar supplies evidence, Map preserves place and time, Impact prioritizes investigation, and Report hands a reviewed plan to the people who will use it. History makes retained evidence discoverable; Replay lets users inspect it over time.

Storm Forecast → Storm Alert → Storm Radar → Storm Map → Storm Impact → Storm Report
Preparation      Warning       Evidence      Place/time  Priorities     Field handoff

Storm History and Storm Replay support the entire journey. They are customer capabilities and shared foundations for testing, not two extra steps after Report.

These capabilities share application infrastructure and can ship incrementally. Users can enter through a warning, radar window, history entry, replay, map, or report. Shared sources, identities, revisions, and permissions keep those entry points coherent.

First release: a Missouri report

The proposed first release is a Storm Report: a supervisor reviews county weather-exposure priorities and sourced or reviewed canvassing areas, publishes a web report, and sends an authorized canvasser an email link to read on a phone. Start with Missouri → counties → canvassing areas. Neighborhood names require a boundary source; reviewed work areas can serve the pilot when named neighborhood data is unavailable.

This release can precede parcel matching, roof-replacement modeling, full physical-storm tracking, and Forecast ingestion. It still needs accepted county and work-area geometry, a reviewed ranking rule, retained evidence, and working publication and delivery. A bounded History and Replay slice retains and reopens the pilot evidence using the same contracts exercised by tests. The report release contract defines completion. Radar-derived priorities say where to investigate first; they do not certify damage or replacement need.

Explore the capabilities

Storm Forecast

Prepare for potential severe weather beyond the warning window.

Storm Alert

Notify an eligible user and preserve the warning context when they open the alert.

Storm Radar

Turn MRMS observations into attributable evidence with time, units, and limits.

Storm Map

Follow an individual storm through time without losing a historical selection.

Storm Impact

Prioritize county and work-area exposure first, then parcels and roofs as evidence becomes available.

Storm Report

Publish a reviewed briefing and send canvassers a clear starting area.

Storm History

Find retained storm windows, evidence, and reports by place and time.

Storm Replay

Inspect evidence through time, preserve revisions, and reproduce a selected view.

Choose a reader path

Need Page Result
Learn Follow a storm journey A fictional report draft that preserves evidence gaps.
Look up a contract Journey contract and readiness Current code, missing links, required fields, and acceptance checks.
Plan the first release Storm Report release contract Pilot scope, ranking inputs, delivery, and acceptance.
Look up ranking rules Impact ranking contract Geographic membership, aggregation, scoring modes, and unknowns.
Look up history and replay History and Replay contract Shared time, retention, product, and test acceptance.
Understand identity Storm events and revisions Distinguish a warning, observation, physical storm, and revision.
Run existing behavior Inspect a local benchmark Exercise implemented MRMS ingestion and replay.
Prepare a change Review a product change A bounded implementation task with evidence and acceptance.

Shared data dependencies

Datasets and source contracts owns source availability. Missouri parcel research prepares identities and later parcel evidence; it does not supply the accepted county or work-area polygons required for the first report. The live revision reference owns current publication, history, and retention behavior.

Developer Docs