/
Transport/
Specialized fields/
Inland waterways and locksInland waterways, measured for every passage.
Barges need water under the keel, clearance under bridges and a lock ready when they arrive. Level and flow sensors along the river, weather stations and cameras at locks report to one record that the waterway authority, lock keepers and skippers share through river information services.
Plan a deploymentHow it worksStation Builder- Industry
- Transport
- Measurements
- 5
- Sources cited
- 4
Transport · Inland waterways and locks
Water under the keel
A barge loads to the water it expects to find downstream. Too little water and it grounds; too much and the next bridge is too low. Waterways that measure levels along every reach let skippers load right, plan every passage and pass every bridge safely.
What is measured
Levels, depths, flows and weather
Gauges at locks, weirs, bridges and critical reaches read water level against the datum; surveys give fairway depth; weirs and gauging sections give flow. Weather stations at locks and bends read wind and visibility, and cameras watch lock approaches and bridges.
- Instruments
- Level gauges · Hydrographic surveys · Weir flows · Weather and visibility · Lock cameras
The base node
A lock node that knows the clearance
Each lock’s node reads its gauges and cameras, signs every value and keeps it through any lost link. It follows levels up and down the reach, computes depth and bridge clearance available now and raises low-water, high-water and visibility notices.
Radio and links
LoRaWAN along the river, cellular home
Gauges along a reach reach a gateway at the nearest lock over LoRaWAN at very low power. Locks report to the waterway centre over the public cellular network along the river, and skippers keep their marine radio while notices reach them through river information services.
- Links
- LoRaWAN · Public cellular · VHF marine radio
How it works
From a falling gauge to a loading plan
A gauge at a shallow reach reads the level falling. The endpoint signs it and sends it over LoRaWAN to the lock node, which computes the depth available and issues a low-water notice through the river information services. Skippers upstream adjust their loads, and the record keeps the notice.
From order to operation · Order
Scope the waterway and its notices
The scope reads the waterway’s locks, weirs, bridges and shallows, the river information services in place and the flood arrangements. Nexus Observatory Inc. returns the point plan by reach, the radio design, the integration with river information services and a price per point and per service.
Plan a deploymentFrom order to operation · Survey
Survey from the bank and the boat
Crews survey with the authority’s engineers from the bank and by boat: stable gauge sites at locks, weirs and bridges, levels of the highest recorded water, gateway coverage along each reach and camera views of lock approaches. They record access in high and low water.
From order to operation · Permits
Banks, structures and the river
Points on locks, weirs and bridges need the authority’s or the owner’s consent, and works in the river need the water authority’s permission. Data sharing with flood managers is agreed in writing, and every consent is kept with the point it covers.
From order to operation · Build
Build for the riverbank
Gauges, weather stations, cameras, endpoints, gateways and nodes are built, tested together and enrolled with their identities. Each is configured for its reach, the datum and its notice levels, and labelled with its river kilometre. Spares are kept at each lock for quick swaps.
Open the Station BuilderFrom order to operation · Install
Install at low water
Crews install at low water: gauges on stable structures levelled to the datum, weather stations at locks and bends, cameras on lock approaches and gateways at the locks. Every point is photographed and located by river kilometre for the record.
From order to operation · Commission
Check against the staff gauge
Each device proves its identity. Levels are checked against staff gauges and the datum, flows against field measurements, weather against a reference. Notices are tested through the river information services to skippers and lock control. Each point joins the record only when every check passes.
From order to operation · Operate
Plan every passage on evidence
Skippers see levels, depth and bridge clearance along their route and load to the water available. Lock keepers see approaches and conditions, and the authority issues notices when water is low or high. Flood managers use the same levels, and every notice is kept on record.
From order to operation · Maintain
Keep levels true to the datum
Gauges are checked against staff gauges and the datum on schedule and after floods, debris is cleared, cameras cleaned and batteries changed on plan. Every change is recorded, so long level series stay consistent for navigation and flood planning. Spares are kept at the locks.
Book field servicesData products
For skippers, lock keepers and flood managers
Skippers and fleet planners receive levels, depth and bridge clearance along their route; waterway authorities issue low- and high-water notices; lock keepers receive approach conditions; flood managers receive the same river levels. Each product carries its datum, siting and calibration.
See the data productsEvidence
Levels skippers can trust
Every reading, notice and check is signed and kept with its time and river kilometre. Levels follow hydrological practice, depths follow hydrographic survey standards, and notices travel through harmonised river information services, so skippers, authorities and flood managers read the same evidence.
- Drawn against
- WMO-No. 168 · IHO S-44 · Directive 2005/44/EC · OGC WaterML
What you get
Hydrometeorological and flood observing networks
Stream gauges, rain gauges, weather radar and automatic weather stations built to WMO practice, reporting through WIS 2.0 where the agency requires it. Delivered as hardware + software, managed service and build-operate-transfer, for national meteorological and hydrological services, river-basin agencies, utilities.
Talk to salesNext step
Plan inland waterways and locks with us
Tell us the site, the measurements and the rules it answers to. We reply with a survey proposal, a design and a scope for inland waterways and locks. An engineer replies with a survey proposal and a scope, and the plan grows from one site to the network you need, at your pace.
Plan a deploymentOpen the Station BuilderOpen the Studio
01The place and its hazards
Where it runs, and what can go wrong.
Operating contextWaterway authorities manage rivers and canals for navigation with locks, weirs and dredged channels. Skippers plan loading on the depth available and pass bridges on the clearance at the current level. River information services share levels, notices and traffic, and the same measurements serve flood management.
Hazards
- Low water limiting loads or closing the waterway
- High water reducing bridge clearance or closing locks
- Strong currents and wind at locks and bends
- Fog and poor visibility
- Lock and weir failures
02What must be measured
What, where, how often, and under which rules.
Each measurement names where it is taken, how often, and the public standard or regulation behind it. Numbers in the sources column open the cited source below.
| Measurement | Where | Cadence | Sources |
|---|---|---|---|
| Water level | Gauges at locks, weirs, bridges and critical reaches | Continuous | 12 |
| Fairway depth | Channels and shallows, from hydrographic surveys | On the authority’s survey schedule and after floods | 3 |
| Flow at weirs | Weirs and gauging sections | Continuous | 1 |
| Wind and visibility | Locks, bends and exposed reaches | Continuous | 4 |
| Lock and bridge images | Lock approaches and bridges | Continuous to lock control | 2 |
03The observation stack
From one base unit to a network.
The same blocks at every scale: instruments and a base node, a site with its radio, a fleet run as one, and a network federated on the open protocol.
- 01
Base unit
A river point: a level gauge or weather station on a LoRaWAN endpoint that signs every value, or a lock node with its cameras.
Build a station → - 02
Site
A reach: points from lock to lock, a gateway at each lock and a cellular link to the waterway centre.
Plan a site → - 03
Fleet
Every reach of a waterway run as one fleet, with one record.
Managed offers → - 04
Network
Waterway authorities, flood managers and skippers exchange levels and notices through river information services and open standards.
The open protocol →
- 01Water level gauge
- 02Flow meter
- 03Compact weather station
- 04PTZ camera
- 05LPWAN endpoint
- 06LoRaWAN gateway
- 07Edge node (Wedge)
- 08Cellular modem/router
- 09Solar array
- 10Pole
Radio and links
LoRaWAN
Gauges along a reach reach a gateway at the nearest lock at very low power.
Radio and links
Public cellular
Locks and gateways report to the waterway centre over the public network along the river.
Radio and links
VHF and UHF radio
Skippers keep their marine radio; level notices reach them through river information services and voice.
Edge computeEach lock’s node follows levels up and down the reach, computes the depth and bridge clearance available now and raises low-water, high-water and visibility notices for the river information services.
PowerGauges run on batteries or small solar panels above the highest recorded water; lock nodes run on lock power with a battery.
04How it works
From the instrument to the product.
One observation’s path, tier by tier, with the interface on every link and a bill of materials below; then how the one node grows to a site, a fleet and federated networks.
Inland waterways and locks: data path
– of 08
01 Instruments Measurement with sensor identity andcalibration 02 Field radio 03 Gateway 04 Node – Wrap in an observation envelope with timequality– Measure quality and uncertainty, attachquality flags– Buffer locally (store-and-forward when thelink drops) 05 Backhaul Commit with transactional outbox andpublish, delivered at least once 06 Site Consumer inbox deduplicates and applieseach record once into governed data 07 Data store Governed product through API, map orexport, correction-aware 08 Products OGC WaterML 2.0OGC SensorThings APIRiver Information Services 09 Power and structure Supplies 12 V DC, 24 V DC, 48 V DC to thefield equipment 01 Water level gauge SDI-12 · RS-485 · Ethernet 02 Flow meter SDI-12 · RS-485 · Ethernet 03 Compact weather station SDI-12 · RS-485 · Ethernet 04 PTZ camera Ethernet 05 LPWAN endpoint Analogue I/O · SDI-12 · RS-485 06 LoRaWAN gateway Ethernet · RF · GNSS antenna 07 Edge node (Wedge) Ethernet · Fibre · USB · RS-485 ·BMC 08 Cellular modem/router Ethernet · USB · RS-232 Site MQTT 5 with Sparkplug B Governed data store Versioned, correction-aware Levels, depth and bridge clearance Low- and high-water notices Lock approach conditions River levels for flood management 09 Solar array RS-485 10 Pole SDI-12 SDI-12 SDI-12 Ethernet LoRaWAN Ethernet Ethernet LTE/NR| Item | Equipment | Data ports | Protocols | Power in |
|---|---|---|---|---|
| 01 | Water level gaugeRadar, pressure or float gauge for river, lake, reservoir or tide level. | SDI-12RS-485Ethernet | SDI-12, Modbus, MQTT 5, OGC SensorThings API | 12 V DC |
| 02 | Flow meterOpen-channel or pipe flow meter (Doppler, ultrasonic, electromagnetic). | SDI-12RS-485Ethernet | SDI-12, Modbus, MQTT 5, OGC SensorThings API | 12 V DC |
| 03 | Compact weather stationAll-in-one or compact station for temperature, humidity, pressure, wind and rain at a site. | SDI-12RS-485Ethernet | SDI-12, Modbus, MQTT 5, OGC SensorThings API | 12 V DC |
| 04 | PTZ cameraPan-tilt-zoom camera for wide-area visual monitoring (wildfire, flood, traffic). | Ethernet | RTSP with ONVIF profiles | PoE, 24 V DC |
| 05 | LPWAN endpointBattery-powered endpoint on LoRaWAN, NB-IoT or LTE-M that carries one or more sensors. | Analogue I/OSDI-12RS-485 | LoRaWAN, OMA LwM2M, CoAP | Internal battery, Energy harvesting |
| 06 | LoRaWAN gatewayMulti-channel LoRaWAN gateway that forwards uplinks to a network server and schedules downlinks within duty limits. | EthernetRFGNSS antenna | LoRaWAN, MQTT 5 | PoE, 12 V DC |
| 07 | Edge node (Wedge)Rugged edge node that boots from signed media, attests itself and establishes a site cell from little or no infrastructure. | EthernetFibreUSBRS-485BMC | MQTT 5, DMTF Redfish, IEEE 1588 PTP, NTP with NTS, OPC UA | 12 V DC, 24 V DC, 48 V DC, AC mains |
| 08 | Cellular modem/routerLTE or NR modem or router that uses a public carrier or private network as backhaul. | EthernetUSBRS-232 | 3GPP E-UTRA air interface, 3GPP NR air interface, OMA LwM2M | 12 V DC, PoE |
| 09 | Solar arrayPV modules with charge controller sized to the site’s load and climate. | RS-485 | Modbus | — |
| 10 | PoleUtility, street or dedicated pole with clamp positions. | — | — | — |
How it scales
01 Instruments Arbitrary qualified sensors and instruments whosemeasurements are ingested with calibration, units,geometry, time, custody and uncertainty. ×n 02 Node The minimum useful deployable unit: server, ruggedappliance, radio node, sensor gateway, satelliteterminal, AI, scientific, vehicle or virtual node. Node Node agent 03 Site The minimum independently operable localgovernance and failure domain: one or more nodesplus local network, identity, policy, evidence,storage, products and operator surfaces.SITE
Node Node Node ×n 04 Cluster An optional scale or specialisation domain forscheduling, shared storage, accelerators or datalocality.CLUSTER
×n 05 Fleet Coordinates plans, acknowledgements,convergence evidence, update campaigns andcorrection propagation across nodes and sites.FLEET
Fleet controller ×n 06 Federation An exchange of products, capabilities, events orwork across approved, independently administeredtrust domains, using explicit trust, policy,data-locality, version and correction contracts.TRUST DOMAIN
TRUST DOMAIN
TRUST DOMAIN
×n Verifier Applications Data in the field Telemetry Control Data upstream Control Data upstream Control Exchange Evidence Events Exchange- Data in the field
- MQTT 5 with Sparkplug B; connectors for LoRaWAN, OPC UA and instrument buses.
- Telemetry
- OpenTelemetry OTLP.
- Control
- TLS 1.3 with mutual authentication; protobuf messages over gRPC or HTTP/2.
- Data upstream
- At-least-once publication with repeat-safe keys over the control channel or NATS JetStream; QUIC MAY be used on lossy links.
- Evidence
- DSSE-signed in-toto statements; SLSA provenance; SCITT transparency receipts.
- Events
- Event envelopes mapped to CloudEvents 1.0; channels described in AsyncAPI 3.
- Exchange
- OpenAPI 3.1; the OGC API family; SensorThings; STAC; WIS 2.0.
05From order to operation
Every step, from the first call to a running site.
The same crew and the same record carry the work from scope to maintenance.
- 01 Order
Scope the waterway and its notices
The scope reads the waterway’s locks, weirs, bridges and shallows, the river information services in place and the flood arrangements. Nexus Observatory Inc. returns the point plan by reach, the radio design, the integration with river information services and a price per point and per service. 2
- 02 Survey
Survey from the bank and the boat
Crews survey with the authority’s engineers from the bank and by boat: stable gauge sites at locks, weirs and bridges, levels of the highest recorded water, gateway coverage along each reach and camera views of lock approaches. They record access in high and low water.
- 03 Permits
Banks, structures and the river
Points on locks, weirs and bridges need the authority’s or the owner’s consent, and works in the river need the water authority’s permission. Data sharing with flood managers is agreed in writing, and every consent is kept with the point it covers.
- 04 Build
Build for the riverbank
Gauges, weather stations, cameras, endpoints, gateways and nodes are built, tested together and enrolled with their identities. Each is configured for its reach, the datum and its notice levels, and labelled with its river kilometre. Spares are kept at each lock for quick swaps.
- 05 Install
Install at low water
Crews install at low water: gauges on stable structures levelled to the datum, weather stations at locks and bends, cameras on lock approaches and gateways at the locks. Every point is photographed and located by river kilometre for the record. 1
- 06 Commission
Check against the staff gauge
Each device proves its identity. Levels are checked against staff gauges and the datum, flows against field measurements, weather against a reference. Notices are tested through the river information services to skippers and lock control. Each point joins the record only when every check passes.
- 07 Operate
Plan every passage on evidence
Skippers see levels, depth and bridge clearance along their route and load to the water available. Lock keepers see approaches and conditions, and the authority issues notices when water is low or high. Flood managers use the same levels, and every notice is kept on record. 23
- 08 Maintain
Keep levels true to the datum
Gauges are checked against staff gauges and the datum on schedule and after floods, debris is cleared, cameras cleaned and batteries changed on plan. Every change is recorded, so long level series stay consistent for navigation and flood planning. Spares are kept at the locks.
06Data products and integration
What it delivers, to whom, and into which systems.
Data products
- Levels, depth and bridge clearanceSkippers and fleet planners
- Low- and high-water noticesSkippers and waterway authorities
- Lock approach conditionsLock keepers
- River levels for flood managementFlood managers
Integration
- River information servicesLevels and notices are delivered to the services skippers already use.
- Flood forecastingLevels and flows are shared through OGC WaterML and SensorThings.
- Lock controlConditions and images reach lock control screens beside its own systems.
Exchanged through OGC WaterML 2.0, OGC SensorThings API, River Information Services.
07Questions buyers ask
Before you scope it.
Do skippers need new equipment?
No. Levels and notices reach them through the river information services they already use.
Can the same gauges serve flood warning?
Yes. Flood managers read the same levels, under their own procedures.
What about fog?
Visibility sensors at locks and bends raise notices when visibility falls.
Are gauges safe in floods?
They are mounted above recorded floods and keep their data through any lost link.
08Resources
The sources behind this page.
Public standards, regulations and guidance, cited where they apply. Each applies only where its jurisdiction or scope does.
- 1Guide to Hydrological Practices (WMO-No. 168)World Meteorological Organization
- 2Directive 2005/44/EC on harmonised river information servicesEuropean Union · 2005
- 3IHO Standards for Hydrographic Surveys (S-44)International Hydrographic Organization
- 4Guide to Instruments and Methods of Observation (WMO-No. 8)World Meteorological Organization
09Related
Use cases and solutions.
Use caseLow-cost stream gauge network
Radar or pressure level sensors with low-power radio and solar power, as a cheaper tier beside a national gauge network.The full use case →SolutionHydrometeorological and flood observing networks
Stream gauges, rain gauges, weather radar and automatic weather stations built to WMO practice, reporting through WIS 2.0 where the agency requires it.Solutions for transport →SolutionTransport and logistics corridor sensing
Road weather, rail condition, port and cold-chain sensing along corridors, with connectivity where coverage ends.Solutions for transport →10Transport: specialized fields
Other fields of this industry.
Specialized fieldRoads and bridges
Road weather and surface state, traffic counts, bridge vibration and scour, and cameras along the corridor, on cellular and fibre to the traffic centre, for safer winters and evidence-based maintenance.The full field →Specialized fieldRailways
Earthworks and structures, track-side weather and flooding, rail temperature and cameras at level crossings, on the railway’s own mobile network and fibre, for fewer speed restrictions and safer lines.The full field →Specialized fieldPorts and terminals
Wind for cranes, water levels and depths, air quality and noise at the boundary, and cameras over the quays, on a private 5G network across the terminal and fibre to the port’s systems.The full field →Specialized fieldAirports
Weather beside the runways, wind shear and visibility support, aircraft noise and air quality in the communities around, on the airport’s fibre and private network, alongside the official aviation weather service.The full field →Specialized fieldRoad and rail tunnels
Air quality and visibility, air flow and ventilation, fire detection, cameras and radio coverage inside the tube, on a radiating cable and fibre with an industrial network kept apart from the internet.The full field →Specialized fieldUrban transit
Passenger counts, station air and climate, escalator and lift condition, traction energy and cameras for metros, trams and buses, on private 5G and fibre, with real-time information riders can use.The full field →Bring us the site.
Plan a deployment, configure a station, model it in the Studio or talk to sales. The form names who receives your details.
Plan a deploymentStation BuilderOpen the StudioTalk to salesRequest a quote