Field Boundary Map

Handling parcel splits and merges in an annual boundary refresh

Tractor wheel tracks curving through a young green cereal crop towards a line of trees

Every registry team that runs an annual refresh hits the same snag around week two: the new boundary layer doesn't match the old one, parcel for parcel. A field that was one polygon last year is now two. Three small parcels that used to sit on separate folios suddenly trace as one continuous block. Before you can push the new layer live, somebody has to decide what happened to each one and carry the history forward correctly.

This is the part of a refresh that software alone doesn't solve. A fresh satellite pass or an updated vector layer will show you the boundary as it exists on the ground today. It won't tell you that parcel 4471 was subdivided between a father and two sons, or that 4472 and 4473 got bought by the same operator and fenced as a single field. That context lives in your registry, so the matching work has to run through a person who knows the local file.

Spotting a split or merge before it becomes a data problem

The first pass is geometric, not administrative. Overlay the new boundary layer on last year's polygons and look for anywhere the area doesn't reconcile one-to-one:

Flag these during the overlay step rather than after you've already loaded attributes. A split caught at the geometry stage takes ten minutes to resolve. A split caught after payments or loan collateral have already been tied to the wrong polygon takes a phone call to the farmer, a correction request, and a note in the file explaining why the record changed twice in one season.

Carrying attributes forward without losing the chain of title

Once you've flagged the geometry, the harder question is what to do with the attribute history: parcel ID, enrolled area, subsidy claim history, loan collateral status, whatever your registry tracks against that polygon.

For a split, the clean approach is to retire the parent parcel ID and issue two or more child IDs that reference it, rather than reassigning the old ID to whichever new polygon happens to be bigger. That keeps the audit trail intact if anyone later needs to trace a claim back through a subdivision. For a merge, resist the urge to just pick one of the old IDs and drop the other. Retire both and issue a new ID for the combined polygon, with both parents noted, so a lender or paying agency checking collateral history doesn't hit a dead end on the parcel that got absorbed.

Area reconciliation deserves its own line in the QA log. If the two child parcels from a split sum to noticeably more or less than the parent's enrolled area, that's not necessarily an error. It can mean the original digitised boundary was loose, or that the actual split line moved slightly from what the farmer reported. Either way, note the delta rather than silently averaging it away. Whoever reviews claims against that parcel next year will want to know why the number moved.

Building this into a yearly rhythm

Teams that handle this well tend to run the split/merge check as its own step, separate from the general boundary update, with its own sign-off before the new layer gets published. That means someone sits down specifically to resolve the mismatches flagged in the overlay, not just eyeball the finished layer and hope the edge cases got caught. It also means keeping a simple running log of parent and child IDs year over year, since a parcel that splits again two cycles later is a lot easier to trace if the first split was documented instead of just absorbed into the new numbering.

If your current refresh still starts with a digitiser tracing screens from scratch each year, a lot of this reconciliation work is really just you rebuilding the boundary layer from nothing and hoping it lines up. Field Boundary Map delivers an edit-ready polygon layer from the current reference year's imagery. That's the layer you overlay and match against last year's boundaries, already drawn, so your cycle goes into reconciliation work instead of retracing parcel edges from scratch.

If you're due for this year's boundary refresh, get in touch and we'll talk through how the layer fits your registry workflow.

Get started

← Back to the blog