These sources provide the preferred authority for weather, geospatial, platform, API, and standards behavior. Verify time-sensitive platform details against the current source before implementation.
NOAA National Severe Storms Laboratory MRMS ↗ provides the primary scientific and operational overview.
NOAA MRMS in the Registry of Open Data on AWS ↗ documents public bucket access, distribution cadence, notification details, and NOAA Open Data Dissemination terms.
Operational MRMS GRIB2 tables ↗ provide the product catalog authority for MESH, POSH, SHI, accumulated products, units, cadence, and missing values.
NSSL Severe Weather 101: Hail detection ↗ provides plain-language MESH and hail-detection context.
NEXRAD in the Registry of Open Data on AWS ↗ documents current public Level II and Level III access.
NWS API documentation ↗ defines general NWS API integration behavior.
NWS Alerts Web Service ↗ documents watches, warnings, advisories, Common Alerting Protocol data, JSON-LD, redistribution, and polling guidance.
NOAA Storm Prediction Center ↗ provides convective outlooks, watches, mesoscale discussions, and preliminary severe-weather reports.
SPC Convective Outlooks ↗ provides forecast products for severe convective weather.
SPC Preliminary Storm Reports ↗ provides preliminary ground-report context.
NCEI Storm Events Database ↗ provides historical severe-weather reconciliation and the records used for NOAA Storm Data.
Storm Events bulk data ↗ supports historical fixtures, analytics, and backtesting.
TIGER/Line Shapefiles ↗ provide geographic entities and identifiers. The files do not contain demographic data by themselves.
TIGER/Line technical documentation ↗ defines file behavior and geographic concepts.
Cloudflare Workers is the primary execution-platform reference.
Cloudflare D1 documents relational database behavior, limits, migrations, and runtime bindings.
Cloudflare R2 documents object storage for weather objects, reports, evidence, photos, and exports.
Cloudflare Durable Objects documents globally addressable stateful compute with attached strongly consistent storage.
Cloudflare Queues documents asynchronous processing and delivery semantics. StormTrust consumers require idempotent processing.
Cloudflare Workflows documents durable multistep orchestration.
Cloudflare Workers AI documents approved serverless inference workloads.
Workers storage options compares D1, R2, KV, Durable Objects, Queues, and other platform primitives.
Wrangler is the canonical application deployment and Cloudflare developer-tooling reference.
Cloudflare infrastructure as code supports the StormTrust Terraform and Wrangler ownership model.
OpenAPI Specification ↗ provides a language-agnostic description format for HTTP APIs. StormTrust should pin the supported minor version in its API contract.
OpenAPI 3.1.1 ↗ provides one candidate minor-version authority.
JSON Schema ↗ supports schema-driven configuration and payload validation.
RFC 7946: The GeoJSON Format ↗ defines interoperable API geometry where GeoJSON is appropriate.
OASIS CAP 1.2 ↗ defines the alert format relevant to NWS ingestion.
Witt, A., Eilts, M. D., Stumpf, G. J., Johnson, J. T., Mitchell, E. D. W., and Thomas, K. W. authored An Enhanced Hail Detection Algorithm for the WSR-88D in Weather and Forecasting (1998). It provides foundational scientific context for MESH.
Smith, T. M., and collaborators authored Multi-Radar Multi-Sensor Severe Weather and Aviation Products: Initial Operating Capabilities. The NOAA MRMS open-data registry includes it in the MRMS publication set.
The internal product specification defines the responsive release model, weather core, product requirements, sources, security, infrastructure, and implementation priorities.
The HailTrace research covers public presence, media, search, reports, events, partnerships, acquisition, retention, and competitive requirements.
The Hail Recon research covers pricing, programmatic search, monitoring, canvassing, reports, widgets, APIs, and mobile positioning.
Pioneer documentation remains authoritative for framework-level application structure, routing, validation, models, queues, scheduling, providers, compiler behavior, and APIs. StormTrust documentation links to Pioneer rather than duplicating those subjects.