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 ndre and crop canopy interpretation in cassava production plots. The immediate decision is to select plots for crop-stage assessment. Useful reference evidence includes planting records, canopy cover and dated plot visits. The case is an illustrative planning context, with assumptions to check against the actual sensor, landscape and project requirements.
The setting: Cassava production plots
Cassava plots may have different planting dates, harvest strategies and mixtures of neighbouring vegetation. The commercial product develops below ground, while an optical satellite primarily observes the surface and canopy. This distinction is fundamental to the monitoring objective. A visible vegetation pattern can support investigation of plot development or cover, but a claim about root production needs a demonstrated relationship with representative harvest measurements for the relevant production setting.
Start with boundaries that describe the area actually planted and a calendar that captures establishment and any partial harvesting. Small plots can contain substantial mixed pixels along their margins, particularly where paths, trees or other crops surround them. Track the proportion of valid observations and the spatial support used for each summary. Repeated measurements should be compared in a way that accounts for plot age rather than assuming all cassava fields share a single seasonal cycle.
Field visits should record crop stage, canopy continuity, intercropping and management events that might explain the image pattern. Sampling locations need enough context to identify whether they represent the plot interior or an edge mixture. If an analytical model is developed, reserve independent plots or periods for evaluation and communicate its limits. A dependable first service may be a plot inventory and inspection workflow, with more specific production claims added only when the evidence supports them.
Define the Red Edge measurement precisely
NDRE uses the contrast between near-infrared reflectance and a selected Red Edge band, commonly expressed as a normalised difference. Its meaning depends on the actual spectral response of those channels. Two instruments described as having Red Edge capability may observe different wavelength intervals, so their index values are not automatically interchangeable. Record the selected bands, the product level and any resampling applied to them. This is particularly important when a monitoring service combines observations from several satellite or aerial instruments.
The Red Edge region captures a transition between strong absorption in red wavelengths and the higher reflectance often observed in near-infrared wavelengths over vegetation. A measurement in that transition can provide information that differs from a conventional red band. However, canopy structure, growth stage, soil visibility and illumination also influence the observed signal. An apparent improvement over another index should be demonstrated for a defined crop parameter and evaluation dataset, rather than inferred from the presence of an additional spectral channel alone.
Separate spectral sensitivity from agronomic evidence
A sound comparison uses compatible surface reflectance inputs and observations of similar quality. Inspect cloud edges, shadows, band alignment and field boundaries before interpreting small changes. Bands with different native spatial sampling may require a common grid, but resampling does not create new measured ground detail. Where the field contains only a few usable pixels, boundary mixing can dominate the result. Summarising an interior area separately from the full field can help reveal that sensitivity, provided the exclusion rule is documented consistently.
An agricultural model built around NDRE needs independent measurements of the parameter it claims to estimate. If the objective concerns leaf or canopy condition, the field protocol should specify what is measured, where, when and at what scale. Keep calibration observations separate from the final evaluation sample. Examine performance across crop ages and management regimes, including difficult cases. The resulting evidence can support a targeted application, while uncertainty and sampling limits remain visible. A spectral response is an observation; an agronomic conclusion requires an additional, tested relationship.
Use observation labels with consistent meanings
A reference label should describe an observation that another person could recognise or reproduce. Broad terms such as good, damaged, or unusual can conceal substantial differences between collection teams. Begin by defining the feature or condition being recorded, the observation unit, and the evidence needed to assign a label. Where possible, distinguish a direct measurement from an interpretation made by the observer.
Provide a short collection guide with examples, boundary cases, and a way to record uncertainty. Train observers using shared cases before relying on independently collected labels. If two observers disagree, preserve the disagreement long enough to understand its cause. It may reveal an unclear definition, a genuinely ambiguous condition, a difference in observation scale, or a problem in matching the reference record to the remote measurement.
Retain the context that makes the label interpretable. Location, time, collection method, observer role, and relevant surface conditions can be essential for later review. Changes to the label scheme should be documented and related to earlier versions where a defensible correspondence exists. Consistent labels do not eliminate uncertainty, but they make it possible to investigate disagreement, evaluate analytical methods, and identify where better definitions or additional measurements would improve the evidence.
Define a representative reference sample
A reference sample should represent the situations in which a method will be used. Begin by defining the target population: locations, time periods, management conditions, surface types, or instrument states that belong within the intended application. A collection of convenient observations may be valuable for exploration, but it does not automatically support conclusions about that wider population. Make the scope of the sample visible before calculating a summary of performance.
Consider a stratified design when important conditions are unevenly represented. Relevant strata might include different landscape types, developmental stages, observation quality levels, or ranges of the variable being estimated. Choose sample locations within those groups using a documented rule, and retain the information needed to understand their selection. Where access restrictions affect the sample, record the excluded conditions so that the limits of the resulting evaluation remain clear.
Keep development and evaluation evidence separate where the purpose of the study requires an independent test. Nearby observations or repeated measurements can share information, so a random split of individual records may overstate independence. A split organised by location, period, or operational unit can provide a more demanding comparison. The appropriate design follows the intended deployment, the structure of the observations, and the errors that matter to the user.
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.



