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 designing reproducible cloud processing workflows around protected horticulture sites. The immediate decision is to separate structural mapping from crop interpretation. Useful reference evidence includes cover material, structure boundaries and accessible crop observations. The case is an illustrative planning context, with assumptions to check against the actual sensor, landscape and project requirements.
Move the computation with a clear plan
Cloud processing can place analysis near a large satellite archive and reduce repeated transfers to a local computer. Its value depends on the workload. A small study may be easier to complete with a few downloaded scenes, while a continental time series benefits from selective reads and distributed processing. Begin with the geographic extent, dates, variables and output resolution that the analysis actually needs.
Inspect the storage format before choosing an execution pattern. Tiled imagery can support reading only intersecting blocks, and chunked multidimensional arrays can support selected time and spatial slices. These benefits depend on how data are organized and how the reader accesses them. Repeatedly opening complete remote files for tiny requests can waste time and bandwidth. Match processing chunks to source layout where practical, and avoid creating more small tasks than the scheduler can manage efficiently.
Make each run explainable and recoverable
Keep source identifiers, processing versions, input checksums where available, parameters and software dependencies with the workflow. Explicitly record projections, resampling methods, scale factors, masks and time aggregation rules. An output filename alone cannot capture these decisions. A small manifest linking inputs to outputs is useful when an archive is reprocessed or a result must be reproduced months later.
Develop on a representative subset that includes awkward cases such as missing bands, empty intersections and scenes with extensive cloud. Check numerical results and output metadata before expanding the workload. Design individual tasks so they can safely restart without duplicating completed results. Write intermediate output to a temporary location, verify it, and only then mark the task complete. Retain useful logs without recording access credentials.
Estimate storage, compute and data transfer costs together. Compression, unnecessary copies and repeated intermediate materialization can change the budget substantially. Monitor resource use during a pilot run and establish sensible limits before launching a large batch. Permissions should give each process the access it needs, and credentials should come from an appropriate secure mechanism. Finally, export an accessible result with provenance and quality information. A fast calculation becomes useful science only when another person can understand and inspect what was produced.
The setting: Protected horticulture sites
Protected horticulture introduces an important distinction between observing a production site and observing the plants inside it. Greenhouse roofs, shade structures and covering materials can dominate the surface signal recorded from above. A satellite image may help map the extent or arrangement of these structures without providing a direct measurement of crop condition beneath them. Define the intended output clearly before selecting features or making claims about a growing operation.
A site inventory should distinguish covered areas, open-field production, service surfaces and neighbouring land cover. Changes in roof materials, maintenance or illumination can alter image appearance independently of the crop. Review the acquisition geometry and the scale at which individual structures are actually resolved. Where the management question requires plant-level information, consider what complementary measurements can be obtained inside the structure rather than assuming an outdoor crop workflow will transfer unchanged.
Validation should record the type and condition of covering materials as well as the boundaries and use of the structures. Crop observations collected inside should retain their own measurement context and should not be treated as though the satellite directly viewed the same surface. A useful initial application may be production-site mapping or monitoring land-use change around facilities. More specific crop interpretations require evidence that connects the observed signal with the underlying variable under the relevant covering conditions.
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.
Define a representative reference sample
A reference sample should represent the situations in which a method will be used. Begin by defining the target population: locations, time periods, management conditions, surface types, or instrument states that belong within the intended application. A collection of convenient observations may be valuable for exploration, but it does not automatically support conclusions about that wider population. Make the scope of the sample visible before calculating a summary of performance.
Consider a stratified design when important conditions are unevenly represented. Relevant strata might include different landscape types, developmental stages, observation quality levels, or ranges of the variable being estimated. Choose sample locations within those groups using a documented rule, and retain the information needed to understand their selection. Where access restrictions affect the sample, record the excluded conditions so that the limits of the resulting evaluation remain clear.
Keep development and evaluation evidence separate where the purpose of the study requires an independent test. Nearby observations or repeated measurements can share information, so a random split of individual records may overstate independence. A split organised by location, period, or operational unit can provide a more demanding comparison. The appropriate design follows the intended deployment, the structure of the observations, and the errors that matter to the user.
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.



