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 geolocation accuracy for field-level monitoring in open-field tomato production. The immediate decision is to select tomato rows for crop review. Useful reference evidence includes transplanting dates, canopy observations and field management notes. The case is an illustrative planning context, with assumptions to check against the actual sensor, landscape and project requirements.
Absolute location and relative alignment answer different questions
Geolocation describes where an observation is placed on Earth. For a field-level application, its quality affects which measurements are assigned to each management unit and whether an alert can be found during inspection. Absolute accuracy concerns the relationship with a suitable geographic reference. Relative alignment concerns the relationship between observations, such as images from different dates. A series can align well internally while still being displaced from a field boundary dataset. Both relationships should be considered when they matter to the intended decision.
The geographic reference includes more than a familiar coordinate system label. Map projection, datum, axis order, units and any relevant height reference can affect how data are combined. Field boundaries also have an origin and uncertainty of their own. A boundary drawn from an old image may not represent the current cultivated area, even if the satellite product is positioned correctly. Preserve the provenance of both the image and vector data, and distinguish a positional mismatch from a real change in land management.
Test accuracy at the management scale
Accuracy assessment needs independent, appropriate reference information distributed across the area of interest. Choosing only easy points can underrepresent difficult terrain or surface conditions. Define the feature being measured and check that it is identifiable at the image's spatial scale. Report the evaluation method and the distribution of residuals, rather than relying only on a single average error. A visual overlay is useful for finding issues, but it is not a substitute for an assessment designed around the accuracy claim being made.
The acceptable error depends on the task. A displacement that has little effect on a large plantation block may be consequential for a narrow field or a small validation plot. Evaluate how plausible location errors influence the derived statistic or operational instruction. Where necessary, revise the reporting unit, improve the reference data or obtain a complementary observation. The objective is not an impressive accuracy number in isolation. It is a defensible connection between the satellite measurement, the field record and the place where a person will use the result.
The setting: Open-field tomato production
Open-field tomato production can involve short management cycles, staggered planting and repeated operations within neighbouring parcels. The field calendar is therefore central to interpreting a satellite observation. Newly transplanted plants, established rows and areas nearing the end of production can show different responses for ordinary reasons. Record the planted area and the relevant management unit carefully, particularly where a commercial holding contains several crops or planting stages at the same time.
The image footprint may mix plants with soil, mulch, access routes and irrigation infrastructure. Determine whether the spatial resolution supports the intended row-level interpretation or whether a broader field summary is more appropriate. Examine the quality and age of observations before proposing a management use that depends on rapid response. A monitoring workflow should communicate when cloud gaps or the acquisition schedule leave insufficient current evidence for that decision.
Validation should document crop stage, canopy continuity, recent operations and the area represented by each sample. Field staff may use a mapped anomaly to choose an inspection location, but the subsequent diagnosis requires suitable observations and expertise. If production or quality is the target, collect reference information for those outcomes rather than assuming that greener vegetation implies more marketable fruit. The evaluation should measure whether the product improves a defined scouting or management process.
Locate the uncertainty that matters to the decision
An uncertainty budget is a practical description of where a result could become unreliable. Begin with the observation chain: acquisition, calibration, geographic matching, reference measurements, feature calculation, modelling, and delivery. Identify the assumptions at each stage and ask which could materially change the interpretation. The purpose is not to assign a precise number to every limitation. It is to locate the sources that deserve attention for the intended decision.
Separate limitations that can be measured from those that currently require a qualitative description. Repeated measurements may help characterise variability, while comparisons with independent references can reveal systematic differences. Some uncertainties interact, so combining individual error estimates without examining their relationships can produce a misleading impression of precision. Keep the method of assessment visible and avoid treating an unexamined assumption as though it were a negligible contribution.
Use the budget to prioritise further work. The largest visible source of variation is not always the one whose reduction would most improve the decision. Consider which additional observation, test, or contextual record would change confidence in an actionable way. Revisit the budget when the application, observation source, or deployment conditions change. This turns uncertainty analysis into a guide for improving the workflow rather than a qualification added only after the result has been delivered.
Define a representative reference sample
A reference sample should represent the situations in which a method will be used. Begin by defining the target population: locations, time periods, management conditions, surface types, or instrument states that belong within the intended application. A collection of convenient observations may be valuable for exploration, but it does not automatically support conclusions about that wider population. Make the scope of the sample visible before calculating a summary of performance.
Consider a stratified design when important conditions are unevenly represented. Relevant strata might include different landscape types, developmental stages, observation quality levels, or ranges of the variable being estimated. Choose sample locations within those groups using a documented rule, and retain the information needed to understand their selection. Where access restrictions affect the sample, record the excluded conditions so that the limits of the resulting evaluation remain clear.
Keep development and evaluation evidence separate where the purpose of the study requires an independent test. Nearby observations or repeated measurements can share information, so a random split of individual records may overstate independence. A split organised by location, period, or operational unit can provide a more demanding comparison. The appropriate design follows the intended deployment, the structure of the observations, and the errors that matter to the user.
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.



