Comparisons through time are valuable only when the observations are sufficiently comparable for the question being asked. A difference between dates can reflect real change, a normal stage in a seasonal cycle, or a difference in how the surface was observed. This perspective examines the reference period, the timing of acquisitions, and the contextual records needed to interpret a sequence. It encourages the use of appropriate baselines rather than treating every previous observation as an equivalent benchmark. The objective is to identify changes that remain meaningful after normal variation and measurement conditions are considered.
This working guide considers reading uncertainty in remote sensing products within urban green-space mosaics. The immediate decision is to select green-space locations for assessment. Useful reference evidence includes canopy cover, surface context and appropriately timed measurements. The case is an illustrative planning context, with assumptions to check against the actual sensor, landscape and project requirements.
The setting: Urban green-space mosaics
Urban green spaces form mosaics of trees, grass, bare ground, paths, buildings and water. The observation needed depends on whether the project concerns vegetation cover, land-surface temperature or a particular use of the space. These are distinct variables. Visible and near-infrared imagery can describe vegetation-related patterns, while a temperature study requires suitable thermal measurements and an interpretation that respects what those measurements represent rather than treating greenness as a temperature sensor.
Define park or management boundaries and inspect how surrounding urban surfaces contribute to each observation. Shade, seasonal foliage and maintenance can affect vegetation comparisons, while acquisition timing matters strongly to a thermal interpretation. Data from different instruments may also have different spatial support. A fine-looking display should not suggest that a coarse thermal measurement resolves the same detail as an optical image or an individual tree inventory.
Field validation should record the target variable with methods and timing suited to the intended claim. Canopy observations, surface measurements and information about how people use a site provide different evidence streams. A remotely observed pattern may help choose assessment locations without establishing a complete account of human exposure or park performance. Evaluate the specific management decision, and communicate the scale, observation time and uncertainty that determine how the resulting map can be used.
Identify what the uncertainty describes
A satellite product is the result of a measurement chain, rather than a direct copy of conditions on the ground. Detector noise, calibration, atmospheric correction, geolocation and retrieval assumptions can all affect the final value. Their importance changes with the target. A small location error may matter greatly beside a narrow river, while an imperfect aerosol correction may dominate a water reflectance estimate.
Start by reading the variable definition, units, spatial support and quality documentation. An uncertainty layer may describe an estimated standard deviation, a confidence interval, disagreement among models or another quantity entirely. These measures are not interchangeable. A model's class probability also does not automatically represent a calibrated probability that its label is correct. Check how the quantity was obtained and whether it has been evaluated against independent observations.
Carry uncertainty into the decision
Separate systematic differences from random variation. Averaging many observations can reduce independent random noise, but it does not remove a shared calibration bias. Nearby pixels and repeated observations may share errors, so treating every value as independent can produce confidence intervals that are too narrow. When comparing dates, consider whether the same processing method, sensor characteristics and environmental conditions apply.
Quality flags identify conditions that deserve screening or special treatment. They may indicate clouds, saturation, poor retrieval geometry or inputs outside a method's tested range. Preserve the original flags and record the filtering rule. A strict mask can improve reliability while leaving a sample that overrepresents clear weather or easier terrain. Report missing coverage alongside the measurements that remain.
For a practical assessment, perturb influential inputs within defensible ranges and examine how the result changes. Compare alternative valid processing choices, stratify errors by landscape or season and use independent reference data. Classification summaries should include class specific errors rather than relying on one overall accuracy figure. For continuous estimates, examine bias and the distribution of residuals as well as an aggregate error statistic. A useful final product states the tested domain, describes meaningful limitations and shows whether the uncertainty is small enough for the intended decision.
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.
Design an evaluation that reflects deployment
A model evaluation should resemble the conditions in which the model will be used. Start by identifying which relationships the development data share: nearby locations, repeated observations of the same unit, common collection teams, or measurements from a single period. These relationships can make records less independent than they appear. An evaluation that ignores them may test the ability to recognise familiar conditions rather than the ability to operate in a new setting.
Choose a split strategy that matches the intended transfer. Holding out locations, seasons, operational units, or acquisition conditions can answer different questions. Document which question each split is designed to address, and keep the held-out evidence separate while selecting features and tuning the method. Repeatedly inspecting the same evaluation set to improve a model gradually makes that set part of development, even if it retains its original label.
Report results at a scale that is meaningful to the user. A strong average can hide poor performance for important subgroups or unusual conditions. Examine error patterns and retain examples of both successful and unsuccessful predictions. Where the evidence covers only a limited range of conditions, describe that range explicitly. The evaluation then becomes a practical guide to suitable use, further testing, and the collection of additional reference observations.
Bring the evidence back to the decision
A useful comparison preserves the dates, quality conditions, and contextual assumptions behind its baseline. Review unusual results against the actual observation sequence rather than relying entirely on a summary statistic. Where seasonal timing is important, describe how comparable stages were identified. The resulting analysis should help users distinguish an informative change from an expected cycle or an observation artefact, while making gaps and remaining uncertainty visible enough to guide further investigation.
Sources & further reading
Explore the bhumisat spacecraft concept and our vision towards 2030, or return to the journal.



