Field Boundary Map

What is an LPIS quality assessment, and how does a paying agency pass it?

Tractor tracks curving through a green cereal field toward a line of trees

If you work inside a paying agency's GIS unit, "LPIS QA" is not an abstract compliance exercise. It's the annual exercise that decides whether your parcel register holds up under audit, and whether the agency ends up writing a financial correction into next year's budget.

What the quality assessment actually checks

The Land Parcel Identification System quality assessment is the yearly check that your reference parcels still match what's on the ground. It's run against a sample of the register, usually against current ortho-imagery, and it's looking for a specific set of mismatches:

None of this is a surprise audit. The agency knows roughly what the sample will flag before the inspector shows up, because the same drift shows up every year in the same places: the parcels nobody has re-walked since digitisation.

Why boundary layers drift between assessments

Most LPIS registers were built by a digitiser tracing screens against whatever imagery was current at the time, then left alone until something forced a re-check: a farmer appeal, a merge request, a flagged inconsistency. In between, the ground keeps changing. Field margins get ploughed in or out, parcels get split for inheritance, irrigation changes the cultivated edge by a few metres here and there. By the time the next QA cycle comes round, a chunk of the register no longer matches what a current satellite pass shows.

This is the gap the quality assessment is built to find, and it's also the gap that costs the most to close by hand. Re-tracing a parcel layer across a region, one boundary at a time, is slow work, and it's usually the first thing that gets deprioritised when the team is also processing claims, appeals, and site visits.

What "passing" actually means

Passing the assessment means the error rate in the sample stays under the threshold the regulation sets, and that the agency can show it has a process for catching and correcting drift rather than relying on a static layer from whenever it was last fully digitised. Auditors want evidence of maintenance: when the layer was last refreshed, what triggered the refresh, and how discrepancies get corrected once found.

That's the part a lot of agencies get wrong. They treat LPIS maintenance as a reactive task, fixing parcels only after a claim gets flagged, instead of refreshing the whole reference layer on a fixed cycle. A register that's updated once every few years against current imagery will always outperform one that's only touched when something breaks, because it catches drift before it shows up in the audit sample rather than after.

Keeping the register current without re-tracing everything

Agencies that stay ahead of the assessment re-run boundary extraction against current imagery on a schedule, every season or every year, rather than waiting for the QA cycle to surface the gaps. Field Boundary Map takes a region and a reference year and returns a polygon layer, with area, ready to drop into the registry without a digitiser re-tracing every edge from scratch. That's the difference between finding drift during your own internal check and finding it during the inspector's sample.

Treat the annual refresh as part of the compliance calendar, not as cleanup after the fact. A register that gets re-aligned to current imagery before each QA cycle starts the inspection from a position of "we already know what changed," which is a much better place to be than explaining a correction letter after the fact.

If your boundary layer is overdue for a refresh, send us the region and the reference year and see what the next layer looks like.

Get started

← Back to the blog