Satellite intelligence Editorial draft

Harmonising satellite observation time series in potato growing fields — an interpretation guide

Explore harmonising satellite observation time series in potato growing fields. Practical guidance for interpretation and defensible observations.

ShareLinkedInFacebookXWhatsApp

Editorial draft. This generated working guide combines technical guidance with an illustrative context and requires individual editorial review.

Editorial illustration: Harmonising satellite observation time series in potato growing fields — an interpretation guide
Original editorial illustration for this article. Shapes and colours are conceptual, not measured observation data.

Remote observations show patterns, while practical decisions depend on explaining what those patterns could mean. Interpretation therefore requires more than locating a high or low value on a map. A useful analysis considers the timing of the observation, the physical processes that influence the measurement, and the information available from complementary sources. This perspective separates an observed signal from a proposed explanation and from an action recommended to a user. Keeping those stages distinct makes it easier to investigate alternative causes, communicate ambiguity, and choose a proportionate next step.

This working guide considers harmonising satellite observation time series in potato growing fields. The immediate decision is to focus scouting within potato fields. Useful reference evidence includes emergence records, canopy stage and representative plot observations. 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: Potato growing fields

Potato monitoring begins with the distinction between the canopy visible from above and the crop component ultimately harvested below ground. Establishment timing, variety, row structure and management can create different canopy patterns across fields. An image service should specify whether it is supporting crop-stage assessment, identifying areas for inspection or estimating a defined production variable. These objectives require different reference measurements and should not be combined into one unqualified vegetation score.

Maintain a field timeline that includes planting, emergence and the operations that can affect canopy appearance. Early observations may contain a large soil contribution, while later observations may show a more continuous canopy. Cloud and shadow contamination, field edges and neighbouring land cover can alter summaries at either stage. Compare observations using suitable quality rules and retain the acquisition dates so that a recent-looking map does not conceal an old measurement.

A field team should collect consistent crop-stage and canopy observations across both flagged and typical areas. Record management context and sampling support rather than relying on an isolated photograph. A vegetation change cannot establish the presence of a specific disease, and a canopy index is not a direct measurement of tuber yield. Evaluate any production model with appropriate harvest data and independent assessment, while keeping the simpler inspection-priority product transparent about what it actually observes.

Maintain the geographic units of analysis

Many observation services summarise measurements within a field, management block, catchment, forest unit, or other mapped boundary. The meaning of that summary depends on whether the boundary accurately represents the unit being discussed. Start with a clear source for the geometry and record its date, coordinate reference, and intended use. A boundary drawn for visual orientation may require additional checking before it becomes a measurement unit.

Inspect overlaps, gaps, narrow fragments, and features that may have changed since mapping. A geometrically valid polygon can still describe an outdated operational unit. Ask the responsible team how divisions, mergers, new infrastructure, and management changes are recorded. Where pixels or reference measurements cross a boundary, define how they are assigned or excluded so that results remain comparable between analysts and processing runs.

Version the boundaries alongside the observations. If a unit changes, preserve a relationship between the previous and revised geometry rather than replacing the history without explanation. Comparisons through time should identify whether they use a constant spatial unit or the operational units valid at each date. This makes it easier to distinguish a change in the measured surface from a change introduced by the geography used to summarise it.

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

A strong interpretation states what was observed, which explanations remain plausible, and what additional evidence would help distinguish them. Avoid presenting a convenient label as a confirmed cause when the measurements support only a broader pattern. Connect the proposed next step to the significance of the decision and the confidence available. This creates an interpretation that a field team, analyst, or project partner can examine, challenge, and improve as further observations become available.

Sources & further reading

  1. NASA — Harmonized Landsat Sentinel-2 algorithms
  2. NASA — HLS data products

Explore the bhumisat spacecraft concept and our vision towards 2030, or return to the journal.

ShareLinkedInFacebookXWhatsApp
A CONVERSATION STARTS HERE

Build the next
perspective with us.

Tell the TechnoGIS team where you would like to collaborate.

Opens your email app so you can review and send your enquiry.