Spatial Info

Description

The Spatial Info step measures each geometry and appends the measurements as columns. It is the equivalent of the Alteryx Spatial Info tool and runs in the workflow engine.

Measurements are WGS84 geodesic, not planar. This matters: the SQL form of these measures is a planar degrees² value scaled by an equatorial constant, and because that constant does not shrink with longitude as latitude rises, it overstates area and length — roughly a quarter high at US latitudes. Computing them geodesically gives one answer that matches Alteryx on every warehouse.

Conversion Only

Spatial Info has no step type of its own. It is produced by Alteryx conversion as an Alteryx Executor step carrying the spatial_info operation, so it cannot be added from the step palette.

Spatial Info measures each geometry — area, length, centroid, and more — and appends the results as columns, computed on the WGS84 geodesic.

Source & Options

• Source Table / Output Table — the input geometries and where the measured rows are written.
• Geometry column — the WKT geometry column to measure.
• Measurements — which measures to append. Each selection adds the columns below.

Output Columns

Measurement	Columns Added	Type
Area (miles)	AreaSqMi	number
Area (km)	AreaSqKm	number
Length (miles)	LengthMi	number
Length (km)	LengthKm	number
Centroid coordinates	CentroidX, CentroidY	number
Bounding rectangle coordinates	BR_Left, BR_Top, BR_Right, BR_Bottom	number
Centroid object	Centroid	WKT geometry
Bounding rectangle object	BoundingRect	WKT geometry
Bounding rectangle polygon	BoundingRectPolygon	WKT geometry
Object type	SpatialObjType	text
Number of parts	NumParts	number
Number of points	NumPoints	number
End-point coordinates	EndPointX, EndPointY	number
End-point object	EndPoint	WKT geometry

The bounding rectangle object and bounding rectangle polygon serialize to the same five-vertex ring in WKT, so both columns carry the same value.

Notes

Object type, part count, point count, and end points are appended under best-effort column names — Alteryx documents the measures but names no output column, so the exact names are verified against a real workflow by a follow-up. The one info type not converted is the Peano key, a proprietary Alteryx spatial index with no public specification: it is skipped, and conversion emits a note naming it so the omission is visible in the converted workflow.

Related

• Geospatial steps
• Geometry Functions — the SQL measures, for cases where planar values are acceptable