Skip to article frontmatterSkip to article content
Site not loading correctly?

This may be due to an incorrect BASE_URL configuration. See the MyST Documentation for reference.

Operational response prioritisation

Question: with limited teams, relief items and DREF funds, where do we act first?

Exposure (UC1) says who was at risk, impact (UC2) says where it hit; this notebook weighs observed severity against pre-existing vulnerability, the history of disasters and response, and operational reality — and publishes the ranking back to Montandon for the International Charter.

Source
Source
Source
Area: Karnali · 1 subdivisions
Event: Earthquake in Nepal (Gorkha region) — example event · 20260901-NPL-GEO-EAR-GRO-1-GCDB

Component signals (normalised 0–1)

SignalSourceThis version
Observed severityEO-derived impact (UC2)overlap of each zone with the observed extent, × population density
Vulnerability & coping capacityINFORM Subnational (UC1)synthetic, seeded per zone
Historical burden & recurrenceMontandon past events / DREFMontandon query when a token is set, else synthetic
Operational gap & accessibilityIFRC GO 3W, OSM remotenesssynthetic
Source
Loading...

Composite index, confidence and rationale

Source
Loading...
Source
Source
Source
Source

Write-back: response-prioritisation STAC collection

One item per ranked area with the composite score, components, confidence and rationale, tied to the event by monty:corr_id and linked to the source event with derived_from. The app publishes this collection to Montandon after the run (when MONTANDON_WRITEBACK_ENABLED is set), where the Charter Mapper or a chatbot can fetch it with a single call.

Source
wrote response-prioritisation-20260901-npl-geo-ear-gro-1-gcdb with 1 items to /app/data/work/84481c51-1dc4-4c3f-87bc-28e4b0a5d9b9/outputs/stac