Satellite intelligence Editorial draft

Harmonising satellite observation time series in humid tropical forests — an interpretation guide

Explore harmonising satellite observation time series in humid tropical forests. 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 humid tropical forests — 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 humid tropical forests. The immediate decision is to prioritise forest-change inspections. Useful reference evidence includes canopy observations, disturbance evidence and representative plots. The case is an illustrative planning context, with assumptions to check against the actual sensor, landscape and project requirements.

The setting: Humid tropical forests

A humid tropical forest presents a complex upper canopy shaped by species mixtures, crown structure, terrain and disturbance history. Optical imagery can describe aspects of that visible surface, but it does not directly inventory every tree or the conditions beneath the canopy. Define whether the intended task concerns cover change, a disturbance alert or a forest parameter before interpreting an image pattern. These objectives require different reference information and different levels of spatial support.

Persistent cloud, shadow and haze can leave gaps in the observation record. A change map should show when usable evidence was available and whether a reported event is constrained to a broad interval between acquisitions. Terrain and canopy shadows can create additional differences that are unrelated to a new disturbance. Combine quality screening with an understanding of the landscape, and retain the dates and valid areas used to establish each mapped observation.

Field validation should distinguish a change in canopy appearance from the explanation for that change. Record plot or inspection locations, the area represented and the evidence used to identify disturbance or recovery. Tree measurements can support structural or biomass studies when collected and analysed for that purpose. A general vegetation index alone cannot establish forest carbon stocks. The practical monitoring product should state what was observed, how confidently it was located and which additional information supports its interpretation.

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.

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.

Translate the decision into observation requirements

Start with the decision that the information is intended to support. Describe the geographic unit, the time available for acting, and the consequence of an incorrect interpretation. A requirement such as detecting an unusual pattern across management blocks is different from identifying its cause. Keeping that distinction explicit helps a team select measurements that are relevant to the application and prevents later evaluation from drifting towards whatever result happens to be easiest to demonstrate.

Build a compact requirements matrix linking each decision to the evidence needed, the proposed observation source, and an acceptance condition. Include geographic accuracy, temporal relevance, quality screening, and the context required for interpretation. The matrix should also identify the evidence used to justify each requirement. An engineering preference or a convenient data source can inform a study, but neither should silently replace a documented information need.

Review the matrix with the people who will use the result. Ask how their response would change when information is delayed, incomplete, or uncertain. Record unresolved requirements as questions for a pilot rather than converting them into confident specifications. This produces a practical framework for comparing technical options, designing tests, and explaining why an observation is useful to the intended workflow.

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.