Data quality Editorial draft

Cloud and shadow screening for optical imagery across sediment-runoff catchments — a validation guide

Explore cloud and shadow screening for optical imagery across sediment-runoff catchments. Practical guidance for validation and defensible observations.

ShareLinkedInFacebookXWhatsApp

Editorial draft. This generated working guide combines technical guidance with an illustrative context and requires individual editorial review.

Editorial illustration: Cloud and shadow screening for optical imagery across sediment-runoff catchments — a validation guide
Original editorial illustration for this article. Shapes and colours are conceptual, not measured observation data.

A method that produces a plausible result has not automatically demonstrated that it works for its intended users. Validation requires a defined question, suitable reference evidence, and an evaluation design that reflects how the method will be used. This perspective examines which observations should be compared, how they should be sampled, and which errors matter in practice. It also considers the difference between evidence used to develop a method and evidence reserved for evaluating it. The objective is a test that can reveal weaknesses as well as confirm useful performance.

This working guide considers cloud and shadow screening for optical imagery across sediment-runoff catchments. The immediate decision is to connect sampling priorities across land and water. Useful reference evidence includes timed water samples, runoff context and land-cover observations. The case is an illustrative planning context, with assumptions to check against the actual sensor, landscape and project requirements.

The setting: Sediment-runoff catchments

A catchment monitoring project connects land-cover patterns, drainage pathways and observations of receiving waters. These evidence streams operate at different spatial and temporal scales. A bare land patch or a bright water plume may be relevant to a sampling question, but an image alone does not establish that one caused the other. Define whether the task is mapping potential source areas, tracking a visible water pattern or evaluating a particular sediment-related variable.

Maintain suitable land and water masks and compare acquisitions with their rainfall and flow context where that information is available. Clouds can obscure the period of greatest interest, and conditions may change rapidly after runoff events. Land adjacency, shallow water and surface reflections can also affect optical interpretation. A useful monitoring record identifies the dates and valid areas supporting each observation instead of presenting a continuous causal story across missing measurements.

Field validation should collect water measurements with clear location, timing and sampling methods, alongside the evidence used to describe land conditions. Sampling only the most obvious plume may overlook other parts of the response or ordinary background variation. More specific source attribution needs an investigation designed for that claim. A practical first product can organise catchment observations and prioritise coordinated sampling, while keeping remotely observed associations distinct from explanations established through additional measurements.

A quality mask changes the evidence available

Clouds and their shadows can produce strong changes in optical imagery that have little to do with the condition of the land beneath them. A quality mask identifies observations that should be excluded or treated cautiously for a particular analysis. It is not simply a cosmetic step used to improve an image. The mask determines which measurements contribute to an index, field statistic or time-series model. Its assumptions therefore belong in the analytical record and should remain available when a result is reviewed.

A scene with a low overall cloud percentage can still be unsuitable for a particular farm. Conversely, a partly cloudy scene may contain useful observations over the target fields. Evaluate quality at the area of interest rather than relying only on scene-level metadata. Cloud edges, haze and shadow boundaries can be difficult to classify consistently. Depending on the application, an additional exclusion around a flagged feature may be appropriate. The effect of that choice on usable coverage should be measured instead of hidden.

Check the mask as part of the result

Inspect representative successful and unsuccessful cases before adopting a mask rule across a large archive. Check whether bright soil, roofs, water or dark vegetation are being confused with cloud or shadow. Compare automatic flags with image context and, where available, independent observations. A mask that removes too much valid data can be harmful, while one that retains contamination can create false alerts. The acceptable balance depends on the downstream task and the costs of missed observations and misleading interpretations.

Each delivered field result should state the acquisition date and the fraction of the relevant area supported by valid measurements. If too little remains, a missing result can be more informative than a precise-looking number based on an unrepresentative fragment. Keep observation gaps visible in charts and maps. When the masking method or product version changes, assess how the update affects historical comparability. Treating cloud and shadow screening as part of the evidence chain makes the final agricultural or environmental interpretation easier to audit and more dependable in practice.

Define a representative reference sample

A reference sample should represent the situations in which a method will be used. Begin by defining the target population: locations, time periods, management conditions, surface types, or instrument states that belong within the intended application. A collection of convenient observations may be valuable for exploration, but it does not automatically support conclusions about that wider population. Make the scope of the sample visible before calculating a summary of performance.

Consider a stratified design when important conditions are unevenly represented. Relevant strata might include different landscape types, developmental stages, observation quality levels, or ranges of the variable being estimated. Choose sample locations within those groups using a documented rule, and retain the information needed to understand their selection. Where access restrictions affect the sample, record the excluded conditions so that the limits of the resulting evaluation remain clear.

Keep development and evaluation evidence separate where the purpose of the study requires an independent test. Nearby observations or repeated measurements can share information, so a random split of individual records may overstate independence. A split organised by location, period, or operational unit can provide a more demanding comparison. The appropriate design follows the intended deployment, the structure of the observations, and the errors that matter to the user.

Locate the uncertainty that matters to the decision

An uncertainty budget is a practical description of where a result could become unreliable. Begin with the observation chain: acquisition, calibration, geographic matching, reference measurements, feature calculation, modelling, and delivery. Identify the assumptions at each stage and ask which could materially change the interpretation. The purpose is not to assign a precise number to every limitation. It is to locate the sources that deserve attention for the intended decision.

Separate limitations that can be measured from those that currently require a qualitative description. Repeated measurements may help characterise variability, while comparisons with independent references can reveal systematic differences. Some uncertainties interact, so combining individual error estimates without examining their relationships can produce a misleading impression of precision. Keep the method of assessment visible and avoid treating an unexamined assumption as though it were a negligible contribution.

Use the budget to prioritise further work. The largest visible source of variation is not always the one whose reduction would most improve the decision. Consider which additional observation, test, or contextual record would change confidence in an actionable way. Revisit the budget when the application, observation source, or deployment conditions change. This turns uncertainty analysis into a guide for improving the workflow rather than a qualification added only after the result has been delivered.

Bring the evidence back to the decision

The validation record should explain the population represented by the test, the reference observations used, and the limitations of the comparison. Report meaningful errors alongside useful successes, and retain examples that challenge the method. Treat wider deployment as a new opportunity to evaluate transfer across relevant conditions. A well-designed validation programme gives users a defensible basis for deciding where the method is useful, where additional evidence is needed, and where another approach may be appropriate.

Sources & further reading

  1. USGS — Landsat Collection 2 Quality Assessment Bands
  2. NASA — HLS atmospheric correction and quality screening

Explore the bhumisat spacecraft concept and our vision towards 2030, or return to the journal.

ShareLinkedInFacebookXWhatsApp
A CONVERSATION STARTS HERE

Build the next
perspective with us.

Tell the TechnoGIS team where you would like to collaborate.

Opens your email app so you can review and send your enquiry.