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 harmonising satellite observation time series 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.
More observations require a common measurement definition
Combining observations from different satellites can increase the information available through time, but the resulting series needs a common analytical definition. Instruments may differ in spectral response, spatial sampling, viewing geometry and processing history. Two bands with similar names are not necessarily equivalent measurements. Harmonisation addresses selected differences so that observations can be used together more consistently. It should be understood as a documented processing approach with remaining limitations, rather than a guarantee that every value from every sensor is interchangeable.
A suitable workflow begins with the variables that need to be compared. Identify the input products, their physical meaning and the transformations already applied. A common grid helps organise observations spatially, while atmospheric correction, geometry normalisation and spectral adjustments may address other differences. These operations have distinct purposes. Applying only one of them should not be described as complete harmonisation. Retain sensor identity and acquisition metadata even when the user sees one combined series, because those attributes remain valuable for diagnosing an apparent discontinuity.
Validate continuity before interpreting a longer record
Test continuity using overlapping or otherwise comparable observations and independent evidence where available. Inspect several surface types and canopy conditions rather than evaluating only one convenient landscape. A consistent average relationship can still hide a meaningful difference for a particular crop or season. Examine how the combined record affects the final product, including index thresholds, fitted timing metrics and change alerts. The relevant question is whether the remaining differences are acceptable for that application, not merely whether the images appear similar on a map.
A longer record also requires a stable policy for quality screening and updates. Changes in input collections, calibration or processing versions can affect historical outputs. Version the workflow and preserve enough information to reproduce earlier results when necessary. When a series crosses a known processing change, evaluate the transition explicitly. A harmonised dataset can provide a strong foundation for monitoring, but field context and validation still determine the usefulness of its interpretation. Maintaining traceability allows additional observations to improve coverage without concealing their origins or implying a precision that has not been demonstrated.
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.
Maintain the geographic units of analysis
Many observation services summarise measurements within a field, management block, catchment, forest unit, or other mapped boundary. The meaning of that summary depends on whether the boundary accurately represents the unit being discussed. Start with a clear source for the geometry and record its date, coordinate reference, and intended use. A boundary drawn for visual orientation may require additional checking before it becomes a measurement unit.
Inspect overlaps, gaps, narrow fragments, and features that may have changed since mapping. A geometrically valid polygon can still describe an outdated operational unit. Ask the responsible team how divisions, mergers, new infrastructure, and management changes are recorded. Where pixels or reference measurements cross a boundary, define how they are assigned or excluded so that results remain comparable between analysts and processing runs.
Version the boundaries alongside the observations. If a unit changes, preserve a relationship between the previous and revised geometry rather than replacing the history without explanation. Comparisons through time should identify whether they use a constant spatial unit or the operational units valid at each date. This makes it easier to distinguish a change in the measured surface from a change introduced by the geography used to summarise it.
Check spatial alignment before comparison
A comparison between images, channels, maps, or field measurements assumes that the observations refer to the same locations at a suitable level of precision. Small alignment errors can become especially important near boundaries or narrow features. Before interpreting differences, inspect whether identifiable, stable features agree between the sources. A common coordinate reference is necessary for many workflows, but it does not by itself demonstrate accurate alignment.
Use control features that are appropriate for the observation scale and remain stable across the comparison period. Evaluate alignment in more than one part of the area, because a single location cannot reveal spatially varying distortion. Record the method used to estimate any correction and retain independent features for checking the corrected result. Where surfaces have genuinely changed, avoid using those changes as evidence of an alignment error.
Propagate the implications of remaining misalignment into the analysis. A workflow may exclude boundary pixels, summarise at a broader scale, or qualify interpretations for small features. The choice should follow the application rather than a preference for visually smooth output. Preserve both the original and corrected geographic references, and document resampling decisions so that future users can understand how measurements were moved onto a common spatial framework.
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.



