# Storm Event Records — US NOAA / NCEI (`nexgensignal/storm-event-records`) Actor

Keyless, pay-per-record NOAA/NCEI Storm Events Database — one row per US storm event with type, county, dates, casualties, damages (USD), and magnitude. Public-domain; no narratives, no person data.

- **URL**: https://apify.com/nexgensignal/storm-event-records.md
- **Developed by:** [NexGen Signal](https://apify.com/nexgensignal) (community)
- **Categories:** Business, News, Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $33.50 / 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/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Storm Event Records — US NOAA / NCEI

**Keyless. Pay per record. Every US storm event, with damages, casualties, and magnitude.**

This actor turns the **US NOAA / NCEI Storm Events Database** into clean, per-event records — the authoritative log of severe and significant weather across the United States. Each run reads NOAA's public annual bulk file and delivers one row per storm event: the type and location, the begin and end times, the injuries and deaths, the property and crop damage, the magnitude, and — for tornadoes — the Enhanced Fujita scale and path dimensions. Event grain, structured for engineering use, in the public domain, with NOAA's own official-data disclaimer on every record. **Free-text narrative fields are never emitted.**

### What this is, in one paragraph

The Storm Events Database is NOAA's official record of storms and other significant weather phenomena — tornadoes, hail, floods, thunderstorm winds, winter storms, heat, wildfire, and dozens more event types — compiled from National Weather Service reports. This actor reads the annual "details" file for the year you choose, filters to the state and event type you want, and flattens each event into a single analysis-ready record: identity, classification, county/zone geography, timing, human impact, economic damage, and hazard-specific magnitudes. Values are exactly as published by NOAA, with damage strings additionally parsed into plain USD numbers. You are billed only for records actually delivered.

### Who buys this and for what job

- **Insurance, reinsurance, and catastrophe modellers** building a structured US storm loss history — damages, casualties, and magnitudes keyed by event and county.
- **Climate and atmospheric researchers** studying event frequency, severity, and trends across decades and regions.
- **Risk, agriculture, and infrastructure teams** quantifying exposure to hail, wind, flood, and tornado events by state and county.
- **Data engineers and data journalists** who want the storm log as clean rows without parsing NOAA's fixed-format bulk files.

### Public-domain data — with NOAA's official-data caveat

Two honesty riders travel on every record. First, **licensing**: NOAA / NCEI Storm Events data is a **work of the US federal government** — no copyright, **public domain** under 17 U.S.C. §105 — free to reuse with attribution to NOAA / NWS. Second, **fitness**: Storm Data is an official NOAA publication, but some information may be **unverified by the National Weather Service, which does not guarantee the accuracy or validity of the information**, and location precision varies by era (older records are coarser). This is informational data, not a basis for legal, emergency, navigational, or safety-of-life decisions.

### Event grain — no person data, no narratives

This actor works at event grain: storm types, places, times, impacts, and magnitudes. The database includes two free-text narrative fields (episode and event narratives) that can contain eyewitness accounts naming individuals — **this actor drops both entirely and never emits them**, alongside a person-key guard on every record as a backstop. What you get is the structured, non-narrative event record.

### Pricing

| Event | Free plan | Bronze | Silver | Gold / Platinum / Diamond |
|-------|-----------|--------|--------|---------------------------|
| `storm_event_record` | $0.05 | $0.045 | $0.04 | $0.0335 |

Delivered before charged. Blocked runs and empty results cost nothing.

### Input

| Field | Type | Default | Description |
|-------|------|---------|-------------|
| `year` | integer | 2024 | Data year of the Storm Events details file to read. |
| `state` | string | — | Optional. Keep only events in this US state/territory (full name as NOAA uses it, e.g. TEXAS). |
| `eventType` | string | — | Optional. Keep only events whose type contains this text (e.g. Tornado, Hail, Flash Flood). |
| `maxRecords` | integer | 500 | Ceiling on records delivered and billed. |

### Output

One JSON object per storm event. Real example (values as published by NOAA, an EF0 tornado in Davis County, Iowa, 2024):

```json
{
  "record_id": "1216653",
  "event_id": "1216653",
  "episode_id": "196653",
  "event_type": "Tornado",
  "state": "IOWA",
  "cz_type": "C",
  "cz_name": "DAVIS",
  "wfo": "DMX",
  "year": 2024,
  "begin_date_time": "05-NOV-24 11:01:00",
  "end_date_time": "05-NOV-24 11:02:00",
  "deaths_direct": 0,
  "injuries_direct": 0,
  "damage_property": "120.00K",
  "damage_property_usd": 120000.0,
  "damage_crops_usd": 0.0,
  "report_source": "Trained Spotter",
  "tor_f_scale": "EF0",
  "tor_length": 0.32,
  "tor_width": 50.0,
  "begin_location": "BELKNAP",
  "begin_lat": 40.803,
  "begin_lon": -92.3482,
  "end_lat": 40.8062,
  "end_lon": -92.3437,
  "source": "US NOAA/NCEI Storm Events Database",
  "licence": "US NOAA/NCEI Storm Events Database — ... public domain (17 U.S.C. §105) ...",
  "disclaimer": "Storm Data is an official NOAA publication ... NWS does not guarantee the accuracy ...",
  "observed_at": "2026-08-21T00:00:00Z"
}
```

An unbilled `RUN_RECEIPT` records the robots check, the year and file, the filters, source rows seen and delivered, whether charged equals delivered, and a note that narrative fields are never emitted.

### Field reference

Each record is one storm event. Identity: `record_id` / `event_id`, `episode_id`, and `event_type`. Geography: `state`, `state_fips`, `cz_type` (county or NWS zone), `cz_fips`, `cz_name`, `wfo`, and the point coordinates `begin_lat`, `begin_lon`, `end_lat`, `end_lon`, plus the named references `begin_range`/`begin_azimuth`/`begin_location` and the matching `end_` set. Timing: `year`, `month_name`, `begin_date_time`, `end_date_time`, and `cz_timezone`. Human impact: `injuries_direct`, `injuries_indirect`, `deaths_direct`, and `deaths_indirect`. Economic impact: `damage_property` and `damage_crops` (as published), plus `damage_property_usd` and `damage_crops_usd` (parsed to numbers). Hazard specifics: `magnitude`, `magnitude_type`, `flood_cause`, `category`, `tor_f_scale`, `tor_length`, and `tor_width`. Provenance and caveats: `report_source`, `data_source`, `source`, `source_url`, `licence`, `attribution`, `disclaimer`, and `observed_at`.

### How a run works

A run first re-reads NCEI's robots posture from your runtime — the Storm Events files live under `/pub/data/...`, which the site's `Disallow: /data*` rule does not cover — and stops at the door if that ever changes. It then resolves the current details filename for your chosen `year` from NOAA's directory index (the filename carries a creation-date suffix that changes as data is revised), downloads the gzipped CSV, and streams it row by row. Each row is checked against your optional `state` and `eventType` filters before delivery, so you are billed only for events that pass them. Each matching row is flattened to one record — with the two narrative fields dropped — damage strings parsed to USD, and delivered **before** it is charged, so a blocked or empty run costs you nothing. The actor stops at your `maxRecords` ceiling and records `charge_equals_delivered` in the receipt.

### Event types and coverage

The database spans the full range of severe and significant weather, and this actor surfaces the `event_type` on every row. Common pulls include **Tornado** (with EF scale, path length and width), **Hail** (with size magnitude), **Thunderstorm Wind** (with speed magnitude), **Flash Flood** and **Flood** (with flood cause), **Winter Storm**, **Heavy Snow**, **Blizzard**, **Excessive Heat**, **Drought**, **Wildfire**, **High Wind**, **Lightning**, **Coastal Flood**, and many more. Because each record also carries county/zone geography and begin/end coordinates, you can scope by place as well as by hazard. Pass a single `eventType` to build a focused feed — say, only tornadoes with their scales and paths — or pull a whole year and group by `event_type` and `state` downstream. Paired with `state`, one run gives you a bounded, low-cost slice of a single state's season.

### Cost guidance

One `storm_event_record` per delivered event: cost = events delivered × your plan's per-record price. A single year's details file holds tens of thousands of events across all states and types, so scope with `state` and `eventType` to keep runs bounded — one state's tornadoes in a year is typically a few dozen to a few hundred. 1,000 events is **$50** (Free) / **$33.50** (Gold).

### Honest limitations

- **Official, but not guaranteed.** Some entries are unverified by the NWS, which does not guarantee accuracy or validity; treat the data as informational.
- **Precision varies by era.** Older records (especially pre-1996) have coarser location and coverage than recent years.
- **Not for safety-of-life use.** Do not use this feed for emergency, navigational, or evacuation decisions.
- **No narratives.** The free-text episode and event narratives are never emitted; this is the structured record only.
- **As published, plus parsed damages.** Values are exactly as NOAA distributes them; the only derived fields are the USD parses of the damage strings.
- **No person data** is emitted.

### Differentiation

The NexGenData fleet draws on the **US NOAA Storm Events Database** in several places, and this actor sits alongside them as the **consolidated full-event record**. The sibling actors **noaa-storm-events-feed**, **noaa-storm-damage-impact**, and **noaa-storm-locations** split the same source into focused slices — the event feed, the damage/casualty impact, and the event locations respectively. This actor instead delivers **one row per event carrying all of it together**: identity and type, county/zone geography and coordinates, timing, injuries and deaths, property and crop damage (parsed to USD), and hazard-specific magnitudes including tornado EF scale, length, and width — the whole structured record in a single pull. Same official source; choose this actor when you want the complete event record in one place rather than a single dimension of it. The fleet also ships **natural-hazard-event-records** (NASA EONET) — a *global* catalogue of curated natural events with latest position and magnitude — which is a different source and job from this US official storm log with impacts.

### The NexGen Signal family

Part of the NexGen Signal family of pay-per-record data products:

- [Natural Hazard Event Records — NASA EONET](https://apify.com/nexgensignal/natural-hazard-event-records)
- [Air Quality Monitor Records — US EPA AQS](https://apify.com/nexgensignal/air-quality-monitor-records)
- [EPA Facility Compliance Records — Envirofacts](https://apify.com/nexgensignal/epa-facility-compliance-records)
- [National Macro Indicator Records — World Bank](https://apify.com/nexgensignal/national-macro-indicator-records)
- [US Treasury Fiscal Records — Rates & Debt](https://apify.com/nexgensignal/treasury-fiscal-records)

*Source: US NOAA National Centers for Environmental Information (NCEI) Storm Events Database. Data is a work of the US federal government, no copyright, public domain (17 U.S.C. §105); free to reuse with attribution to NOAA/NWS. Storm Data is an official NOAA publication but some information may be unverified by the NWS, which does not guarantee accuracy or validity; not for safety-of-life use. Reformatted to event records; free-text narratives and person data are never emitted.*

# Actor input Schema

## `year` (type: `integer`):

Data year of the NOAA Storm Events details file to read (e.g. 2024). Recent years are updated as reports arrive.

## `state` (type: `string`):

Optional. Keep only events in this US state or territory (full name as NOAA uses it, e.g. TEXAS, CALIFORNIA, PUERTO RICO). Case-insensitive.

## `eventType` (type: `string`):

Optional. Keep only events whose type contains this text (e.g. Tornado, Hail, Flash Flood, Thunderstorm Wind, Winter Storm). Case-insensitive.

## `maxRecords` (type: `integer`):

Maximum records delivered and billed. You are billed only for records delivered.

## Actor input object example

```json
{
  "year": 2024,
  "maxRecords": 500
}
```

# Actor output Schema

## `results` (type: `string`):

The delivered NOAA storm event records.

# 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 '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "year": 2024,
    "maxRecords": 500
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgensignal/storm-event-records").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 '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "year": 2024,
    "maxRecords": 500,
}

# Run the Actor and wait for it to finish
run = client.actor("nexgensignal/storm-event-records").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 '{
  "year": 2024,
  "maxRecords": 500
}' |
apify call nexgensignal/storm-event-records --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgensignal/storm-event-records"
        }
    }
}

```

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 <APIFY_API_TOKEN>` 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/t673S59DnookjWPQb/builds/f3IOwKjOnR6F6fb5r/openapi.json