A convincing image can still contain measurements that are unsuitable for a particular task. Quality control asks whether the inputs, transformations, and outputs meet the requirements of the intended application. This perspective follows evidence through the workflow, from acquisition metadata and reference observations to the final interpretation. It encourages teams to define acceptance conditions before seeing the result, rather than adjusting them to favour a preferred conclusion. The purpose is a repeatable way to distinguish usable observations, observations requiring qualification, and observations that should be excluded from a decision.
This working guide considers mapping flood extent with optical and radar imagery in coastal payload studies. The immediate decision is to connect coastal applications to instrument requirements. Useful reference evidence includes water-reference measurements and documented observation conditions. The case is an illustrative planning context, with assumptions to check against the actual sensor, landscape and project requirements.
Read the water signal in context
A flood extent map describes water visible at a particular observation time. It does not automatically describe maximum inundation, water depth, or the safety of a road. Begin by defining the event window, study boundary, permanent water baseline, and the smallest flooded area the analysis needs to represent. These decisions determine whether individual scenes, a time series, or several complementary sensors are appropriate. A satellite may pass after a short flood has already receded, so absence of mapped water is not evidence that flooding never occurred.
Optical imagery can separate open water from many surrounding surfaces because water strongly absorbs near infrared and shortwave infrared radiation. Clouds, cloud shadows, turbid water, floating vegetation, and dark roofs complicate that interpretation. Radar can observe through cloud and without sunlight, but its response depends on surface roughness, viewing geometry, polarization, and vegetation. Smooth open water often appears dark; wind can brighten it, while flooded vegetation can produce stronger returns. Neither a universal darkness threshold nor a single water index works reliably in every landscape.
Build and qualify an extent product
For optical analysis, use compatible reflectance products, inspect quality flags, and retain explicit masks for cloud and shadow. For radar, apply the corrections required by the selected product, account for terrain effects, and compare acquisitions with similar viewing geometry. A pre-event reference helps distinguish newly inundated land from reservoirs, wetlands, and persistent channels. Elevation and drainage information can expose implausible isolated detections, but a terrain rule should not silently remove real flooding behind an embankment.
Keep observed flood, permanent water, dry land, and unobserved areas as separate classes. Check results against independent reference observations collected close to acquisition time, including difficult boundaries and built environments. Document missed inundation and false alarms instead of reporting only a visually convincing example. Record acquisition timestamps, sensor and processing versions, thresholds, and validation limitations with the exported layer. When several dates are combined, identify the composite period clearly. An exposure overlay can then intersect the qualified extent with roads, settlements, or fields while preserving the distinction between observed water and inferred consequences.
The setting: Coastal payload studies
A coastal satellite payload study should specify which observations the proposed instrument is intended to support. Mapping visible water boundaries, distinguishing broad surface patterns and estimating a particular water variable create different requirements. Coastal measurements can contain contributions from atmosphere, water, seabed, surface reflection and nearby land. The study therefore needs a clear application definition before a spectral configuration is treated as sufficient evidence that a useful product can be delivered.
Early application trials can use suitable existing observations and representative field measurements to examine these requirements. Record the water types, acquisition conditions and spatial scales represented in each trial. A method that behaves well in one setting may not transfer to another coastal environment without further evaluation. Image detail and the ability to separate narrow features should be assessed through the actual measurement chain rather than inferred from the appearance of a concept rendering.
The resulting requirements should address spectral response, calibration, geometry and the timing of usable observations alongside power, pointing and data delivery. Reference campaigns need measurements that describe the target variable under conditions relevant to the intended use. A practical study links each proposed capability to a test and an application need. This allows a future coastal mission concept to develop through evidence rather than relying on a general promise that additional bands alone will resolve every interpretation problem.
Connect observations within a catchment
Water-related observations often depend on processes beyond the immediate pixel or sampling location. Begin by identifying the geographic relationships that are relevant to the question: upstream areas, connected drainage paths, contributing land uses, and the receiving water body. A local pattern may be easier to interpret when placed within that wider setting. The catchment boundary is a useful organising unit, but its suitability should be checked against the process and observation scale.
Combine the remote observation with contextual records that can help explain its timing and spatial pattern. Rainfall, water level, land management, and known interventions can influence what is observed. Preserve the dates and geographic meaning of those records rather than treating them as timeless attributes. Where drainage connections are uncertain or change with conditions, state the limitation and consider whether additional mapping or reference observations would materially improve the interpretation.
Plan reference sampling across locations that distinguish plausible explanations. A set of measurements concentrated at an easily accessible outlet may provide a different view from one that also represents tributaries, source areas, and contrasting conditions. Document how each location contributes to the evaluation. Interpret spatial agreement with care, because connected observations can share influences and may not provide independent evidence. The resulting workflow should connect local measurements with a defensible account of the wider system they help describe.
Plan the evidence needed for calibration
Calibration connects an instrument's recorded response with a measurement that can be interpreted consistently. Begin by identifying which aspects of the response matter to the application: variation across channels, changes with operating conditions, geometric alignment, or differences between repeated observations. A calibration plan should state the quantities being assessed and the evidence needed to determine whether the response is sufficiently characterised for the intended use.
Design tests around controlled and documented conditions. Record the reference source, instrument configuration, exposure settings, temperature conditions, and processing applied to the measurements. Repeat suitable observations to investigate variability and distinguish a consistent response from a single favourable result. The reference itself has limitations, so preserve its characterisation and avoid assuming that every difference originates in the instrument under evaluation.
Connect calibration activities with the expected operating environment and processing chain. A correction that works under one test condition may require further evidence before being applied elsewhere. Define how calibration parameters are versioned, checked, and associated with the observations they support. Include a plan for recognising drift or other changes that could affect interpretation. The outcome should be an instrument response supported by traceable evidence, together with acceptance criteria that remain relevant to the application.
Bring the evidence back to the decision
Quality control is most useful when its results travel with the information being delivered. Preserve the reasons for accepting or rejecting an observation, and expose limitations that could change the user's interpretation. Review recurring failures as clues about the design of the workflow. A clear quality record supports consistent comparisons between operators and processing versions, while helping the team decide whether a problem originates in acquisition, preparation, interpretation, or the underlying observation requirements.
Sources & further reading
Explore the bhumisat spacecraft concept and our vision towards 2030, or return to the journal.



