Skip to main content
AREAZINENotices · US CA UK AU

AreaZineMethodology

How AreaZine is made

Every figure on AreaZine comes from an agency's own record, and every page names that record and links it, so you can check what we show against the source in one click. This page lists the records, how often we read them, how we count, what the pipeline checks, and where each record falls short.

Updated

The records

RecordAgency and fileReadComplete from
U.S. warnings, watches and advisories (live)National Weather Service alerts APIevery 5 minutesApril 2026 (AreaZine record)
U.S. warning counts by state and typeIowa Environmental Mesonet VTEC archive of NWS productsdaily2005; averages from 2008
FEMA disaster declarationsOpenFEMA Disaster Declarations Summaries and FEMA Web Disaster Summariesevery 6 hours1953
Earthquakes (U.S.)USGS earthquake catalog, magnitude 2.5 or moreevery 30 minutesApril 2026 (AreaZine record)
Earthquakes (Canada)Earthquakes Canada (Natural Resources Canada) event service, magnitude 2.5 or morehourly; catalogue daily2000 (catalogue); April 2026 (notices)
Earthquakes (Australia)Geoscience Australia earthquakes catalogue, magnitude 2.5 or morehourly; catalogue daily2000 (catalogue); April 2026 (notices)
Earthquakes (U.K.)British Geological Survey earthquake feed and database: every located event (notices from magnitude 1.5)hourly; database daily2000 (database); September 2026 (notices)
Flood alerts and warnings (England)Environment Agency flood-monitoring API and Historic Flood Warningshourly; history file monthlyJanuary 2006
Weather alerts (Canada)Environment and Climate Change Canada public alertshourlyApril 2026
Fires (New South Wales)NSW Rural Fire Service major incidents feedevery 30 minutesApril 2026
Weather warnings (Australia)Bureau of MeteorologyhourlyApril 2026
Recalls outside the U.S.Health Canada, FSA, MHRA, OPSS, ACCC, FSANZevery 4 to 12 hoursApril 2026

The agencies publish their notices for people to act on now; AreaZine keeps them afterwards, so that a place's record and a warning type's history can be read in one place. Where an agency publishes a complete archive (the NWS through the Iowa Environmental Mesonet, FEMA through OpenFEMA, the Environment Agency through its history file), counts come from that archive. Where it does not, counts come from AreaZine's own record of the live feed, and every such count says from which date the record is kept.

How a notice becomes a page

The pipeline stores each record exactly as the agency sent it. A notice gets a page only if its record meets a data contract: an NWS product needs a VTEC code, an area and a time; a New South Wales incident must be a vegetation fire, a hazard reduction or a burn-off (road crashes, alarms and structure fires are not published); an earthquake must come from its country's own agency (the USGS for the U.S., Earthquakes Canada, Geoscience Australia, the British Geological Survey) at magnitude 2.5 or more (1.5 in the U.K.); a flood notice needs an Environment Agency flood area; a recall needs a product, a date and the agency's page. The title and the first sentence are built from the record's own fields by fixed templates, and the agency's message is quoted as sent. Messages about people, such as child abduction or law enforcement alerts, are never published.

How we count

A National Weather Service product is counted by its VTEC event (office, phenomenon, significance and event number), in the month it was first issued. A warning that covers two states counts once in each state and once in the national total. Yearly averages use 2008 to the last complete year, because the archive holds fewer events for several products in 2005 to 2007, while VTEC coding was still being introduced. This year's count is compared with the same months of earlier years, through the last complete month; a month counts as complete from its 28th day, so the last day or two may be missing from this year's figure. FEMA declarations are counted by declaration date and number; one number can cover many counties. Environment Agency counts include flood alerts, flood warnings and severe flood warnings and leave out updates and the old "flood watch" level.

The checks that run

Each load compares what it read with what the agency's file says it holds, and a rebuild that would lose records it cannot restore stops. The pipeline refreshes what agencies revise: FEMA adds counties and programs to a declaration after the first day, and the USGS reviews an automatic earthquake solution and often changes its magnitude and felt reports, so those records are read again and the page shows the current value. Records whose source stops answering are flagged in the logs rather than shown as zero. Automated tests check the counting rules against samples of the source files. On 30 September 2026 a separate recount script checked 15 figures against the raw files and live catalogues, all equal: Colorado's and Texas's NWS warnings of 2026, the national red flag warnings of 2025 and the averages of 2008-2016 and 2017-2025, Oklahoma's tornado warnings of 2025, the national and Texas tornado watches of 2025 (one per Storm Prediction Center number), FEMA's declarations of 2025 and of 2026 to date and the major disasters among them, a flood area's alerts in the Environment Agency's history, a notice's event number, the U.K. earthquakes of 2026 and those of June 2026 in the British Geological Survey's database.

Licences: what is quoted and what is not

AreaZine's own counts and tables are published under CC BY 4.0. Each agency's record keeps its licence, and a notice page quotes an agency's text only where that licence allows reuse:

How AI tools are used

AreaZine is built with AI tools, which write the code, the page designs and the explanatory text of the guides and research pages. They do not decide the numbers: every figure comes from a database query over the agencies' records, and every notice page is assembled from the agency's fields by templates. Guides and research pages are read against the data before they are published.

The limits

Who answers for it

Questions and errors go to hello@areazine.com. We check a reported error against the agency's record, fix it at the source of the error rather than on one page, and list the correction with its date on the corrections page. The about page says who runs the site.