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 harmonising satellite observation time series around protected horticulture sites. The immediate decision is to separate structural mapping from crop interpretation. Useful reference evidence includes cover material, structure boundaries and accessible crop observations. The case is an illustrative planning context, with assumptions to check against the actual sensor, landscape and project requirements.
The setting: Protected horticulture sites
Protected horticulture introduces an important distinction between observing a production site and observing the plants inside it. Greenhouse roofs, shade structures and covering materials can dominate the surface signal recorded from above. A satellite image may help map the extent or arrangement of these structures without providing a direct measurement of crop condition beneath them. Define the intended output clearly before selecting features or making claims about a growing operation.
A site inventory should distinguish covered areas, open-field production, service surfaces and neighbouring land cover. Changes in roof materials, maintenance or illumination can alter image appearance independently of the crop. Review the acquisition geometry and the scale at which individual structures are actually resolved. Where the management question requires plant-level information, consider what complementary measurements can be obtained inside the structure rather than assuming an outdoor crop workflow will transfer unchanged.
Validation should record the type and condition of covering materials as well as the boundaries and use of the structures. Crop observations collected inside should retain their own measurement context and should not be treated as though the satellite directly viewed the same surface. A useful initial application may be production-site mapping or monitoring land-use change around facilities. More specific crop interpretations require evidence that connects the observed signal with the underlying variable under the relevant covering conditions.
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.
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.
Represent gaps without inventing observations
A monitoring sequence often contains periods without a usable observation. The reason may be cloud, shadow, missing coverage, a failed transfer, or a quality condition that excludes the data. Begin by representing these states explicitly. A missing observation is different from a low measurement, an unchanged surface, or a confirmed absence of the feature being studied. The distinction should survive both the analysis and the presentation of the result.
Define when a temporal gap is acceptable for the intended decision. A workflow may continue using the latest qualified observation, request another source, or suspend an alert until sufficient evidence is available. Whichever response is selected, show the age of the supporting observation. If interpolation is used for a suitable analytical purpose, preserve the distinction between an estimated value and a directly observed measurement, together with the assumptions needed to interpret it.
Review how gaps affect the coverage of the final evaluation. Locations with frequent missing data may differ systematically from those with regular observations. A performance estimate based only on clear, complete records can therefore describe a narrower population than the service is expected to support. Report usable coverage alongside analytical results and use recurring gaps to guide acquisition planning, reference collection, and the selection of complementary observation methods.
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
Explore the bhumisat spacecraft concept and our vision towards 2030, or return to the journal.



