Every observation and interpretation contains uncertainty, but the sources and consequences of that uncertainty differ between applications. Some arise from acquisition conditions, others from reference measurements, processing choices, or the transfer of a model to a new setting. This perspective examines how those sources affect the decision a user is considering. It encourages teams to describe uncertainty in a form that can influence action, rather than adding a generic qualification at the end of a report. The objective is to support proportionate decisions while keeping the limits of the available evidence understandable.
This working guide considers atmospheric correction for comparable imagery in open-field tomato production. The immediate decision is to select tomato rows for crop review. Useful reference evidence includes transplanting dates, canopy observations and field management notes. The case is an illustrative planning context, with assumptions to check against the actual sensor, landscape and project requirements.
The setting: Open-field tomato production
Open-field tomato production can involve short management cycles, staggered planting and repeated operations within neighbouring parcels. The field calendar is therefore central to interpreting a satellite observation. Newly transplanted plants, established rows and areas nearing the end of production can show different responses for ordinary reasons. Record the planted area and the relevant management unit carefully, particularly where a commercial holding contains several crops or planting stages at the same time.
The image footprint may mix plants with soil, mulch, access routes and irrigation infrastructure. Determine whether the spatial resolution supports the intended row-level interpretation or whether a broader field summary is more appropriate. Examine the quality and age of observations before proposing a management use that depends on rapid response. A monitoring workflow should communicate when cloud gaps or the acquisition schedule leave insufficient current evidence for that decision.
Validation should document crop stage, canopy continuity, recent operations and the area represented by each sample. Field staff may use a mapped anomaly to choose an inspection location, but the subsequent diagnosis requires suitable observations and expertise. If production or quality is the target, collect reference information for those outcomes rather than assuming that greener vegetation implies more marketable fruit. The evaluation should measure whether the product improves a defined scouting or management process.
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.
Preserve a reproducible processing history
A result should be linked to the inputs and processing choices that produced it. Record source identifiers, software versions, configuration values, reference data versions, and the time of processing. The record does not need to expose every internal implementation detail to the end user. It must preserve enough information for the producing team to investigate a result, reproduce a comparison, and explain why a revised product differs from an earlier version.
Version changes that can affect the meaning of the output. Updated boundaries, a new quality mask, revised calibration, different model parameters, or altered aggregation rules can all change results even when the source imagery is unchanged. Avoid overwriting an earlier product without retaining a suitable history. A clear relationship between versions helps users distinguish an improvement in processing from a real change in the observed surface.
Use representative regression cases when modifying the workflow. Select cases that cover ordinary conditions and known failure modes, then compare meaningful outputs before and after the change. Investigate differences against the intended purpose of the revision rather than assuming that a closer visual match is always preferable. Preserve the review decision with the version record. Reproducibility becomes practical when the team can trace a result through a documented sequence of inputs, transformations, tests, and delivery decisions.
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
Useful uncertainty communication identifies the limitation, explains how it could affect the result, and connects it to a practical response. Some decisions can proceed with a qualified estimate; others require another observation or an independent check. Preserve uncertainty information through processing and delivery so that it is available at the point of use. This makes the analysis more accountable and gives the team a clearer basis for deciding which additional evidence would most improve the outcome.
Sources & further reading
Explore the bhumisat spacecraft concept and our vision towards 2030, or return to the journal.



