A useful observation programme begins with a decision that somebody can act on. Before selecting imagery or instruments, define the area of interest, the people responsible for inspecting it, and the time available for a response. This planning perspective connects remote measurements with the practical questions that shape a survey or monitoring service. The aim is to identify which observations would change a decision, how supporting evidence would be collected, and what should happen when information is incomplete. A clear plan makes later technical choices easier to assess against an operational purpose.
This working guide considers designing ground validation for satellite products within cloud-based analysis teams. The immediate decision is to make analytical results reproducible. Useful reference evidence includes input versions, processing parameters and independent product checks. 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: Cloud-based analysis teams
A cloud-based analysis team needs to connect a scientific method with repeatable processing and an interpretable result. The same nominal dataset can produce different outputs when input versions, masks, resampling choices or analytical parameters differ. Begin by defining the product and the decisions it is intended to support. A visually successful demonstration is useful, but it does not establish that the workflow will behave consistently across regions, seasons or repeated processing runs.
The processing record should identify input observations, acquisition times, quality screening, software or method versions and the parameters relevant to interpretation. Preserve missing-data conditions and distinguish an analytical result from a task that merely completed without a technical error. For field-level products, boundary versions and the spatial support used for summaries also matter. These details make it possible to explain why two apparently similar runs produced different maps or numerical values.
Validation should include checks of both the analytical claim and the delivery process. Compare representative outputs with suitable reference observations, and test whether another operator can reproduce the result from the recorded inputs. Retain limitations in the product metadata rather than relying on informal knowledge held by one team member. A dependable cloud service makes a chain of evidence accessible, allowing users to understand what was observed, how it was processed and which conclusions the available validation supports.
Translate the decision into observation requirements
Start with the decision that the information is intended to support. Describe the geographic unit, the time available for acting, and the consequence of an incorrect interpretation. A requirement such as detecting an unusual pattern across management blocks is different from identifying its cause. Keeping that distinction explicit helps a team select measurements that are relevant to the application and prevents later evaluation from drifting towards whatever result happens to be easiest to demonstrate.
Build a compact requirements matrix linking each decision to the evidence needed, the proposed observation source, and an acceptance condition. Include geographic accuracy, temporal relevance, quality screening, and the context required for interpretation. The matrix should also identify the evidence used to justify each requirement. An engineering preference or a convenient data source can inform a study, but neither should silently replace a documented information need.
Review the matrix with the people who will use the result. Ask how their response would change when information is delayed, incomplete, or uncertain. Record unresolved requirements as questions for a pilot rather than converting them into confident specifications. This produces a practical framework for comparing technical options, designing tests, and explaining why an observation is useful to the intended workflow.
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.
Bring the evidence back to the decision
The practical outcome should be a short observation plan that another team can follow. It should name the decision, the required evidence, the responsible roles, and the conditions that trigger a field visit or further analysis. Keep the plan small enough to test, then revise it using the results of real inspections. A useful monitoring workflow improves because its assumptions are examined systematically, and its observations remain connected to decisions throughout the process.
Sources & further reading
Explore the bhumisat spacecraft concept and our vision towards 2030, or return to the journal.



