November 2, 2026

Minimum patch size for a section shutoff: the math

Sunlit rows of young corn plants in a cultivated field.

Every section shutoff costs you something: a valve cycle, a half-second of controller lag, and a strip of boom that's either spraying nothing it should or something it shouldn't while it catches up. Below a certain patch size, that cost is higher than just running the section wide open across the gap. The hard part is knowing where that line sits for your rig.

Why there's a minimum at all

Boom section control doesn't switch instantly. Between the controller flagging "weed detected" and the nozzle opening or closing, there's a response lag, usually somewhere in the half-second to one-second range depending on your valve type and controller. At 12 km/h that lag alone covers a meter and a half of ground. At 20 km/h it's closer to three meters.

That means a patch shorter than your lag distance, plus the width of the section doing the switching, never gets a clean on/off cycle. You get overspray on the leading edge, underspray on the trailing edge, or both. The shutoff fires, but by the time the section responds the sprayer's already past the patch or already into it. You've worn a solenoid and gained nothing.

Doing the math for your own section

Start with three numbers you already have written down somewhere, or should:

  • Section width: the physical length of boom that one solenoid controls.
  • Response time: ask your controller manufacturer or check the spec sheet; it's usually quoted in milliseconds.
  • Working speed: your actual field speed for this pass, not the number on the quote.

Multiply response time by speed to get your lag distance. Add that to the section width. That total is roughly the shortest patch, measured along the direction of travel, where a shutoff actually closes and opens cleanly instead of smearing across the whole move.

Say your section is 3 m wide, your controller lags 0.6 seconds, and you're running 15 km/h (about 4.2 m/s). Lag distance is roughly 2.5 m. Add the section width and you're at 5.5 m before a shutoff does what you think it's doing. Anything smaller and you're better off either treating that stretch at blanket rate or accepting a bit of overspray and moving on, because the valve can't react fast enough to make the gap worth it.

This number isn't universal. A narrower section or a faster-responding valve brings the threshold down. A faster pass speed, which is often what you want on a tight spray window, pushes it back up. Set it per rig, per section config, before the pass starts, not mid-field when you're trying to decide on the fly whether that scrap of resistant ryegrass is worth flagging.

Where the treat map fits

A treat map built at leaf scale will show you patches well under a meter across. That resolution is the point: it tells you exactly where the weed is. But not every patch it shows is worth triggering a section for. If your math says 5.5 m is the floor, any patch under that size on the map either gets folded into blanket coverage for that section or gets left for a different pass, rather than tripping a shutoff that won't execute cleanly anyway.

That's a filtering step worth doing before you load the job, not during the run. Decide your minimum patch size against your own section geometry and lag, then treat the map as the input to that rule rather than a command to chase every dot. Weed Mapping builds the spray-ready patch map from the UAV pass that flew the field, matched to that pass, so you've got the patch sizes in hand before the sprayer rolls and can set your section thresholds with real numbers instead of guesswork.

If you're running spot spray this week and want the patch map ready before the window opens, that's the whole offer.

Start a pilot

← Back to the blog