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 viewing geometry and brdf effects in humid tropical forests. The immediate decision is to prioritise forest-change inspections. Useful reference evidence includes canopy observations, disturbance evidence and representative plots. The case is an illustrative planning context, with assumptions to check against the actual sensor, landscape and project requirements.
The observed surface has a direction-dependent response
A surface does not necessarily reflect incoming light equally in every direction. Its measured brightness can change as the positions of the Sun, surface and sensor change, even when the surface itself is similar. The bidirectional reflectance distribution function provides a framework for describing this directional behaviour. In practical image analysis, the relevant lesson is that a difference between observations may contain a geometry effect as well as a real surface change. Canopy structure, shadows and surface roughness can all influence that relationship.
The magnitude and pattern of a geometry effect depend on the landscape and spectral measurement. A row crop, closed forest and exposed soil need not behave in the same way. Terrain introduces another layer because slope and aspect alter local illumination. A simple brightness adjustment is not automatically an adequate solution. A workflow should first identify the type of comparison it needs and whether the available product already includes a relevant normalisation. Applying an additional correction without understanding prior processing can create a new inconsistency.
Normalise geometry with a clear purpose
Geometry normalisation uses a model or adjustment to express observations under a more consistent reference condition. It is an approximation designed for a defined purpose, and its performance should be checked rather than assumed. Keep the input geometry, model assumptions and processing version where they are available. Compare representative surfaces before and after the adjustment. A useful test examines whether the correction reduces systematic variation in stable areas while preserving changes that are supported independently by management records or field observations.
For an agricultural service, the importance of this effect depends on the size of the change being interpreted. A subtle trend can be more sensitive to residual geometry variation than a major harvest event. Evaluate whether an apparent improvement in a time series survives across seasons and fields, including those with different canopy arrangements. Retain a clear explanation of what has been normalised and what remains uncertain. Viewing geometry becomes manageable when it is treated as part of the measurement context instead of being attributed silently to crop condition or land-cover change.
The setting: Humid tropical forests
A humid tropical forest presents a complex upper canopy shaped by species mixtures, crown structure, terrain and disturbance history. Optical imagery can describe aspects of that visible surface, but it does not directly inventory every tree or the conditions beneath the canopy. Define whether the intended task concerns cover change, a disturbance alert or a forest parameter before interpreting an image pattern. These objectives require different reference information and different levels of spatial support.
Persistent cloud, shadow and haze can leave gaps in the observation record. A change map should show when usable evidence was available and whether a reported event is constrained to a broad interval between acquisitions. Terrain and canopy shadows can create additional differences that are unrelated to a new disturbance. Combine quality screening with an understanding of the landscape, and retain the dates and valid areas used to establish each mapped observation.
Field validation should distinguish a change in canopy appearance from the explanation for that change. Record plot or inspection locations, the area represented and the evidence used to identify disturbance or recovery. Tree measurements can support structural or biomass studies when collected and analysed for that purpose. A general vegetation index alone cannot establish forest carbon stocks. The practical monitoring product should state what was observed, how confidently it was located and which additional information supports its interpretation.
Locate the uncertainty that matters to the decision
An uncertainty budget is a practical description of where a result could become unreliable. Begin with the observation chain: acquisition, calibration, geographic matching, reference measurements, feature calculation, modelling, and delivery. Identify the assumptions at each stage and ask which could materially change the interpretation. The purpose is not to assign a precise number to every limitation. It is to locate the sources that deserve attention for the intended decision.
Separate limitations that can be measured from those that currently require a qualitative description. Repeated measurements may help characterise variability, while comparisons with independent references can reveal systematic differences. Some uncertainties interact, so combining individual error estimates without examining their relationships can produce a misleading impression of precision. Keep the method of assessment visible and avoid treating an unexamined assumption as though it were a negligible contribution.
Use the budget to prioritise further work. The largest visible source of variation is not always the one whose reduction would most improve the decision. Consider which additional observation, test, or contextual record would change confidence in an actionable way. Revisit the budget when the application, observation source, or deployment conditions change. This turns uncertainty analysis into a guide for improving the workflow rather than a qualification added only after the result has been delivered.
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.



