Dataset

Hazard history for a location

A single answer for one location: the incidents, warnings and mapped extents official sources recorded within a radius of it, together with every disaster declaration that covered its local government area, counted once per AGRN. Both lanes are returned because both are needed. A Lismore address returns the February 2022 flood only through the declared lane, because the spatial record holds nothing for it at address precision. Every record states how precisely it was located, and records whose source never supplied a date are returned flagged rather than dated or dropped.

Coverage
The locatable part of the historical archive plus the live-era incident history and the declarations layer. Of the archive, 4.0 million of 4.8 million records carry a usable location, and 938,588 of those sit at a postcode centroid rather than at an address; both facts are reported in every response so a reader can see what a match meant.
Freshness
The declared lane follows the declarations layer; the observed lane is fixed for the historical archive and follows the live feeds for recent events.
Provenance
The same official agency feeds, DisasterAssist, NEMA and state declaration records that back the incidents, archive and declarations datasets, identified per record.
Access
Enterprise. Public demo available.

Endpoints

  • POST /api/v1/hazard-history/point: observed record and declared status for a lat/lng; coordinates are never logged or echoed

Full reference: docs · Try it: Five worked locations