A workflow that succeeds on a small study area may encounter different constraints when the number of observations, locations, or users increases. Scaling requires attention to processing capacity, data organisation, reference coverage, and the effort needed to review results. This perspective looks beyond whether a calculation can run on a larger dataset. It asks whether the complete service can preserve its meaning, quality, and delivery commitments as its scope expands. The objective is a design that identifies bottlenecks early and increases throughput without silently weakening the evidence available to users.
This working guide considers radiometric calibration and reflectance consistency within mission readiness studies. The immediate decision is to connect mission claims to measured evidence. Useful reference evidence includes documented requirements, test results and unresolved design questions. The case is an illustrative planning context, with assumptions to check against the actual sensor, landscape and project requirements.
The setting: Mission readiness studies
A mission readiness study connects the intended application with the evidence available from the spacecraft and ground system. A target launch year or an attractive rendering can help communicate a vision, but neither establishes that the observation service is ready. Begin with the capabilities the mission is supposed to demonstrate and identify how each will be assessed. Requirements should remain traceable to user needs rather than accumulating as an unrelated list of desirable specifications.
The review should consider the observation payload, pointing, power, communications, processing and delivery as parts of one chain. A promising subsystem test may still leave an important gap elsewhere in that chain. Record the conditions under which each result was obtained, the applicable uncertainty and the design version it represents. Changes in architecture or application requirements should trigger a review of which earlier evidence remains relevant and which measurements need to be repeated.
Progress can be organised around clear evidence milestones, including application trials, integrated testing and documented end-to-end demonstrations. Keep unresolved questions visible and distinguish a proposed capability from a measured one. A finding that leads to a design change is valuable information when it improves the match between the mission and its intended use. The practical result is a defensible account of readiness, remaining work and the conditions that must be satisfied before a stronger public performance claim can be supported.
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.
Deliver quality flags that users can interpret
Quality information should describe the condition of an observation in terms that remain useful through the workflow. A single valid or invalid label may be sufficient for some calculations, but operational users often need to know why an observation was qualified. Distinguish acquisition limitations, processing failures, uncertain reference matches, and conditions that make interpretation ambiguous. These categories point towards different responses and should not be merged without a clear purpose.
Define a small, documented set of flags with stable meanings. Record whether a flag applies to a complete scene, a geographic unit, an individual measurement, or a derived result. A unit containing a mixture of qualified and unqualified observations may also require a coverage measure. Include the rule used to combine flags when summarising data so that a favourable average does not conceal a substantial fraction of unusable input.
Test the flags with the people receiving the product. Ask what they would do differently for each state and whether the terminology supports that choice. Keep the original flags available even if the interface presents a simpler summary. When flag definitions change, version the rules and review their effects on historical comparisons. Useful quality communication makes the condition of the evidence visible at the moment when a user decides how much confidence to place in the result.
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.
Bring the evidence back to the decision
Expansion should be guided by measured workload, visible quality conditions, and an understanding of which tasks require expert attention. Test the workflow under representative data volumes before treating a successful demonstration as evidence of operational capacity. Preserve a route for investigating individual observations even when most processing is automated. A scalable service keeps its results traceable and useful as it grows, with clear choices about where to automate, where to review, and where to invest in additional evidence.
Sources & further reading
Explore the bhumisat spacecraft concept and our vision towards 2030, or return to the journal.



