Skip to content
The Register

Severe Weather Business Impact Monitor — NWS, By Location

Matches active NOAA/NWS severe weather alerts against your specific business locations (lat/lon), not a raw statewide feed. Severity, urgency, and certainty are NWS's own official classification, never a re-derived heuristic. Free, keyless, real-time.

Severe Weather Business Impact Monitor — NWS, By Location returns 18 documented output fields, including locationLabel, lat, lon, resolvedCity and resolvedState. Every field carries a declared type, a written description and an example value. 23 runs are recorded on Apify.

Run it on ApifyPay per result · no subscription
18
Output fields
3
Inputs
23
Runs
2026-10-16
Last run

01 — output

What it returns

Every field the extractor writes to its dataset, with its type, a written description and an example value.

FieldTypeWhat it holdsExample
locationLabelstringnullShort human-readable label for this location.Austin, Texas
latnumbernullLatitude in decimal degrees. Negative is south.30.2672
lonnumbernullLongitude in decimal degrees. Negative is west.-97.7431
resolvedCitystringnullCity resolved from the raw published address.<resolvedCity>
resolvedStatestringnullState resolved from the raw published address.<resolvedState>
alertIdstringnullIdentifier of this alert.<alertId>
eventstringnullEvent as recorded for this row.<event>
headlinestringnullHeadline as published.<headline>
severitystringnullSeverity as classified by the source.moderate
urgencystringnullHow urgent this row is, in words.medium
certaintystringnullCertainty as recorded for this row.<certainty>
areaDescstringnullGeographic area the declaration covers, as the source words it.<areaDesc>
effectivestringnullDate the record takes effect.<effective>
expiresstringnullISO 8601 timestamp after which this record is no longer valid.<expires>
descriptionstringnullDescription of this record, as published by the source.<description>
instructionstringnullInstruction for resolving this finding.<instruction>
statusstringnullOutcome recorded for this row.ok
verdictstringnullThe Actor's conclusion for this row, stated in words.pass

02 — sample

One record

Assembled from the example values declared on the schema above, not invented at render time.

{
  "locationLabel": "Austin, Texas",
  "lat": 30.2672,
  "lon": -97.7431,
  "resolvedCity": "<resolvedCity>",
  "resolvedState": "<resolvedState>",
  "alertId": "<alertId>",
  "event": "<event>",
  "headline": "<headline>"
}

03 — input

What you give it

InputTypeDescription
locationsarrayrequiredBusiness locations to check, each with a lat/lon and an optional label. Example: [{"label": "Warehouse A", "lat": 34.05, "lon": -118.24}]. US locations only (NWS coverage).
minSeveritystringoptionalOnly return alerts at or above this severity. Leave empty for all severities.
maxItemsintegeroptionalHard cap on items returned. You are never charged beyond this.

04 — run

Run Severe Weather Business Impact Monitor on your own input

It runs in the cloud on Apify. Nothing to install, and you are billed per result returned rather than per attempt.

Open on Apify ↗

05 — questions

Asked before running it

18 of 18 fields described

What does Severe Weather Business Impact Monitor — NWS, By Location return?
It returns 18 documented output fields: locationLabel, lat, lon, resolvedCity, resolvedState, alertId, event, headline, severity, urgency, certainty and areaDesc. Each field declares its type, a description of what it holds, and an example value. The remaining 6 are listed in the output schema below.
What input does Severe Weather Business Impact Monitor — NWS, By Location require?
locations is required. A further 2 inputs are optional. The full input schema, with types and defaults, is below.
Does Severe Weather Business Impact Monitor — NWS, By Location need an API key or login?
No. None of its inputs is a credential, and it reads only public data. Nothing to sign up for before the first run.
How do I run Severe Weather Business Impact Monitor — NWS, By Location?
It runs on Apify. Start it from its listing with the inputs above, or call the Apify API with the Actor's ID. Results land in a dataset you can export as JSON, CSV or Excel, or read through the Apify API into your own pipeline.