Event start datetime

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.

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.

Annual final national files for every qualifying U.S. fatal motor-vehicle traffic crash, with coordinated crash, vehicle, person, ordered event, circumstance, decoded-vehicle, imputation, and auxiliary tables. Inventory is pinned to 2024 Final and does not claim nonfatal or preliminary coverage.

A separately named Version 2 station summary product publishing hourly, daily, and monthly observations in station-year CSV files and monthly summary forms. It is derived from NCEI station datasets but has its own documented 125-column CSV schema, metric bulk files, U.S.-focused station coverage with limited U.S. Air Force locations abroad, and standing per-station/year plus all-station archive access.

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.

Historical reanalysis API at archive-api.open-meteo.com/v1/archive for arbitrary WGS84 points, multiple coordinates, and ISO dates. It publishes gap-filled, model-assisted—not station-only—hourly weather. Available models include global ERA5 from 1940, ERA5-Land from 1950, and ECMWF IFS from 2017. Paid Professional-or-higher access uses the same syntax on reserved customer endpoints and grants commercial use.

Annual commercial subscription with standing portal access. One boundary contains complementary CORE exposure/loss data and EXTENDED country-level loss data; public releases and the portal are not separate Sources.

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.

Virginia DEQ Pollution Response Program (PREP) incident reports — oil/hazmat spills, sewage discharges, fish kills, open burning, etc. State-native source matching the Chubb PREP description (provider va_deq, no divergence). VA DEQ Environmental Data Hub public ArcGIS layer 'PReP Reports' (apps.deq.virginia.gov/arcgis/.../public/EDMA/MapServer/175). 31,379 point records (within predicted 25000 ±55% = 11250-38750). Single-attribute (SPILLS). Strong fill on BOTH address and coordinates: ds_street 96.7% (PRP_SITE_ADDRESS1), ds_city 97.4%, ds_state 100% (PRP_SITE_STATE, ~99.99% VA), ds_zip 75.2%, ds_lat/lon 100% (point geometry) -> Fit.

Florida DEP's 'ERIC Waste Cleanup' master cleanup-site database (Division of Waste Management, CLEANUP_SP MapServer layer 8), filtered to PROGRAM_TYPE='RESPONSPARTY' (Responsible Party Cleanup) -- sites where a legally responsible party, not the state, is conducting or funding cleanup. Covers 8,192 open, closed, on-hold, and unconditionally-closed sites statewide with address, county, discharge date, and WGS84 point coordinates (server-side reprojection of native geometry, not geocoded). Same shared MapServer as sibling fl_dep Sources filtered to other PROGRAM_TYPE values (HWS, VCP).

Reported North Carolina sanitary sewer overflow and bypass incidents, with incident timing, location, released volume, receiving-water impact, cause, and resolution.

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.

Open SPC historical severe-report database compiled from NWS Storm Data, currently covering U.S. tornadoes 1950–2025 and hail/damaging wind 1955–2025. Annual/full-period CSVs and SVRGIS path/initial-point shapefiles are one product family. Tornado files include raw state/county segments and de-segmented actual tracks. Magnitude means F/EF rating for tornado, inches for hail, and knots for wind with measured/estimated gust/sustained qualifier. Dated releases can correct and reprocess records, so retain release metadata. It is not a complete census, radar footprint, or building-impact dataset. SVRGIS creates a 0.0001-degree offset endpoint when no real endpoint was reported.

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.

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.

Commercial POST /v4/historical API for buyer-selected point, line, or polygon locations, fields, one-hour or one-day timestep, and ISO-8601 start/end times. The archive is a reanalysis product blending forecasts and observations; core worldwide-land fields generally run from 2000-01-01 through seven days before present, with 7–90-day processing latency depending on field. Each call is limited to a 31-day range.

Daily crash-grain E-Crash public data for CPD-jurisdiction crashes on Chicago streets. Coverage begins partially in 2015 and is citywide only from September 2017; finalized and amended reports update rows. Officer-recorded conditions are not independently inferred weather.

Public REST services behind the USGS Short-Term Network and Flood Event Viewer. The API supports event, site, and location-based retrieval of high-water marks and returns event/site identifiers, coordinates, flag and survey dates, surveyed elevation, vertical datum, mark quality, height above ground, and riverine/coastal environment.

Open OGC API product family for USGS continuous sensor measurements, daily values, time-series metadata, and monitoring-location metadata. Continuous and daily observations carry site and series identifiers, parameter/statistic codes, observation time, a precision-preserving string value, unit, approval status, qualifier, and last-modified time. Parameter code 00060 is discharge in cubic feet per second and 00065 is gage height in feet.

Commercial version-2.0.1 API returning daily or hourly NOAA-reanalysis history for arbitrary latitude/longitude points, postal codes, DMAs, and OnPoint identifiers. Coverage is every landmass worldwide and up to 200 miles offshore; the public specification does not pin the earliest retained date.

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.