Data quality Editorial draft

Cloud and shadow screening for optical imagery along shallow reef-adjacent coasts — a seasonal comparison guide

Explore cloud and shadow screening for optical imagery along shallow reef-adjacent coasts. Practical guidance for seasonal comparison 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 along shallow reef-adjacent coasts — a seasonal comparison guide
Original editorial illustration for this article. Shapes and colours are conceptual, not measured observation data.

Comparisons through time are valuable only when the observations are sufficiently comparable for the question being asked. A difference between dates can reflect real change, a normal stage in a seasonal cycle, or a difference in how the surface was observed. This perspective examines the reference period, the timing of acquisitions, and the contextual records needed to interpret a sequence. It encourages the use of appropriate baselines rather than treating every previous observation as an equivalent benchmark. The objective is to identify changes that remain meaningful after normal variation and measurement conditions are considered.

This working guide considers cloud and shadow screening for optical imagery along shallow reef-adjacent coasts. The immediate decision is to select coastal habitat survey areas. Useful reference evidence includes water conditions, survey timing and mapped substrate observations. The case is an illustrative planning context, with assumptions to check against the actual sensor, landscape and project requirements.

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.

The setting: Shallow reef-adjacent coasts

A shallow coastal image can contain a mixture of water-column effects, bottom reflectance, surface reflection and adjacent land. The contribution of the seabed depends on conditions that vary across space and time. A monitoring task should therefore identify what can reasonably be observed at the selected scale. Mapping broad substrate patterns or selecting survey locations is different from diagnosing the condition of individual coral colonies or other small habitat features.

Review water clarity, depth context where available, cloud, atmospheric quality and sun glint before interpreting a spectral difference. Changes in the water above the bottom may alter the image without a corresponding change in the substrate. Shorelines and narrow reef features are also sensitive to mixed pixels and alignment. Comparisons should retain their acquisition dates and processing assumptions so that users can understand what environmental conditions support the proposed interpretation.

Field surveys should document the area represented by each observation and distinguish substrate descriptions from measurements of biological condition. Survey timing and water conditions matter when relating those records to imagery. A broad remotely sensed class cannot validate every feature inside its footprint. Use representative and independent assessment locations where possible, and communicate where the result supports a landscape-scale interpretation or a survey priority rather than a fine-scale ecological conclusion.

Keep an auditable review record

A review record should explain how a result moved from an analytical output to an accepted interpretation or operational decision. Preserve the product identifier, the evidence considered, the reviewer role, and the outcome of the review. A short, consistent record is often more useful than an extensive free-text note that cannot be compared between cases. The objective is to make important decisions traceable without turning routine review into unnecessary administrative work.

Separate observations from conclusions within the record. Describe the evidence visible to the reviewer, the alternative explanations considered where relevant, and the reason for accepting, qualifying, or rejecting the result. If a correction is required, identify what should change and how the revised product relates to the earlier version. Keep unresolved questions visible so that they can be addressed by another observation or by the person responsible for the next action.

Use the accumulated record to improve the workflow. Recurring review reasons can reveal unclear requirements, missing contextual information, unstable processing steps, or an evaluation gap. Examine whether similar cases receive similar decisions across reviewers and over time. Preserve the relationship between feedback and subsequent revisions so that improvements can be assessed against the evidence that motivated them. An auditable record supports learning, accountability, and consistent delivery while allowing the technical process to evolve.

Deliver quality flags that users can interpret

Quality information should describe the condition of an observation in terms that remain useful through the workflow. A single valid or invalid label may be sufficient for some calculations, but operational users often need to know why an observation was qualified. Distinguish acquisition limitations, processing failures, uncertain reference matches, and conditions that make interpretation ambiguous. These categories point towards different responses and should not be merged without a clear purpose.

Define a small, documented set of flags with stable meanings. Record whether a flag applies to a complete scene, a geographic unit, an individual measurement, or a derived result. A unit containing a mixture of qualified and unqualified observations may also require a coverage measure. Include the rule used to combine flags when summarising data so that a favourable average does not conceal a substantial fraction of unusable input.

Test the flags with the people receiving the product. Ask what they would do differently for each state and whether the terminology supports that choice. Keep the original flags available even if the interface presents a simpler summary. When flag definitions change, version the rules and review their effects on historical comparisons. Useful quality communication makes the condition of the evidence visible at the moment when a user decides how much confidence to place in the result.

Bring the evidence back to the decision

A useful comparison preserves the dates, quality conditions, and contextual assumptions behind its baseline. Review unusual results against the actual observation sequence rather than relying entirely on a summary statistic. Where seasonal timing is important, describe how comparable stages were identified. The resulting analysis should help users distinguish an informative change from an expected cycle or an observation artefact, while making gaps and remaining uncertainty visible enough to guide further investigation.

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.