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 cloud and shadow screening for optical imagery in cotton production fields. The immediate decision is to prioritise cotton field scouting. Useful reference evidence includes planting dates, growth stage and canopy observations. The case is an illustrative planning context, with assumptions to check against the actual sensor, landscape and project requirements.
A quality mask changes the evidence available
Clouds and their shadows can produce strong changes in optical imagery that have little to do with the condition of the land beneath them. A quality mask identifies observations that should be excluded or treated cautiously for a particular analysis. It is not simply a cosmetic step used to improve an image. The mask determines which measurements contribute to an index, field statistic or time-series model. Its assumptions therefore belong in the analytical record and should remain available when a result is reviewed.
A scene with a low overall cloud percentage can still be unsuitable for a particular farm. Conversely, a partly cloudy scene may contain useful observations over the target fields. Evaluate quality at the area of interest rather than relying only on scene-level metadata. Cloud edges, haze and shadow boundaries can be difficult to classify consistently. Depending on the application, an additional exclusion around a flagged feature may be appropriate. The effect of that choice on usable coverage should be measured instead of hidden.
Check the mask as part of the result
Inspect representative successful and unsuccessful cases before adopting a mask rule across a large archive. Check whether bright soil, roofs, water or dark vegetation are being confused with cloud or shadow. Compare automatic flags with image context and, where available, independent observations. A mask that removes too much valid data can be harmful, while one that retains contamination can create false alerts. The acceptable balance depends on the downstream task and the costs of missed observations and misleading interpretations.
Each delivered field result should state the acquisition date and the fraction of the relevant area supported by valid measurements. If too little remains, a missing result can be more informative than a precise-looking number based on an unrepresentative fragment. Keep observation gaps visible in charts and maps. When the masking method or product version changes, assess how the update affects historical comparability. Treating cloud and shadow screening as part of the evidence chain makes the final agricultural or environmental interpretation easier to audit and more dependable in practice.
The setting: Cotton production fields
Cotton fields can differ in planting time, variety, stand density and management, producing different image trajectories through the season. A monitoring programme should organise those differences before deciding which fields are unusual. Early observations often combine crop and soil, while later management and crop-stage changes can alter the canopy in ways that require contextual interpretation. A reliable field calendar is therefore as important as the choice of a vegetation measure.
Compare observations that meet consistent quality requirements and inspect whether a mapped pattern persists across suitable dates. Field boundaries, tracks, wet areas and neighbouring crops can affect irregular management units. Record the valid area contributing to a summary, especially when clouds or shadows leave only part of a field visible. If several image products are combined, evaluate their alignment and measurement consistency before treating a difference as evidence of crop change.
A scouting visit should collect observations that address the intended decision, such as uneven development or a need for agronomic review. Record crop stage, recent operations and the sampling area consistently. An optical anomaly is not a direct measurement of fibre characteristics or a confirmed diagnosis of a particular problem. Models for commercial outcomes require corresponding reference data and independent evaluation, while inspection products can be assessed through their usefulness in directing representative and timely field visits.
Budget the complete processing workflow
A processing budget should cover the complete path from source observations to a maintained product. Data access and computing are only part of that path. Include preparation, geographic updates, reference collection, expert review, delivery, and support where those activities belong to the service. A calculation that runs cheaply on a small demonstration can still require substantial effort when the surrounding work is repeated across many locations.
Measure representative tasks rather than assuming that every observation costs the same amount to process. Record data volume, processing time, retry frequency, manual interventions, and the conditions that create unusually demanding cases. Separate fixed setup work from work that grows with the number of observations or users. These records support decisions about batching, caching, storage policy, and the point at which a different processing design becomes worthwhile.
Connect the budget to a defined level of service. Faster delivery, more frequent observation, broader coverage, or more detailed review can each change the resources required. Describe these trade-offs before promising a delivery pattern that the workflow has not demonstrated. Review the budget using operational evidence and preserve enough detail to understand changes between processing versions. The aim is a sustainable service whose resource choices remain aligned with the information that users value.
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.



