You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(spp_hazard): re-land CAP vocabulary severity with upgrade migration (from #76)
Re-lands the spp_hazard severity->vocabulary change from reverted PR #76,
together with the dependent adaptations in spp_drims, spp_drims_sl_demo and
spp_hazard_programs, plus the two fixes the original PR lacked:
- migrations/19.0.2.1.0/post-migration.py backfills severity_id /
severity_override_id from the legacy 1-5 Selection columns for databases
upgrading from v19.0.2.0.x (release Biliran ships the old schema).
Mapping: 1->minor, 2->moderate, 3->severe, 4->severe, 5->extreme.
- hazard_demo.xml incident-area records now use severity_override_id
vocabulary refs; the stale severity_override field broke demo installs.
Includes migration regression tests (mapping, area override, idempotency,
unmapped values, fresh-install no-op).
- feat: incident areas expose `effective_severity_id` (area override or incident severity) and a numeric 1-5 `severity_numeric` derived from CAP severity codes for choropleth visualization (re-land from #76, follows the spp_hazard severity vocabulary change).
0 commit comments