What a change tile index is, and how it differs from an orthophoto mosaic

View from an airplane window of a wing over patchwork farmland seen from altitude.

Anyone who has sat through a production review knows the orthophoto mosaic by heart. Fly the block, correct the imagery for lens and terrain distortion, tie it to ground control, seam it into one continuous picture of the area. It's the base layer everything else in the agency gets hung on: parcel lines, road centerlines, hydrography, the whole stack. A mosaic answers one question well: what does this ground look like, rectified and to scale, right now.

A change tile index answers a different question, and it's the one that actually decides where the survey truck goes next week: which tiles in that mosaic no longer match what's on the ground.

Two products, two jobs

The mosaic is a picture. The change tile index is a worklist, built by comparing continuous high-resolution optical coverage against your current basemap layer, tile by tile, and scoring each one for how much it has moved away from what the map already shows. A new subdivision grading out a field edge scores high. A parking lot that got repainted scores low or doesn't register at all. The output is a layer plus a table, and the table is what your dispatcher opens before assigning anyone a route.

That table is the tile ID CSV: tile identifier, change score, maybe a timestamp, one row per tile in the index. No photo interpretation required to read it. Sort by score, draw a line under the threshold your program uses for "worth a look," and that's your field list for the cycle. Compare that to how a resurvey cycle usually gets planned, which is geographic coverage on a fixed rotation regardless of whether anything in that quadrant has changed since the last pass.

Why the distinction matters for planning

Agencies that run strictly on a resurvey calendar tend to treat the orthophoto mosaic as both the evidence and the trigger: a new flight comes in, someone eyeballs it against the old layer, and change detection happens informally, in someone's head, usually the same senior cartographer every time. That works until the backlog grows faster than the eyeball time does, which is most agencies right now.

A change tile index separates those two jobs on purpose. The mosaic stays the record of ground truth for the area, the thing you deliver and archive and defend in a map accuracy report. The change layer sits on top as a filter, routing attention to the subset of tiles where the ground and the basemap have diverged, measured against a cadence you don't have to wait a full mapping cycle to see. A supervisor doesn't need a GIS tech to generate that shortlist. The CSV does the sorting. A project lead reads it in the morning meeting and assigns tiles the same way a dispatcher assigns routes: by what came in overnight, not by what's next on a rotation schedule set two years ago.

It also changes what "coverage" means internally. A full-extent resurvey treats every tile as equally worth a revisit. A change-based worklist treats tiles as earning a revisit, and a tile that scores zero three cycles running is a tile your field crews stop walking past out of habit. That's hours back, and it's hours that go to the tiles moving.

Reading the score, not just the color

Most teams start by treating the change score like a stoplight, red tiles first, then amber, then whatever's left if there's budget. That's a reasonable first pass. Where it breaks down is treating a low score as proof of nothing happening. A score reflects what the comparison caught between the basemap vintage and the latest coverage. It doesn't replace a surveyor's judgment about whether a flagged tile is a genuine mapping discrepancy or a shadow, a seasonal crop change, construction scaffolding that'll be gone by spring. The index narrows where to look; it doesn't make the field call.

If your resurvey cycle is still built around flying the whole extent and hoping someone notices what moved, National Change Alerts is built to replace that guesswork with a tile-by-tile worklist you can hand straight to dispatch.

Get started

← Back to the blog