SPM for ZWCAD > Features > Export data > Export options

Export options in ZWCAD

Export selected objects as polygons, features, or full drawings to geospatial destinations

Export entities from your current drawing to spatial formats or data servers—whether into new or existing tables, files, or database schemas. Select specific objects, entire layers, or the whole drawing. You can also choose to treat closed polylines as polygons, ensuring accurate geometry when moving from CAD to GIS environments.

Editions: Professional
What's included in the feature Export options

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

Objects exported to geospatial files or servers

From the current drawing to new or existing tables in files or schemas inside files or databases.

Objects exported to geospatial files or servers<span style='font-size: 1rem;'></span>

Select the objects to be exported

Choose between exporting the selected objects, the objects in a layer or the whole drawing.

Select the objects to be exported<span style='font-size: 1rem;'></span>

Option to treat the closed polylines as polygons

Most of the time the closed polylines represent polygonal elements on the target data format and this conversion can be automatic.

Option to treat the closed polylines as polygons<span style='font-size: 1rem;'></span>
Related features
Data export<span style='font-size: 1rem;'> - <a href='../data-export/' class='app_color_link'>More info ></a></span>

Data export

Select and export rich data from ZWCAD objects

Optimized export<span style='font-size: 1rem;'> - <a href='../optimized-export/' class='app_color_link'>More info ></a></span>

Optimized export

Export with precision and flexibility, including direct format conversion

Export to KML and KMZ<span style='font-size: 1rem;'> - <a href='../../google-earth-publishing/' class='app_color_link'>More info ></a></span>

Export to KML and KMZ

Export objects directly from ZWCAD to Google Earth with a single click

Export to spatial files and databases<span style='font-size: 1rem;'> - <a href='../export-to-spatial-files-and-databases/' class='app_color_link'>More info ></a></span>

Export to spatial files and databases

 Enhanced in V10

Export ZWCAD objects to geospatial files or servers

Related Posts
Export elevation labels in feet in Google Earth

Google Earth internally works with meters as elevation units and this can be an obstacle when feet are the desired measurement units. This tutorial explains an easy workaround for viewing... more

Esri Geodatabase File to DWG/DXF

An ESRI Geodatabase File (FileGDB), is a powerful database system designed to store, query, and manage spatial data as a collection of files stored directly on disk without the requirement... more

Convert height units when exporting to Google Earth and other formats

Height units remain unchanged when coordinate conversions are applied, but sometimes it is required to change them, especially when the target format is limited to a specific unit, this happens... more

Export more 3D objects to Google Earth (KML/KMZ)

3D modeled objects are exported to Google Earth (KML/KMZ) in a very easy and intuitive way. Different altitude and height modes are available depending on how the model has been... more

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