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 atmospheric correction for comparable imagery during multisensor field campaigns. The immediate decision is to align observations across measurement scales. Useful reference evidence includes coordinated timestamps, sample support and instrument reference records. The case is an illustrative planning context, with assumptions to check against the actual sensor, landscape and project requirements.
Know which reflectance product is being compared
An optical satellite measures a signal that has interacted with both the surface and the atmosphere. Atmospheric correction estimates a surface-related reflectance quantity by accounting for relevant atmospheric contributions under a set of assumptions. This makes many comparisons more meaningful, especially across dates, but it does not turn every pixel into an exact ground measurement. The corrected product still carries uncertainty and may be unsuitable where clouds, strong haze, unusual illumination or difficult surface conditions violate the assumptions used by the processing method.
The processing level should match the analytical purpose. A visually useful image, a top-of-atmosphere reflectance product and a surface reflectance product can all represent the same acquisition while supporting different interpretations. Mixing these products inside one time series can create a discontinuity unrelated to the land. Record the product definition, processing version and quality information. Apply stored scale factors and offsets correctly before using numerical values in an index or model, and avoid assuming that all products from a named mission follow identical conventions.
Evaluate correction quality in the target landscape
A correction method should be examined in the landscape where its output will be used. Water, bright soil, complex terrain and vegetation can pose different challenges. Inspect the associated quality flags and review suspicious patterns against image context rather than accepting every corrected value automatically. Compare multiple dates and include stable reference areas when appropriate. A sudden change affecting many unrelated surfaces may indicate an acquisition or processing issue that deserves investigation before it is interpreted as an agricultural or environmental event.
A robust workflow treats correction quality and observation suitability as related but distinct decisions. Atmospheric correction does not remove clouds from the ground, and it does not resolve all effects of shadow, viewing geometry or surface mixing. Retain a policy for excluding unsuitable measurements and communicating gaps. If a processor update changes the historical record, assess the effect on derived statistics and alerts. The practical aim is a consistently defined observation series whose remaining limitations are understood, so that a user can evaluate a surface interpretation against the quality of its inputs.
The setting: Multisensor field campaigns
A multisensor field campaign brings together observations that may represent different surfaces, times and spatial scales. A ground measurement can describe a small sample, a drone product a local scene and a satellite observation a wider footprint. Their values should not be expected to match automatically. Define the variable of interest and the area represented by each method before treating the campaign as a direct comparison between interchangeable measurements.
Coordination should account for acquisition timing, crop or environmental change, positioning and the conditions relevant to each instrument. Record whether a sample represents a plot interior, an edge mixture or another setting that influences its relationship with imagery. A common coordinate reference helps align the observations, but it does not remove differences in measurement support. Aggregation and comparison rules should be chosen to address those differences explicitly rather than only making the maps look aligned.
The evaluation should preserve uncertainty in both the reference data and the remotely sensed products. Include representative ordinary conditions as well as unusual sites, and keep development samples separate from independent assessment where a model is being tested. A successful relationship within one campaign does not establish transfer to all other settings. The useful outcome is a traceable account of how the observations relate, where they disagree and what those disagreements reveal about the proposed application.
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.
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.



