A convincing image can still contain measurements that are unsuitable for a particular task. Quality control asks whether the inputs, transformations, and outputs meet the requirements of the intended application. This perspective follows evidence through the workflow, from acquisition metadata and reference observations to the final interpretation. It encourages teams to define acceptance conditions before seeing the result, rather than adjusting them to favour a preferred conclusion. The purpose is a repeatable way to distinguish usable observations, observations requiring qualification, and observations that should be excluded from a decision.
This working guide considers measuring forest cover without confusing canopy and land use in fire-affected forest areas. The immediate decision is to prioritise post-event field assessment. Useful reference evidence includes dated disturbance evidence and representative recovery observations. The case is an illustrative planning context, with assumptions to check against the actual sensor, landscape and project requirements.
Define what the map measures
Forest cover is not a single self-evident quantity. One project may need the fraction of a pixel occupied by tree crowns; another may need a categorical forest mask based on canopy cover, height, and minimum area. A land use inventory may treat temporarily cleared forest differently from a map of visible tree cover. Write the definition before collecting labels, and identify how plantations, orchards, mangroves, sparse woodland, and urban trees will be handled. A consistent definition matters as much as a sophisticated classifier when comparing places or years.
Optical observations provide information about foliage, moisture, and seasonal behavior, but similar vegetation types can have overlapping spectra. A green pixel does not establish tree height or distinguish a natural forest from a plantation. Time series can capture leaf emergence, dry season persistence, and disturbances that a single image misses. Radar adds sensitivity to vegetation structure and moisture, although relationships vary with wavelength, geometry, and forest conditions. Combining observations can improve discrimination when each input has a clear role and compatible spatial support.
Make estimates comparable and testable
Prepare a stable analysis grid, inspect geolocation, and apply consistent atmospheric and quality screening to optical inputs. Choose seasonal windows that suit the local ecology rather than assuming one calendar works everywhere. When clear observations are sparse, report the observation count and the age of the composite. Train with examples spanning forest types, canopy densities, topography, and confusing nonforest classes. Keep independent assessment locations separate from training areas, especially where neighboring pixels share the same stand.
Evaluate omission and commission errors for forest and relevant subclasses. A high overall accuracy can conceal poor performance in a rare forest type or along fragmented edges. For area reporting, use a probability sample and an estimator appropriate to its design rather than treating classified pixel counts as exact. Compare annual products with the same class definitions and processing assumptions. Abrupt canopy loss can indicate harvesting, fire, storms, or conversion, and the image alone may not identify the cause. Preserve that distinction in summaries, and accompany trend estimates with uncertainty and a description of what canopy recovery does and does not establish.
The setting: Fire-affected forest areas
A fire-affected forest can contain a mixture of changed canopy, exposed soil, surviving vegetation and areas whose appearance is influenced by shadow or smoke. A monitoring workflow should state whether it aims to map an affected area, describe change or follow recovery. These outputs require different interpretation rules and reference observations. An image pattern associated with disturbance is not by itself a complete measurement of ecological impact across every part of the landscape.
Use suitable observations before and after the event, while checking seasonal comparability and data quality. The available dates may constrain the timing of change only to an interval. During recovery, green ground vegetation can increase before the former forest structure returns. Track that distinction where the management objective concerns trees or habitat, and retain the supporting acquisition dates rather than presenting all changes in greenness as equivalent evidence of recovery.
Field validation should represent the range of mapped responses, including apparently unaffected locations and areas with ambiguous observations. Record the evidence of disturbance, vegetation layers and the spatial setting of each sample. If a product estimates severity or a restoration outcome, define the variable and collect reference information for that claim. A transparent first output can identify where observations support change and where additional field assessment is needed to understand its consequences.
Deliver quality flags that users can interpret
Quality information should describe the condition of an observation in terms that remain useful through the workflow. A single valid or invalid label may be sufficient for some calculations, but operational users often need to know why an observation was qualified. Distinguish acquisition limitations, processing failures, uncertain reference matches, and conditions that make interpretation ambiguous. These categories point towards different responses and should not be merged without a clear purpose.
Define a small, documented set of flags with stable meanings. Record whether a flag applies to a complete scene, a geographic unit, an individual measurement, or a derived result. A unit containing a mixture of qualified and unqualified observations may also require a coverage measure. Include the rule used to combine flags when summarising data so that a favourable average does not conceal a substantial fraction of unusable input.
Test the flags with the people receiving the product. Ask what they would do differently for each state and whether the terminology supports that choice. Keep the original flags available even if the interface presents a simpler summary. When flag definitions change, version the rules and review their effects on historical comparisons. Useful quality communication makes the condition of the evidence visible at the moment when a user decides how much confidence to place in the result.
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
Quality control is most useful when its results travel with the information being delivered. Preserve the reasons for accepting or rejecting an observation, and expose limitations that could change the user's interpretation. Review recurring failures as clues about the design of the workflow. A clear quality record supports consistent comparisons between operators and processing versions, while helping the team decide whether a problem originates in acquisition, preparation, interpretation, or the underlying observation requirements.
Sources & further reading
Explore the bhumisat spacecraft concept and our vision towards 2030, or return to the journal.



