Satellite intelligence Editorial draft

Harmonising satellite observation time series on highland coffee farms — an uncertainty guide

Explore harmonising satellite observation time series on highland coffee farms. Practical guidance for uncertainty 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 on highland coffee farms — an uncertainty guide
Original editorial illustration for this article. Shapes and colours are conceptual, not measured observation data.

Every observation and interpretation contains uncertainty, but the sources and consequences of that uncertainty differ between applications. Some arise from acquisition conditions, others from reference measurements, processing choices, or the transfer of a model to a new setting. This perspective examines how those sources affect the decision a user is considering. It encourages teams to describe uncertainty in a form that can influence action, rather than adding a generic qualification at the end of a report. The objective is to support proportionate decisions while keeping the limits of the available evidence understandable.

This working guide considers harmonising satellite observation time series on highland coffee farms. The immediate decision is to select coffee plots for field review. Useful reference evidence includes shade cover, coffee growth stage and terrain-aware field notes. The case is an illustrative planning context, with assumptions to check against the actual sensor, landscape and project requirements.

The setting: Highland coffee farms

Coffee farms in highland terrain can combine coffee plants, shade trees, paths, soil and other crops within the same image footprint. The observed canopy may therefore describe the wider agroforestry system as much as the coffee itself. Before choosing an analytical method, decide whether the intended output concerns farm-level vegetation, shade management or a coffee-specific variable. These are distinct tasks and require different reference observations and levels of spatial detail.

Slope, aspect and changing illumination complicate comparisons between locations and acquisition dates. A dark patch on a shaded slope should not immediately be classified as stressed vegetation. Inspect terrain and shadow conditions alongside the image quality information, and compare areas with similar observation geometry where possible. Farm boundaries should also be checked carefully because small geolocation differences can move a sampling footprint from coffee into a neighbouring tree canopy or access track.

Field teams should document coffee stage, shade structure, recent pruning and the location of the plants or plots they measure. Samples collected beside a convenient path may not represent the full farm. A practical service could help organise visits or describe changes in farm cover, but claims about coffee condition or production need their own validation. Preserve these distinctions in the report so that a useful landscape observation is not presented as a plant-level diagnosis.

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.

Budget the complete processing workflow

A processing budget should cover the complete path from source observations to a maintained product. Data access and computing are only part of that path. Include preparation, geographic updates, reference collection, expert review, delivery, and support where those activities belong to the service. A calculation that runs cheaply on a small demonstration can still require substantial effort when the surrounding work is repeated across many locations.

Measure representative tasks rather than assuming that every observation costs the same amount to process. Record data volume, processing time, retry frequency, manual interventions, and the conditions that create unusually demanding cases. Separate fixed setup work from work that grows with the number of observations or users. These records support decisions about batching, caching, storage policy, and the point at which a different processing design becomes worthwhile.

Connect the budget to a defined level of service. Faster delivery, more frequent observation, broader coverage, or more detailed review can each change the resources required. Describe these trade-offs before promising a delivery pattern that the workflow has not demonstrated. Review the budget using operational evidence and preserve enough detail to understand changes between processing versions. The aim is a sustainable service whose resource choices remain aligned with the information that users value.

Preserve a reproducible processing history

A result should be linked to the inputs and processing choices that produced it. Record source identifiers, software versions, configuration values, reference data versions, and the time of processing. The record does not need to expose every internal implementation detail to the end user. It must preserve enough information for the producing team to investigate a result, reproduce a comparison, and explain why a revised product differs from an earlier version.

Version changes that can affect the meaning of the output. Updated boundaries, a new quality mask, revised calibration, different model parameters, or altered aggregation rules can all change results even when the source imagery is unchanged. Avoid overwriting an earlier product without retaining a suitable history. A clear relationship between versions helps users distinguish an improvement in processing from a real change in the observed surface.

Use representative regression cases when modifying the workflow. Select cases that cover ordinary conditions and known failure modes, then compare meaningful outputs before and after the change. Investigate differences against the intended purpose of the revision rather than assuming that a closer visual match is always preferable. Preserve the review decision with the version record. Reproducibility becomes practical when the team can trace a result through a documented sequence of inputs, transformations, tests, and delivery decisions.

Bring the evidence back to the decision

Useful uncertainty communication identifies the limitation, explains how it could affect the result, and connects it to a practical response. Some decisions can proceed with a qualified estimate; others require another observation or an independent check. Preserve uncertainty information through processing and delivery so that it is available at the point of use. This makes the analysis more accountable and gives the team a clearer basis for deciding which additional evidence would most improve the outcome.

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.