Remote observations show patterns, while practical decisions depend on explaining what those patterns could mean. Interpretation therefore requires more than locating a high or low value on a map. A useful analysis considers the timing of the observation, the physical processes that influence the measurement, and the information available from complementary sources. This perspective separates an observed signal from a proposed explanation and from an action recommended to a user. Keeping those stages distinct makes it easier to investigate alternative causes, communicate ambiguity, and choose a proportionate next step.
This working guide considers designing ground validation for satellite products around active construction sites. The immediate decision is to prioritise sites requiring progress review. Useful reference evidence includes dated site records and consistently located surface observations. The case is an illustrative planning context, with assumptions to check against the actual sensor, landscape and project requirements.
Start with the intended claim
Validation tests how well a product represents a defined quantity under specified conditions. It differs from calibration, which adjusts an instrument or model using reference information. Begin with the claim the product needs to support: class membership, surface reflectance, canopy height, water quality, or an area estimate. State the required spatial scale, time interval, and acceptable error. These choices determine the reference method and sample design. Collecting convenient field points first and deciding later what they prove usually leaves important conditions untested.
Reference measurements also contain uncertainty. Positioning error can place a sample in the wrong satellite pixel, a point instrument may not represent a heterogeneous footprint, and measurements made on different dates can describe real surface change. Record instrument calibration, sampling protocols, timestamps, coordinates, observation conditions, and uncertainty where available. For interpreted labels, retain the evidence used, class rules, and ambiguous cases. Agreement among interpreters is useful to examine, but agreement alone does not guarantee that the shared interpretation is correct.
Keep the assessment independent
Separate validation data from observations used to fit thresholds, train models, select features, or tune processing. If assessment sites repeatedly influence revisions, they have become development data and a fresh independent assessment is needed. Spatially clustered samples can make performance look stronger when neighboring training and test locations share conditions. Use a design that reflects the target population and report its limitations, including inaccessible areas or environmental conditions missing from the sample.
Choose metrics that match the product. For categorical maps, examine a confusion matrix and errors for individual classes, not just overall agreement. For continuous measurements, report bias and a suitable error measure alongside sample count and the range of reference values. Plot residuals against relevant conditions to expose failures hidden by an average. For area estimates, carry the probability sampling design through estimation and uncertainty calculations. Preserve rejected matchups and their reasons so that quality screening remains auditable. A useful validation report explains where the product works, where evidence is sparse, and which errors matter for the intended decision. Publishing reference protocols and assessment code makes later comparisons more credible and helps others reproduce the evaluation.
The setting: Construction site change
A construction site can progress through clearing, ground works, temporary storage, structural development and surface finishing. A satellite image may reveal some visible changes without establishing whether the project has reached a contractual or operational milestone. Define the monitoring objective in terms of observable surfaces and the decisions the information should support. Site boundaries and a reliable sequence of dated records provide the context needed to distinguish project activity from changes in neighbouring land.
The size and arrangement of features determine what the image can resolve. Stockpiles, temporary access routes and partly completed structures may be mixed with other surfaces within an observation. Shadows and acquisition geometry can also change the appearance of buildings. Compare quality-screened observations and retain the dates supporting each mapped change. A map should not imply that every visible feature was measured independently or that its physical dimensions are known more precisely than the data allow.
Validation should use dated site observations that describe the same area and feature definition as the analysis. Record temporary works and other context that might explain an apparent change. A remote observation can help select a site for review, while more specific statements about project progress need relevant project records. Evaluate whether the product provides useful and timely evidence for that review, including examples where a conspicuous image change had an ordinary or temporary explanation.
Prioritise alerts using evidence and consequence
An alert is a request for attention, so its design should consider both the evidence available and the cost of responding. Begin by distinguishing a measured change, a proposed interpretation, and the action expected from the recipient. A large numerical difference is not automatically the most urgent case. The significance of the location, the age of the observation, the confidence in the interpretation, and the consequences of delay can all influence priority.
Create a review queue with enough context to support consistent decisions. Useful information can include the supporting dates, quality qualifications, previous observations, geographic unit, and the reason the case entered the queue. Define when an alert can be closed, escalated, or held for another observation. A documented rule is easier to improve than an informal practice that depends entirely on the memory of the operator reviewing the result.
Collect feedback from inspections and operational responses. Record alerts that led to a useful finding, alerts that required no action, and important conditions that the system failed to flag. Review these outcomes across different settings rather than relying only on a total count of alerts. The objective is a queue that directs limited attention towards meaningful decisions, while generating evidence for adjusting thresholds, improving context, and reducing repeated sources of unnecessary work.
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 strong interpretation states what was observed, which explanations remain plausible, and what additional evidence would help distinguish them. Avoid presenting a convenient label as a confirmed cause when the measurements support only a broader pattern. Connect the proposed next step to the significance of the decision and the confidence available. This creates an interpretation that a field team, analyst, or project partner can examine, challenge, and improve as further observations become available.
Sources & further reading
Explore the bhumisat spacecraft concept and our vision towards 2030, or return to the journal.



