Storm Map

Storm Map lets a user select a storm and inspect how its observations and boundaries change over time. The selected storm, time, revision, layers, and geographic scope must travel together into Storm Impact.

Use a stable physical-storm identity for the requested product experience. The timeline contains observations, warning changes, reports, derived boundaries, and revisions associated with that storm. These timeline entries are not new storm identities each time MRMS is polled.

The current operational feed uses mrms-conus, a national feed container. Named benchmark windows support replay, but neither convention establishes an automated individual-storm tracker. Detection, association, split/merge lineage, and user selection are explicit gaps in the journey contract.

Storm History owns finding retained windows and revisions. Storm Replay owns playback, gaps, time interpretation, and correction selection. Map supplies the shared geographic view. A report can open a regional evidence window before physical-storm tracking exists, provided that scope is labeled explicitly.

At the live edge, show the latest complete available revision with its source time and lag. During historical inspection, preserve viewport, layers, selected geography, and revision while updates wait behind Jump to latest. The History and Replay contract defines retention, reconnect, and acceptance; the live revision reference owns current runtime behavior and limits. A map timeline is not a promise of unlimited historical coverage.

Users should not infer critical information from color alone. Every visual layer has a legend, unit, time, source, classification, and confidence when applicable.

StormTrust supports coordinates, points, polygons, multipolygons, parcels, cities, counties, states, ZIP Code Tabulation Areas (ZCTAs), radii, and custom territories.

Current place search can pan to a coordinate or fit a provider bounding box. Production administrative-boundary and parcel datasets are not ingested. Place search, administrative boundaries, and parcels remain separate data contracts; one does not substitute for another.

United States Census Bureau TIGER/Line files may provide public geographic boundaries. TIGER/Line files contain geographic entity codes. They do not contain demographic data by themselves.

StormTrust does not describe a ZCTA as identical to a United States Postal Service delivery ZIP code without qualification.

The map and list represent one query:

Map viewport changes
        ↓
Query boundary changes
        ↓
Result list updates
        ↓
Selected row highlights map feature
        ↓
Selected map feature highlights row

Mobile workflows prioritize large touch targets, current location, limited persistent chrome, resilient field capture, rapid property actions, and clear map-and-list switching.

Release 1 remains a responsive web application rather than a native mobile application.

StormTrust provides equivalent tables, lists, summaries, keyboard navigation, textual severity labels, and non-color distinctions. The map never becomes the only way to reach essential information.