Geospatial Annotation
Annotate satellite, aerial, and large-raster imagery with deep zoom, spatial coordinates, structured ontologies, and AI-assisted segmentation.
Unitlab supports geospatial annotation across large satellite, aerial, and drone imagery. Teams can move from area overview to object detail, preserve geospatial context, label land cover and infrastructure, and review model-assisted geometry within governed workflows.
See geospatial annotation in action
The demo shows current large-image navigation and spatial annotation for geospatial data.
Before you begin
Create or select a project whose data and ontology match this modality.
Confirm the project instructions define the unit of annotation, boundary or timing policy, required properties, and review route.
Open the project and enter the assigned item from the project data view or queue. The Workbench loads the modality-native editor inside the shared Unitlab shell.
See Annotation Workbench for navigation, saving, item state, comments, issues, and workflow actions.
Understand the geospatial work surface
The geospatial experience applies Unitlab’s visual Workbench to large spatial rasters. Deep zoom preserves a continuous image while annotation geometry, ontology values, comments, history, and workflow actions remain available around the active view.

Large-image support keeps broad spatial context available while labeling small objects and boundaries.
Supported annotation model
Bounding box
Vehicles, structures, assets, and other localized objects.
Segmentation mask
Roads, water, vegetation, buildings, damage, and land-cover regions.
Polygon
Parcels, rooftops, fields, sites, and irregular boundaries.
Line or polyline
Roads, paths, utilities, coastlines, and other linear features.
Point or keypoint
Poles, signs, landmarks, and inspection targets.
Skeleton
Defined landmark structures where a connected point model is required.
Cuboid
Perspective-aware 3D-like extent for supported aerial targets.
Item Property
Source, capture condition, sensor, scene, and quality context for the complete image.
Relation
Connections among buildings, roads, vehicles, parcels, and other objects.
Write spatial rules for tile edges, partial objects, minimum mapping unit, occlusion, shadows, seasonal change, coordinate reference, and whether repeated features require exhaustive coverage.
Coordinate-aware spatial context
Keep georeferencing and spatial coordinates attached to the large image and its annotations. Zoom or pan should change only the view, not the underlying coordinate meaning. Confirm coordinate expectations before export, especially when downstream systems require a specific reference or projection.

The same labeled feature remains grounded in the source image’s spatial context.
Geospatial ontologies and relations
Use hierarchical classes for buildings, roads, land cover, crops, utilities, and project-specific targets. Add required properties such as type, condition, surface, confidence, or source; use Item Properties for capture and scene context; connect objects with governed relations such as adjacent-to or connected-to.

Structured ontology values turn shapes into consistent spatial training data.
AI-assisted masks and repetitive features
Use supported model assistance, Magic Touch, or Find Similar to propose visual labels, then inspect every boundary and object in source context. Repetitive rooftops, roads, fields, or vegetation can accelerate well, but seasonal variation, shadows, occlusion, small structures, and domain shift require human correction.

Assisted geospatial labels remain editable proposals inside the human review workflow.
Annotate one production item
Quality review
Spatial reference
Preserve image identity, coordinate meaning, and expected export reference.
Coverage
Apply the same exhaustive or sampled labeling rule across the full area.
Boundary policy
Check shadows, occlusion, partial objects, seasonal change, and the minimum mapping unit.
Topology
Review connected lines, adjacent polygons, overlaps, gaps, and object relations.
Scale
Confirm geometry at detail resolution and semantic correctness at regional context.
A saved annotation is not automatically a production-ready annotation. Required values, boundary or timing policy, cross-item consistency, and the configured review stage still apply.
Move from labels to governed data
Geospatial outputs should preserve source raster identity, spatial coordinates, geometry, ontology values, relations, version, and reviewer provenance. Use curated cohorts, dataset versions, and releases to separate geography, season, sensor, and domain conditions for reproducible model development.

Use workflows to keep model output, human correction, review, and approval in one traceable operating path.
Next steps
Use Detect Anything (SAM 1–SAM 3) to calibrate interactive and batch assistance.
Use Multimodal overview when related files or views must stay in one task.
Curate difficult cases and review cohorts in Data curation.
Read the current geospatial annotation product overview for the feature overview and current media.