TEXAS HOMEOWNER FIELD GUIDE

How we use NOAA hail records

Source provenance, county boundaries, event counts, and the limits of what weather data can tell you.

Product and provenance

We imported local copies of NOAA/NCEI Storm Events detail CSVs for 2017–2026 on September 20, 2026. The latest month in the 2026 source file is April. These are archived event records, not preliminary local storm reports or radar estimates. This build does not claim to contain the latest NOAA release.

The original retrieval date is unknown. The prior project’s metadata records an August 6, 2026 build timestamp, which is not independently verified as the download date. Source filenames, SHA-256 hashes, and import date are preserved in the manifest.

Reproducible geography

Filter STATE_FIPS = 48, CZ_TYPE = C, EVENT_TYPE = Hail, and county FIPS 113 (Dallas), 201 (Harris), 453 (Travis), or 029 (Bexar). County context is used because NOAA identifies these records by county. These selections do not reconstruct city or metro boundaries. No radius or coordinate-based address matching is used.

What we count

One row is one hail event detail record. EVENT_ID uniqueness is checked, and duplicate identifiers stop the import for investigation. Distinct observations in the same episode are retained. Counts do not represent unique storms, claims, or damaged homes.

Rows with missing magnitude or reported location remain included and are labeled. The complete source fields are retained in the event downloads, including time basis, narrative, and source filename.

Monthly calculations

Chronological counts group BEGIN_YEARMONTH. The seasonal chart aggregates January through December across the nine complete calendar years 2017–2025, excluding partial 2026. All 112 covered year-months appear in the chronological table. Zero means no matching rows in the supplied source snapshot; months after April 2026 are unavailable.

Highest-count months are observed maxima with ties retained. There is no invented high-hail cutoff. Reporting density and revisions affect comparisons. Missing reports are not proof that hail did not occur.

Dates, limitations, and refresh

Event dates use NOAA’s local recorded date. The display omits times; CSV downloads retain BEGIN_DATE_TIME and CZ_TIMEZONE without conversion. Reported locations and coordinates must not be treated as exact property exposure.

Refresh by obtaining the intended NOAA source files, documenting their actual retrieval dates, and deliberately updating the importer’s coverage contract. Re-run the importer, transformation tests, site build, and route checks. Reconcile revised event IDs and counts before replacing the snapshot. Preserve the prior manifest for audit.

Download provenance and file hashes ↓