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 near-infrared observations of vegetation and land along shallow reef-adjacent coasts. The immediate decision is to select coastal habitat survey areas. Useful reference evidence includes water conditions, survey timing and mapped substrate observations. The case is an illustrative planning context, with assumptions to check against the actual sensor, landscape and project requirements.
The setting: Shallow reef-adjacent coasts
A shallow coastal image can contain a mixture of water-column effects, bottom reflectance, surface reflection and adjacent land. The contribution of the seabed depends on conditions that vary across space and time. A monitoring task should therefore identify what can reasonably be observed at the selected scale. Mapping broad substrate patterns or selecting survey locations is different from diagnosing the condition of individual coral colonies or other small habitat features.
Review water clarity, depth context where available, cloud, atmospheric quality and sun glint before interpreting a spectral difference. Changes in the water above the bottom may alter the image without a corresponding change in the substrate. Shorelines and narrow reef features are also sensitive to mixed pixels and alignment. Comparisons should retain their acquisition dates and processing assumptions so that users can understand what environmental conditions support the proposed interpretation.
Field surveys should document the area represented by each observation and distinguish substrate descriptions from measurements of biological condition. Survey timing and water conditions matter when relating those records to imagery. A broad remotely sensed class cannot validate every feature inside its footprint. Use representative and independent assessment locations where possible, and communicate where the result supports a landscape-scale interpretation or a survey priority rather than a fine-scale ecological conclusion.
Understand what contributes to the NIR response
Near-infrared wavelengths lie outside the range of human vision, but they are important in optical observations of vegetation and land. A near-infrared image should not be confused with a thermal image. Reflected sunlight in this region and emitted thermal radiation describe different physical processes. This distinction matters when communicating crop information: a bright or dark NIR response is not a direct temperature reading. Its interpretation depends on the surface, the observation geometry and the particular wavelength interval measured by the instrument.
Vegetation can show a strong near-infrared response because of interactions within leaves and canopies. At landscape scale, the observed signal also changes with canopy cover, leaf arrangement, shadows and the proportion of visible soil or water. A field with a different crop age may therefore differ substantially from another field without either being abnormal. NIR is useful partly because it adds contrast beyond visible appearance, but that contrast still needs a meaningful comparison. The analytical task determines which associated measurements and field records are required.
Use NIR in a traceable analytical chain
When combining NIR with another band in an index or model, check that the channels refer to comparable ground locations and acquisition conditions. Differences in band resolution, alignment or spectral response can influence the result. Preserve reflectance scale factors, quality flags and any processing applied before the combination. Where resampling is necessary, choose a documented common grid and recognise that the operation changes representation rather than increasing the original observation detail. These controls are particularly important near field edges and in small management units.
An application should demonstrate the benefit of the NIR measurement using evidence appropriate to its stated purpose. For vegetation monitoring, that might mean a relationship with independently recorded canopy conditions or a reliable separation of relevant land-cover classes. For water or soil interpretation, a different protocol may be needed. Review errors as well as successful examples and retain cases that challenge the initial explanation. A clear observation chain makes NIR a useful part of a broader decision process without assigning the band capabilities it does not independently provide.
Keep an auditable review record
A review record should explain how a result moved from an analytical output to an accepted interpretation or operational decision. Preserve the product identifier, the evidence considered, the reviewer role, and the outcome of the review. A short, consistent record is often more useful than an extensive free-text note that cannot be compared between cases. The objective is to make important decisions traceable without turning routine review into unnecessary administrative work.
Separate observations from conclusions within the record. Describe the evidence visible to the reviewer, the alternative explanations considered where relevant, and the reason for accepting, qualifying, or rejecting the result. If a correction is required, identify what should change and how the revised product relates to the earlier version. Keep unresolved questions visible so that they can be addressed by another observation or by the person responsible for the next action.
Use the accumulated record to improve the workflow. Recurring review reasons can reveal unclear requirements, missing contextual information, unstable processing steps, or an evaluation gap. Examine whether similar cases receive similar decisions across reviewers and over time. Preserve the relationship between feedback and subsequent revisions so that improvements can be assessed against the evidence that motivated them. An auditable record supports learning, accountability, and consistent delivery while allowing the technical process to evolve.
Locate the uncertainty that matters to the decision
An uncertainty budget is a practical description of where a result could become unreliable. Begin with the observation chain: acquisition, calibration, geographic matching, reference measurements, feature calculation, modelling, and delivery. Identify the assumptions at each stage and ask which could materially change the interpretation. The purpose is not to assign a precise number to every limitation. It is to locate the sources that deserve attention for the intended decision.
Separate limitations that can be measured from those that currently require a qualitative description. Repeated measurements may help characterise variability, while comparisons with independent references can reveal systematic differences. Some uncertainties interact, so combining individual error estimates without examining their relationships can produce a misleading impression of precision. Keep the method of assessment visible and avoid treating an unexamined assumption as though it were a negligible contribution.
Use the budget to prioritise further work. The largest visible source of variation is not always the one whose reduction would most improve the decision. Consider which additional observation, test, or contextual record would change confidence in an actionable way. Revisit the budget when the application, observation source, or deployment conditions change. This turns uncertainty analysis into a guide for improving the workflow rather than a qualification added only after the result has been delivered.
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.



