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 designing reproducible cloud processing workflows around energy infrastructure sites. The immediate decision is to review visible changes around infrastructure. Useful reference evidence includes site boundaries, operation context and dated field observations. The case is an illustrative planning context, with assumptions to check against the actual sensor, landscape and project requirements.
The setting: Energy infrastructure sites
An energy infrastructure site can combine buildings, equipment, access routes, vegetation, water and managed open land. A remote observation may be useful for reviewing visible changes around the site, but its interpretation depends on the feature and decision being studied. Mapping land-cover change, documenting surrounding vegetation and investigating a water pattern are separate objectives. Establish the site boundary and the relevant observation units before selecting analytical features or thresholds.
Large structures can introduce shadows and geometric effects, while narrow management zones may contain mixed observations. Review whether the image resolution supports the detail presented in the report. A change in nearby vegetation may follow normal maintenance, seasonal development or another land-use activity. Preserve the acquisition dates and any available operational context so that an observed pattern can be investigated without assigning an unsupported explanation to it.
Validation should describe the actual surface or feature observed and the spatial area represented by each record. Measurements inside the site and observations of its surroundings may answer different questions and should remain distinguishable. A satellite-derived alert can support a site review without establishing equipment performance or a particular operational condition. Evaluate whether the product provides relevant, interpretable evidence for the intended monitoring task, including instances where follow-up found that a visible change was expected or temporary.
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.
Validate land-cover transitions
A mapped change should describe a transition between meaningful surface states, not merely a difference between two classifications. Begin by defining the land-cover categories, the geographic unit, and the kinds of transition relevant to the application. Categories should be interpretable in the observations available at each date. A distinction that cannot be recognised consistently can create apparent change even when the underlying surface remains similar.
Evaluate the observations supporting both sides of the transition. Differences in acquisition conditions, geographic alignment, seasonal vegetation, shadows, or class definitions can influence the result. Review stable locations alongside apparent changes, and retain the source imagery or other evidence needed to investigate ambiguous cases. Where multiple changes occur within a geographic unit, describe how the workflow represents mixtures rather than forcing a single label that conceals important variation.
Use reference evidence that reflects the timing and scale of the claimed transition. A recent inspection may confirm the current surface without establishing when a previous condition changed. Historical imagery, dated records, and complementary observations can strengthen that sequence where available. Report uncertainty in the transition itself, including ambiguous starting or ending states. This produces a change product that users can examine as a documented account of land-cover evolution rather than an unexplained set of coloured differences.
Organise imagery and results for reliable retrieval
A useful storage design helps people and software find the right observation without relying on informal knowledge of folder names. Separate immutable source data from temporary processing files and delivered products. Give each observation a stable identifier and preserve its acquisition metadata alongside the file. A predictable organisation reduces the chance that a later analysis accidentally uses a preview, an outdated result, or an intermediate product whose meaning has not been documented.
Choose an indexing scheme that reflects the questions the workflow needs to answer. Location, acquisition time, source, product type, and processing version are often useful search dimensions. The physical arrangement of files can differ from the logical catalogue, provided that the relationship is maintained reliably. Record checksums or other integrity information where appropriate, and test whether an observation can be recovered using the catalogue rather than a particular operator's memory.
Define retention rules for source, intermediate, and delivered information. Some intermediate products are inexpensive to reproduce, while others embody costly preparation or expert review. Keep the inputs and configuration needed to rebuild a result before removing reproducible files. Test backup and recovery procedures with representative products, including their metadata and geographic references. Reliable retrieval is demonstrated by a successful reconstruction of useful information, rather than by the existence of an untested copy.
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.


