Yellow River dynamic monitoring & early-warning system
A dynamic monitoring and early-warning system for a river authority: space-air-ground IoT devices se...
View Details →About Ice Floods
Unlike summer floods, the threat is ice, not rain. Understanding the three stages explains the design — every stage has its own module on watch.
Sensing Matrix
Five technical means behind the scenes are not the same job done five times — they are five given conditions of the same equation.
| Source | What it sees | Why it cannot be replaced |
|---|---|---|
| Cameras | Live footage of key reaches, control works and bridges | The only always-on way to actually see the site: ice colour, drift speed and shore-ice extent cannot be read by a sensor |
| Drone patrols | Mobile patrol flights over priority reaches, managed as an address list | Fills the blind spots of fixed points: ice moves, so fly to where the jam is; footage lands straight on the one-map |
| Weather radar | Regional weather processes and temperature trends | Temperature is the first driver of ice: cooling freezes, warming breaks; the forecast needs to know how cold it will be next |
| Hydro stations | Continuous automatic series of stage and discharge | The quantitative baseline: why stage rises at freeze-up and how discharge evolves at break-up is answered by the series |
| Remote sensing | Macro view of ice extent and channel morphology | The view from above: freeze extent across the whole reach cross-checks the ground points |
The frequent question is “can we connect fewer?”. The five sources cover each other's blind spots: cameras see points but not the line, remote sensing sees the line but not the detail, hydro stations give numbers but no picture.
So the integration is all five, each in its place: footage goes to monitor lists and the one-map, series go to live monitoring and the model, macro views go to risk assessment. Remove any one and the forecast loses a given condition.
Many systems treat weather as decoration. Here it is a core variable: temperature decides whether ice forms and whether it melts.
Together with temperature-trend records at control works, the duty officer starts every shift by answering “how much colder than yesterday, and which way is the ice heading”. Forecasting starts from that sentence.
Wall Maps
Login lands on the home page where three ice-flood wall maps are one click away: the operation map answers “how to fight”, the risk map answers “where it hurts”, the deployment map answers “who is where”. The basemap underneath switches four ways.
Pops up the flood-ice emergency operation map: hazard sections, rescue routes and force deployment on one sheet. When a hazard hits, the commander's first screen is it — from “there is a hazard” to “how to fight it” without a meeting.
Pops up the risk map: jam-prone reaches and historically hazardous works, coloured by risk level. Duty rosters follow the risk map — higher-risk reaches get denser watches and more frequent patrols.
Pops up the defence-force deployment map; the duty module lists works names with contact phones. The risk map says where to defend, the deployment map says who goes and how to call — read together, dispatch lands.
Imagery for the site as it is, terrain for the ground, the water-conservancy layer for the works system, vector for annotations and links. One dataset, four readings: assess ice on imagery, deploy forces on terrain, look up works on the water layer.
Map Toolbox
Every icon and button on the map is an entry into one class of works data — the map is the entrance, the data is the point.
| Tool | What it does | Question it answers |
|---|---|---|
| Works pop-up | Click any ICON on the map for flood-defence works info of that area | What is this works, who owns it, what class |
| Temperature trend | Curve of temperature history at control works of river nodes | How cold has it been, which way is the ice heading |
| Node registry | Show the node data of all flood-defence areas at once | The full river inventory, section by section |
| Bridge info | Bridges on priority reaches | Where the jam-prone bridges are and what a jam would affect |
| Custom ring | Draw an area of interest on the map | Mark a reach and hand it to patrol and assessment |
| Distance tool | Measure between any two points | Real distance from hazard to resources, for dispatch timing |
The ring and distance tools deserve a special note: they connect to no data at all, yet they are the two most used buttons in assessment meetings — turning verbal descriptions into circles and lines on the map cuts communication cost by a notch.
AI Pipeline
AI forecasting is not a score in a black box. It is a pipeline: five sensing streams feed one data foundation, the model produces forecasts, forecasts become tiered alerts that reach the flood-control units — every step stays inside the system.
The value of an alert is not “it was issued” but “it reached the person who must act”. Tiers translate a forecast into actions: each level maps to watch density, patrol scope and readiness, triggered down to specific nodes and crews.
With ice alerts logging the alert time, every warning carries a complete chain — when issued, to whom, when answered. An alert stops being a sentence and becomes a traceable record.
The industry often splits them: a forecast model here, a monitoring platform there. The result: a wrong forecast cannot be diagnosed, and an anomalous reading cannot be compared with what the forecast said.
This system keeps them together: monitoring data is the forecast's raw material and its referee. The model says stage will rise; the hydro curve confirms or refutes it within hours; the deviation stays in the system as input for the next iteration.
Reporting Loop
Sensors and AI cover what machines can see; ice observed by human eyes enters the system through field reporting. Five steps turn a field observation into a traceable response.
With five sensing streams covering stage, discharge, footage and macro ice, field reporting can look redundant. But many key signals sit exactly in the sensors' gaps: shore-ice shapes, oddities in small channels, reports from residents — the human eye is the most flexible sensing source.
The “report now” form turns field observations into structured records that sit beside AI alerts in the same consolidation. The more automated the sensing, the more valuable the human report — it covers exactly what machines cannot see.
Ice-flood response plans are organised by flood-defence node: each works has its own plan timeline and guidance documents. When a hazard hits a reach, open that works and the plan is at hand — not one generic document for the whole river.
That is the value of “documents follow the works”: the more urgent the moment, the less time there is to search for documents. Plans granular to the node make response procedural.
FAQ
Different driver: summer floods are driven by rain; ice floods are driven by ice — the river runs with floes, freezes over, and rising water at break-up comes from ice jams, with the risk concentrated at break-up. So the forecast inputs are not only stage and discharge but also air temperature, water temperature and ice observations, and the sensing must additionally cover the ice surface and channel morphology.
The evolution of an ice flood couples air temperature, discharge and channel morphology — hard to quantify by experience alone. AI forecasting puts multi-source data (cameras, radar, hydro stations, remote sensing) into one model that keeps analysing and produces checkable outputs, cross-checked against live monitoring.
Ice is a moving target: run density, freeze position and jam shape all change, and fixed points cannot cover the whole reach. Drones patrol priority reaches by an address list, fill the unseen segments, and their footage lands straight on the one-map.
Air and water temperature directly drive ice formation and melt. Temperature-trend records at control works let duty officers read freezing and melting trends against stage and discharge — a key model input and the first-hand material for break-up assessment.
Deliverables & Results
The most direct change: judgements now stand on data. Stage and discharge no longer travel by phone; ice conditions are covered by five sensing streams; the forecast gives a checkable view of the future; tiered alerts trigger down to nodes and crews.
The second change is at the front line: field reporting replaced paper, records export in one click; phones hang on the works, priority reaches link straight to monitors — dispatch no longer starts with “find the person, then find the number”.
The third change compounds: each winter's observations, alerts and responses stay in the same system, so every year's forecast stands on more history than the last. As agreed, this page shows no client name and no production screenshots.
Building a sensing-plus-forecasting flood monitoring system? The hard parts are how the sources cover each other's blind spots, how forecasting and monitoring cross-check, and how plans hook onto duty rosters.
MORE CASES
A dynamic monitoring and early-warning system for a river authority: space-air-ground IoT devices se...
View Details →An ice-flood AI forecasting and monitoring system for a river authority: cameras, drone patrols, wea...
View Details →A smart application platform for a Yellow River authority: space-air-ground IoT sensing of hydrology...
View Details →Start with our pricing logic, then let's talk requirements — cost structure, technology comparison and acceptance criteria, all laid out in the open.