A convincing image can still contain measurements that are unsuitable for a particular task. Quality control asks whether the inputs, transformations, and outputs meet the requirements of the intended application. This perspective follows evidence through the workflow, from acquisition metadata and reference observations to the final interpretation. It encourages teams to define acceptance conditions before seeing the result, rather than adjusting them to favour a preferred conclusion. The purpose is a repeatable way to distinguish usable observations, observations requiring qualification, and observations that should be excluded from a decision.
This working guide considers radiometric calibration and reflectance consistency across mixed smallholder farms. The immediate decision is to build a reliable farm-level inspection list. Useful reference evidence includes current crop inventory, plot boundaries and representative visits. The case is an illustrative planning context, with assumptions to check against the actual sensor, landscape and project requirements.
Define the quantity that the instrument records
Radiometric calibration establishes a documented relationship between an instrument's recorded output and the physical quantity it is intended to represent. A stored pixel value may be a digital number, a scaled radiance or reflectance value, or another processed representation. Those alternatives should not be treated as interchangeable. The calibration chain explains how the recorded signal becomes an interpretable measurement and which corrections have already been applied. Understanding that chain is essential before comparing dates, combining bands or transferring a model between instruments.
Instrument response can vary across detectors, channels and operating conditions. Calibration therefore concerns more than selecting one conversion coefficient. A study may need to consider offsets, response differences, noise, saturation and changes in behaviour over time. The appropriate characterisation depends on the instrument and its intended use. For a future payload concept, these are requirements to investigate rather than capabilities established by an attractive render. The presence of a multispectral camera alone does not demonstrate that its channels produce consistent, quantitatively comparable observations.
Track consistency through the complete chain
At the product level, begin with the supplier's definitions and metadata. Check scale factors, additive offsets, fill values and valid ranges before deriving an index or statistical summary. Preserve the processing version so that an output can be reproduced later. Inspect whether extreme values correspond to real surfaces or to invalid observations. When a dataset is updated, compare representative old and new results rather than assuming that a familiar file name guarantees an unchanged numerical meaning throughout the archive.
Validation should cover the full chain that supports the stated application. A stable response in a laboratory test is valuable evidence, while operational imagery introduces additional effects from atmosphere, geometry and scene complexity. Use independent references suited to the measurement scale and report the relevant uncertainty. Maintain a record of corrections and their limitations when delivering results to users. A traceable radiometric workflow supports meaningful comparisons and helps separate a change in the observation system from a change in the landscape that a monitoring service is trying to describe.
The setting: Mixed smallholder farms
A smallholder landscape can contain several crops, trees, buildings and paths within a compact area. Ownership boundaries may differ from the boundaries of the crop actually observed, and planting dates can vary between nearby plots. The first useful product is often a reliable inventory of what is being monitored. Record the crop, the planted area and the management question before deciding whether a satellite summary can represent that unit adequately.
Mixed pixels and boundary uncertainty deserve explicit attention. A value displayed over a small plot may include substantial contributions from neighbouring vegetation or other surfaces. Higher visual detail in the map does not remove this limitation. Use observation products appropriate for the plot size, review alignment carefully and retain information about valid coverage. Where satellite data do not resolve the required unit, complementary field observations may be more useful than a finer-looking interpretation.
A practical field programme should sample the diversity of crops, plot sizes and management conditions in the service area. Record location, date, crop stage and the circumstances that explain a mapped pattern. A model developed for one crop or estate should not be assumed to transfer directly to these mixed settings. Evaluate the specific farm-level decision, such as planning visits or updating an inventory, and communicate which conclusions are supported at plot scale and which remain broader landscape observations.
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.
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
Quality control is most useful when its results travel with the information being delivered. Preserve the reasons for accepting or rejecting an observation, and expose limitations that could change the user's interpretation. Review recurring failures as clues about the design of the workflow. A clear quality record supports consistent comparisons between operators and processing versions, while helping the team decide whether a problem originates in acquisition, preparation, interpretation, or the underlying observation requirements.
Sources & further reading
Explore the bhumisat spacecraft concept and our vision towards 2030, or return to the journal.



