# NOAA Storm Events Database Scraper (`nexgenwatch/noaa-storm-events-feed`) Actor Scrape the NOAA Storm Events Database: event type, location, date, damage and casualties. One record per result. Pay per result. - **URL**: https://apify.com/nexgenwatch/noaa-storm-events-feed.md - **Developed by:** [NexGen Watch](https://apify.com/nexgenwatch) (community) - **Categories:** Developer tools, News, Automation - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $13.40 / 1,000 storm event records This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md. ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run. For examples already wired to this Actor's own input schema, see the [API](#api) section below. Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`). # README ## πŸ”” NOAA Storm Events Database Scraper **Scrape the NOAA Storm Events Database: event type, location, date, damage and casualties.** Run it once and you get the current records as a dataset; put it on a schedule to keep the list current. Structured **storm-event records** from the U.S. NOAA/NCEI **Storm Events Database**, read directly from the official public bulk directory (`www.ncei.noaa.gov/pub/data/swdi/stormevents/csvfiles/`). One record per row of the annual **details** file, streamed by incremental gunzip and carried source-native and **verbatim** β€” including the raw damage strings exactly as published (e.g. `1.00K`, `25.00M`). Output is one `storm_event_record` row per result; billing is pay-per-event, the value event being one storm event record (a $0.02 start fee per run, then $0.02 per storm event record). Source: www.ncei.noaa.gov. No login, no API key and no CAPTCHA solving are involved: the source is read logged-out with an identified contact User-Agent. **Who buys this** Buyers usually search for **NOAA storm events** or **storm data**. - Analysts, researchers and journalists who need NOAA storm events as clean rows. - Risk, insurance and planning teams joining storm data to their own data. - Data teams that want the official source without building a scraper. ### πŸ“Š Sample Output [![NOAA Storm Events Database Scraper sample output β€” a table of real storm event record rows (begin_yearmonth, begin_day, begin_time, event_type) from run sMDP3bm9eXTmMlXVz on build 0.1.10](https://api.apify.com/v2/key-value-stores/80Y7h3rmVN5CWK7Mw/records/noaa-storm-events-feed-sample-nw)](https://apify.com/nexgenwatch/noaa-storm-events-feed?fpr=2ayu9b) Real rows from run `sMDP3bm9eXTmMlXVz` on build 0.1.10 (2026-09-27), the same input as the Quick start below β€” every value is as the source published it (emails masked, long text shortened): | begin_yearmonth | begin_day | begin_time | event_type | begin_date_time | end_date_time | |---|---|---|---|---|---| | 202601 | 1 | 0 | Drought | 01-JAN-26 00:00:00 | 31-JAN-26 23:59:00 | | 202601 | 1 | 0 | Drought | 01-JAN-26 00:00:00 | 31-JAN-26 23:59:00 | | 202601 | 1 | 0 | Drought | 01-JAN-26 00:00:00 | 31-JAN-26 23:59:00 | | 202601 | 10 | 1140 | Thunderstorm Wind | 10-JAN-26 11:40:00 | 10-JAN-26 11:42:00 | | 202601 | 10 | 1122 | Thunderstorm Wind | 10-JAN-26 11:22:00 | 10-JAN-26 11:24:00 | | 202601 | 10 | 1132 | Thunderstorm Wind | 10-JAN-26 11:32:00 | 10-JAN-26 11:34:00 | | 202601 | 31 | 1855 | Extreme Cold/Wind Chill | 31-JAN-26 18:55:00 | 31-JAN-26 23:59:00 | | 202601 | 10 | 758 | Thunderstorm Wind | 10-JAN-26 07:58:00 | 10-JAN-26 08:00:00 | The run finished with the status message: `NORMAL: 50 unique rows (0 duplicates collapsed) from d2026_c20260918. billable=50` ### βœ… What you get Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is `null`): - `record_type` (string/null) β€” e.g. `storm_event_record` - `begin_yearmonth` (string/null) β€” e.g. `202601` - `begin_day` (string/null) β€” e.g. `1` - `begin_time` (string/null) β€” e.g. `0` - `end_yearmonth` (string/null) β€” e.g. `202601` - `end_day` (string/null) β€” e.g. `31` - `end_time` (string/null) β€” e.g. `2359` - `episode_id` (string/null) β€” e.g. `210653` - `event_id` (string/null) β€” e.g. `1315253` - `state` (string/null) β€” e.g. `GEORGIA` - `state_fips` (string/null) β€” e.g. `13` - `year` (string/null) β€” e.g. `2026` - `month_name` (string/null) β€” e.g. `January` - `event_type` (string/null) β€” e.g. `Drought` - `cz_type` (string/null) β€” e.g. `Z` - `cz_fips` (string/null) β€” e.g. `2` - `cz_name` (string/null) β€” e.g. `WALKER` - `wfo` (string/null) β€” e.g. `FFC` - `begin_date_time` (string/null) β€” e.g. `01-JAN-26 00:00:00` - `cz_timezone` (string/null) β€” e.g. `EST-5` - `end_date_time` (string/null) β€” e.g. `31-JAN-26 23:59:00` - `injuries_direct` (string/null) β€” e.g. `0` - `injuries_indirect` (string/null) β€” e.g. `0` - `deaths_direct` (string/null) β€” e.g. `0` - `deaths_indirect` (string/null) β€” e.g. `0` - `damage_property` (string/null) β€” e.g. `0.00K` - `damage_crops` (string/null) β€” e.g. `0.00K` - `source` (string/null) β€” e.g. `noaa-storm-events-feed` - `magnitude` (string/null) β€” e.g. `52.00` - `magnitude_type` (string/null) β€” e.g. `EG` - `flood_cause` (string/null) β€” null in every sample row - `category` (string/null) β€” null in every sample row - `tor_f_scale` (string/null) β€” null in every sample row - `tor_length` (string/null) β€” null in every sample row - `tor_width` (string/null) β€” null in every sample row - `tor_other_wfo` (string/null) β€” null in every sample row - `tor_other_cz_state` (string/null) β€” null in every sample row - `tor_other_cz_fips` (string/null) β€” null in every sample row - `tor_other_cz_name` (string/null) β€” null in every sample row - `begin_range` (string/null) β€” e.g. `.77` - `begin_azimuth` (string/null) β€” e.g. `WNW` - `begin_location` (string/null) β€” e.g. `HILYER` - `end_range` (string/null) β€” e.g. `.77` - `end_azimuth` (string/null) β€” e.g. `WNW` - `end_location` (string/null) β€” e.g. `HILYER` - `begin_lat` (string/null) β€” e.g. `32.9852` - `begin_lon` (string/null) β€” e.g. `-84.9917` - `end_lat` (string/null) β€” e.g. `32.9852` - `end_lon` (string/null) β€” e.g. `-84.9917` - `episode_narrative` (string/null) β€” e.g. `The Severe to Extreme Drought that characterized Fall 2025 persisted into Januar` - `event_narrative` (string/null) β€” e.g. `According to the U.S. Drought Monitor, Walker County remained primarily under D2` - `data_source` (string/null) β€” e.g. `CSV` - `provenance` (string/null) β€” e.g. `NOAA/NCEI Storm Events Database (details file); values carried source-native and` - `release_file` (string/null) β€” e.g. `StormEvents_details-ftp_v1.0_d2026_c20260918.csv.gz` - `release_year` (string/null) β€” e.g. `2026` - `release_version` (string/null) β€” e.g. `20260918` - `partial_year_file` (boolean/null) β€” e.g. `True` - `partial_year_note` (string/null) β€” e.g. `the 2026 annual file is an IN-PROGRESS (incomplete) year β€” NOAA is still collect` - `source_url` (string/null) β€” e.g. `https://www.ncei.noaa.gov/pub/data/swdi/stormevents/csvfiles/StormEvents_details` - `record_key` (string/null) β€” e.g. `1315253` - `release_date` (string/null) β€” e.g. `d2026_c20260918` - `observed_at` (string/null) β€” e.g. `2026-09-27T16:24:52Z` - `release_checksum` (string/null) β€” e.g. `20260918` - `license` (string/null) β€” e.g. `U.S. NOAA National Centers for Environmental Information (NCEI), Storm Events Da` - `attribution` (string/null) β€” e.g. `NOAA National Centers for Environmental Information (NCEI) β€” Storm Events Databa` - `terminal` (string/null) β€” null in every sample row - `scope` (string/null) β€” null in every sample row - `note` (string/null) β€” null in every sample row - `reported_total` (string/integer/null) β€” null in every sample row - `raw_seen` (string/integer/null) β€” null in every sample row - `duplicates` (string/integer/null) β€” null in every sample row - `unique_found` (string/integer/null) β€” null in every sample row - `delivered` (string/integer/null) β€” null in every sample row **βœ… What you get** - `record_type` (string/null) β€” e.g. `storm_event_record` - `begin_yearmonth` (string/null) β€” e.g. `202601` - `begin_day` (string/null) β€” e.g. `1` - `begin_time` (string/null) β€” e.g. `0` - `end_yearmonth` (string/null) β€” e.g. `202601` - `end_day` (string/null) β€” e.g. `31` - `end_time` (string/null) β€” e.g. `2359` - `episode_id` (string/null) β€” e.g. `210653` - `event_id` (string/null) β€” e.g. `1315253` - `state` (string/null) β€” e.g. `GEORGIA` - `state_fips` (string/null) β€” e.g. `13` - `year` (string/null) β€” e.g. `2026` - `month_name` (string/null) β€” e.g. `January` - `event_type` (string/null) β€” e.g. `Drought` - `cz_type` (string/null) β€” e.g. `Z` - `cz_fips` (string/null) β€” e.g. `2` - `cz_name` (string/null) β€” e.g. `WALKER` - `wfo` (string/null) β€” e.g. `FFC` - `begin_date_time` (string/null) β€” e.g. `01-JAN-26 00:00:00` - `cz_timezone` (string/null) β€” e.g. `EST-5` - `end_date_time` (string/null) β€” e.g. `31-JAN-26 23:59:00` - `injuries_direct` (string/null) β€” e.g. `0` - `injuries_indirect` (string/null) β€” e.g. `0` - `deaths_direct` (string/null) β€” e.g. `0` - `deaths_indirect` (string/null) β€” e.g. `0` - `damage_property` (string/null) β€” e.g. `0.00K` - `damage_crops` (string/null) β€” e.g. `0.00K` - `source` (string/null) β€” e.g. `noaa-storm-events-feed` - `magnitude` (string/null) β€” e.g. `52.00` - `magnitude_type` (string/null) β€” e.g. `EG` - `flood_cause` (string/null) β€” null in every sample row - `category` (string/null) β€” null in every sample row - `tor_f_scale` (string/null) β€” null in every sample row - `tor_length` (string/null) β€” null in every sample row - `tor_width` (string/null) β€” null in every sample row - `tor_other_wfo` (string/null) β€” null in every sample row - `tor_other_cz_state` (string/null) β€” null in every sample row - `tor_other_cz_fips` (string/null) β€” null in every sample row - `tor_other_cz_name` (string/null) β€” null in every sample row - `begin_range` (string/null) β€” e.g. `.77` - `begin_azimuth` (string/null) β€” e.g. `WNW` - `begin_location` (string/null) β€” e.g. `HILYER` - `end_range` (string/null) β€” e.g. `.77` - `end_azimuth` (string/null) β€” e.g. `WNW` - `end_location` (string/null) β€” e.g. `HILYER` - `begin_lat` (string/null) β€” e.g. `32.9852` - `begin_lon` (string/null) β€” e.g. `-84.9917` - `end_lat` (string/null) β€” e.g. `32.9852` - `end_lon` (string/null) β€” e.g. `-84.9917` - `episode_narrative` (string/null) β€” e.g. `The Severe to Extreme Drought that characterized Fall 2025 persisted into Januar` - `event_narrative` (string/null) β€” e.g. `According to the U.S. Drought Monitor, Walker County remained primarily under D2` - `data_source` (string/null) β€” e.g. `CSV` - `provenance` (string/null) β€” e.g. `NOAA/NCEI Storm Events Database (details file); values carried source-native and` - `release_file` (string/null) β€” e.g. `StormEvents_details-ftp_v1.0_d2026_c20260918.csv.gz` - `release_year` (string/null) β€” e.g. `2026` - `release_version` (string/null) β€” e.g. `20260918` - `partial_year_file` (boolean/null) β€” e.g. `True` - `partial_year_note` (string/null) β€” e.g. `the 2026 annual file is an IN-PROGRESS (incomplete) year β€” NOAA is still collect` - `source_url` (string/null) β€” e.g. `https://www.ncei.noaa.gov/pub/data/swdi/stormevents/csvfiles/StormEvents_details` - `record_key` (string/null) β€” e.g. `1315253` - `release_date` (string/null) β€” e.g. `d2026_c20260918` - `observed_at` (string/null) β€” e.g. `2026-09-19T04:45:28Z` - `release_checksum` (string/null) β€” e.g. `20260918` - `license` (string/null) β€” e.g. `U.S. NOAA National Centers for Environmental Information (NCEI), Storm Events Da` - `attribution` (string/null) β€” e.g. `NOAA National Centers for Environmental Information (NCEI) β€” Storm Events Databa` - `terminal` (string/null) β€” null in every sample row - `scope` (string/null) β€” null in every sample row - `note` (string/null) β€” null in every sample row - `reported_total` (string/integer/null) β€” null in every sample row - `raw_seen` (string/integer/null) β€” null in every sample row - `duplicates` (string/integer/null) β€” null in every sample row - `unique_found` (string/integer/null) β€” null in every sample row - `delivered` (string/integer/null) β€” null in every sample row **βœ… What you get** - `record_type` (string/null) β€” e.g. `storm_event_record` - `begin_yearmonth` (string/null) β€” e.g. `202601` - `begin_day` (string/null) β€” e.g. `1` - `begin_time` (string/null) β€” e.g. `0` - `end_yearmonth` (string/null) β€” e.g. `202601` - `end_day` (string/null) β€” e.g. `31` - `end_time` (string/null) β€” e.g. `2359` - `episode_id` (string/null) β€” e.g. `210653` - `event_id` (string/null) β€” e.g. `1315253` - `state` (string/null) β€” e.g. `GEORGIA` - `state_fips` (string/null) β€” e.g. `13` - `year` (string/null) β€” e.g. `2026` - `month_name` (string/null) β€” e.g. `January` - `event_type` (string/null) β€” e.g. `Drought` - `cz_type` (string/null) β€” e.g. `Z` - `cz_fips` (string/null) β€” e.g. `2` - `cz_name` (string/null) β€” e.g. `WALKER` - `wfo` (string/null) β€” e.g. `FFC` - `begin_date_time` (string/null) β€” e.g. `01-JAN-26 00:00:00` - `cz_timezone` (string/null) β€” e.g. `EST-5` - `end_date_time` (string/null) β€” e.g. `31-JAN-26 23:59:00` - `injuries_direct` (string/null) β€” e.g. `0` - `injuries_indirect` (string/null) β€” e.g. `0` - `deaths_direct` (string/null) β€” e.g. `0` - `deaths_indirect` (string/null) β€” e.g. `0` - `damage_property` (string/null) β€” e.g. `0.00K` - `damage_crops` (string/null) β€” e.g. `0.00K` - `source` (string/null) β€” e.g. `noaa-storm-events-feed` - `magnitude` (string/null) β€” e.g. `52.00` - `magnitude_type` (string/null) β€” e.g. `EG` - `flood_cause` (string/null) β€” null in every sample row - `category` (string/null) β€” null in every sample row - `tor_f_scale` (string/null) β€” null in every sample row - `tor_length` (string/null) β€” null in every sample row - `tor_width` (string/null) β€” null in every sample row - `tor_other_wfo` (string/null) β€” null in every sample row - `tor_other_cz_state` (string/null) β€” null in every sample row - `tor_other_cz_fips` (string/null) β€” null in every sample row - `tor_other_cz_name` (string/null) β€” null in every sample row - `begin_range` (string/null) β€” e.g. `.77` - `begin_azimuth` (string/null) β€” e.g. `WNW` - `begin_location` (string/null) β€” e.g. `HILYER` - `end_range` (string/null) β€” e.g. `.77` - `end_azimuth` (string/null) β€” e.g. `WNW` - `end_location` (string/null) β€” e.g. `HILYER` - `begin_lat` (string/null) β€” e.g. `32.9852` - `begin_lon` (string/null) β€” e.g. `-84.9917` - `end_lat` (string/null) β€” e.g. `32.9852` - `end_lon` (string/null) β€” e.g. `-84.9917` - `episode_narrative` (string/null) β€” e.g. `The Severe to Extreme Drought that characterized Fall 2025 persisted into Januar` - `event_narrative` (string/null) β€” e.g. `According to the U.S. Drought Monitor, Walker County remained primarily under D2` - `data_source` (string/null) β€” e.g. `CSV` - `provenance` (string/null) β€” e.g. `NOAA/NCEI Storm Events Database (details file); values carried source-native and` - `release_file` (string/null) β€” e.g. `StormEvents_details-ftp_v1.0_d2026_c20260918.csv.gz` - `release_year` (string/null) β€” e.g. `2026` - `release_version` (string/null) β€” e.g. `20260918` - `partial_year_file` (boolean/null) β€” e.g. `True` - `partial_year_note` (string/null) β€” e.g. `the 2026 annual file is an IN-PROGRESS (incomplete) year β€” NOAA is still collect` - `source_url` (string/null) β€” e.g. `https://www.ncei.noaa.gov/pub/data/swdi/stormevents/csvfiles/StormEvents_details` - `record_key` (string/null) β€” e.g. `1315253` - `release_date` (string/null) β€” e.g. `d2026_c20260918` - `observed_at` (string/null) β€” e.g. `2026-09-19T04:13:48Z` - `release_checksum` (string/null) β€” e.g. `20260918` - `license` (string/null) β€” e.g. `U.S. NOAA National Centers for Environmental Information (NCEI), Storm Events Da` - `attribution` (string/null) β€” e.g. `NOAA National Centers for Environmental Information (NCEI) β€” Storm Events Databa` - `terminal` (string/null) β€” null in every sample row - `scope` (string/null) β€” null in every sample row - `note` (string/null) β€” null in every sample row - `reported_total` (string/integer/null) β€” null in every sample row - `raw_seen` (string/integer/null) β€” null in every sample row - `duplicates` (string/integer/null) β€” null in every sample row - `unique_found` (string/integer/null) β€” null in every sample row - `delivered` (string/integer/null) β€” null in every sample row **What you get** One `storm_event_record` per details row β€” all NOAA columns carried verbatim (`event_id`, `episode_id`, `state`, `year`, `event_type`, begin/end date-times, `cz_name`, `wfo`, `damage_property`, `damage_crops`, `magnitude`, tornado `tor_*` fields, lat/lon, narratives, etc.) plus `provenance`, `release_file`, `release_year`, `release_version`, `source_url`. A column canary fails loud on header drift. ### βš™οΈ Sample inputs **1. Quick start β€” the Store example (this is what the sample above came from)** ```json { "states": [ "GEORGIA" ], "maxRecords": 10 } ``` The sample run charged exactly: 1 Γ— $0.02 apify-actor-start + 50 Γ— $0.02 storm_event_record = **$1.02** on the Free tier β€” every delivered row was billed. If you leave `maxRecords` out, the run delivers at most 50 rows (the schema default); pass a number up to 5000 for a bigger export. An explicit value is always honoured up to that maximum. **2. A smaller, narrowed run** ```json { "states": [ "GEORGIA" ], "maxRecords": 5 } ``` Caps the run at 5 rows β€” about $0.12 on the Free tier ($0.02 start + 5 Γ— $0.02). **3. A full-size run** ```json { "states": [ "GEORGIA" ], "maxRecords": 5000 } ``` Up to 5000 rows β€” about $100.02 on the Free tier ($0.02 start + 5000 Γ— $0.02) if the source has that many. **4. A filtered run** ```json { "states": [ "GEORGIA" ], "maxRecords": 10, "fieldMatch": { "cz_name": "WALKER" } } ``` Keeps only rows whose `cz_name` contains `WALKER` (a value from the sample run above), matched case-insensitively after the source is read and **before** the `maxRecords` cap, so the cap counts matches and only delivered matches are billed. `searchText` does the same across every column. Zero matches end the run as `EMPTY_SELECTION` with no row charged β€” if the source has moved on since that sample run, pick a value you see in your own first run. The source is still read in full β€” this narrows what you receive and pay for, not what the source serves. ### 🧾 JSON sample record One real record from run `sMDP3bm9eXTmMlXVz`, exactly as it lands in the dataset (emails masked, long text shortened): ```json { "record_type": "storm_event_record", "begin_yearmonth": "202601", "begin_day": "1", "begin_time": "0", "end_yearmonth": "202601", "end_day": "31", "end_time": "2359", "episode_id": "210653", "event_id": "1315253", "state": "GEORGIA", "state_fips": "13", "year": "2026", "month_name": "January", "event_type": "Drought", "cz_type": "Z", "cz_fips": "2", "cz_name": "WALKER", "wfo": "FFC", "begin_date_time": "01-JAN-26 00:00:00", "cz_timezone": "EST-5", "end_date_time": "31-JAN-26 23:59:00", "injuries_direct": "0", "injuries_indirect": "0", "deaths_direct": "0", "deaths_indirect": "0", "damage_property": "0.00K", "damage_crops": "0.00K", "source": "noaa-storm-events-feed", "magnitude": null, "magnitude_type": null, "flood_cause": null, "category": null, "tor_f_scale": null, "tor_length": null, "tor_width": null, "tor_other_wfo": null, "tor_other_cz_state": null, "tor_other_cz_fips": null, "tor_other_cz_name": null, "begin_range": null, "begin_azimuth": null, "begin_location": null, "end_range": null, "end_azimuth": null, "end_location": null, "begin_lat": null, "begin_lon": null, "end_lat": null, "end_lon": null, "episode_narrative": "The Severe to Extreme Drought that characterized Fall 2025 persisted into January 2026 as north and central Georgia failed to benefit from the typical 'recharge' period. A more active weather pattern in the second half of the month allowed ", "event_narrative": "According to the U.S. Drought Monitor, Walker County remained primarily under D2 (Severe Drought) conditions throughout January. Following the initial onset of D2 on December 30, 2025, the county experienced a brief period of marginal impro", "data_source": "CSV", "provenance": "NOAA/NCEI Storm Events Database (details file); values carried source-native and unmodified", "release_file": "StormEvents_details-ftp_v1.0_d2026_c20260918.csv.gz", "release_year": "2026", "release_version": "20260918", "partial_year_file": true, "partial_year_note": "the 2026 annual file is an IN-PROGRESS (incomplete) year β€” NOAA is still collecting/revising 2026 data; pin a complete year with the `year` input for a finalized dataset", "source_url": "https://www.ncei.noaa.gov/pub/data/swdi/stormevents/csvfiles/StormEvents_details-ftp_v1.0_d2026_c20260918.csv.gz", "record_key": "1315253", "release_date": "d2026_c20260918", "observed_at": "2026-09-27T16:24:52Z", "release_checksum": "20260918", "license": "U.S. NOAA National Centers for Environmental Information (NCEI), Storm Events Database β€” U.S. Government work, public domain. Acknowledgement: data from NOAA/NCEI. No implied NOAA endorsement. Raw values (including damage strings) are carri", "attribution": "NOAA National Centers for Environmental Information (NCEI) β€” Storm Events Database (https://www.ncei.noaa.gov/pub/data/swdi/stormevents/csvfiles/)" } ``` ### πŸ”§ How it works **Source.** The actor reads www.ncei.noaa.gov β€” endpoints: `https://www.ncei.noaa.gov/pub/data/`, `https://www.ncei.noaa.gov/pub/data/swdi/stormevents/csvfiles/`. Public pages and feeds only; nothing behind a login. **Transport.** Plain HTTPS from the Apify platform, no proxy. robots.txt is read first and a disallowed path is never fetched. Every request carries an identified contact User-Agent. Pacing: `CRAWL_DELAY`=0.0. **Terminal states.** A run ends NORMAL, CAPPED (your cap was reached), PARTIAL (something was withheld and the message says what), GENUINE_EMPTY (the source was read and truly had nothing in scope) or BLOCKED (the source refused or changed shape β€” the run FAILS loud and bills nothing). A zero-row run is never reported as a silent success. **Charging.** Each storm event record is charged at the moment it is pushed (`storm_event_record`); a row that fails to charge is not delivered, so the dataset count always equals the charged count. **Person-level fatality data is NEVER read** This actor reads **only** the `details` file. It **never** fetches, constructs, or parses the `StormEvents_fatalities-*` file β€” the person-level fatality table (age, sex, location of death). The file resolver **refuses** any non-details member, and no code path anywhere builds a fatalities URL. The details file's `deaths_*` / `injuries_*` columns are **event-level aggregate counts** (not person records) and are carried as NOAA publishes them. **Latest annual file β€” and pinning a year** The actor **discovers the latest versioned annual details file** from the directory each run (NOAA re-publishes corrected `c` editions). NOAA is a **living source**: at the turn of a year the directory carries both the completed prior year and a new in-progress current-year file, so the default resolves to the newest (current, in-progress) year. Pin a specific year with the `year` input (e.g. `"2025"` for the latest complete year). **Filters** Supply **at least one** of `states`, `eventTypes`, `czNames`, or `episodeIds` β€” the annual file is never emitted in full. `maxRecords` caps delivery (one charge per delivered record, hard cap 5000); `maxScanRows` bounds the scan. **Robots & door** `www.ncei.noaa.gov/robots.txt` disallows `/data*` and `/orders*`. This actor fetches **only** under `/pub/data/` (which is not under `/data*` and is permitted) and never anything else. Robots is re-read every run and the actor STOPs (fails, charges nothing) on any real Disallow covering the path. NOAA/NCEI acknowledgement; no implied NOAA endorsement. **Source & licence** U.S. NOAA National Centers for Environmental Information (NCEI), Storm Events Database β€” U.S. Government work, **public domain**. Acknowledgement: data from NOAA/NCEI (https://www.ncei.noaa.gov/pub/data/swdi/stormevents/csvfiles/). **What is not done.** No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation. ### ⏰ Optional: run it on a schedule A single run returns the current records. If you also want to be told what changed over time, open the actor in Apify Console β†’ **Schedules** β†’ **Create new**, add this actor with the input you want, and pick a cadence: - **Daily** β€” `0 7 * * *` (07:00 UTC): catch changes within a day. - **Weekly** β€” `0 7 * * 1`: a Monday digest. Each run is independent; keep the same input on the schedule so the results stay comparable. Schedules can also POST results to a webhook (Console β†’ Integrations). ### πŸ’° Pricing example | Event | Free | Bronze | Silver | Gold | |---|---|---|---|---| | Actor Start (`apify-actor-start`) | $0.02 | $0.02 | $0.02 | $0.02 | | Storm event record (`storm_event_record`) | $0.02 | $0.018 | $0.016 | $0.0134 | Worked at the live Free-tier price: - 8 storm event records: $0.02 start + 8 Γ— $0.02 = **$0.18** - 25 storm event records: $0.02 start + 25 Γ— $0.02 = **$0.52** - 50 storm event records: $0.02 start + 50 Γ— $0.02 = **$1.02** A run that delivers zero rows charges the $0.02 start fee only. A BLOCKED run (source refused) fails loud and charges no value event. The start fee is charged once per GB of run memory; the default run memory is 4096 MB. Yield on the sample run: `NORMAL: 50 unique rows (0 duplicates collapsed) from d2026_c20260918. billable=50`. `maxRecords` is a hard ceiling on what is delivered and billed, never a target. ### βš–οΈ Legal & ToS This actor reads public, logged-out pages and feeds published by www.ncei.noaa.gov. It collects only what the source publishes to any visitor, keeps to the source's robots rules (checked on every run), identifies itself with a contact User-Agent, and does not access accounts, private data or anything behind authentication. Use the output in line with the source's terms and your local law; the intended use is B2B research and monitoring. ### ❓ FAQ **Q: Do I need an API key or a login?**\ A: No. The source (www.ncei.noaa.gov) is read logged-out; the input schema has no key field and the actor carries no secrets. **Q: Why did my run return 0 rows?**\ A: Read the run's status message. GENUINE_EMPTY means the source was read and had nothing in scope for your input; BLOCKED means the source refused and the run failed without billing a value event β€” retry later or narrow the input. A zero-row run bills the start fee only. **Q: How many rows can one run return?**\ A: Up to `maxRecords` (default 50). Raise the cap for a bigger run; you pay per delivered row. **Q: How fresh is the data?**\ A: Every run reads the source live at run time; nothing is cached between runs. Put it on a schedule for a continuous feed. **Q: What formats can I export?**\ A: The dataset downloads as JSON, CSV, Excel, XML or RSS from the run's Dataset tab or the Apify API, and any run can push to a webhook or integration. **Q: How is this different from the other NexGen Watch actors actors?**\ A: Same output shape and billing model; this one covers www.ncei.noaa.gov. The siblings under **Related Actors** cover the other sources or slices β€” run several on one schedule for a combined feed. **Q: Are there rate limits?**\ A: The actor paces itself against the source (`CRAWL_DELAY`=0.0) and honours its robots rules; there is no per-buyer limit beyond your Apify plan's concurrency. ### πŸ†˜ Troubleshooting - **Run FAILED with BLOCKED** β†’ the source refused the request or changed its page shape β†’ nothing was billed beyond the start fee; retry after a while, and if it persists open an Issue with the run id. - **Status says CAPPED** β†’ your cap (`maxRecords`) was reached β†’ raise it for a bigger run. - **Input validation error on start** β†’ a field is outside the schema's allowed values β†’ start from the Quick start block and change one field at a time. - **Run TIMED-OUT** β†’ a very wide request on a slow day β†’ raise the run timeout in Run options or narrow the input; what was delivered before the timeout is still in the dataset. ### πŸ”— Related Actors - [NOAA GHCN-Monthly Average Temperature](https://apify.com/nexgenwatch/noaa-ghcn-monthly-temperature?fpr=2ayu9b) β€” Structured monthly average-temperature (TAVG) station-year records from the U.S - [NOAA ISD Hourly Surface Observations](https://apify.com/nexgenwatch/noaa-isd-hourly-observations?fpr=2ayu9b) β€” Structured hourly surface weather observations from the U.S. NOAA/NCEI Integrated Surface Database (ISD), read directly from the official public bulk… - [NOAA Storm Damage & Impact Feed](https://apify.com/nexgenwatch/noaa-storm-damage-impact?fpr=2ayu9b) β€” A deterministic impact subset of the U.S. NOAA/NCEI Storm Events Database details file β€” only storm events with a published impact are emitted - [NOAA Storm Events Locations](https://apify.com/nexgenwatch/noaa-storm-locations?fpr=2ayu9b) β€” Structured storm-event location points from the U.S. NOAA/NCEI Storm Events Database, read directly from the official public bulk directory (www.ncei… - [NY OCM Licence Registry](https://apify.com/nexgenwatch/ny-ocm-licence-registry?fpr=2ayu9b) β€” One ocm_licence_record per licence or application: entity name, DBA, licence type, status (label AND source status code preserved verbatim), see-cate… - [NYC DCWP Business Licence Registry](https://apify.com/nexgenwatch/nyc-dcwp-business-licence-registry?fpr=2ayu9b) β€” One business_licence_record per DCWP licence: licence number, business + DBA name, category, type, status, creation/expiration dates, contact phone,… - 🏒 **About NexGen Watch** β€” NexGen Watch is a catalog of more than 300 public data actors built on official sources, pay-per-result. Browse the catalog at [apify.com/nexgenwatch](https://apify.com/nexgenwatch?fpr=2ayu9b). ### ⭐ Found this useful? If this actor saved you a manual check, a quick **[review on the Apify Store](https://apify.com/nexgenwatch/noaa-storm-events-feed?fpr=2ayu9b)** helps other teams find it. Feature request or a source that changed? Open it from the **Issues** tab β€” every one is read. # Actor input Schema ## `states` (type: `array`): State names as published (UPPERCASE), e.g. \["GEORGIA","TEXAS"]. At least one of states / eventTypes / czNames / episodeIds is REQUIRED β€” the annual file is never emitted in full. ## `eventTypes` (type: `array`): NOAA event types, e.g. \["Thunderstorm Wind","Tornado","Flash Flood"]. ## `czNames` (type: `array`): CZ_NAME values (UPPERCASE), e.g. \["CARROLL"]. ## `episodeIds` (type: `array`): EPISODE_ID values to pull all events in an episode. ## `year` (type: `string`): Pin a specific storm-events year, e.g. "2025" (the latest complete year). Default: the latest versioned annual file in the directory (currently the in-progress current year). ## `maxRecords` (type: `integer`): Max storm-event records delivered (buyer bound; one charge per delivered record). Hard-capped at 5000. ## `maxScanRows` (type: `integer`): Hard scan bound over the streamed annual file. Default 100000 (covers a full year). ## `userAgent` (type: `string`): Override the transparent crawler UA. ## `searchText` (type: `string`): Optional. Keep only rows where any field contains this text (case-insensitive, substring). Applied after the source is read and BEFORE the maxRecords cap, so the cap counts matches and only delivered matches are billed. Zero matches = EMPTY_SELECTION, nothing charged beyond the start fee. ## `fieldMatch` (type: `object`): Optional. {"column": "text"} keeps rows whose named output column contains the text (case-insensitive); a list of texts means any of them; several columns must all match. Column names are the dataset fields shown in the sample output. Applied BEFORE the maxRecords cap and before billing. ## Actor input object example ```json { "states": [ "GEORGIA" ], "eventTypes": [], "czNames": [], "episodeIds": [], "maxRecords": 10, "maxScanRows": 100000 } ``` # Actor output Schema ## `results` (type: `string`): No description # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "states": [ "GEORGIA" ], "maxRecords": 10 }; // Run the Actor and wait for it to finish const run = await client.actor("nexgenwatch/noaa-storm-events-feed").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`πŸ’Ύ Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // πŸ“š Want to learn more πŸ“–? Go to β†’ https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "states": ["GEORGIA"], "maxRecords": 10, } # Run the Actor and wait for it to finish run = client.actor("nexgenwatch/noaa-storm-events-feed").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"πŸ’Ύ Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # πŸ“š Want to learn more πŸ“–? Go to β†’ https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "states": [ "GEORGIA" ], "maxRecords": 10 }' | apify call nexgenwatch/noaa-storm-events-feed --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgenwatch/noaa-storm-events-feed" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/FevdLopnQAhuLP4pb/builds/lqAmGSaWkPuJogVeM/openapi.json