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 how pointing and motion affect satellite imagery within ground-station data delivery. The immediate decision is to test delivery of usable observation products. Useful reference evidence includes transfer records, acquisition metadata and complete product checks. The case is an illustrative planning context, with assumptions to check against the actual sensor, landscape and project requirements.
Separate the different pointing requirements
A camera can point near its intended target while still producing an image with poor geometry or blur. Pointing accuracy describes how closely the spacecraft achieves a commanded orientation. Pointing knowledge describes how well that orientation is estimated. Stability concerns changes over a relevant interval, including the detector integration period. These quantities serve different purposes and should be specified separately with a clear reference frame and time basis.
Orientation estimates combine information from sensors such as gyroscopes, Sun sensors and star trackers, depending on the architecture. Actuators then change or maintain the attitude. Reaction wheels exchange angular momentum with the spacecraft, while magnetic torquers interact with Earth's magnetic field and may support momentum management. Their suitability depends on the orbit, operating modes and disturbance environment. A component's advertised accuracy does not automatically become the pointing performance of the integrated spacecraft.
Evaluate the complete image motion budget
Ground features move across a detector because the spacecraft travels along its orbit and may rotate during imaging. Exposure time, scan timing and any motion compensation must be consistent with that movement. Residual motion during integration spreads signal across pixels and reduces contrast. High frequency vibration can produce a different image effect from slow drift, so one average attitude error may conceal an important problem.
Build an image motion budget that includes control behavior, structural response, actuator disturbances and timing uncertainties. Consider the mechanical path between attitude sensors and the optical payload: a flexible interface can change their relative alignment. Thermal distortion can also alter boresight alignment over an orbit. Test realistic operating combinations, including wheel speeds and other mechanisms that may run during an exposure, and assess whether laboratory support equipment affects the measurement.
Geometric processing uses orbit information, attitude knowledge, timing and an Earth model to locate observations. Ground control and image matching can improve some errors, but processing cannot always restore information lost to blur. For repeat observations, test relative registration as well as absolute location. Report residual errors across the field and across relevant operating conditions. A useful requirement links a user consequence, such as registration between spectral bands, to a measurable spacecraft or payload behavior and a verification method. This keeps pointing discussions connected to the quality of the delivered imagery.
The setting: Ground-station data delivery
A ground-station workflow connects acquired observations with the data products a user eventually receives. Successful communication is one part of that chain, while completeness, timing, processing and interpretation determine whether the observation is useful. Define what the delivery system must preserve, including acquisition identifiers, instrument settings, timing and the metadata needed for later calibration or geolocation. A received file should not automatically be treated as a complete and ready-to-use image product.
A test sequence should follow data from a known input through transfer, storage, processing and delivery. Record missing segments, failed attempts and changes in processing state instead of hiding them behind a simple success label. The operational question may concern when an agricultural user receives a current observation or whether a researcher can reproduce a product. These uses require traceable timestamps and a clear distinction between preliminary material and the version accepted for analysis.
Validation can use controlled test data and documented end-to-end checks before any independent satellite service becomes operational. Assess whether the delivered product retains its expected content and whether failures are represented clearly enough for a user to respond appropriately. A concept timetable cannot establish actual service availability. The practical output is evidence about the delivery workflow, its measured constraints and the information users need to judge the age, completeness and processing status of an observation.
Design an evaluation that reflects deployment
A model evaluation should resemble the conditions in which the model will be used. Start by identifying which relationships the development data share: nearby locations, repeated observations of the same unit, common collection teams, or measurements from a single period. These relationships can make records less independent than they appear. An evaluation that ignores them may test the ability to recognise familiar conditions rather than the ability to operate in a new setting.
Choose a split strategy that matches the intended transfer. Holding out locations, seasons, operational units, or acquisition conditions can answer different questions. Document which question each split is designed to address, and keep the held-out evidence separate while selecting features and tuning the method. Repeatedly inspecting the same evaluation set to improve a model gradually makes that set part of development, even if it retains its original label.
Report results at a scale that is meaningful to the user. A strong average can hide poor performance for important subgroups or unusual conditions. Examine error patterns and retain examples of both successful and unsuccessful predictions. Where the evidence covers only a limited range of conditions, describe that range explicitly. The evaluation then becomes a practical guide to suitable use, further testing, and the collection of additional reference observations.
Check spatial alignment before comparison
A comparison between images, channels, maps, or field measurements assumes that the observations refer to the same locations at a suitable level of precision. Small alignment errors can become especially important near boundaries or narrow features. Before interpreting differences, inspect whether identifiable, stable features agree between the sources. A common coordinate reference is necessary for many workflows, but it does not by itself demonstrate accurate alignment.
Use control features that are appropriate for the observation scale and remain stable across the comparison period. Evaluate alignment in more than one part of the area, because a single location cannot reveal spatially varying distortion. Record the method used to estimate any correction and retain independent features for checking the corrected result. Where surfaces have genuinely changed, avoid using those changes as evidence of an alignment error.
Propagate the implications of remaining misalignment into the analysis. A workflow may exclude boundary pixels, summarise at a broader scale, or qualify interpretations for small features. The choice should follow the application rather than a preference for visually smooth output. Preserve both the original and corrected geographic references, and document resampling decisions so that future users can understand how measurements were moved onto a common spatial framework.
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.



