A useful observation programme begins with a decision that somebody can act on. Before selecting imagery or instruments, define the area of interest, the people responsible for inspecting it, and the time available for a response. This planning perspective connects remote measurements with the practical questions that shape a survey or monitoring service. The aim is to identify which observations would change a decision, how supporting evidence would be collected, and what should happen when information is incomplete. A clear plan makes later technical choices easier to assess against an operational purpose.
This working guide considers ndvi crop monitoring in vineyard production parcels. The immediate decision is to prioritise vineyard zone inspections. Useful reference evidence includes vine growth stage, row management and sampling locations. The case is an illustrative planning context, with assumptions to check against the actual sensor, landscape and project requirements.
What the index can describe
NDVI expresses the contrast between near-infrared and red reflectance as their difference divided by their sum. The result is a compact description of spectral behaviour, rather than a direct measurement of crop health. A growing canopy often changes both of these measurements, but soil exposure, standing water, illumination and the mixture of materials inside a pixel can also affect the index. An operational interpretation therefore starts with the crop, its development stage and the surface actually represented by the pixels.
A useful monitoring baseline describes comparable conditions. Comparing a newly planted field with an older field can produce a strong difference that simply reflects age. Comparing the same field before and after harvest can be useful if the management record confirms the event. The analytical question should be stated before choosing an alert threshold: detecting an unexpected departure from normal development is different from mapping current canopy cover. Neither task automatically establishes the cause of a low value or the action a grower should take.
Build a comparison that can be checked
Before computing field statistics, screen unsuitable observations and retain their quality information. The processing record should identify the imagery source, acquisition date, reflectance product, band mapping and mask rules. Report how much valid area remains inside each field. A median calculated from a small cloud-free corner should not be presented as if it represented the entire management block. Keeping a distribution or selected percentiles alongside the central value can reveal variation that a single coloured label would hide from the user.
Validation should connect an apparent change with an independent observation at a relevant time. A field team can record canopy condition, crop stage, recent operations and any visible disturbance, including observations that contradict the alert. Revisit both flagged and apparently normal areas to evaluate missed changes and false alarms. Once a relationship has been demonstrated, monitor whether it remains stable across seasons and management systems. NDVI is most useful when it helps organise a defensible comparison and directs attention to places where additional information is needed.
The setting: Vineyard production parcels
Vineyard imagery combines vine rows with inter-row vegetation, exposed soil, tracks and sometimes steep terrain. Row direction, canopy training and management can substantially influence the observed pattern. The relevant unit may be a parcel, a management zone or a sampled part of a row, and these units should be defined before analysis begins. A map with many small coloured areas does not necessarily provide measurements at the scale of an individual vine.
Build comparisons around growth stage and known operations such as canopy management or changes in inter-row cover. Inspect terrain-related illumination and geometric alignment where slopes or narrow parcels make these effects important. Record the proportion of valid observations used to describe each zone. When integrating drone and satellite imagery, consider their different acquisition times and spatial support rather than assuming that agreement should occur at every displayed pixel.
Field sampling should represent the range of mapped zones and include locations that appear ordinary. Record vine stage, management context and the precise area represented by each measurement. Relationships with fruit characteristics or production need reference observations that address those outcomes directly. A useful operational product can begin as a consistent zoning and inspection workflow, with stronger agronomic interpretations introduced only after the relationship between the image pattern and the field evidence has been evaluated.
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.
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.
Bring the evidence back to the decision
The practical outcome should be a short observation plan that another team can follow. It should name the decision, the required evidence, the responsible roles, and the conditions that trigger a field visit or further analysis. Keep the plan small enough to test, then revise it using the results of real inspections. A useful monitoring workflow improves because its assumptions are examined systematically, and its observations remain connected to decisions throughout the process.
Sources & further reading
Explore the bhumisat spacecraft concept and our vision towards 2030, or return to the journal.



