Supported Import Formats

VC Planner supports various file formats for importing different types of data into planning projects. All data must be imported through the upload functionality in the planning toolbar or planning editor.

Import Methods

All data (raster data, vector data, and 3D models) can only be imported through:

  • Upload button in the Planning Toolbar

  • Upload dialog in the planning editor

The upload process includes:

  1. Drag and drop files into the upload area

  2. File explorer access by clicking the icon paperclip icon

  3. Import button to start the upload and conversion process

After uploading, the system triggers a conversion job in the Planner backend. Successful conversions appear as data records/layers in their corresponding categories within the planning editor, e.g., GeoJSON will end up in vector layers, GLTF (or 3D Tiles) will end up in for 3D models and PNG/JPEG (raster data) will end up in raster layers.
If you are facing visualization issues after the successful upload, please refer to the Upload Troubleshooting section.
If you are facing issues with unreferenced (not georeferenced) files please refer to the Unreferenced Files Troubleshooting section.

Vector Layer Formats

The following vector formats are supported for importing spatial vector data:

Format File Extension Description

Shapefile

.shp

ESRI Shapefile format including associated files (.dbf, .shx, .prj)

KML/KMZ

.kml / .kmz

Keyhole Markup Language (compressed and uncompressed)

GeoJSON

.json / .geojson

Geographic JavaScript Object Notation

Raster Layer Formats

The following raster formats are supported for importing spatial raster data:

Format File Extension Description

PNG

.png

Portable Network Graphics

JPEG

.jpg / .jpeg

Joint Photographic Experts Group

TIFF/GeoTIFF

.tif / .tiff / .geotiff

Tagged Image File Format (with geographic information)

3D Model Formats

For importing 3D models into planning projects the VC Planner by default supports the following formats:

Format File Extension Description

GLTF

.gltf / .glb

Graphics Language Transmission Format (text and binary versions, only version 1.0 is supported)

CityGML

.gml

Geographic Markup Language for 3D city models (only untextured models)

3D Tiles

.json / .b3dm / .i3dm / .pnts / .cmpt

OGC 3D Tiles specification for streaming massive 3D content as zip file

OBJ

.obj

Wavefront OBJ 3D model format

DAE

.dae

COLLADA Digital Asset Exchange format
GLTF models can be used both as standalone 3D models and as standard models applied to point objects in vector layers.

For importing 3D models into planning projects the VC Planner (extended) also supports the following formats:

Format File Extension Description

ESRI Multipatch

.shp

ESRI Shapefile with 3D multipatch geometry as zip file

DXF

.dxf

AutoCAD Drawing Exchange Format

DWG

.dwg

AutoCAD Drawing Database file format

3DS

.3ds

3D Studio Max native format

STL

.stl

Stereolithography file format for 3D printing

FBX

.fbx

Autodesk Filmbox format for 3D models and animations

IFC

.ifc

Industry Foundation Classes format for Building Information Modeling (BIM)

RVT

.rvt

Autodesk Revit project file format

Supported Drawing Objects

When working with vector layers, the following drawing objects can be created and exported and imported:

  • Line

  • Polygon

  • Bounding Box

  • Circle

  • Rectangle

  • Text Label

Format Considerations

Vector Layer Properties

  • Each vector feature can have individual properties that override layer defaults

  • Performance considerations apply, especially when displaying models (no tiling available)

  • Support for elevation modes: 'On terrain', 'Relative to terrain', 'Absolute'

  • Classification options: objects, terrain, or both

3D Model Properties

  • Model scaling: Values greater than 1.0 enlarge, less than 1.0 reduce

  • Model orientation: Rotation around negative z-axis

  • Model inclination: Rotation around negative y-axis

  • Model rotation: Rotation around positive x-axis

  • Base URL support for resolving relative model URLs (HTTP/HTTPS)

Display Order (z-index)

  • Both vector and raster layers support z-index for display ordering

  • Default z-index of 0 for new layers

  • Negative z-index values supported

  • Different behavior in 2D vs 3D map views:

    • 2D view: Complete z-index support across all layer types

    • 3D view: z-index maintained within same layer type only (raster layers always below vector layers)

For optimal performance and compatibility, ensure your data files follow standard specifications for their respective formats.
In 2D map view, layers with negative z-indices are placed below the base map. In 3D map view, all layers appear above the base map regardless of z-index due to Cesium interface limitations.