Skip to content

Geospatial Steps

Workflow steps that read, build, transform, and match geometry. Together with the geometry expressions they cover the whole Alteryx spatial toolset — see the Alteryx conversion matrix for the tool-by-tool mapping.

Every spatial step reads and writes geometry as WKT (well-known text) in an ordinary text column. There is no special geometry type to declare and no conversion between steps: a geometry column produced by Spatial File Import is directly usable by Spatial Buffer, Spatial Match, or a SQL expression, in any order.

Each step runs by the simplest route that gives the right answer.

Route What runs there Why
SQL — in the database Find Nearest, Match, plus the geometry expressions Predicate joins and column expressions scale with the table; no rows leave the warehouse
Workflow engine — Shapely and GDAL Everything that reshapes geometry Buffering, smoothing, and dissolving are not expressible in database SQL

You do not choose the route; each step type has one. The distinction matters when you are sizing a job: SQL-route steps scale with the warehouse, engine-route steps scale with the workflow pod.