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 designing ground validation for satellite products in rainfed rice landscapes. The immediate decision is to focus visits after uneven rainfall. Useful reference evidence includes planting dates, field moisture observations and crop stage. The case is an illustrative planning context, with assumptions to check against the actual sensor, landscape and project requirements.
Start with the intended claim
Validation tests how well a product represents a defined quantity under specified conditions. It differs from calibration, which adjusts an instrument or model using reference information. Begin with the claim the product needs to support: class membership, surface reflectance, canopy height, water quality, or an area estimate. State the required spatial scale, time interval, and acceptable error. These choices determine the reference method and sample design. Collecting convenient field points first and deciding later what they prove usually leaves important conditions untested.
Reference measurements also contain uncertainty. Positioning error can place a sample in the wrong satellite pixel, a point instrument may not represent a heterogeneous footprint, and measurements made on different dates can describe real surface change. Record instrument calibration, sampling protocols, timestamps, coordinates, observation conditions, and uncertainty where available. For interpreted labels, retain the evidence used, class rules, and ambiguous cases. Agreement among interpreters is useful to examine, but agreement alone does not guarantee that the shared interpretation is correct.
Keep the assessment independent
Separate validation data from observations used to fit thresholds, train models, select features, or tune processing. If assessment sites repeatedly influence revisions, they have become development data and a fresh independent assessment is needed. Spatially clustered samples can make performance look stronger when neighboring training and test locations share conditions. Use a design that reflects the target population and report its limitations, including inaccessible areas or environmental conditions missing from the sample.
Choose metrics that match the product. For categorical maps, examine a confusion matrix and errors for individual classes, not just overall agreement. For continuous measurements, report bias and a suitable error measure alongside sample count and the range of reference values. Plot residuals against relevant conditions to expose failures hidden by an average. For area estimates, carry the probability sampling design through estimation and uncertainty calculations. Preserve rejected matchups and their reasons so that quality screening remains auditable. A useful validation report explains where the product works, where evidence is sparse, and which errors matter for the intended decision. Publishing reference protocols and assessment code makes later comparisons more credible and helps others reproduce the evaluation.
The setting: Rainfed rice landscapes
Rainfed rice fields often follow planting calendars shaped by local rainfall, water retention and household decisions. Nearby fields may begin their crop cycles at different times, and some areas may remain unplanted during a reporting period. A monitoring system needs to separate these timing differences from potentially unusual crop development. Start with field boundaries and a record of whether a crop was actually established, together with the best available estimate of its establishment date.
Interpreting an image sequence requires attention to both vegetation and the recent water context. Soil background, temporary standing water and incomplete canopy cover can strongly influence early observations. Rainfall information can help describe the season, but it should not be treated as a direct measurement of water available to every field. Differences in drainage, soil properties and topographic position can create contrasting conditions within a short distance.
Use the analysis to select field questions that can be checked, such as delayed establishment or uneven canopy development. Record crop stage, recent management, visible water conditions and the circumstances that affected planting. Where production estimates are proposed, connect them to representative harvest observations rather than relying on an index threshold. Results should show observation dates and missing periods so that users can judge how current the evidence is before arranging an inspection.
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.
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.
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.



