Skip to content
farmsorted

Check variable-rate zones still fit each paddock’s shape

When a fence comes out and two paddocks become one, the zones from three seasons of yield maps still sit on the old boundaries. The controller runs a flat default rate on the strip in the middle, or rejects the file on the first morning of sowing.

The Variable-rate mapper compares the boundary each paddock’s zones were built on with its shape on the map and finds paddocks merged or redrawn since, and redrafts their zones for your agronomist to set rates and sign off.

When · Scheduled
In March, before the sowing variable-rate files are built
You get
Paddocks whose zones no longer fit, with the hectares left out; zones redrafted on the current boundary; nothing sent to a machine
Approval level
Recommend. Suggests an action. You do it. You can change it.
Useful for
Cropping

What it reads

  • Paddock map: current shapes and areas
  • Zone files in Documents, with the boundary each was built on
  • Yield maps for the last three seasons
  • [agronomist]’s rates by zone from last year

What you get

  • Paddocks where the map and the zones disagree, with the hectares out
  • Zones redrafted on the map’s boundary, saying which seasons they come from
  • The redrafted files saved for [agronomist] to set rates and sign off
  • A note on any strip with less than two seasons of data

When it stops and asks you

  • The new strip has only one season of yield data
  • The map shape looks wrong, not the zones
  • The agronomist wants zones from soil tests instead

How often

Once a year, before sowing

Who uses it

OwnersManagersAdvisors and consultants

Nothing official leaves the farm without your yes.This job runs at Recommend: suggests an action. You do it. You can change that any time.

See the guardrails

The conversation

How the job plays out, step by step.

Variable-rate mapper

Started 6:00am · Scheduled

Start to done
5 min
Agent actions
4
Needed you
2×
[AGENT NAME]For the Variable-rate mapper

On schedule · 6:00am

March: variable-rate files for sowing to be built

Variable-rate mapper

Compared each paddock’s zone boundary with its shape on the map

Paddock 8 is 236 ha on the map since the fence came out, but its zones still sit on the old 168 ha. The 68 ha that was Paddock 9 has no zones, so the controller would run its default rate there. The other 8 paddocks fit.

[AGENT NAME] · 6:00am

Can you join them up? We’ve got yield maps off both.

You · 6:02am

Yes. Old 9 has 3 seasons of yield maps, same as 8, so I can build one set of zones across the 236 ha. It’ll be a draft with no rates for [agronomist] to fill in and sign off. Do it?

[AGENT NAME] · 6:02am

Approved

Go for it.

You · 6:05am

Variable-rate mapper

Redrafted the zones on the new boundary

Done · 6:05am2 waiting for you

  • Paddocks where the map and the zones disagree, with the hectares outSaved
  • Zones redrafted on the map’s boundary, saying which seasons they come fromWaiting for you
  • The redrafted files saved for [agronomist] to set rates and sign offWaiting for you
  • A note on any strip with less than two seasons of dataSaved

Behind the scenes

  1. 6:00am

    Trigger On schedule

    March: variable-rate files for sowing to be built

    • Schedule: first Monday in March
  2. 6:00am+10 sec

    Variable-rate mapper works on it · 2 steps

    Compared each paddock’s zone boundary with its shape on the map

    • records.search9 paddocks with zone files; Paddock 8 is now 8 and 9 joined, 236 ha on the map
    • documents.readPaddock 8 zone file built on the old 168 ha boundary
  3. 6:00am+2 sec

    [AGENT NAME] messages you

    “Paddock 8 is 236 ha on the map since the fence came out, but its zones still sit on the old 168 ha. The 68 ha that was Paddock 9 has no zones, so the controller would run its default rate there. The other 8 paddocks fit.”

  4. 6:02am+3 min

    You reply

    “Can you join them up? We’ve got yield maps off both.”

  5. 6:02am+2 sec

    [AGENT NAME] asks for your yes

    “Yes. Old 9 has 3 seasons of yield maps, same as 8, so I can build one set of zones across the 236 ha. It’ll be a draft with no rates for [agronomist] to fill in and sign off. Do it?”

  6. 6:05am+3 min

    You approve

    “Go for it.”

  7. 6:05am+10 sec

    Variable-rate mapper works on it · 2 steps

    Redrafted the zones on the new boundary

    • vr.export_mapPaddock 8, 236 ha, 4 zones from [year] to [year] yield maps, no rates set
    • plans.draftnote for [agronomist], Paddock 8 zones rebuilt with old 9 joined in
  8. 6:05am+3 sec

    Variable-rate mapper Done

    Paddock 8’s zones redrafted on the 236 ha boundary and saved for [agronomist] to set rates and sign off; nothing sent to a machine; the other 8 paddocks confirmed as fitting

    • reports.draftzone check before sowing, [year]

An example with made-up data. Names and figures in [brackets] are placeholders.

The agent behind it

Variable-rate mapperCropping

The Variable-rate mapper turns yield maps and soil tests into variable-rate seed and fertiliser plans, zone by zone.

What it won’t do

  • Set rates without your agronomist’s sign-off
  • Send a file to a machine
  • Build zones from one season alone without saying so

More jobs the Variable-rate mapper does.

The farm software this job works from

Put [AGENT NAME] to work on your farm.

We’re taking a small number of pilot farms in Australia. Start with one or two agents and add more as you go.

Pilot farms wanted

Want to try it out?

Join the pilot, or book a demo and we’ll walk you through this job on a farm like yours. You text the team from your phone. Some connections are still being built, and we’ll tell you which.

  • Nothing to install

Free report

Getting started with AI.

A free practical guide for Australian farms and agribusinesses

Where AI actually helps on a farm, what it needs from you, the risks to watch, and a 90-day plan to start small.

  • Where it actually helps
  • What it needs from you
  • Risks and guardrails
  • Working out the return
Book a demoJoin the pilot