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 connecting drone surveys with satellite observations in maize production fields. The immediate decision is to prioritise uneven-development scouting. Useful reference evidence includes emergence dates, plant stand notes and field stage. The case is an illustrative planning context, with assumptions to check against the actual sensor, landscape and project requirements.
The setting: Maize production fields
Maize fields can differ in emergence date, variety, plant density and management even within the same growing region. An image comparison is more meaningful when those differences are recorded. Early in the cycle, visible soil and row arrangement can influence a field summary substantially. Later, the canopy may become dense enough that some vegetation measures respond less clearly to additional growth. Interpret the observations in relation to the crop stage and the variable of interest.
Construct a field timeline that marks establishment, important field operations and the dates of usable observations. A decline or delayed increase in a signal can suggest a place to investigate, but several explanations may be possible. Soil conditions, weeds, storm effects and crop timing can produce patterns that require field context. Avoid turning a general anomaly map into a specific diagnosis without measurements that distinguish between these alternatives.
A scouting plan should include representative normal areas as well as the locations ranked most unusual. Record crop stage, stand continuity, visible damage and management information consistently. Production models require their own training and evaluation data, ideally covering different fields and seasons. For operational use, assess whether a satellite-derived priority list helps the field team find relevant conditions efficiently, and report the observation age whenever weather leaves a gap in the current image sequence.
Give each platform a clear role
Drone surveys and satellites observe the same landscape at different scales and with different constraints. A drone can collect detailed local observations at a selected time, while satellites provide repeated coverage over larger regions. Combining them is useful when the local survey answers a specific question: checking crop rows, describing canopy gaps, measuring a surface, or supporting reference interpretation. Define that role before planning the flight. A detailed orthomosaic does not automatically become accurate reference data merely because its pixels are small.
Radiometric consistency requires attention to exposure settings, sensor response, illumination, and calibration targets where appropriate. Geometric quality depends on camera calibration, flight geometry, image overlap, tie points, and the accuracy of positioning and ground control. Surface reconstruction can struggle over water, moving vegetation, uniform textures, or repeated patterns. Keep independent checkpoints separate from control points used to fit the reconstruction, and evaluate horizontal and vertical accuracy against the requirements of the intended measurement.
Compare like with like
Align coordinate systems, vertical datums where relevant, and acquisition times before comparing products. A field can change after irrigation, rainfall, harvest, or a different sun angle, so a convenient date may not represent the satellite overpass. Satellite bands also have different spectral response functions from a drone camera. Matching band names does not guarantee that their reflectance values are equivalent. Describe these differences and select a comparison that the measurements can support.
Aggregate drone observations to the satellite pixel footprint or another justified analysis unit rather than simply sharpening the satellite grid. Include edge effects, positional uncertainty, and spatial heterogeneity in the comparison. A satellite pixel may mix trees, soil, shade, and roads that the drone resolves individually. Sample drone sites across the conditions present in the larger region; surveying only easy access sites can bias a calibration model. Keep training and evaluation locations independent when drone products support machine learning. Deliver the local survey with flight dates, processing settings, calibration records, accuracy checks, and known gaps. The combined workflow should make the relationship between local detail and regional inference explicit, including where the drone sample does not justify extrapolation.
Design field observations around the information need
Field observations are most useful when they answer a defined question within the monitoring workflow. Begin by identifying the variable, condition, or management event that needs to be recorded and the geographic unit to which it applies. Distinguish direct measurements from an observer's interpretation. A consistent record of crop stage, management timing, and visible conditions can provide valuable context even when the field team is not collecting a complex set of measurements.
Prepare a collection protocol that reflects the variability of the site. Define where observations are made within a unit, how many locations are represented, and how the position and time are recorded. Avoid selecting only the most dramatic or convenient examples. Include apparently normal conditions and records that might challenge the remote interpretation. Where a measurement method has known limitations, preserve the information needed to assess whether those limitations affect the intended comparison.
Link field records to the corresponding remote observations without losing their original detail. Geographic matching, timing, and the scale represented by each record should remain visible. Review disagreements with the collecting team before changing a label or excluding an observation. A disagreement may reveal a timing mismatch, a mixed surface, or an incomplete interpretation rather than a simple error. The field programme should improve the understanding of the monitoring process as well as provide evidence for evaluating its outputs.
Prioritise alerts using evidence and consequence
An alert is a request for attention, so its design should consider both the evidence available and the cost of responding. Begin by distinguishing a measured change, a proposed interpretation, and the action expected from the recipient. A large numerical difference is not automatically the most urgent case. The significance of the location, the age of the observation, the confidence in the interpretation, and the consequences of delay can all influence priority.
Create a review queue with enough context to support consistent decisions. Useful information can include the supporting dates, quality qualifications, previous observations, geographic unit, and the reason the case entered the queue. Define when an alert can be closed, escalated, or held for another observation. A documented rule is easier to improve than an informal practice that depends entirely on the memory of the operator reviewing the result.
Collect feedback from inspections and operational responses. Record alerts that led to a useful finding, alerts that required no action, and important conditions that the system failed to flag. Review these outcomes across different settings rather than relying only on a total count of alerts. The objective is a queue that directs limited attention towards meaningful decisions, while generating evidence for adjusting thresholds, improving context, and reducing repeated sources of unnecessary work.
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.



