Field Boundary Map

What topology validation is, and why your parcel layer has to pass it first

A wooden fence line separates a golden stubble field from a green pasture, with trees beyond.

If you've ever had a shapefile bounce back from your registry's import routine with a cryptic error about "invalid geometry," you already know topology validation matters even if nobody's explained what it actually checks.

Topology, in plain terms, is the set of rules that govern how polygons in a layer relate to each other and to themselves. Every edge in a parcel boundary layer has to behave: no parcel can overlap its neighbor, no parcel can leave an unaccounted sliver of land between it and the next one, and no single polygon can fold back and cross its own boundary. Topology validation is the QA pass that catches these problems before the layer ever reaches your subsidy, lending, or insurance records.

The three checks that actually matter for a parcel layer

Most cadastral GIS topology rulesets boil down to a handful of checks, but three of them cause the bulk of rejected imports.

Gaps. A gap is a sliver of unclassified ground sitting between two parcels that should share a boundary. Sometimes it's a genuine right-of-way or watercourse and belongs there. More often it's a digitising artifact: two adjacent fields traced a meter apart instead of snapped to a shared line. A gap and overlap check on the parcel layer flags every instance so someone can decide which gaps are real and which are errors.

Overlaps. The opposite problem. Two polygons claim the same ground, which in a subsidy or lending context isn't a cosmetic issue, it's a double-counted area that throws off payment calculations or loan collateral figures for both parcels involved. Overlap checks are usually run as a geometry intersection test across the whole layer, flagging every pair of polygons that share area rather than just a boundary.

Self-intersecting polygons. This is the one that trips up manual digitising most often. A self-intersecting polygon is a single parcel boundary where the outline crosses itself, usually from a vertex that got dragged to the wrong side of an adjacent line, or a trace that loops back on itself at a corner. Most registry import routines reject these outright because the area calculation on a self-intersecting shape is undefined or wrong. A self-intersecting polygon fix usually means finding the offending vertex and either moving it back inside the boundary or splitting the shape into the two polygons it was trying to be.

Why registries enforce this before import, not after

A registry that accepts topologically broken geometry inherits every downstream problem that geometry causes. Area totals stop reconciling with declared hectares. Adjacent-parcel queries return the wrong neighbor. Automated area-based payment or risk calculations run against a polygon that doesn't close at all. None of this shows up immediately. It shows up months later when an auditor pulls a parcel and the area field doesn't match the shape on screen, or when two farmers both get paid for the same quarter-hectare strip.

That's why most registry import routines run topology validation as a gate, not a suggestion. A layer either passes, meaning it's edit-ready and can be loaded as-is, or it fails and comes back with a list of the specific gaps, overlaps, and self-intersections that need fixing before resubmission. Teams running this on a digitiser's manual trace often find the same handful of errors recur, because the same junctions and field corners get re-traced slightly differently every cycle.

Where the time goes

Fixing topology errors after the fact is one of the slower parts of maintaining a parcel registry, mostly because it's reactive. Someone has to open the failed layer, zoom to each flagged location, and decide by eye whether a gap is a real right-of-way or a tracing slip. On a county-scale layer with thousands of parcels, that review queue adds up fast, and it's the same queue every renewal cycle if the boundaries are being redrawn by hand each year.

Field Boundary Map builds parcel boundaries straight from high-resolution satellite imagery rather than manual tracing, which is where most of these topology errors originate in the first place. If your registry's import step keeps bouncing layers back for gaps, overlaps, or self-intersections, it's worth seeing what a boundary layer built without screen-tracing looks like for your region and reference year.

Get started

← Back to the blog