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 keeping earth observation data usable over time around aquaculture pond clusters. The immediate decision is to prioritise pond-cluster monitoring visits. Useful reference evidence includes pond boundaries, operation status and timed water measurements. The case is an illustrative planning context, with assumptions to check against the actual sensor, landscape and project requirements.
The setting: Aquaculture pond clusters
An aquaculture landscape contains ponds at different operating stages together with embankments, channels, roads and service areas. A satellite observation may support a pond inventory or a broader review of visible water patterns, but it should not be assumed to measure conditions within every individual production unit. Begin with boundaries and a record of pond status. Empty, recently filled and active ponds can have different appearances for ordinary operational reasons.
The size of a pond relative to the observation footprint determines how much embankment or neighbouring water contributes to a measurement. Review alignment and exclude unsuitable mixed areas where necessary. Surface reflections, cloud and atmospheric conditions can complicate optical comparison, while short-term management changes may occur between usable acquisitions. Retain observation dates and quality masks so that the image record does not imply continuous knowledge of rapidly changing pond conditions.
Validation should record the unit, collection time, operational context and the measurement method for any water variable being studied. A sample from one pond cannot automatically validate an adjacent pond or an entire cluster. A colour anomaly may help select a monitoring visit without establishing a particular biological condition or production outcome. More specific estimates require a demonstrated relationship with representative measurements, while inventory and inspection-priority products can be evaluated against the practical decisions they support.
Define the responsibilities around the files
Data governance is the set of practical decisions that makes an archive trustworthy and usable. It covers who can publish a product, who maintains its description, how corrections are approved and how users discover changes. These responsibilities matter even for a small project. Without them, an attractive map may become detached from its source scenes, processing method and known limitations.
Assign stable identifiers to datasets and distinguish a collection from its individual files. Record the producer, contact route, geographic extent, time coverage, coordinate reference system, units and missing value conventions. Describe the processing level and whether the values represent measurements, corrected observations or model estimates. A clear data dictionary is especially important when a compact code or numeric flag carries a meaning that would otherwise remain implicit.
Preserve context as products evolve
Maintain provenance from source acquisition through processing and publication. Preserve source identifiers, algorithm versions, parameter settings and links to validation material. When a correction changes values, create a traceable version rather than silently replacing a file and leaving its description untouched. Explain the reason for the revision and whether earlier analyses should be revisited. Checksums help detect changes or corruption but cannot establish that a scientific interpretation is correct.
Access rules should reflect the actual data and agreements involved. Public satellite imagery does not automatically make every associated field record or derived dataset unrestricted. Location records may reveal sensitive ecological sites, and field photographs may include identifiable people. Review the relevant terms before combining or distributing sources, and express reuse conditions in plain language with a suitable license where appropriate. Preserve acknowledgement and citation requirements alongside the data.
Plan retention, backups and recovery before storage becomes crowded. Keep essential documentation and reproducible processing materials with the deliverable, while identifying intermediate files that can be regenerated. Test that a restored copy opens correctly and has the expected metadata. A release checklist should include file integrity, machine readable metadata, readable documentation and a useful contact path. Periodic stewardship reviews can detect broken links, obsolete formats and orphaned responsibilities. The aim is a product that remains interpretable after the original analyst has moved on.
Prioritise alerts using evidence and consequence
An alert is a request for attention, so its design should consider both the evidence available and the cost of responding. Begin by distinguishing a measured change, a proposed interpretation, and the action expected from the recipient. A large numerical difference is not automatically the most urgent case. The significance of the location, the age of the observation, the confidence in the interpretation, and the consequences of delay can all influence priority.
Create a review queue with enough context to support consistent decisions. Useful information can include the supporting dates, quality qualifications, previous observations, geographic unit, and the reason the case entered the queue. Define when an alert can be closed, escalated, or held for another observation. A documented rule is easier to improve than an informal practice that depends entirely on the memory of the operator reviewing the result.
Collect feedback from inspections and operational responses. Record alerts that led to a useful finding, alerts that required no action, and important conditions that the system failed to flag. Review these outcomes across different settings rather than relying only on a total count of alerts. The objective is a queue that directs limited attention towards meaningful decisions, while generating evidence for adjusting thresholds, improving context, and reducing repeated sources of unnecessary work.
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.
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.



