October 13, 2026
Treat map vs prescription map: what it actually tells the sprayer

A grower hands you a prescription map from their agronomist. Your controller wants a treat map. Somewhere in that handoff, half the operators I talk to just assume they're the same file with a different name. They're not, and the gap between them is usually where a spray job goes sideways.
Prescription map: the agronomy input
A prescription map (often shortened to Rx map) is an agronomic recommendation. It's built from soil sampling, yield data, NDVI zones, or a combination of all three, and it tells you rate: how much nitrogen, how much fungicide, how much of whatever product, per management zone across the field. It's usually drawn at a coarser grid, zone by zone rather than plant by plant, and it answers an input question: how much product to put down by zone, decided ahead of the pass. A prescription map doesn't know what the field looked like this morning. It knows what the agronomist decided the field needed when the plan was written, which might've been weeks ago.
That's fine for variable rate fertility or a blanket fungicide pass where the zones don't move much between visits. It's the wrong tool for weeds, because a weed patch three weeks ago is not the weed patch today.
Treat map: the spray-day output
A treat map is what the boom executes. It's built from the current pass, flown specifically to find what's there right now, and it's formatted for the sprayer's section control, not the agronomist's zone plan. Where a prescription map says "zone 4 gets 18 oz," a treat map says "spray this patch, skip this square metre, shut off section 6 here." It's a binary or near-binary on/off instruction tied to plant position at leaf scale, built from where the weeds are standing on this pass.
The confusion mostly comes from the file format. Both can land in your cab as a shapefile the controller reads the same way. But a prescription map encodes a rate decision made in advance, and a treat map encodes a weed location found on this pass. Load the wrong one and you either blanket-spray a field that needed spot treatment, or you try to run section shutoff off a rate file that was never built for it.
Patch map vs variable rate map
This is really the same split by another name. A variable rate map is a prescription map's close cousin: it dials rate up or down by zone, but the whole field still gets product, just at different volumes. A patch map does something different. It treats the weed patches and leaves the rest of the pass untreated. A patch map narrows where the rate applies, leaving untreated ground untouched instead of just dosing it lighter.
For spot spray work that distinction decides your chemical spend for the week. A variable rate file still covers every acre, just unevenly. A patch map, built from imagery flown close enough to separate weed from crop, covers only the acres that have a weed problem.
A quick glossary for the cab
- Prescription map (Rx map): agronomic rate plan by zone, built in advance.
- Variable rate map: executes the Rx map, rate varies by zone, full-field coverage.
- Treat map: spray-day instruction built from the current pass, tells the boom where to spray and where to shut off.
- Patch map: a treat map where the unit is the weed patch itself, not a zone grid.
- Section shutoff: what the controller does with a treat map when it hits ground with no weed on it.
If your controller is asking for one file and your agronomist handed you the other, that's worth sorting before the spray window closes, not after the tank's half empty.
Weed Mapping builds the treat-map side of that equation: a spray-ready patch map matched to the pass that flew it, built from imagery sharp enough to separate weed from crop at leaf scale instead of guessing by zone. If this week's run needs that kind of map rather than a rate file, that's the problem we're working on with pilot partners right now.