VECTOR / CAPABILITIES

3D city models

Explore the city in 3D.

URBAN CONTEXT

From local files to urban context.

Bring textured buildings and local 3D models into the map. Explore urban detail and place annotations in geographic context.

Concept illustration of source buildings and facade textures processed into levels of detail for a textured map view — Model-processing concept — local source, prepared detail levels and map display.

Choose the source

Import a local package containing OBJ and its materials, a self-contained GLB scene, or supported CityGML buildings.

Prepare and position

Supply the model origin, scale, orientation and height reference when the source has no geographic placement. Review alignment against the map.

Process once, reuse locally

The C++ model service optimizes OBJ and CityGML into cached 3D Tiles with detail levels and compressed textures. Static GLB scenes retain their supplied geometry.

URBAN VIEWS & SHARED OBJECTS

Local city detail.
Connected mission context.

Use the city model to understand buildings and streets, then place geographic objects in that context. Other operators can locate shared objects within their own map.

Concept illustration of a textured city with a geographic marker and area shown in a second workstation’s 2D map — Urban-context concept — shared geographic objects over independently loaded maps and models.

Manage local packages

Use Settings → Local 3D models to select a package, follow processing progress, cancel a job or show and hide an installed dataset.

Explore the prepared scene

Move between the surrounding map and textured building detail. Prepared OBJ and CityGML datasets use distance-based detail levels; placement follows the supplied geographic information.

Share geographic meaning

Share supported map drawings and airspace through Mesh while each workstation loads its own required model package. The shared object’s location remains separate from the model files.

HOW IT CONNECTS

Two connections. One workspace.

Model processing runs locally through the C++ service. Mesh sharing does not automatically transfer the city’s geometry or texture files to another workstation.

Explore Mesh & DDS

Local model service
Source files become a cached dataset for the map.
VECTOR city view
Buildings, streets and geographic annotations.
Mesh / DDS
Supported shared-object updates between workstations.

All capabilities NEXT CAPABILITYGeospatial awareness

YOUR NEXT PERSPECTIVE

Bring your mission.
See it in VECTOR.

Explore the platform through the workflows that matter to your team.

Request a demo