Satellite intelligence Editorial draft

Harmonising satellite observation time series at calibration reference sites — a field-planning guide

Explore harmonising satellite observation time series at calibration reference sites. Practical guidance for field planning 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 at calibration reference sites — a field-planning guide
Original editorial illustration for this article. Shapes and colours are conceptual, not measured observation data.

A useful observation programme begins with a decision that somebody can act on. Before selecting imagery or instruments, define the area of interest, the people responsible for inspecting it, and the time available for a response. This planning perspective connects remote measurements with the practical questions that shape a survey or monitoring service. The aim is to identify which observations would change a decision, how supporting evidence would be collected, and what should happen when information is incomplete. A clear plan makes later technical choices easier to assess against an operational purpose.

This working guide considers harmonising satellite observation time series at calibration reference sites. The immediate decision is to select repeatable calibration observations. Useful reference evidence includes target properties, measurement conditions and acquisition geometry. The case is an illustrative planning context, with assumptions to check against the actual sensor, landscape and project requirements.

The setting: Calibration reference sites

A calibration reference site is useful when its properties and observation conditions are understood well enough for a defined comparison. The relevant target depends on the instrument and measurement being evaluated. A site chosen for geometric checks may not provide the evidence needed for a radiometric assessment. Define the quantity being tested, the spatial area represented and the expected sources of variation before treating a convenient surface as a reliable reference.

Repeatable measurements require more than returning to the same coordinates. Illumination, atmosphere, surface condition, viewing geometry and the instrument operating state can all influence the result. Record the factors that matter to the chosen test and identify circumstances that make an observation unsuitable. The target should occupy an appropriate fraction of the measurement footprint, with enough surrounding context to assess mixing, alignment and other effects relevant to the comparison.

The evaluation should preserve measurement uncertainty and distinguish calibration evidence from an application demonstration. A successful comparison at one reference site does not establish performance under every mission condition. Repeat observations, independent checks and clear acceptance criteria strengthen the interpretation. The practical output is a traceable record of what was measured, under which conditions and against which reference, so that a later processing or hardware change can be assessed using a consistent and defensible basis.

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.

Plan the evidence needed for calibration

Calibration connects an instrument's recorded response with a measurement that can be interpreted consistently. Begin by identifying which aspects of the response matter to the application: variation across channels, changes with operating conditions, geometric alignment, or differences between repeated observations. A calibration plan should state the quantities being assessed and the evidence needed to determine whether the response is sufficiently characterised for the intended use.

Design tests around controlled and documented conditions. Record the reference source, instrument configuration, exposure settings, temperature conditions, and processing applied to the measurements. Repeat suitable observations to investigate variability and distinguish a consistent response from a single favourable result. The reference itself has limitations, so preserve its characterisation and avoid assuming that every difference originates in the instrument under evaluation.

Connect calibration activities with the expected operating environment and processing chain. A correction that works under one test condition may require further evidence before being applied elsewhere. Define how calibration parameters are versioned, checked, and associated with the observations they support. Include a plan for recognising drift or other changes that could affect interpretation. The outcome should be an instrument response supported by traceable evidence, together with acceptance criteria that remain relevant to the application.

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.

Bring the evidence back to the decision

The practical outcome should be a short observation plan that another team can follow. It should name the decision, the required evidence, the responsible roles, and the conditions that trigger a field visit or further analysis. Keep the plan small enough to test, then revise it using the results of real inspections. A useful monitoring workflow improves because its assumptions are examined systematically, and its observations remain connected to decisions throughout the process.

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.