SPM for ZWCAD > Features > Export data > Optimized export

Optimized export in ZWCAD

Export with precision and flexibility, including direct format conversion

Exporting spatial data is made easier with automated geometric adjustments such as curve segmentation for polygonal formats and review of selected objects to match the target specification. Once the export is complete, you can open the file location or launch it in Google Earth if exporting to KML/KMZ. Use direct export to convert data between different geospatial formats and sources without needing to go through a drawing.

Editions: Professional
What's included in the feature Optimized export

Discover the full potential of this set of tools designed to enhance GIS data integration and editing within ZWCAD.

Automatic complex geometric operations

Review and editing of the selected objects in order to export geometries accommodated in the target format, such as the polygonal segmentation on curves if required.


Filtering of incompatible objects

There are a few object types not supported by the export processes (such as complex 3D objects), which are automatically filtered. The filter result is displayed before exporting.


Opening help

Upon completion of any export process to a file, the file location can be opened directly. When exporting to a KML or KMZ file it can be chosen to open the file in Google Earth (if installed).


Geospatial direct Exporting

This function allows direct conversion between different data providers formats and sources without the need to import/export into/from drawing.

frequently asked questions
Current compatible ZWCAD applications:
  • ZWCAD and ZWCAD Architecture
  • Professional edition (Classic and Standard editions are not compatible, but you can use Spatial Manager Desktop™ to import/export via DXF files)
  • Versions: From v.2017 to v.2026 both included. Review the version compatibility page for more details.
System requirements:
  • Windows 7 or higher, within the operating system versions supported by the ZWCAD version used
  • 500 MB free disk space, or more
  • Windows Installer 3.1 or later
Spatial files
  • Esri Shape file - (SHP)
  • Google Earth file - (KML, KMZ)
  • OpenStreetMap file - (OSM, PBF, OSC) (1)
  • LiDAR file - (LAS, LAZ)
  • GPS exchange format file - (GPX)
  • Esri ASCII Grid file - (ASC, ASCII) (1)
  • ASCII text file - (ASC, CSV, NEZ, TXT, XYZ, UPT)
  • SQLite file - (SQLITE, DB)
  • GeoPackage file - (GPKG)
  • GML file - (GML, GZ, XML)
  • Raster image file - (TIF, PNG, JPG, JPEG, TIFF) (1)
  • Autodesk SDF file - (SDF) (3)
  • MicroStation v.7 file - (DGN) (2)
  • AutoCAD DXF file - (DXF) (2)
  • Esri ArcInfo export file (ASCII) - (E00) (1) (2)
  • MapInfo file - (TAB) (2)
  • MapInfo interchange format file - (MIF/MID) (2)
  • GeoJSON file - (GEO.JSON)

Spatial raster files
  • Raster image file - (TIF, PNG, JPG, JPEG, TIFF) (1)
    • Georeference sources - (World files, Google Earth .GEPRINT, etc.)
  • Variable resolution Raster image file - (Cloud Optimized GeoTIFF/COG TIFF) (1) (4)

Spatial data servers and Geo-databases
  • Esri Geodatabase File - (GDB) (1)
  • PostGIS database
  • Microsoft SQL Server Spatial database
  • MySQL database (1) (3)

Image map servers
  • WMS/OGC API Maps Web Map Services (4)
  • WMTS/OGC API Tiles Web Map Tile Services (4)
  • XYZ/TMS Tile Map Services (4)

Other spatial data sources
  • Open Database Connectivity ODBC (1)
  • WFS/OGC API Features data store (1)
  • WFS data store (FDO) (1) (3) (5)
  • WFS data store (OGR) (1) (2) (5)

(1) Read-only
(2) OGR data source
(3) FDO provider
(4) Background Maps technology
(5) DEPRECATED - Whenever possible use the native WFS/OGC API Features data provider

Note: certain data Providers are only valid for some Editions of the application