GeoAI Can Extract Building Footprints. Making Them Database-Ready Is the Harder Problem
Building extraction is one of GeoAI’s most established use cases, but high segmentation accuracy does not guarantee usable vector data. Once raster masks are converted to polygons, production teams still encounter merged buildings, fragments, distorted boundaries and false positives that cannot be accepted into authoritative databases without review.
A new study addresses this post-segmentation stage. Rather than proposing another extraction network, the researchers developed a quality-control layer that evaluates individual footprint polygons and identifies those likely to require removal or manual inspection.
Testing the full raster-to-vector workflow

The research used 15 cm RGB orthophotos from five UAV survey sites in Bangladesh’s Dhaka Division. Candidate footprints were generated with two different architectures: U-Net with a ResNet-34 backbone and a LoRA-adapted Segment Anything model.
The masks were vectorized, geometrically regularized and consolidated to remove competing representations of the same building. This resembles a practical GIS workflow more closely than evaluating pixel-level segmentation alone. Esri’s own building-extraction example notes that detected polygons require post-processing to eliminate geometric artifacts.
Regularization improves cartographic form, but it does not determine whether a polygon represents the correct building. The researchers therefore described every candidate using 24 variables drawn from three domains.
Geometric variables captured properties such as compactness, elongation and boundary complexity. Spatial-context variables measured local density, nearest-neighbor relationships, orientation consistency and whether a building’s area appeared unusual relative to its surroundings. Raster variables described color, brightness and texture within the footprint.
Human reviewers labeled the resulting objects as acceptable or erroneous. Data from three sites supported model development, while a fourth site containing 4,162 objects was held out as a spatially independent test set.

Geometry and context carried the strongest signal
The best-performing configuration was a decision tree using geometric and spatial-context variables. On the held-out site, it achieved 95.31% accuracy, an F1 score of 91.06% and a Matthews correlation coefficient of 0.880.
At database level, the model identified 87.34% of erroneous footprints while retaining 98.31% of acceptable ones. The reported proportion of errors in the retained dataset fell from 27.32% to 4.62%.
Adding all raster-derived variables did not improve the best result. Direct evidence from polygon form and neighborhood structure was more useful for detecting boundary problems than the most feature-rich combination.
This is an important result for production GeoAI. A footprint’s quality is not only an image-classification problem. It is also a spatial-data problem involving topology, geometry and consistency with surrounding settlement patterns.
What the results do not establish
The independent test site strengthens the evaluation, but all five sites are located in one region. Transfer to different sensors, roof materials, building conventions and urban morphologies remains unproven. A quality model used nationally or globally would require broader geographic validation.
The workflow also depends on manually classified footprint examples. It can reduce the volume of objects requiring inspection, but it does not remove human judgment from the process.
Nor does it solve omission errors. The classifier evaluates candidate polygons that already exist. A building missed by both extraction models will not be recovered by screening their outputs.
These limitations point toward a realistic division of labor. Extraction models can create candidate data at scale. A second model can prioritize suspicious objects. GIS professionals can then concentrate on omissions, ambiguous cases and acceptance standards rather than checking every polygon equally.
As GeoAI moves into cadastral mapping, urban planning and infrastructure databases, this distinction will matter increasingly. The relevant benchmark is not how convincing the initial segmentation looks. It is how much reliable, auditable vector data reaches the database—and how efficiently the remaining uncertainty is handled.
How do you like this article? Read more and subscribe to our monthly newsletter!

