Cadastral vs. topographic revision: why the two map layers drift apart

A golden stubble field with rows stretching toward the horizon under a clear sky.

Most revision schedules lump "boundary work" and "feature work" into one line item, as if a parcel edit and a new road segment come from the same trigger and deserve the same cycle. They don't. A cadastral update usually starts with a legal instrument: a subdivision plan, a survey return, a court order on a disputed line. A topographic revision usually starts with the ground itself changing shape, a new building footprint, a rerouted stream, a quarry that's eaten another two hectares. Different triggers, different evidence requirements, and in practice, different timelines that rarely line up.

Two layers, two kinds of truth

The cadastral layer is a record of rights. It changes when a legal document says it changes: a subdivision plan is filed, a survey return comes back, an easement is registered, two adjacent lots are merged on paper. The surveyor's job is to transcribe that instrument onto the parcel fabric correctly. A boundary can sit unchanged on the ground for decades while the cadastral database still needs an update for exactly that reason, the paperwork moved even though the fence didn't.

The topographic database works the other way. There's no instrument to wait for. A feature revision exists because something was built, demolished, eroded, flooded, or regrown, and the only way to know is to look. That's why topographic revision has historically run on a fixed cycle, five years, seven years, whatever the agency can afford, while cadastral revision runs continuously but narrowly, triggered lot by lot as paperwork arrives.

Put those two cycles side by side on a map and the mismatch is obvious. A district with heavy subdivision activity might see its cadastral layer touched monthly while its topographic sheet hasn't had a field crew on it in six years. A forested district with almost no land transactions might be cadastrally stable for a decade while the road network, tree line, and drainage have moved substantially.

Where the two cycles collide

This matters most at the point where a parcel edit and a feature edit sit on the same tile. A new subdivision plan comes in, the cadastral team updates the lot lines, and nobody checks whether the access road shown on the topo base was ever built as shown, or whether it ended up somewhere else once construction started. The two revisions get filed separately, and the topo layer quietly goes stale right where the cadastral layer just got fresh attention.

Knowing, tile by tile, which layer has drifted from the ground and by how much lets the two workflows route survey effort to the same place when it's warranted and skip it when it isn't. That's a harder question to answer from a desk than "has a subdivision plan been filed," because topographic change doesn't file paperwork. It has to be detected.

This is the gap a continuously updated change index is built to close: instead of waiting for the next scheduled topo sweep or hoping a field crew notices a mismatch while they're out for a cadastral job, you get a running list of tiles where recent high-resolution optical coverage no longer matches the topographic basemap, scored and ready to compare against wherever the cadastral team is already working that month. When a subdivision triggers a boundary edit and the change index flags the same tile for a feature mismatch, that's the signal to send one crew to do both jobs in one trip instead of two separate visits six months apart.

What this changes in practice

This doesn't collapse cadastral and topographic maintenance into one process. They answer different questions and will keep running on different clocks. But a maintenance lead who can see, for any given tile, whether the trigger is legal (an instrument) or physical (ground change) stops treating "when was this last surveyed" as the only planning input. The question becomes "has anything here actually changed," and for the topographic side of that question, satellite comparison answers it faster than a fixed-cycle sweep ever could.

Worth a look if your topo layer has gone stale in places your cadastral team visits anyway.

Get started

← Back to the blog