Spatial Info
Description
Section titled “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.
Source & Options
Section titled “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
Section titled “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 |
The bounding rectangle object and bounding rectangle polygon serialize to the same five-vertex ring in WKT, so both columns carry the same value.
Alteryx offers several further info types — object type, part count, point count, Peano key, and end-point coordinates — that have no verified Alteryx-parity definition here. They are skipped, and conversion emits a note naming the ones it dropped so the omission is visible in the converted workflow.
Related
Section titled “Related”- Geospatial steps
- Geometry Functions — the SQL measures, for cases where planar values are acceptable