Somalia Riverine Flood Trigger / operational note

The new Google model and the Gu windows

Google has released a new version of the flood model behind Flood Hub (November 2026). The two Gu windows run on Google. This page replays them on the new model with exactly the method used to design them on the old one: the same seven points, the same March–May season, the same 1999–2023 calibration years, the same return periods and vote counts. Only the per-point levels are refitted, on the new model's own record. The Deyr windows and the readiness leg run on GloFAS and do not change. 4 November 2026.

4 → 3
Gu Juba activations 1999–2023, old → new
4 → 4
Gu Shabelle activations 1999–2023, old → new
1-in-3.2 → 1-in-3.7
all four windows together, old → new
2–10 days
later on the new model, wherever both models meet the rule (record or forecast)

1What changes

Before Google switches Flood Hub to the new model. On 4 November 2026 the Flood Hub API still serves the old model (same gauge identifiers, unchanged warning levels). The monitoring pipeline reads Google with Gu levels fitted on the old model, frozen in the pipeline's threshold file. If the API moves to the new model before those levels are refitted, the old levels would sit far below the new model's ordinary Gu flows: on the new record they would have activated Gu Juba in 12 and Gu Shabelle in 5 of the 25 Gu seasons 1999–2023. The refitted levels are the "new level" columns below. Signals that the switch has happened: Flood Hub's warning levels or gauge model identifiers change for these gauges, or the gauge identifiers move from hybas_ to subhybas_ as in the new dataset (not confirmed).

2The two versions

Old model (design)New model (November 2026)
Record (reanalysis)1980 – Dec 2023Dec 1980 – Dec 2025
Forecast archive (reforecast)issued Jan 2016 – Jun 2023, leads 0–7 daysissued Jan 2016 – Dec 2025, leads 0–10 days
Modellumped, one model per basinsemi-distributed, routed along the HydroBASINS river network
Pointsthe same seven HydroBASINS basins, with identical outlet coordinates (Dollow on the Juba main stem, as live)

Both versions label days the same way (the record for day T equals the forecast issued on day T+1 at lead 0), so the trigger page's reading of forecast dates applies to both unchanged. Leads 8–10 of the new forecast archive are not used here, to keep the action leg as designed.

3Gu Juba: 3 of 4 points over their 1-in-5 level

Each row of the grid is one series, each column one year. River gauges: F a flood season (two gauges over their own 1-in-3 level), S a severe one (two over 1-in-5). Model rows give the most points over their own level on any one day of March to May; a filled cell is a year the rule is met (at least 3). Forecast rows mark a year in which one forecast, at leads of 1 to 7 days, met the rule. Years 1999–2023, the years both versions cover; forecasts 2016–2023, the Gu seasons both forecast archives cover (hatched before). Hover a cell for details.

99000102030405060708091011121314151617181920212223
River gaugesFFFSSS
Old model: points over0000001000020040040404000
New model: points over0000000000000020040404002
Old model: forecast●●●
New model: forecast●●●
Old modelNew model
Activations 1999–20234 (1-in-6.5)3 (1-in-8.7)
Severe Gu seasons caught2 of 32 of 3
Severe Gu seasons missed20232023
Activations outside a Gu flood season2013none
Median correlation with the SWALIM gauges, March–May0.860.88

When the rule is met

First day the model's own record meets the rule, and first forecast issue date that meets it (leads 1–7 days, read as on the trigger page: valid day = issue day + lead). The last two columns are the reference from the river gauges: the day the second gauge crossed its own 1-in-3 level, and how the gauges classed the season.

YearRecord: oldRecord: newChange Forecast: oldForecast: newChangeGauges over 1-in-3Gauge season
201312 Apr––––––no flood
20167 May14 May7 days later1 May8 May7 days later1 Mayflood
201821 Apr24 Apr3 days later15 Apr18 Apr3 days later17 Aprsevere
202030 Apr4 May4 days later24 Apr28 Apr4 days later22 Aprsevere
Old model New model the rule's level (100%)

Daily flow at the point ranked 3rd highest of 4, as a share of that point's own 1-in-5 level, March to May, on each model's record. The rule is met on days the line reaches 100%; dots mark the first such day. Years shown: every year from 1999 to 2023 in which either model or either forecast met the rule.

Levels at each point

1-in-5 level fitted on the March–May seasonal maxima 1999–2023 of each model's own record (Weibull plotting position, as in the trigger analysis) and mean March–May flow (m³/s), and the best-lag rank correlation with the point's SWALIM gauge, computed as in the trigger page's station table.

PointOld levelNew levelNew / old Old meanNew meanOld correlationNew correlation
Dollow5088451.66x1662370.860.88
Luuq4338331.92x1262310.870.89
Bardheere3778092.14x1052190.860.88
Bualle3917962.04x1052080.880.87
Other return periods, same vote count
LevelOld model, yearsNew model, years
1-in-32003, 2010, 2013, 2016, 2018, 2020, 20232005, 2010, 2013, 2016, 2018, 2020, 2023
1-in-42010, 2013, 2016, 2018, 20202010, 2013, 2016, 2018, 2020, 2023
1-in-52013, 2016, 2018, 20202016, 2018, 2020
1-in-62013, 2016, 2018, 20202016, 2018, 2020

