Skip to content

The Spatial File Import step reads a spatial file — MapInfo .TAB, ESRI .shp, .kml, .geojson, or SRC .geo — and its sidecar files into a table, one row per feature with a WKT geometry column. It is the equivalent of the Alteryx Input Data tool pointed at a spatial file and runs in the workflow engine (GDAL).

  • Source — the spatial file in the document store. Its sidecar companions (e.g. a .TAB’s .dat/.map/.id/.dbf, or a shapefile’s .shx/.dbf/.prj) are read automatically from alongside it.
  • Target Table — the table the features are written to.

The output schema is taken from the file, so there is no column mapping. A SRC .geo file’s proprietary geometry cannot be read; its .dbf attributes are imported with empty geometry values.