Hand-digitised vs satellite-derived mangrove extent maps: what changes year to year

If you've sat through a verification call and had a reviewer ask why this year's mangrove boundary jogs inward by thirty meters where last year's didn't, you've run into the core problem with hand-digitised extent maps. Most of the time the canopy didn't move. A different person traced the line, at a different zoom level, off a different scene.

How hand-digitised extent maps actually get made

Most blue carbon monitoring reports still carry a boundary traced by a GIS technician in QGIS or ArcMap, on-screen, over whatever scene happened to be cloud-free around the reporting window. The method itself produces the inconsistency, year over year, regardless of how good the technician is. Manual mangrove boundary digitising means someone looks at a composite, zooms to a comfortable scale, and runs the cursor along what looks like the canopy edge, pixel by pixel, across the whole project area.

The issue is consistency. A technician digitising at 1:2,000 draws a different line than one working at 1:5,000. Tide stage in the scene shifts what reads as fringe versus mudflat. And when the person doing the tracing changes from one reporting cycle to the next, which happens on almost every multi-year project, the new line carries the technician's eye more than the mangrove's actual edge. None of that shows up as an error in the shapefile. It shows up two years later as a loss polygon that's really just a different hand on the mouse.

There's also the scene problem. Hand digitising needs a clean, cloud-free image to trace from, and in a lot of mangrove geographies that scene doesn't line up neatly with the reporting period. So the extent map ends up dated to whatever imagery was usable, not to the date the registry wants.

What satellite-derived polygons change

Satellite-derived mangrove loss polygons come from a classification run against multispectral imagery using a fixed method, applied the same way every pass. The canopy boundary comes from spectral and spatial rules, applied consistently regardless of who's running the pass this year. Run the same method on next year's imagery and the comparison between years tracks what the canopy did.

This doesn't mean the output skips review. A project team still has to check edge cases, confirm the loss polygons make sense against site knowledge, and decide how to label anything ambiguous like dieback versus clear-cut. What changes is where the judgment call happens: with hand digitising, judgment is baked into every vertex of the line, year after year, invisible in the final file. With an automated pass, the method is fixed and dated, and a reviewer can ask what rule produced a given edge instead of asking whose hand drew it.

For a registry audience, that's the part that matters. A monitoring report has to show change over time, year to year, that a verifier can trace to the canopy itself rather than to whoever ran the tracing that year. A boundary that moves because the classification is consistent is defensible. A boundary that moves because this year's technician traced tighter to the canopy than last year's is a conversation nobody wants to have during verification.

Picking a method for the next reporting cycle

None of this is an argument that manual digitising is wrong, full stop. A small project with one technician who has drawn the same boundary for a decade and knows the site cold can produce a perfectly usable map. The argument is narrower: as soon as a project needs its extent layer to hold up year after year, across technician changes, across whatever scene happened to be available, the method itself needs to be the thing that stays constant, not the person running it.

That's the gap a dated, sourced annual extent layer paired with a project's monitoring cycle is built to close: one pass a year, matched to the reporting window, with the canopy boundary, loss, and regrowth polygons delivered as GeoTIFF and vector so the report has a line that moved because the mangrove did.

If your next extent map needs to survive a verifier's question about why the boundary moved, it might be worth comparing a dated satellite pass against whatever got hand-traced last year.