Available import/export formats

Prev Next

In this document

You will get familiar with the available Energy system designer import and export formats.

Available import formats

KML imports are performed directly within the Energy System Designer.

Format

Integration

Data type

Supported objects

Notes

.kml

✅ Native

Vector boundaries

Polygon, polylines, points

Only 2D objects, no metadata, no layers, only boundaries, PV tables positions cannot be recognized. Polygon, polylines, and points can be converted in Evaluate to segments, buildings, restricted areas, restricted lines, or shading lines.

Tile service (URL)

✅ Native

Visual raster context

raster tile services e.g. GoogleMaps, Nasa Images, local cadasters

Zoom level 15 and 12, services without authorization. Used for contextual basemap (e.g., satellite imagery or terrain shading)

.dwg / .dxf

🔁 Indirect (converted to KML)

Vector boundaries

Same as .kml

Requires projection to WGS84 and export from QGIS or a similar tool.

.shp

🔁 Indirect (converted to KML)

Vector boundaries

Same as .kml

Requires projection to WGS84 and export from QGIS or a similar tool.

Available export formats

Exports are performed directly in the Energy system designer using the File menu.

Format

Integration

Data type

Supported objects

Notes

.kml

✅ Native

Vector boundaries

Segments, Buildings, restricted areas, restricted lines, shading lines

2D positions of object - after loading to GoogleEarth the elevation is adjusted to native elevation model.

.pvc

✅ Native

PVsyst scene

Entire 3D scene with PV table definition and shading objects

terrain is excluded

.dae

✅ Native

3D scene

Entire 3D scene including terrain mesh

no electrical layout or component definition is present

.xlsx

✅ Native

Bill of Materials

Components, constructions, custom items

supports export quantities per Array

.dwg / .dxf

🔁 Indirect

3D scene

.dae => .dwg / .dxf conversion

no layers are preserved, no boundaries are present