Risk → Impact → Action
Each use case answers a different question in the disaster timeline, and each builds on the one before. All three run as parameterized notebooks on the same infrastructure — they differ in their data, their method, and how they are triggered.
How many people and which assets are exposed to a given hazard, before any event — a baseline for preparedness and planning.
Local decision-makers need up-to-date estimates of exposure to natural hazards: how many children are exposed to recurrent heatwaves, which cities are most prone to cyclones, which airports sit in tsunami-risk zones. The INFORM methodology is the main reference, but its subnational coverage and resolution don’t always fit local needs — so this use case makes the underlying data available with notebooks to compute exposure flexibly, at the resolution and thresholds a user chooses.
Who and what fall within the observed extent of an actual disaster, using Copernicus remote-sensing products, in the hours and days after it strikes.
In a response’s first phase, a reliable estimate of the affected zone — from remote sensing, before ground surveys arrive — speeds prioritisation. Products from CEMS, the Disaster Charter and others exist, but local responders often want to go more granular and flexible: their own subdivisions, their own disaggregation, their own extra data. This use case makes CEMS the main source and adds custom post-processing.
Which affected areas to prioritise — combining exposure, impact, Montandon’s disaster history and operational data — and feeding that prioritisation back to the International Charter.
In the first hours and days, National Societies and IFRC face a triage problem: with limited teams, relief items and DREF funds, where do they act first? Exposure (UC1) says who was at risk; impact (UC2) says where it hit — but neither, alone, weighs observed severity against pre-existing vulnerability, the history of disasters and response, and the operational reality of who is already there. This use case synthesises the outputs of the first two into a transparent, adjustable prioritisation.
The output is published as a Montandon STAC collection (response-prioritisation) — one item per ranked area, tied to the event by monty:corr_id, with a derived_from link to the EO response product. A single API call returns the ranked areas with their humanitarian context, ready for the Charter Mapper or a Charter chatbot.
At a glance
| ① Risk Exposure | ② Impact Estimation | ③ Response Prioritisation | |
|---|---|---|---|
| When | Before an event (baseline) | During / just after | First 24–72 hours |
| Question | Who & what is at risk? | Who & what was hit? | Where to act first? |
| Trigger | On-demand, user-driven | Automatic on new event | Automatic on new event |
| Core data | INFORM, hazard layers, WorldPop, OSM | Copernicus EMS extents + base layers | UC1 + UC2 + Montandon history + IFRC GO |
| Output | Exposure map & tables per zone | Affected-extent map, time slider, tables | Ranked areas: priority + confidence + rationale |
| Writeback | — | — | STAC collection back to Montandon / Charter |