Attribute currency vs. positional accuracy in topographic revision

A row of unfinished houses under construction in a new subdivision, with mountains in the background.

A revision lead hears this question from a program manager at least once a cycle: the database lists a tile as current, yet the orthophoto shows three new cul-de-sacs missing from the layer. The tile's geometry was surveyed correctly to spec; the subdivision just wasn't there yet when the attributes were last updated. A topographic database can have accurate geometry and out-of-date attributes in the same tile, and each kind of staleness needs a different fix.

Positional accuracy is about where a feature sits

Positional accuracy asks whether the road centerline, the building footprint, the stream course are drawn where they are on the ground, within the tolerance your specification sets. A feature can be perfectly placed and still be wrong in every other sense: a building shown in the right spot that was demolished two years ago, a road geometry that matches the pavement but is tagged as unpaved, a hydro line that's spatially correct but references a dam that no longer exists. None of that is a positional problem. The geometry is fine. The database just doesn't know what the feature is anymore.

Attribute currency is about what the database knows

Attribute currency, sometimes called feature currency in revision specs, is whether the classification, name, status, and other non-spatial fields still describe reality. A parcel that changed from agricultural to industrial use. A road that was upgraded from gravel to paved. A building that changed from residential to commercial, or simply stopped existing. These are the changes that field crews find most often when they're sent out on a fixed resurvey cycle, because they don't show up in a positional QC pass at all. You can run a full geometric accuracy check on a tile and it will pass clean while the attributes underneath are two editions behind.

Map edition accuracy, as a program-level concept, is really asking both questions at once: did the geometry move, and did the real-world meaning of the feature change. Most revision specs treat these as separate line items in the QC checklist for exactly this reason. A positional audit and an attribute audit don't catch the same errors, and a database maintenance program that only checks one is going to miss the other category entirely, edition after edition.

Why the distinction decides where you send survey teams

This matters operationally because the two kinds of staleness get found by different methods. Positional drift shows up in control surveys, GNSS checks, or geometric comparison against a higher-accuracy reference. Attribute and feature currency problems mostly get found by someone looking at the ground, or at current imagery of the ground, and noticing that the thing the database describes isn't the thing that's there anymore. New construction, land use conversion, a road resurfaced or decommissioned, a building demolished. None of it moves a coordinate. All of it makes the record wrong.

Most revision programs understand the difference fine. What trips them up is the fixed-cycle model, which forces crews to re-check attribute currency across the entire map extent on a schedule, because there's no other way to know which tiles have had real-world change and which haven't. A tile that hasn't changed in six years gets the same crew-hours as a tile with a new subdivision, because the cycle doesn't discriminate. It's a resourcing problem: the program spends its attribute-currency budget uniformly across a map that didn't change uniformly.

This is the gap National Change Alerts is built around: a continuously updated worklist of which tiles no longer match the ground, built from ongoing high-resolution optical coverage compared against the current basemap, so the feature-currency question gets answered before a crew is scheduled, not after. It doesn't replace a positional accuracy program, and it doesn't verify attributes in the field. What it does is tell a revision lead which tiles actually changed since the last edition, so the resurvey list stops being the whole map and starts being the part of the map that moved.

For a program trying to hold edition accuracy on both axes with a fixed field budget, that's the lever worth pulling first. Positional error tends to be rare and localized once a geodetic framework is sound. Feature currency drifts constantly, in every growing region, between every edition. Knowing where it drifted is most of the problem.

If attribute currency is where your program is losing ground between editions, it's worth seeing which tiles on your map have changed since the last cycle.

Get started

← Back to the blog