- Forecast horizon
- 3 h
- Time step and refresh
- 10 min
- Grid spacing
- 4 km
- Inputs: NOAA MRMS, GOES
- Radar + satellite
Four ways to receive the forecast
Each delivery carries the same forecast: rain rate every 10 minutes, three hours ahead, on a 4 km grid.
- 01
Site series
For a venue, an airport, or a work site: rain rate at each 10-minute step, and when rain starts and stops.
JSON · one call per site GET /nowcast/sites/{site_id} { "issued": "2026-09-24T20:30Z", "step_min": 10, "horizon_min": 180, "rain_mm_h": [0.0, 0.4, 2.1, 6.3, …], "periods": [ { "start": "20:50Z", "end": "21:40Z", "peak_mm_h": 6.3 } ] } - 02
Grid
The forecast field for a bounding box or the whole domain, one frame per step, for your own models and dashboards.
JSON, NetCDF, or GeoTIFF GET /nowcast/grid?bbox=-88.2,41.6,-87.5,42.1&format=netcdf rain_rate(time: 18, y, x) mm/h grid: 4 km step: 10 min - 03
Map tiles
A rain overlay for the map your team already runs, one layer per lead time.
XYZ raster tiles /nowcast/tiles/{issued}/{lead_min}/{z}/{x}/{y}.png lead_min: 10, 20, … 180 - 04
Threshold alert
A push to your system when rain at a site crosses a rate you set, or when a start or stop enters the horizon.
Webhook POST https://your-system.example/rain { "site_id": "ramp-north", "event": "threshold_crossed", "at": "21:10Z", "threshold_mm_h": 4, "rate_mm_h": 6.3, "issued": "2026-09-24T20:30Z" }
We implement this delivery for your sites when you engage. If the envelope has to match a system you already run, say so on the call.
Put the forecast in your system.
Tell us the decision, the sites, and where the forecast has to land.