Agriculture

Agriculture is the domain where remote sensing has the longest track record and the clearest economics. Crops are spatially extensive, they change week to week, and nearly every decision about them is made under uncertainty about a field nobody has walked recently. This page is about the domain rather than the method: who needs the observations, what they decide with them, and where the value actually comes from. The mechanics are covered elsewhere on this site — Agricultural Analysis is the seasonal workflow, and NDVI Monitoring is the index-through-time engine underneath it. Read those for how; read this for for whom, to decide what, and what changes when the answer arrives.

The decisions imagery is actually feeding

“Agriculture” is not one audience. A grower or agronomist decides where to scout this week, whether to vary seed, nitrogen, or irrigation across a field, and when a block is ready to harvest. A cooperative or agribusiness decides how to allocate scarce agronomists across hundreds of fields, and how much volume to expect at the elevator. An insurer or agricultural lender decides whether a claimed loss is consistent with what the season looked like, and how to price an area-based index product. A ministry of agriculture or a food-security early warning programme decides whether a region is heading for a shortfall, and whether to move procurement, imports, or aid before prices do.

Those four audiences want different things from the same imagery. They report on different units — a management zone, a farm portfolio, a policy district — and they tolerate different amounts of error, because a wrong scouting trip costs an afternoon while a wrong national forecast moves markets. Most importantly they run on different clocks. Being right after the decision window has closed is indistinguishable from being wrong, and the window in agriculture is set by the crop, not by the analyst. Naming the audience first is what keeps a project from producing a technically sound map that nobody had a use for.

Field scale: managing variability you cannot see from the gate

The premise of precision agriculture is that a field is not uniform, and that the variation inside it is large enough and persistent enough to be worth treating differently. Soil depth, drainage, compaction, planting quality, and pest pressure all vary at scales far below the parcel, and a grower standing at the gate sees almost none of it. Repeated overhead observation is the cheapest instrument that covers the whole field every week, which is why it anchors variable-rate input plans, irrigation zoning, replant decisions, and trial evaluation.

The value is differential treatment. If nitrogen, water, or seed can be varied across a field, then knowing which parts of the field respond differently converts directly into either lower input cost or higher yield on the same ground. If they cannot be varied — a single-rate applicator, a flood-irrigated block — then the same map is interesting but not yet actionable, and it is worth saying so before the season starts.

The honest limit is attribution. A vegetation index tells you where the crop is developing differently, not why. Remote sensing in a field is a triage instrument: it ranks where a human should look, and the human, the soil probe, or the yield monitor supplies the cause. Treating it that way sets the right expectation with growers, who quickly lose confidence in a system that asserts a diagnosis their own eyes contradict. It also sets the right economics, because the return comes from the scouting trips avoided and the problems caught early, not from the map itself.

Regional scale: yield outlook and food security

Change the unit to a district, a province, or a growing region and the same observations serve a different purpose. Here the question is not which corner of a field is struggling but whether an entire production area is tracking above or below normal, and how early that can be said with enough confidence to act on. Consumers of that answer include national statistical and agriculture agencies, famine early-warning programmes, humanitarian logistics planners, and commodity analysts.

Lead time is the whole product. A credible signal that a harvest will fall short is worth far more in the middle of a growing season, when import contracts, strategic reserves, and pre-positioned aid can still be moved, than it is at harvest when the shortfall is a fact. That is why regional agricultural work leans so hard on long, consistent archives and anomaly framing: the claim is always relative to what this region normally looks like at this point in its calendar. That makes a long, consistent archive a domain requirement rather than a preference: a baseline reaching back only three seasons cannot separate a bad year from a new normal, and that distinction is exactly what a food-security judgement turns on, which is why multi-decade records like Landsat carry weight here out of proportion to their pixel size. How such a baseline is paired with a denser current season is the selection question NDVI Monitoring works through; what changes at this scale is that the multi-temporal reasoning the Time Series concept develops is applied to a whole production region rather than a single field. At this scale imagery is also rarely used alone — it is one input beside weather data, crop calendars, market prices, and survey statistics, and its contribution is spatial completeness and timeliness rather than precision on any single field.

What determines whether the value is real

Three things separate agricultural remote sensing that changes a decision from work that merely describes a season. The first is timing against the decision window, which is set by phenology: an answer that arrives after the top-dress window, the irrigation set, or the planting date has passed cannot be acted on at any accuracy. The second is whether the reporting unit matches the decision unit. Field boundaries, management zones, and administrative districts are the units people act on, and where fields are smaller than a few pixels — which describes a large share of the world’s smallholder agriculture — the mismatch described by the Resolution concept is not a technical footnote but a question of who the analysis can serve at all. The third is the asymmetry in the cost of being wrong. A false alarm costs a scouting trip; a missed stress event costs yield; an insurance or subsidy decision made on a bad signal costs money and trust. Which error to prefer is a domain judgement, and it should be made deliberately rather than inherited from a default threshold.

Where the domain stays hard

Ground truth is scarce and often private, because yield monitor records, field boundaries, and input applications are commercially sensitive, so validation data is harder to obtain than imagery. Many of the world’s most food-insecure regions have growing seasons that coincide with persistent cloud, which pushes serious work toward radar and the SAR reasoning that comes with it. Mixed cropping, intercropping, and irregular smallholder parcels break assumptions that hold comfortably on large uniform fields. And adoption is a real constraint: an output that contradicts a grower’s direct experience without explaining itself gets ignored, however good the underlying analysis.

Where to go next

The workflow mechanics live in Agricultural Analysis, which covers the crop calendar, seasonal metrics, and validation, and in NDVI Monitoring for the index and baseline reasoning it builds on. As with the rest of this site, none of the framing here depends on a particular tool — a browser environment like Google Earth Engine is one convenient way to run a season, and a Python stack (rasterio, xarray, geopandas) is another, and the decision the analysis serves is what determines whether either one was worth pointing at the field.