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 harmonising satellite observation time series over inland reservoir waters. The immediate decision is to select water-sampling locations. Useful reference evidence includes water samples, acquisition timing and reservoir-level context. The case is an illustrative planning context, with assumptions to check against the actual sensor, landscape and project requirements.
More observations require a common measurement definition
Combining observations from different satellites can increase the information available through time, but the resulting series needs a common analytical definition. Instruments may differ in spectral response, spatial sampling, viewing geometry and processing history. Two bands with similar names are not necessarily equivalent measurements. Harmonisation addresses selected differences so that observations can be used together more consistently. It should be understood as a documented processing approach with remaining limitations, rather than a guarantee that every value from every sensor is interchangeable.
A suitable workflow begins with the variables that need to be compared. Identify the input products, their physical meaning and the transformations already applied. A common grid helps organise observations spatially, while atmospheric correction, geometry normalisation and spectral adjustments may address other differences. These operations have distinct purposes. Applying only one of them should not be described as complete harmonisation. Retain sensor identity and acquisition metadata even when the user sees one combined series, because those attributes remain valuable for diagnosing an apparent discontinuity.
Validate continuity before interpreting a longer record
Test continuity using overlapping or otherwise comparable observations and independent evidence where available. Inspect several surface types and canopy conditions rather than evaluating only one convenient landscape. A consistent average relationship can still hide a meaningful difference for a particular crop or season. Examine how the combined record affects the final product, including index thresholds, fitted timing metrics and change alerts. The relevant question is whether the remaining differences are acceptable for that application, not merely whether the images appear similar on a map.
A longer record also requires a stable policy for quality screening and updates. Changes in input collections, calibration or processing versions can affect historical outputs. Version the workflow and preserve enough information to reproduce earlier results when necessary. When a series crosses a known processing change, evaluate the transition explicitly. A harmonised dataset can provide a strong foundation for monitoring, but field context and validation still determine the usefulness of its interpretation. Maintaining traceability allows additional observations to improve coverage without concealing their origins or implying a precision that has not been demonstrated.
The setting: Inland reservoir waters
A reservoir image records water alongside shorelines, shallow areas, vegetation and surrounding land. The mixture visible at its margins changes as water level varies. A monitoring programme should distinguish mapping water extent from estimating a particular water-quality variable. These tasks may share observations, but they require different reference data and different rules for excluding surfaces that do not represent the open water of interest.
Optical interpretation depends on atmospheric conditions, surface reflections and the substances influencing the water signal. A bright patch could have several explanations, so an image feature should be treated as a question for investigation unless its relationship with a defined variable has been evaluated. Review clouds, shadows, sun glint and adjacency to bright land. Sampling footprints near a shoreline may need separate treatment because their measurements can include both land and water.
Field validation should connect each water sample to its location, collection time and the conditions relevant to the acquisition. A sample taken after a major change in inflow may not represent what the satellite observed earlier. Include different parts of the reservoir and the range of conditions expected in use. The final product should communicate whether it shows a spectral pattern, a calibrated estimate or a confirmed sampling result, rather than presenting those forms of evidence as identical.
Match coastal observations with changing conditions
Coastal observations can be influenced by conditions that change within a day as well as across seasons. The meaning of an image or reference measurement may depend on water level, currents, recent weather, and the state of the surrounding land. Begin by documenting the exact acquisition time and the contextual records relevant to the question. A comparison based only on calendar dates can conceal differences that are important to interpretation.
Define which conditions need to be comparable across observations. A shoreline analysis, an intertidal habitat study, and an investigation of water appearance can require different timing assumptions. Select reference locations and measurement procedures that address the specific application. Preserve information about observation depth, sampling position, and the duration represented by a reference measurement where those details affect the comparison.
Review apparent differences against the physical and observational context before assigning a cause. A change in visible extent or spectral response may reflect the state of the water and atmosphere as well as a change in the feature being studied. Where suitable contextual information is unavailable, qualify the comparison or use additional observations to test competing explanations. A dependable coastal workflow makes its timing assumptions explicit and preserves the information needed to reconsider them when further evidence becomes available.
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.



