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 rgb satellite imagery for field interpretation in shaded cocoa agroforestry. The immediate decision is to identify sites for canopy assessment. Useful reference evidence includes cocoa canopy and overstory observations collected separately. The case is an illustrative planning context, with assumptions to check against the actual sensor, landscape and project requirements.
The setting: Shaded cocoa agroforestry
A shaded cocoa farm contains multiple vegetation layers whose contributions cannot always be separated in a satellite image. Large shade trees may dominate the upper canopy, while the cocoa plants of commercial interest occupy a lower layer. The first task is to define what the observation is intended to represent. Monitoring tree-cover change, evaluating shade structure and estimating a cocoa parameter are related objectives, but they should not be treated as interchangeable outputs.
Build a farm register that captures boundaries, management units and known differences in shade arrangement. Compare imagery at suitable dates and exclude contaminated observations, while recognising that stable upper-canopy greenness can conceal changes below it. Canopy openings, recent pruning, intercropping and storm damage may alter the signal for different reasons. Contextual information helps turn these patterns into questions for field investigation instead of unsupported explanations about cocoa health.
A validation visit should record cocoa condition and overstory characteristics separately. Photograph or describe the sampled area consistently, and retain its location and date so that it can be related to the observation footprint. Sampling only accessible farm edges risks overlooking different conditions in the interior. Reports should explain whether they describe whole-farm vegetation or a validated cocoa-specific measurement, and identify the additional evidence needed before a management recommendation can be made.
Use visible context carefully
A familiar colour image combines red, green and blue measurements into a display that resembles human visual experience. That familiarity helps people recognise fields, roads, exposed soil, water and settlement patterns. It can also create a false sense that interpretation is effortless. Satellite imagery is influenced by acquisition conditions, processing and display choices. The image may not show the same colours an observer would have seen from the ground. Its value lies in spatial context, supported by a clear account of how the display was produced.
Contrast stretching makes subtle patterns easier to see, but it can make two dates look different even when the underlying reflectance is similar. An automatic stretch selected separately for each image is useful for exploration and less suitable as evidence of a measured change. Keep acquisition dates visible and distinguish a display adjustment from an analytical transformation. When comparing scenes, use a consistent viewing approach and inspect the original values or a suitable quantitative product before drawing a conclusion from colour alone.
Prepare a repeatable visual review
Visible imagery supports a practical first review of a monitoring result. Check whether a field boundary follows the current cultivated area and whether paths, buildings or neighbouring vegetation are included accidentally. Look for management changes that may explain a spectral anomaly, such as harvest, replanting or newly exposed ground. A visual check can identify a plausible explanation and guide field inspection. It should not be presented as proof of a specific disease, nutrient deficiency or production outcome without evidence suited to that claim.
A repeatable review protocol records what the analyst examined and how confidently it could be interpreted. The record can include cloud and shadow presence, obvious mapping errors, the age of the image and any feature requiring confirmation. Use agreed descriptions so that different reviewers can compare their findings. Where a detail is smaller than the available spatial information, acknowledge that limitation and seek a complementary observation. RGB imagery is a useful interface between technical analysis and field knowledge when its visual clarity is accompanied by disciplined interpretation.
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.
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
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.



