Event type

NHC's official post-storm best-track data product for Atlantic cyclones from 1851 and Northeast/North Central Pacific cyclones from 1949. Two basin files are delivery partitions of one HURDAT2 product. Records provide native six-hourly and selected asynoptic positions, status, winds, central pressure, wind radii, and landfall/peak identifiers.

Cumulative Alabama subset of National Response Center (NRC) oil/HazMat spill-release incident reports, 1990-2024 = 20,823 incidents. Sourced from NRC because Alabama DEM (the Integration's assigned provider) publishes NO public spill-incident dataset — ADEM's Emergency Response page only gives reporting phone numbers and directs reporters to the NRC. NRC publishes one XLSX per year (nrc.uscg.mil/FOIAFiles/CY<YY>.xlsx); fetch.py reads the INCIDENT_COMMONS sheet, filters LOCATION_STATE='AL', dedups by SEQNOS, converts DMS lat/lon to decimal. ds_street 77.9% (from LOCATION_ADDRESS) / ds_city 91.7% / ds_lat-lon 9.0% → Passable (street-driven). Provider = us_uscg_nrc (federal) — mismatch with al_adem, by necessity.

Arizona subset of the National Response Center (NRC) incident-report archive, 1990-2025 = 6,933 oil/chemical/hazmat release reports. PROVIDER DIVERGENCE: Integration #97 is keyed to az_deq, but Arizona DEQ publishes no comprehensive public spill dataset (Hazardous Material Incident Logbook frozen Nov 2001; legacy.azdeq.gov blocked) and explicitly redirects post-2001 records to the federal NRC. Source owned by us_uscg_nrc and linked to the az_deq Integration. Built from per-year NRC workbooks (nrc.uscg.mil/FOIAFiles/CY<YY>.xlsx), INCIDENT_COMMONS sheet filtered to LOCATION_STATE='AZ'. Single-attribute (SPILLS). Address-described, coordinate-sparse: ds_street 81.8% (LOCATION_ADDRESS), ds_city 97%, ds_state=AZ, ds_lat/lon 3.2% (DMS-assembled) -> Passable on ds_street.

Kentucky subset of the National Response Center (NRC) incident-report archive, 1990-2025 = 16,411 oil/chemical/hazmat release reports. PROVIDER DIVERGENCE: Integration #105 is keyed to ky_dep, but Kentucky EEC publishes no public spill/incident dataset (ER Branch page is contact-only; eSearch exposes only Agency Interest/permits/documents; EEC Data Access Tool lists no spill route; no EEC ArcGIS layer). Source owned by us_uscg_nrc and linked to the ky_dep Integration — same pattern as us_uscg_nrc__incident_reports_az (#97). Built from per-year NRC workbooks (nrc.uscg.mil/FOIAFiles/CY<YY>.xlsx), INCIDENT_COMMONS filtered to LOCATION_STATE='KY'. Single-attribute (SPILLS). Address-described, coordinate-sparse: ds_street 83.7% (LOCATION_ADDRESS), ds_city 97%, ds_state=KY, ds_lat/lon 1.8% (DMS-assembled) -> Passable on ds_street.

Louisiana subset of the federal National Response Center (NRC) oil/chemical/hazmat incident-report archive (USCG). Full archive 1990-2025, filtered to LOCATION_STATE='LA' from the per-year NRC FOIA workbooks (INCIDENT_COMMONS sheet). 144,173 reports. Provider divergence: Integration 106 is keyed to la_deq, but Louisiana DEQ's Single Point of Contact (SPOC) is an intake-only system with no public dataset, so the authoritative source is the federal NRC (us_uscg_nrc). Each record: incident date, type, cause, description, location address/city/county/zip, and (where reported) lat/lon assembled from NRC DMS components. NRC posts initial, unvalidated reports.

Minnesota subset of the U.S. Coast Guard National Response Center (NRC) incident-report archive — petroleum and hazardous-material spill/release reports, 1990–2025 (per-year FOIA workbooks, INCIDENT_COMMONS sheet, filtered to LOCATION_STATE='MN'). 8,633 reports. Federal-substitute source: the Minnesota Pollution Control Agency's own Emergency Response / MERTS spill-incident database is not published for bulk download, so this Source is owned by us_uscg_nrc and linked to the mn_pca Integration #107 (provider divergence). Single-attribute: SPILLS.

Missouri subset of the federal National Response Center (NRC) oil/chemical/hazmat incident-report archive (USCG). Full archive 1990-2025, filtered to LOCATION_STATE='MO' from the per-year NRC FOIA workbooks (INCIDENT_COMMONS sheet). 12,972 reports. Provider divergence: Integration 108 is keyed to mo_dnr, but MO DNR's Environmental Emergency Response tracking systems (MEERTS ≤Oct 2021; MERLIN since Nov 2021) are search-only web interfaces with no bulk download/API, so the authoritative downloadable source is the federal NRC (us_uscg_nrc). Scope caveat: NRC captures the federally-reported subset of MO's EER universe (which also logs state-spill-line-only reports), so this ~13k runs below the ~25k full-state-DB prediction. Each record: incident date, type, cause, description, location address/city/county/zip, and (rarely) lat/lon. NRC posts initial, unvalidated reports.

Cumulative New Jersey subset of National Response Center (NRC) oil/HazMat spill-release incident reports, 1990-2024 = 20,792 incidents. Sourced from NRC because the NJDEP-native spill data (Communications Center / Environmental Action Line in NJEMS DataMiner) is not programmatically sourceable: DataMiner is behind Imperva Advanced Bot Protection AND its record-level report times out/resets on export, with no ArcGIS/Open-Data mirror. NRC publishes one XLSX per year (nrc.uscg.mil/FOIAFiles/CY<YY>.xlsx); fetch.py reads INCIDENT_COMMONS, filters LOCATION_STATE='NJ', dedups by SEQNOS, converts DMS lat/lon to decimal. ds_street 87.8% (from LOCATION_ADDRESS) / ds_city 97.4% / ds_lat-lon 3.4% → Passable (street-driven). Provider = us_uscg_nrc (federal) — substitution for nj_dep, same as AL #96 / AZ #97.

Pennsylvania subset of the National Response Center (NRC) incident-report archive, 1990-2025 = 28,451 oil/chemical/hazmat release reports. PROVIDER DIVERGENCE: Integration #113 is keyed to pa_dep, but PA publishes no broad public hazmat-incident dataset (PEIRS is PEMA/internal; eFACTS is storage-tank-only; no incidents on data.pa.gov; no PASDA incidents layer). Source owned by us_uscg_nrc and linked to the pa_dep Integration — same pattern as AZ #97 / KY #105. Built from per-year NRC workbooks (nrc.uscg.mil/FOIAFiles/CY<YY>.xlsx), INCIDENT_COMMONS filtered to LOCATION_STATE='PA'. Single-attribute (SPILLS). Address-described, coordinate-sparse: ds_street 86.2% (LOCATION_ADDRESS), ds_city 97.8%, ds_state=PA, ds_lat/lon 1.8% (DMS-assembled) -> Passable on ds_street.

South Carolina subset of the federal National Response Center (NRC) oil/chemical/hazmat incident-report archive (USCG). Full archive 1990-2025, filtered to LOCATION_STATE='SC' from the per-year NRC FOIA workbooks (INCIDENT_COMMONS sheet). 12,596 reports. Provider divergence: Integration 114 is keyed to sc_des, but SC DES's Oil & Chemical Emergency Response division takes reports by phone and publishes no public spill dataset (no data.sc.gov dataset; gis.des.sc.gov Emergency_Response folder has only a physiographic map; SC DHEC AGOL org has only aggregated count layers), so the authoritative downloadable source is the federal NRC (us_uscg_nrc). Each record: incident date, type, cause, description, location address/city/county/zip, and (rarely) lat/lon. NRC posts initial, unvalidated reports.

Cumulative Wisconsin subset of National Response Center (NRC) oil/HazMat spill-release incident reports, 1990-2024 = 6,754 incidents. Sourced from NRC because WI DNR's own spill data (BRRTS activity code 04) is not programmatically sourceable: the full archive lives only in the BRRTS bulk zip (apps.dnr.wi.gov, US-geo-locked + binary, unreachable/un-proxyable here), WI DNR publishes no spills GIS layer (entire RR_Sites_Map ArcGIS enumerated — only ERP/LUST activity points), and the open-spills web table is open-only + county-level. NRC publishes one XLSX per year (nrc.uscg.mil/FOIAFiles/CY<YY>.xlsx); fetch.py reads INCIDENT_COMMONS, filters LOCATION_STATE='WI', dedups by SEQNOS, DMS lat/lon to decimal. ds_street 85.5% / ds_city 97.9% / ds_lat-lon 2.8% → Passable. BELOW predicted band (13,500-46,500) by design: NRC = federally-reported subset, not the full BRRTS state archive. Provider = us_uscg_nrc (federal) — substitution for wi_dnr, same as AL #96 / NJ #110 / AZ #97.

Licensed historical crash, hazard and construction incident data delivered through the Roadway Analytics Data Downloader for user-selected study areas and date ranges. Current public documentation lists incident history from September 1, 2016 and exposes identity, severity, closure classification, category/subcategory, first/last local seen times, direction, location, affected road extent and codes. Distinct from the current Incident API and historical congestion/bottleneck analytics.

Versioned global multi-agency tropical-cyclone best-track collection. NCEI merges recent and historical agency tracks and publishes v04r01 as complete and subset CSV, NetCDF, and shapefile downloads. The product includes best and provisional tracks; release/version identity is v04r01 and the landing page supplies its update schedule. It is not a substitute name for native HURDAT2.

Licensed high-definition probabilistic catastrophe model for terrorism risk. It covers the entire United States plus key cities in Belgium, Canada, Denmark, France, Ireland, Italy, Türkiye, and the United Kingdom. Its stochastic event framework models conventional and CBRN attacks, occurrence probability and frequency, temporal/spatial interaction, secondary uncertainty, and property and workers' compensation losses. Risk Modeler/Intelligent Risk Platform are delivery surfaces; model versions and event sets stay within this Source; the deterministic Terrorism Scenario Model remains separate.

Statewide crash-event circumstances for the rolling 2021-2024 window. The public asset supplies no crash identifier and cannot be joined to the Vehicle asset.

Statewide vehicle-in-crash rows for the rolling 2021-2024 window. Year plus case_vehicle_id joins the Individual asset but no field joins the Case asset.

Nationwide, unfiltered archive of U.S. Coast Guard National Response Center (NRC) oil/hazardous-material release-notification reports, CY1990-CY2025 (1,032,643 rows). Same upstream yearly workbooks (nrc.uscg.mil/FOIAFiles/CY<YY>.xlsx, INCIDENT_COMMONS sheet) that back the 12 state-filtered us_uscg_nrc__incident_reports_<state> SPILLS sources, kept here unfiltered by state/territory to serve Integration 331 (ERNS/US). Built after confirming no independent EPA ERNS dataset still exists separately from the NRC's own database (EPA's ERNS was structurally just EPA's copy of NRC-reported notifications; no live Envirofacts table or downloadable archive remains). Known upstream limitation: the CY2017-CY2025 yearly files are each truncated by the NRC server to Jan 1-Sep 9 of that year (not a fetch.py bug) — see the .md for details.

Ongoing global historical database of related tsunami source-event and observed runup-location tables, spanning 2100 BC to the present. It emits event source/time/location, cause, validity, magnitude/intensity, maximum water height and historical effects plus runup observation location, arrival/travel time, measurement type, water height, horizontal inundation and location effects. Reporting is heterogeneous and is neither a completeness claim nor prospective hazard. Pin DOI 10.7289/V5PN93H7, retrieval date/query and API schema.

Free annual full-file release of publicly reported U.S. fire incidents, distributed as zipped relational CSV tables with NFIRS coding documentation.

Standing archive of NHC/CPHC advisory forecast track, cone-of-uncertainty and watches/warnings bundles, with related wind-field files, published as downloadable shapefile/KML packages by storm and advisory. This Source preserves forecast-at-issuance evidence and is distinct from final HURDAT2 post-analysis. Geometry remains in source files and is not flattened into speculative scalar Features.

Annual public-use national probability-sample files for eligible police-reported motor-vehicle traffic crashes. Coordinated crash, vehicle, person, event-sequence, related-factor, weather, vPIC-derived, and auxiliary tables are pinned to the 2024 first final release dated 2026-04-01. CRSS is not a census or arbitrary-event lookup; estimates require its survey-design fields.

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.

Pinned archival U.S. event dataset covering 403 disasters from 1980–2024. Costs are total direct economic losses from insured and uninsured sources, not insured losses. Pin to accession 0209268 v21.21, revised 2025-01-21.

Ongoing global historical database of significant volcanic eruptions from 4360 BC to present. An event qualifies if it caused fatalities, caused moderate damage (about USD 1 million or more), had VEI 6+, generated a tsunami, or was associated with a significant earthquake. HazEL emits event timing, volcano identity/location, VEI, fatality agents, direct eruption effects, combined associated effects, comments, and association IDs. It is not the complete GVP catalogue, a current-alert feed, or a prospective hazard model.

Illinois EPA Office of Emergency Response incident tracker layer, including incident type and status, released material and amount, location, responsible party, responders, dates, and response actions.

Oklahoma Corporation Commission Oil and Gas Conservation Division's statewide ArcGIS feature layer of oil and gas incidents, including complaint, investigation, enforcement, release, environmental-impact, violation, finding, and resolution details.

Separately licensed transaction-specific catastrophe industry-loss index service with a continuous trading-license master agreement and event report sequence. Customer transaction limit is excluded from Features.

EPA's PFAS Analytic Tools republishes National Response Center spill reports through the PAT_Spills ArcGIS layer. This integrated source filters Material_Involved for AFFF or FOAM and emits incident identifiers, dates, quantities, materials, narratives, responsible parties, causes, water impacts, raw and geocoded locations, and relative-location descriptors. Its conformed output adds normalized address and coordinate columns plus an AQUEOUS_FOAM_NRC indicator on every selected row.

EPA Region 1 spreadsheet of leaking underground storage tank releases on Indian land, with facility identity, tribal affiliation, release status, event history, address, coordinates, and land status.

Authenticated commercial interactive lookup for historical natural-catastrophe data. External sign-up is offered; no reusable file, API, batch contract, current public schema, or current revision mechanics were verified.

Versioned county-level U.S. hazard-loss database offered through registered buyer-defined queries and licensed reusable CSV downloads. Property damage is not insured loss; crop indemnity is separately identified.

Connecticut reports of environmental releases received by CT DEEP from January 1996 through June 2022, with incident timing, location, responsible party, substance, quantity, affected media, cause, and response details where reported.

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.

Florida State Watch Office (SWO) oil and hazardous-materials spill/incident archive — the 'Hazardous Materials/Petroleum Spills (SWO Incidents)' feature layers hosted in the FL Division of Emergency Management ArcGIS Online org and published for FL DEP. 22,153 statewide incidents (Hazardous Materials 22,041 + Petroleum Spill 112), full historical archive reported 2011-07 through 2024-08. The two upstream layers (identical schema) are unioned into one source; IncidentType/source_layer distinguish them. Each record carries incident ID/number/type/name, status, county, dates, signed WGS84 coordinates, report URL, and (where available) facility name, address, chemical released, amount, and CERCLA §304 flag.

Standing commercial catastrophe-model product for buyer-supplied policies, portfolios, exposure locations, and attack scenarios. The U.S. component supports deterministic, probabilistic, and geospatial terrorism analysis; conventional-bomb, CBRN, and aircraft-crash scenarios; policy- and portfolio-level loss estimation; nationwide 1 km latitude/longitude modeling with finer ZIP resolution in 15 metropolitan areas; and a 500,000-year stochastic catalog. Model loss metrics and associated uncertainty are delivered through the Touchstone user interface and APIs. Touchstone is a delivery platform within this Source boundary, not a separate Source. Outputs are modeled risk and loss estimates, not current threat intelligence or a prediction that one premises will be attacked.

Statewide downloadable register of reportable oil and hazardous-material releases under Chapter 21E, keyed by Release Tracking Number.

Cumulative West Virginia subset of National Response Center (NRC) oil/HazMat spill & release incident reports, 1990–2025 (CY90–CY25 workbooks) = 10,477 rows. One row per reported incident. Federal substitute for the WV OES/EMD stream — see Notes.

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.