Comparisons through time are valuable only when the observations are sufficiently comparable for the question being asked. A difference between dates can reflect real change, a normal stage in a seasonal cycle, or a difference in how the surface was observed. This perspective examines the reference period, the timing of acquisitions, and the contextual records needed to interpret a sequence. It encourages the use of appropriate baselines rather than treating every previous observation as an equivalent benchmark. The objective is to identify changes that remain meaningful after normal variation and measurement conditions are considered.
This working guide considers ndvi crop monitoring across river floodplain areas. The immediate decision is to locate areas needing flood-impact review. Useful reference evidence includes dated water observations and representative field impact records. The case is an illustrative planning context, with assumptions to check against the actual sensor, landscape and project requirements.
The setting: River floodplain areas
A floodplain contains channels, low-lying fields, settlements, wetlands and surfaces that may be wet or dry under ordinary conditions. A flood-monitoring workflow should distinguish a new observation of water from the baseline distribution expected in that setting. Define the event period and the intended output, such as visible inundation extent or locations for field impact assessment. These products do not automatically establish water depth, damage or the cause of a particular local condition.
Cloud cover can limit optical observations during an event, while vegetation and structures may obscure water at the surface. Other observation types can contribute complementary evidence but require interpretation appropriate to their measurement physics. Compare suitable baseline and event acquisitions, check alignment and preserve the actual observation times. A map assembled from different dates should make those differences clear rather than implying that the whole floodplain was observed simultaneously.
Field validation should record when water or impacts were observed, the location and the area represented by each report. Conditions can change between an image acquisition and a visit, so apparent disagreement may reflect timing rather than a simple mapping error. Sample different land-cover settings and include places outside the mapped extent. A useful product communicates the evidence for observed inundation separately from estimates of damage or operational consequences that require further measurements.
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.
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.
Connect observations within a catchment
Water-related observations often depend on processes beyond the immediate pixel or sampling location. Begin by identifying the geographic relationships that are relevant to the question: upstream areas, connected drainage paths, contributing land uses, and the receiving water body. A local pattern may be easier to interpret when placed within that wider setting. The catchment boundary is a useful organising unit, but its suitability should be checked against the process and observation scale.
Combine the remote observation with contextual records that can help explain its timing and spatial pattern. Rainfall, water level, land management, and known interventions can influence what is observed. Preserve the dates and geographic meaning of those records rather than treating them as timeless attributes. Where drainage connections are uncertain or change with conditions, state the limitation and consider whether additional mapping or reference observations would materially improve the interpretation.
Plan reference sampling across locations that distinguish plausible explanations. A set of measurements concentrated at an easily accessible outlet may provide a different view from one that also represents tributaries, source areas, and contrasting conditions. Document how each location contributes to the evaluation. Interpret spatial agreement with care, because connected observations can share influences and may not provide independent evidence. The resulting workflow should connect local measurements with a defensible account of the wider system they help describe.
Bring the evidence back to the decision
A useful comparison preserves the dates, quality conditions, and contextual assumptions behind its baseline. Review unusual results against the actual observation sequence rather than relying entirely on a summary statistic. Where seasonal timing is important, describe how comparable stages were identified. The resulting analysis should help users distinguish an informative change from an expected cycle or an observation artefact, while making gaps and remaining uncertainty visible enough to guide further investigation.
Sources & further reading
Explore the bhumisat spacecraft concept and our vision towards 2030, or return to the journal.



