Admin console — the single data-entry point for this platform. Every data
type it runs on is a set of rows here, not application code: Hazard, Asset (Exposure),
Vulnerability, Risk baseline, and Impact & historical events. Administrative boundaries
are managed on their own registry, Admin →
Boundaries, not duplicated here.
No other screen holds its own registry list or lets an operator edit these rows in place —
analyst-facing screens browse and compose from what's registered here.
Analysts compose vulnerability layers from these
registered rows on the Vulnerability Dashboard's
analysis workspace — they select and run, they do not define new matrix cells, curve
parameters or weights here.
Each row carries the fields the platform needs to know how to run a hazard, not
only that it exists. Hazard type follows the UNDRR-ISC classification; onset class follows
UNDRR Sendai terminology, which defines two classes only —
“intermediate onset” appears in academic literature but is not part of any
official classification, so the registry does not offer it.
Hazard
Hazard type (UNDRR-ISC)
Onset class
Frequency attribute
Evaluation cadence
Forecast horizon
Notification surface
Enabled
Sources
Thresholds
Drought
Meteorological & hydrological
Slow-onset
Seasonal and recurrent, with multi-year persistence
Monthly
Long-range (30 d – 2 yr)
Bulletin workflow
Enabled
4
3
Flood (riverine)
Meteorological & hydrological
Sudden-onset
Seasonal and recurrent, following the rainy season
Continuous during season
Medium-range (3–10 d), operationally capped at +3 d
Alert surface
Enabled
3
4
Cyclone
Meteorological & hydrological
Sudden-onset
Seasonal (Nov–Apr) but irregular within the season
Continuous
Short- to medium-range (12 h – 10 d)
Alert surface
Enabled
2
3
Earthquake registry entry — not operational
Geological
Sudden-onset
No temporal pattern
Permanent detection
None — no forecast exists
Notification on occurrence
Disabled
0
0
Onset class & frequency → platform behaviour
The two columns an Admin sets — onset class and frequency — determine the two the
platform derives. Different onset classes never share a notification surface.
Onset class
Frequency attribute
Platform behaviour
Sudden-onset
Seasonal and recurrent
Continuous evaluation during the season · alert surface · thresholds armed seasonally
Sudden-onset
Seasonal but irregular within it
Continuous evaluation through the season · alert surface · no pre-arming by date
Sudden-onset
No temporal pattern
Permanent detection · notification on occurrence — a warning is not possible where no forecast exists
Slow-onset
Seasonal and recurrent
Scheduled monthly evaluation · bulletin workflow · never the alert surface
Slow-onset
Continuous / non-seasonal
Scheduled weekly or monthly evaluation · bulletin workflow
Sources: UNDRR-ISC Hazard definition and
classification review (2020, rev. 2025) and Hazard Information Profiles ·
UNDRR Sendai Framework Terminology, entries “Disaster” and
“Hazard” · WMO-No. 485 for the forecast ranges.
Each hazard's own data sources, indicators and forecasts need different fields, so each
keeps a separate registry below — jump to one:
DroughtFloodCyclone
SPI-3, zSM and zFAPAR are the three separate indicators the staged drought threshold on
EW-1 Thresholds reads — a single collapsed
“drought level” could not express a staged condition.
Forecasts — Drought
Forecast
Layer
Type
Range (WMO)
Cadence
Last computed
Status
Seasonal precipitation outlook
L-08
External API
Long-range (30 d – 2 yr)
Monthly
2026-07-01 00:00
OK
These are national aggregates for registry monitoring — every indicator's real spatial detail
(per administrative area) is on Dashboard → hazard layers,
not collapsed into one number here.