Hail size

Commercial GET /hail API for continuously updated hail history at an arbitrary U.S. or southern-Canada point selected by coordinates or street address. The linked public schema emits location metadata, requested date range and radius, plus hail-occurrence dates and daily maximum hail size. Current first-party pages conflict on archive depth (the schema says history to 2012, the insurance page says seven years, and the retail report page says 2018 to present), so no fixed archive start is asserted.

Directly purchasable PDF hail-history report for any buyer-selected U.S. address or latitude/longitude, with enterprise bulk accounts. It reports event dates and maximum estimated hail size at the location and within one, three and ten miles. The storefront documents a proprietary hail-verification model combining hail-size algorithms, AI, three-dimensional storm models, remote sensing and point-specific weather data, with one-tenth-inch estimates from 0.7 inches to 4.0+ inches. The marketing page says history starts in 2006 while the current storefront says 2009; the later contract-facing value is used provisionally and the conflict remains a reconciliation pinning gap.

Standing commercial browser/mobile subscription providing live and archived meteorologist-created hail, wind, and tornado maps. Public product material says maps show affected areas, hail size/intensity, impacted states/cities/ZIP codes, NOAA reports, and estimated affected structures. No public scalar response dictionary was found, so no Features are authored.

Governmental GRIB2 grid product family integrating multiple radars, observations, lightning, satellite data, and forecast models. It publishes radar-estimated hail, rotation, reflectivity, precipitation-rate, and accumulation products. MRMS is not a ground-report feed: its hail and precipitation values are algorithmic radar/multi-sensor estimates. Public AWS object storage provides historical and real-time files, and NCEP provides real-time HTTP/LDM delivery.

Free governmental U.S. bulk CSV database of NWS-documented significant weather events. Event-detail and location files identify episodes/events, event type, begin/end time, reporting source, hail or wind magnitude and magnitude type, flood cause, and linked event locations. These are reported/certified event records, distinct from radar estimates.

One contracted HailStrike OneSite report family, not separate Sources for Basic, Lite and Full tiers. A buyer can order an unrelated site report directly, and the publisher offers high-volume orders for hundreds or thousands of locations. Public materials and samples emit location-attributed hail dates, estimated hail size, a defined 1–10 Derived Hail Index, storm movement, wind-gust history, NEXRAD station provenance, report issue/version and verification identifiers. Public pages conflict on history depth (five years, ten years, or storms since 2011), so no universal archive start is asserted. The product does not establish tornado or tropical-cyclone outputs.

Standing automated report product, distinct from WeatherGuidance's manually prepared Forensic reports. A buyer selects any address, latitude/longitude or other location, peril (hail or wind) and search period; reports since 2010 are delivered immediately. Hail reports list events of at least 0.75 inch and maximum sizes at the location and one, two, three and five miles. Wind reports document high-wind history at 50 mph or greater. Histories up to ten years have posted prices and longer periods are offered on request.

Commercial credentialed 65-endpoint Weather API. For `/lightning`, standard access returns global real-time pulse records from the past five minutes, with a 100 km maximum radius and up to 1,000 records per query. The separately available Lightning Enterprise add-on preserves the same product boundary and adds client-defined polygon/bounding-box searches, circles up to 500 km, up to 24 hours per request, archive access from 2016 to the present, and up to 50,000 records per request with `skip` paging. The endpoint emits pulse-level observations, not native area-density, seasonality, denominator, climatology, or completeness outputs. Other Weather API endpoints remain inside this Source but outside this audit.