Skip to content
PlaidCloud

Spatial File Export

Description

Section titled “Description”

The Spatial: File Export step writes a table to a spatial file in a Document account, one feature per row: the geometry from a WKT column and the other columns as the feature’s attributes. Pair it with Spatial File Import.

The step form has a Source and File section for the source table, its columns, the output file and what happens when the file exists, and a Geometry section for the geometry column and coordinate system. Migrated KNIME workflows use this step for their geospatial file writers.

Configuration

Section titled “Configuration”
  • Source Table (source) — the table to export. Source Columns (source_columns) lists the columns written.
  • Output File (output_file) — the Document account and path of the file. The extension picks the format: .shp (ESRI shapefile), .geojson or .json (GeoJSON), .gpkg (GeoPackage), .kml, .gml, or .tab and .mif (MapInfo). A format made of several files, such as a shapefile, is written with its companion files beside it.
  • Geometry Column (geometry_column) — the column holding each feature’s geometry as WKT. The default is SpatialObj.
  • Coordinate System (crs) — the coordinate reference system the geometries are in, such as EPSG:4326, written with the file.
  • A File That Exists (if_exists) — Overwrite it (overwrite, default) replaces a file that is already there; Fail the step, writing nothing (fail) stops the step before anything is written.
Section titled “Related”