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 choosing evi, savi and related indices in shaded cocoa agroforestry. The immediate decision is to identify sites for canopy assessment. Useful reference evidence includes cocoa canopy and overstory observations collected separately. The case is an illustrative planning context, with assumptions to check against the actual sensor, landscape and project requirements.
The setting: Shaded cocoa agroforestry
A shaded cocoa farm contains multiple vegetation layers whose contributions cannot always be separated in a satellite image. Large shade trees may dominate the upper canopy, while the cocoa plants of commercial interest occupy a lower layer. The first task is to define what the observation is intended to represent. Monitoring tree-cover change, evaluating shade structure and estimating a cocoa parameter are related objectives, but they should not be treated as interchangeable outputs.
Build a farm register that captures boundaries, management units and known differences in shade arrangement. Compare imagery at suitable dates and exclude contaminated observations, while recognising that stable upper-canopy greenness can conceal changes below it. Canopy openings, recent pruning, intercropping and storm damage may alter the signal for different reasons. Contextual information helps turn these patterns into questions for field investigation instead of unsupported explanations about cocoa health.
A validation visit should record cocoa condition and overstory characteristics separately. Photograph or describe the sampled area consistently, and retain its location and date so that it can be related to the observation footprint. Sampling only accessible farm edges risks overlooking different conditions in the interior. Reports should explain whether they describe whole-farm vegetation or a validated cocoa-specific measurement, and identify the additional evidence needed before a management recommendation can be made.
Choose the index around the landscape
Vegetation indices emphasise selected relationships between spectral measurements. They are alternative views of the same observed surface, not independent diagnoses of a crop. EVI and SAVI were developed to address particular limitations encountered when interpreting vegetation signals, including background and canopy effects. Their usefulness depends on the data and landscape. A workflow should identify which limitation matters in its application before adding another index. Computing many indices without a clear comparison plan can increase complexity while leaving the original question unresolved.
SAVI introduces an adjustment intended to reduce sensitivity to soil brightness when vegetation cover is limited. The adjustment parameter should be chosen deliberately and retained in the processing record. EVI includes additional terms and commonly uses a blue band, making the quality of that measurement relevant to the result. Implementations must use the appropriate reflectance scaling and coefficient conventions. Applying a formula directly to stored integer values without considering offsets and scale factors can produce values that are mathematically calculable yet physically inconsistent.
Test whether the choice improves the decision
Compare candidate indices using the same quality-screened observations, field boundaries and independent evaluation sample. Otherwise a difference in performance might reflect a different set of pixels or dates rather than the index itself. Inspect sparse, intermediate and dense canopy conditions separately. Include soil exposure and recent management operations in the interpretation. A result that appears clearer on a colour map still needs to be tested against the variable of interest or the operational decision the service is expected to support.
The final choice should also account for maintenance and communication. An index that gives a modest improvement but depends on a less reliable band may require additional quality controls. Users should be told which observations were excluded and why a value is missing. Keep the selected method stable during an evaluation period, and version later changes so that historical comparisons remain interpretable. A concise set of well-understood indicators usually supports a stronger service than a long list of unexplained metrics that imply more certainty than the measurements justify.
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.
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.
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.



