Monthly crop composites: dates and uncertainty matter

Start with the operational question

Document which dates contribute to the composite and how values are selected or combined. Inspect whether fields are represented by different parts of the month.

Separate observation from explanation

A monthly image is not necessarily a simultaneous observation. A composite can blend pre-harvest and post-harvest conditions or hide a short event behind a convenient average.

Read a time series as dated evidence

Keep the actual acquisition dates and the usable observation count. Plot management events beside the series and inspect gaps instead of allowing a smooth line to imply continuous measurement. A composite or interpolated value should be labelled with its method and temporal support. It may summarise several dates rather than describe one moment.

Compare similar crop stages and management histories. Align by planting, cutting, pruning, or another relevant event when calendar dates would mix different stages. Check that the field boundary, sensor treatment, scale factors, and quality rules are consistent. A processing or geometry change can create a break that has no biological cause.

Examine the original imagery around unusual points and seek corroboration from another usable observation or the field record. Distinguish persistent changes from single-date outliers. Report the period that can actually be observed and avoid estimating an event date more precisely than the data support. Preserve uncertainty around cloudy intervals or periods with no suitable ground reference.

Match spatial detail to the question

Agricultural GIS connects field boundaries, observations and imagery, but each dataset has its own spatial support. A point marks a location, a polygon describes an area and a raster pixel summarises a footprint. They should not be treated as equivalent measurements. Before overlaying layers, check their coordinate reference systems, dates and units. A visible alignment problem can arise from a coordinate or georeferencing issue rather than movement or change in the crop itself.

Sentinel-2's bands have different native spatial resolutions. Its visible and broad near-infrared bands are available at finer resolution than its red-edge and shortwave-infrared bands. Resampling can put those bands onto a common grid, but it does not create new observed detail. When a field is narrow or small, boundary pixels may mix crop with roads, trees, water or neighbouring land. Explain that mixture before interpreting a field average as a pure crop measurement.

Preserve quality and time information through the analysis

Optical imagery requires attention to clouds, haze and shadows. A scene with a small overall cloud percentage may still have the target field obscured. Inspect the actual area of interest and retain the masking or quality method used. Compare compatible products and document processing choices, especially when building a time series from different dates or sensors. An unexplained jump may be a data-quality issue rather than a sudden change in vegetation.

Vegetation indices describe combinations of reflected spectral signals. USGS explains that NDVI is sensitive to soil background and can saturate in dense vegetation. Therefore an index is best interpreted with crop stage, canopy structure and field evidence. A colour class is not a direct measurement of nutrient concentration, disease identity or harvestable yield. Those interpretations need suitable calibration and validation, and any prediction should retain its uncertainty and the conditions under which it was evaluated.

Make maps reproducible and useful for the next observer

Keep the original inputs, analysis date, method version and relevant parameters with the output. Use a clear legend that distinguishes observed values, derived indicators and unverified candidates. Where a statistic excludes cloudy pixels or non-crop areas, document the exclusion and the valid coverage. If the coverage changes between dates, acknowledge that the averages may represent different parts of the field. This is especially important when a report turns a sequence of maps into a trend.

Design the validation around the intended use. A model for one crop and season should be tested on independent examples that represent the conditions where it will operate. Field checks should look for missed objects as well as incorrect proposed objects, and classification checks should include each meaningful category. Retain the disagreements and review their causes rather than removing difficult cases. A map becomes operationally valuable when another person can follow its evidence, understand its limits and decide what observation is needed next.

Check the support behind every mapped value

Inspect the source over the actual field of interest. Scene-wide metadata can conceal a cloud, shadow, blurred strip, incomplete survey, or alignment problem exactly where the decision is needed. Record the date, spatial support, quality flags, and valid coverage for each field. An observation with little usable support should remain unavailable rather than being filled with an apparently plausible value.

Review missing values and exclusions separately from valid measurements. A zero, an unvisited location, a masked pixel, and a sensor error describe different circumstances. Preserve the reason for missing data through the summary stage. If an estimated value is used, mark it as estimated and explain the method so that it cannot be mistaken for an independent observation.

Choose acceptance rules before comparing outcomes. Apply them consistently to favourable and unfavourable results. Retain a small collection of difficult examples and revisit it after processing changes. Quality review should include omissions and inaccessible areas as well as the records that were successfully produced. A transparent incomplete dataset is more useful than an apparently complete map whose unsupported values cannot be identified.

Align observations with the crop calendar

Build the calendar from observed field events and management records. Record dates as exact, estimated, or unknown rather than assigning every field the same regional schedule. Several planting, flowering, pruning, or harvesting episodes may occur within a management unit. Preserve that variability when it affects the decision.

Review the image series alongside those events and identify which patterns are visible at the available spatial and temporal resolution. Canopy emergence, closure, removal, and senescence affect the signal, but their appearance varies with crop, environment, management, and the amount of soil or understory in the pixel. A named growth stage needs a suitable reference observation.

Compare fields at similar points in their cycle before classifying a difference as unusual. If the calendar is uncertain, use the map to guide a field check and then update the event record. Report stage confidence and do not imply a precise harvest or maturity date from greenness alone. The calendar should remain a living record that can be corrected as better observations become available.

Define the deliverable and approval

Deliver a composite provenance record with input dates, compositing method, valid-observation counts, and an explanation of the events that the product may smooth over.

A practical review before sharing the result

Check the observation against its source and make sure the field identifier is correct. Review dates, units, missing values, quality exclusions, and geometry versions. Ask a colleague to reproduce one representative result from the recorded inputs. This small independent check often exposes a misunderstood field code or a processing assumption before it affects an entire report.

Write down the alternative explanations for the mapped pattern and identify what evidence would distinguish them. Keep a measured observation separate from the interpretation and from any treatment or management instruction. A decision should name its responsible reviewer and account for local operating procedures. If the evidence is insufficient, the appropriate output is a targeted inspection rather than a confident claim.

Keep the original result, any reviewed version, and a short change log. State which locations and periods the output can reasonably describe. When sharing a map, provide a clear legend, source dates, and an accessible explanation of uncertainty. The recipient should know whether a feature is a confirmed observation, a candidate awaiting inspection, or a model-based estimate.

Turn the investigation into a repeatable field cycle

Prepare the visit with a map that can be used at the intended location and a concise list of questions. Confirm access, permissions, equipment, and the availability of a person familiar with the field. Choose representative stops as well as unusual areas. Record where the planned route could not be followed, because missing observations can change how the result should be interpreted.

After the visit, review the observations while the team can still clarify them. Connect photographs, measurements, and comments to the same field and visit identifiers. Assign a follow-up status and preserve unresolved cases. A correction should explain what changed and why; it should not erase the original evidence or make an earlier interpretation appear to have been certain.

At the next suitable observation date, compare conditions using the same definitions and review any management or weather events that occurred between visits. Record the action actually completed and its operational outcome. This creates an evidence trail from an initial pattern to field confirmation and later review, making the mapping process easier to improve over successive seasons.