14 October 2026
Deficit irrigation vs. no irrigation: what a seasonal pass actually shows

A parcel can look irrigated on a seasonal composite without ever receiving a full delivery. That gap, between "got some water" and "got water," is where a lot of compliance time gets wasted chasing parcels that technically complied and missing ones that didn't.
Why presence isn't the question you're actually asking
When you're scoping a compliance visit, you're not asking whether a parcel greened up at all this season. You're asking whether what you're seeing lines up with the volume on the license. A parcel running at half its allotment and a parcel running at full allotment can both register as "irrigated" if your screening layer is built around simple vegetation presence or a single wet/dry threshold. The license doesn't care if the field turned green. It cares what volume moved and when.
That's the distinction deficit irrigation collapses: the field is wet enough to grow a crop, often a stressed one, but not wet enough to use its full allotment. No irrigation shows up differently, as bare soil or dryland-pattern vegetation with no seasonal green-up tied to a growing window at all. Those two cases call for different follow-up. One might be a legitimate curtailment, or a grower cutting back mid-season on purpose. The other might be a parcel that never pulled from its point of diversion.
What actually separates the two in a seasonal pass
A single snapshot won't settle it. What separates deficit irrigation from no irrigation is the shape of the season, not any one date.
A deficit-irrigated parcel typically shows a real green-up that starts on schedule, plateaus below where a fully watered field of the same crop would plateau, and often tails off early. An unirrigated parcel in the same basin either stays flat through the season or tracks the rainfall pattern of the surrounding dryland, with no canopy response tied to the parcel's own allotment window.
So the read isn't "is there vegetation." It's whether the vegetation trajectory matches a managed irrigation event at all, and if it does, how that trajectory compares to a full-allotment field growing the same crop nearby. Irrigation intensity, not just irrigation presence, is the thing a seasonal layer needs to carry if it's going to be any use for screening. A parcel flagged only "irrigated: yes/no" tells you almost nothing about compliance. A parcel scored against its own licensed window, with some sense of how much of the season it was actually active, tells you where to send a field crew first.
This is also why one cloud-free image from mid-July won't do the job. Deficit irrigation at the start of the season can look identical to full irrigation that just hasn't started yet. You need the shape of the whole water year, not a frame of it.
What this does and doesn't replace
None of this reads as a metered volume. A seasonal layer built off a wide-swath pass can tell you which parcels show activity outside their licensed window, and roughly when that activity happened, enough to tell you where a compliance visit is worth your time this month instead of walking the whole basin. It can't tell you the acre-feet that crossed a headgate. That's still a meter, a diversion record, or a field visit's job.
What it can do is narrow the list before anyone gets in a truck. Irrigated Area Mapping builds that seasonal layer per parcel against licensed allotment windows, and flags the ones worth a closer look: activity outside the license's active window, or a season shape that doesn't match the volume on file.
If you're tired of treating every parcel in the basin the same way during compliance season, that's the gap this is built to close.