Experimental Features Preview

Work-in-progress ideas that aren't part of the official DPS score yet. Everything here is transparent, versioned, and clearly separated from the canonical numbers on the rest of the site — so it can be watched, compared, and graded before any of it graduates.

Nothing on this page changes a storm's DPS score. These are candidate signals shown alongside DPS so they can be validated against real outcomes first.

Forecast Rainfall Hazard

Freshwater flooding from rainfall is the single largest cause of death in tropical cyclones — NHC studies attribute roughly half of US TC fatalities to inland flooding, and the share is higher globally. Yet the Destructive Power Score is a wind/surge index and weighs rainfall almost not at all. That's a known gap (see methodology).

The goal: a forecast rainfall-hazard score (0–100) computed live for any active storm, independent of DPS, that answers "how much rain will this storm deliver, and how dangerous is that." The three options below are the ways it could feed back into StormDPS. The rest of the machinery — building-level flood modeling, radar and river-gauge ingestion — already lives in the sister project SurgeDPS; this is about turning that into one comparable number.

Three integration options

Option C1 · prototype

Nudge the existing rain factor

Feed a forecast rain number into the small rainfall term DPS already has (capped at a few percent). Lowest risk, smallest effect. This is what's running live below — shown separately for now rather than folded in, so it can be checked first.

● Live prototype (kinematic v1)
Option C2 · proposed

A full rain component in DPS

Add rainfall as a proper weighted term in the composite score (~15–25%). Directly reflects that rain is the leading killer — but it would change every historical score and needs a full re-audit, and an earlier study showed a naïve version over-credits the wrong storms.

○ Proposed
Option C3 · proposed (recommended)

A separate "Rain Hazard" axis

Keep DPS as the wind/surge destructive-power number and show Rain Hazard as its own 0–100 axis beside it, with an optional combined "Total Threat" roll-up. Can't regress any historical score; the honest way to display a forecast (uncertain) quantity.

○ Proposed

Live prototype C1 · kinematic v1

A first-order estimate from the official forecast track: peak-intensity rain rate × how long the storm lingers over the worst-hit point (a stalling storm dumps days of rain on one place; a fast mover races through). To be replaced by real forecast-rainfall data (WPC QPF), return-period context (NOAA Atlas 14), and predicted flood depth (National Water Model → HAND) from SurgeDPS.

Checking for active storms…

How it scored recent storms

Run retrospectively over the historical forecast window. The point is that rain hazard is independent of wind: Michael was a Category 5 (one of the highest DPS scores on the site) but a fast mover that produced little rain — so it ranks low here, while slow, rain-heavy storms rank high regardless of category.

StormRain hazardWhy
Harvey 2017100Stalled ~5 days over Texas — record rainfall
Florence 2018100Stalled over the Carolinas
Ian 202252Slowed over Florida; major flooding
Katrina 200551Slow Gulf phase (its story was surge, not rain)
Michael 201828Fast-moving Cat 5 — little rain despite extreme wind

These are experimental estimates, not forecasts. When a storm threatens land, each advisory's forecast rain score is logged so it can be graded afterward against observed rainfall (radar totals, river crests, high-water marks) — that comparison decides which method and which integration option is worth keeping.