Custom Engineering · Scenario Customization

Custom Water Monitoring Systems

Water monitoring systems combine a moving survey platform with an environment that changes faster than the survey cycle. The design has to absorb that.

5 of 10Method note

Overview

Separate what the aerial platform can observe from what needs a sensor in the water, and state the boundary.
Record environmental conditions with every capture; without them the data cannot be interpreted later.
Design for reachable coverage — bank access, launch points and wind exposure along the water body.
Deliver measurements as indications for sampling, never as compliance values.

Water monitoring has a narrower set of reliable measurements

Aerial water monitoring is valuable for a specific set of measurements and unreliable for others, and the distinction should be drawn before a programme is specified. What works reliably: shoreline and intertidal position, floating and stranded material, structures and vegetation at the water's edge, and — where clarity and depth permit — shallow submerged features. What does not: anything requiring photogrammetric reconstruction over open water, and subtle water-quality parameters that need in-situ sampling.

The reason is physical. Open water is a moving, specular, featureless photogrammetric target, so reconstruction over it fails. Water colour and turbidity can be assessed from imagery but are sensitive to sun angle, sky condition and surface state in ways that make casual comparison invalid. Being explicit about this at the requirement stage prevents a programme being scoped against measurements the method cannot support.

Where a client needs parameters that require sampling — dissolved oxygen, specific contaminants, biological indicators — the aerial component is complementary rather than a replacement: it locates where to sample and shows the spatial context, while the measurement comes from the sample. Configurations are better designed with that complementarity stated than with it implied.

Tidal and seasonal referencing

Shoreline and intertidal work is the most reliable water-related deliverable, and it depends entirely on tidal referencing. Comparing a spring low tide to a neap high tide produces apparent change that is an artefact of the tide rather than a finding about the coast. Every epoch must record its tidal state, and comparisons should be made between like states.

That is a planning constraint as much as a data one: the flight schedule has to be built around the tidal window, not the other way round. On sites with a large tidal range, this materially reduces the number of usable days, and the programme should be planned on that basis rather than discovering it.

Seasonality interacts with the same requirement. Vegetation at the water's edge, water level in rivers and wetlands, and sediment state all vary seasonally. Our shoreline change analysis and aquatic vegetation change notes describe the analysis side; the acquisition discipline they depend on is what we configure.

Glare, wind and the coastal operating environment

Sun glint is the dominant optical problem over water and it is managed by planning rather than by processing: fly when the sun is high, orient lines relative to the sun, and use polarising filters where the sensor supports them. Saturated pixels contain no recoverable information, so a sortie lost to glare is a sortie that must be re-flown.

Coastal wind is stronger, more directional and more variable than inland wind, with sea breezes that build through the day. Plan sorties early, set a conservative wind limit, and establish the operating window by measurement rather than by assumption. Our coastal and water survey configuration note covers this in detail.

Salt air is a maintenance programme rather than a flight consideration, and it should be written into the schedule from the start: a post-sortie rinse and dry routine applied without exception, and shortened inspection intervals on exposed components. Programmes that treat it as optional find the cost in the second season.

Integration and reporting

Water monitoring programmes almost always feed an existing reporting obligation or management system, and the aerial output has to arrive in a form that system accepts. Where the receiving system expects a specific geometry, a specific indicator or a specific time series, adaptation is required, and it is cheaper to establish the format before acquisition than after.

Our data interface adaptation and GIS platform integration work cover this, and human review and reporting workflow covers the review and reporting steps around it.

Where data must stay within the client's own infrastructure — common for environmental work with regulatory or commercial sensitivity — our on-premise deployment and data management work covers that deployment model.

Starting a water monitoring engagement

The path is: identify the measurements required and confirm which the aerial method supports; establish the tidal and seasonal referencing discipline; fix the acquisition conditions that glare and wind require; define the output format and reporting path; then run a pilot pair of epochs and check that the comparison is valid.

Where the client already samples in situ and needs aerial context, we scope the engagement to the spatial component rather than proposing a replacement for the sampling programme.

Send your water body type, the parameters or change classes you need, your tidal and seasonal constraints, your reporting obligations and your receiving system to our engineering team. We will state plainly which measurements the configuration supports and which it does not.