Skip to content

Natural-hazard events: NASA EONET weekly severity digest

Commercial use OKFresh
Query in workbench

Follow this dataset

Get a notice in your feed when a new snapshot is published. Optionally, we also POST it to your webhook.

Must be a public https address. We never follow redirects.

The full snapshot isn't published yet — check back after the next refresh.Download sample CSVDownload sample JSONSample rows only (up to 20) — not the complete dataset.

The trailing 7 complete days (UTC) of natural-hazard events tracked by NASA's Earth Observatory Natural Event Tracker (EONET): wildfires, severe storms, floods, volcanoes, landslides, drought, dust/haze, snow, temperature extremes, earthquakes and manmade incidents with at least one observation inside the window (typically 80-150 events/week; sea-ice/water-color monitoring layers excluded by a documented scope gate). Each row is one event: stable EONET id, title, deterministic primary category (highest severity weight wins) plus all categories, open/closed status, window-clipped duration and observation counts, wildfire burned area normalized to hectares, source count and primary source URL, latest in-window coordinates, a documented 0-100 severity score (100*(0.40*category_weight + 0.30*duration_norm + 0.30*obs_norm)) and its rank, per-row EONET URL, and a row hash. Primary key: event_id. Cadence: weekly; the as_of date is the window end, so identical input produces an identical content hash. Caveats: magnitudes are heterogeneous across categories (kts vs hectares) and carried verbatim, not scored; upstream revisions and post-window closures produce honest new snapshots. EONET data is U.S. government public domain — commercial_use = yes. Sample use: order by severity_rank for the week's most severe natural-hazard events.

Rows
70
Columns
24
Source cadence
Weekly
Last refreshed
Sep 25, 2026
Theme
environment

Use your own AI key

Once today's free allowance is used up, AI features can run on your own provider account.

Kept in this browser tab only (cleared when you close it) and sent with each AI request. Our servers use it for that request and never store or log it.