4Gu Shabelle: 2 of 3 points over their 1-in-6 level

Each row of the grid is one series, each column one year. River gauges: F a flood season (two gauges over their own 1-in-3 level), S a severe one (two over 1-in-5). Model rows give the most points over their own level on any one day of March to May; a filled cell is a year the rule is met (at least 2). Forecast rows mark a year in which one forecast, at leads of 1 to 7 days, met the rule. Years 1999–2023, the years both versions cover; forecasts 2016–2023, the Gu seasons both forecast archives cover (hatched before). Hover a cell for details.

99000102030405060708091011121314151617181920212223
River gaugesFFFSFSS
Old model: points over0000000000000030030303000
New model: points over0000000000000000030303003
Old model: forecast●●●●
New model: forecast●●●●
Old modelNew model
Activations 1999–20234 (1-in-6.5)4 (1-in-6.5)
Severe Gu seasons caught2 of 33 of 3
Severe Gu seasons missed2023none
Activations outside a Gu flood season2013none
Median correlation with the SWALIM gauges, March–May0.790.89

When the rule is met

First day the model's own record meets the rule, and first forecast issue date that meets it (leads 1–7 days, read as on the trigger page: valid day = issue day + lead). The last two columns are the reference from the river gauges: the day the second gauge crossed its own 1-in-3 level, and how the gauges classed the season.

YearRecord: oldRecord: newChange Forecast: oldForecast: newChangeGauges over 1-in-3Gauge season
20136 May––––––no flood
201612 May15 May3 days later30 Apr9 May9 days later11 Maysevere
20185 May7 May2 days later27 Apr1 May4 days later7 Mayflood
202030 Apr9 May9 days later22 Apr2 May10 days later5 Maysevere
2023–9 May–26 Apr3 May7 days later17 Aprsevere
Old model New model the rule's level (100%)

Daily flow at the point ranked 2nd highest of 3, as a share of that point's own 1-in-6 level, March to May, on each model's record. The rule is met on days the line reaches 100%; dots mark the first such day. Years shown: every year from 1999 to 2023 in which either model or either forecast met the rule.

Levels at each point

1-in-6 level fitted on the March–May seasonal maxima 1999–2023 of each model's own record (Weibull plotting position, as in the trigger analysis) and mean March–May flow (m³/s), and the best-lag rank correlation with the point's SWALIM gauge, computed as in the trigger page's station table.

PointOld levelNew levelNew / old Old meanNew meanOld correlationNew correlation
Belet Weyne3464341.25x95990.810.89
Bulo Burti3624311.19x94980.790.90
Jowhar3614281.18x94950.780.84
Other return periods, same vote count
LevelOld model, yearsNew model, years
1-in-32000, 2005, 2010, 2013, 2016, 2018, 2020, 20232005, 2010, 2013, 2016, 2018, 2020, 2021, 2023
1-in-42005, 2010, 2013, 2016, 2018, 20202005, 2010, 2016, 2018, 2020, 2023
1-in-52005, 2013, 2016, 2018, 20202010, 2016, 2018, 2020, 2023
1-in-62013, 2016, 2018, 20202016, 2018, 2020, 2023

5All four windows together

The allocation is sized on the union of the four windows. Deyr runs on GloFAS version 5 as designed and is the same in both rows (2006, 2023 on the Juba, 2006, 2014, 2019, 2023 on the Shabelle). Severe years are those in which two gauges on a river crossed their own 1-in-5 level in either season (2006, 2014, 2016, 2018, 2019, 2020, 2023).

Gu windows onActivationsReturn periodYearsSevere caughtSevere missedOutside a flood season
Old model81-in-3.22006, 2013, 2014, 2016, 2018, 2019, 2020, 20237 of 7none2013
New model71-in-3.72006, 2014, 2016, 2018, 2019, 2020, 20237 of 7nonenone

The windows were calibrated jointly to about 1-in-3 on the old model. On the new model the same settings activate less often (1-in-3.7). Whether to re-tune for the new model is a design decision for the working group; this page only shows the adopted settings carried over.

6New model only: 2024 and 2025

The new record and forecast archive run two years past the old ones, so these years have no old-model counterpart and are kept out of every comparison above. Levels are still those fitted on 1999–2023; the gauge season uses the same gauge levels on the gauges still reporting.

WindowYearMost points over on one dayRecord Forecast (leads 1–7)Gauge season
Gu Juba20244 of 4met, 10 Maymet, issued 5 Mayflood
Gu Juba20250 of 4not metnot metnot assessable
Gu Shabelle20240 of 3not metnot metsevere
Gu Shabelle20250 of 3not metnot metno flood

7Method

Generated 4 November 2026 by scripts/build_google_model_page.py (numbers in scripts/google_model_update.py) in ds-aa-som-floods. Design pages: trigger summary, analysis. Related: GloFAS version switch. Live: monitoring.