Damaging-wind occurrence and severity
Where, when, and at what reported, measured, or modelled severity did non-tornadic damaging wind occur during this event?
The data that answers it
Ranked by fit · best firstHailTrace provides live and archived meteorologist-created wind maps depicting areas impacted by severe wind at 58 MPH or greater and describes the mapped measure as maximum gusts. Maps are produced in real time from radar analysis with ground-truth checks, and the wind archive extends to 2020.
Open files classify Thunderstorm Wind and High Wind events and carry begin/end time and linked locations. MAGNITUDE and MAGNITUDE_TYPE distinguish estimated or measured gust and sustained-wind values; reporting source, modification/certification timestamps, and dated release pin the answer. This is reported/certified evidence, not a radar footprint.
The credentialed Xweather Weather API returns U.S. NWS storm reports since 1950 with report identity, coordinates, time, type/category, reporter, and reported wind speed in mph. This directly establishes damaging-wind location, time, and reported severity; it is human/agency report evidence rather than station measurement or continuous footprint.
For buyer-selected historical times and point lists, lines, or grids worldwide, the subscription API returns 10-metre wind-gust severity over a named one-hour interval in mph with per-value valid time. Response version is an API response version, not a weather-model version.
The OneSite Full report attributes a selected site and emits retained high-wind observations with local date, time, and gust in mph, plus report date and source context. It does not establish continuous geometry, damage, or convective/tropical/tornado taxonomy.
For buyer-selected coordinates or multiple points and date ranges, the Historical Weather API returns hourly reanalysis wind speed and 10 m gust values with timestamps and selectable units. This is Strong gap-filled model-assisted severity evidence, not station observation, human report, radar footprint, or a source-emitted damage determination.
For a date/time-identified event, SPC wind rows provide reported coordinates, time, knot-valued magnitude, and measured/estimated gust/sustained qualifier with dated archive release. They do not establish continuous footprint or building impact.
The standing Basic product lets a buyer select an arbitrary location, wind event type, and search period and documents high-wind history at 50 mph or greater with event date and speed. It does not establish continuous geometry or convective taxonomy.
Tomorrow.io's authenticated Historical Weather API returns one-hour or one-day interval-timestamped 10 m wind speed and brief maximum gust for a buyer-selected point, line, or polygon and ISO event interval. This is Strong model-assisted reanalysis, not a direct damage report or station observation.
With event reports enabled, a buyer can query a U.S. location/date range for reported severe-wind damage. Wind events identify time, coordinates, distance from the requested location, and measured or estimated speed where available. This is Strong, not Primary, because it is a proximity search over secondary reports, severity can be absent, and recent reports can be revised.
For a buyer-selected location and time range, Weather Source returns NOAA-reanalysis hourly 10 m wind speed with RFC3339 timestamps and dated daily maximum 10 m wind speed. This is Useful model-assisted wind evidence, not gust, a damaging-wind classification, a station observation, or a continuous spatial footprint.
Related questions
Under Peril event ground truthNeed Damaging-wind occurrence and severity answered at scale?
We will test these sources on your own records, show you match and fill rates, then handle the contract, security review, and delivery into your stack.