A flood year is counted in hundreds of lives.
people killed in Nigeria's 2022 floods, with more than 1.4 million displaced.
National Emergency Management Agency (NEMA) situation reports, October 2022Someone photographs the painted gauge board on the bridge. Watermark reads the water level, checks the photo, and when the water crosses a line your ward agreed, a named person sends the warning to every phone on the ward list, in your language.
Works in any phone browser. A photo waits on the phone until there is signal, then sends itself.
Send GAUGE OGBE 7.4 to the ward number. No data needed. Send JOIN umuoda to get warnings.
Send the gauge photo to the ward number. The reply is the reading and the state. Needs the ward's WhatsApp line.
Warnings can also go out as voice notes for anyone who does not read. Planned for the pilot.
The gauges exist. The forecasts exist. What is missing is the last mile: a reading from this bridge, this morning, turned into a message the people downstream get in time, in a language they speak.
people killed in Nigeria's 2022 floods, with more than 1.4 million displaced.
National Emergency Management Agency (NEMA) situation reports, October 2022people displaced when the Alau Dam gave way and flooded Maiduguri in September 2024.
NEMA and Borno State Government statements, September 2024in 31 states named at high flood risk for 2024. The outlook names the places; it cannot ring the phone in the compound.
Nigeria Hydrological Services Agency (NIHSA), 2024 Annual Flood OutlookRead from the painted board at Ogbe bridge gauge. The reading shows which digits were seen, how sure the reader was, and how far the phone was from the gauge.
A line drawn through the accepted readings. A jump too big to be real asks for a second photo instead of a warning.
Each ward has its own three lines. When one is crossed the message is proposed, a volunteer confirms, and the send is logged with their name.
A silent gauge in a rising week is itself a warning. The volunteer gets a nudge; the LGA desk sees the gap.
This is the real reader on this server. Your photo goes to the AI, which answers in a fixed form. Code checks the photo, works out the level, compares it with the ward's lines and writes the message. Nothing from this page is stored. If you have no gauge near you, pick one of the sample boards.
Free: — of 5 live reads left today
The sample boards are drawn, not photographed. The checks, the decision and the message are the real ones.
The gauges, wards and phone counts here are a sample set for trying the service. The rules are the real ones.
Steps two to five run on this page in Try it; a whole storm runs in Watch a storm.
A metre board is painted on a bridge pier or a bank post. Its map pin, the wards it serves and each ward's three lines (Watch, Warning, Move) are agreed in a meeting and recorded once.
The AI reads where the water line cuts the scale and answers in a fixed form: the level, the digits it saw, and how sure it is. Blurry or dark photos are refused before anything counts.
Code checks the phone's place against the gauge pin (within 60 m), the time the photo was taken, whether the photo was used before, and whether the reading makes sense next to the last one. A failed check asks for a new photo.
A trend is drawn through the accepted readings. The level is compared with each ward's lines. A crossing becomes a proposal, with the ward, the phones, the town criers and the LGA desk it would reach.
The ward volunteer sees the proposal and the photo behind it, and taps Send or Hold. The message goes by SMS in the ward's languages, and the send is logged with their name.
| Step | The program does | The AI does |
|---|---|---|
| Protect the resident | CODEKeeps phone numbers in the ward list; cuts the photo down to the board before reading and stores only its fingerprint. | Only ever sees the photo of the board. |
| Read the level | CODERefuses blurry photos; rejects answers that are not in the fixed form. | AIReads the water line against the scale; reports the level, the digits seen, how sure it is. |
| Check the photo | CODEPlace within 60 m of the pin, time taken, reuse fingerprint, sense against the last reading. | Does no checking. |
| Decide | CODEDraws the trend; compares with each ward's three lines; writes the proposal. | Never decides a state. |
| Write the message | CODEFills a reviewed template; locks the numbers and place names; checks them again after translation. | AITranslates the template into the ward's languages. |
| Send | CODEWaits for a named volunteer's Send; logs who, when and to how many phones. | Cannot send anything. |
A made-up storm at a sample gauge, run on the server through the same checks and decision code the real gauges use, then replayed here. The counters end on what the code counted.
On the way to the farm, phone in hand
The named person who confirms
Every gauge on one screen
The state agency, across the season
Phone numbers belong to the ward list and are shown masked. They are never exported or shown to anyone outside that ward's volunteers.
After reading, only the photo's fingerprint, the level and the checks are stored. Faces, compounds and number plates never reach the database.
Each send is logged with the volunteer who confirmed it, the time and the number of phones reached. A held proposal is logged too, with the reason.
If the reader is down, residents and volunteers type the level from the board. The same place, time, reuse and line checks still run.
The checks below load from the latest test run of this code. If a safety check fails, the release does not go out. The reader is not yet accurate enough on our test boards: 0 of 4 within 10 cm. We show this until it passes.
| Check | Must reach | Latest result |
|---|---|---|
| Reading within 10 cm on the test boards | ≥ 98% | loads from the latest test report |
| Blurry or dark photos refused | 100% | loads from the latest test report |
| Reused photos caught | 100% | loads from the latest test report |
| Line decisions correct per ward | 100% | loads from the latest test report |
| Numbers and place names survive translation | 100% | loads from the latest test report |
| No send without a named confirmer | 100% | loads from the latest test report |
| Board | Drawn level | AI said | Code took | Error | Time |
|---|
Three riverside LGAs, in the dry season. Walk the banks with residents and the ward development committees. Agree the gauge sites and the three lines per ward, in the room, on a map.
Paint the 30 boards. Test the reader on photos of those boards. Connect the SMS line and the LGA dashboard. Run the checks.
Volunteers named per ward. Readings every morning, more when it rains. SEMA on the dashboard. Every warning and every hold logged.
SEMA hosts its own copy. New LGAs are added in the order of the NIHSA outlook. Gauges are re-painted each dry season and the test photos refreshed.
LGAs, State Emergency Management Agencies, NEMA, NIHSA, ward development committees, and the town criers of the traditional rulers.
Free to residents and wards. LGAs, states and donors pay for the plans, the gauges and the SMS bill.
The reader, the checks and the dashboard are open. A state can run it on its own servers with its own gauge list.
Residents and wards never pay to send a reading or get a warning. An office pays for a bigger month: more photo readings, more messages, more people. Prices are in naira a month and can be paid by card, or switched on by request with an invoice.
One ward or a small office, trying it out
A ward development committee or a riverside community
A local government disaster desk
A State Emergency Management Agency
Card payment is through Paystack. If card payment is not switched on yet, ask for the plan from your Plan page and we switch it on by hand and send an invoice.