Extract from Geocolumn
Infoveave Data Automation — Geospatial
You have a polygon column. You need centroid, perimeter length, and area as separate columns. Configure the three output column names — Infoveave reads the WKT and derives all three without a single PostGIS function.
Polygon and linestring geometries stored as WKT strings contain implicit spatial properties — the centroid of a coverage area, the perimeter of a territory boundary, the length of a route, the area of a catchment zone. Extracting these properties for reporting or filtering against normally requires ST_Centroid, ST_Length, and ST_Area functions in PostGIS, or Shapely's centroid, length, and area attributes in Python — tools that require database GIS extensions or library installation. Extract from Geocolumn derives all three spatial properties directly in the data pipeline, adding them as typed columns without requiring any GIS function knowledge. The result is immediately available for filtering by area threshold, ranking by size, joining centroid points to other spatial datasets, and displaying area or length values in reports alongside the geometry column.
What Extract from Geocolumn does
Extract the centroid point, length, and area from WKT polygon and linestring geometry columns in Infoveave. Automatically derive spatial properties from POLYGON, LINESTRING, and POINT geometries without PostGIS ST_Centroid, ST_Length, or ST_Area queries, and without shapely or GIS software.
When to use Extract from Geocolumn
- You have a WKT POLYGON geometry column representing territories, coverage zones, catchment areas, or service regions and you need to add centroid coordinates, perimeter length, and area as separate numeric and point columns for reporting, ranking, or filtering
- You have a WKT LINESTRING geometry column representing routes, paths, or network segments and you need to add the centroid point and length of each segment as separate columns for route analysis and display
- You are validating geometry quality and need to confirm that polygon coverage zones have non-zero area values — use the extracted area column to filter degenerate or empty geometries
- You need to compare the sizes of multiple polygon territories — such as sales territories, delivery zones, or management regions — and want area and length values as numeric columns for sorting and ranking
When to avoid it
- Your geometry column contains only POINT coordinates and you only need to extract latitude and longitude separately — use Extract Latitude/Longitude from Geopoint for point coordinate parsing
- You want to create a coverage area polygon from a point rather than extract properties from an existing polygon — use Create Area Around Geopoint to generate new polygons from point data
- You need to reproject the geometry from one CRS to another before extracting properties — use Change Coordinate System first, then Extract from Geocolumn on the reprojected column
Where it fits in your Infoveave automation
Extract from Geocolumn is one step inside a multi-step Infoveave workflow. Chain it with other activities — no code, no manual hand-offs.
Build this workflow visually in Infoveave Data Automation — drag, connect, and schedule with no infrastructure setup.
How teams use Extract from Geocolumn
Real scenarios where this transformation saves hours of manual work.
Extract Catchment Area and Centroid from Store Coverage Polygons
A retail network team has generated store catchment polygons using the Create Area Around Geopoint transformation. The polygons are stored in a WKT POLYGON column. The team needs the area of each catchment in square kilometers and the centroid point for ranking stores by market coverage size. Extract from Geocolumn is configured to produce CatchmentCentroid, CatchmentPerimeter, and CatchmentArea columns. The area column is used to classify stores as megastores, standard, or compact based on defined thresholds.
Compute Route Length from Delivery Path Linestrings
A logistics planner processes delivery route records where each route is stored as a WKT LINESTRING representing the vehicle's path. The team needs the length of each route in kilometers to calculate fuel cost estimates. Extract from Geocolumn extracts the RouteLength column from the LINESTRING geometry. The centroid column provides the approximate midpoint of each route for regional classification and dispatcher assignment.
Measure Banking Zone Areas for Regulatory Compliance Reporting
A bank's compliance team maintains sales territory polygons in WKT format and must report the geographic area in square kilometers covered by each territory for regulatory submissions. Extract from Geocolumn produces TerritoryArea, PerimeterLength, and TerritoryCenter columns from the zone polygon column. The area values are used in the compliance report and audited against minimum coverage requirements.
See Extract from Geocolumn in action
Input data (left) is transformed using the configuration below. The output table (right) is ready for dashboards or downstream steps.
GeometryWKTCentroidPointPerimeterLengthCoverageAreaInput Data
| ZoneID | ZoneName | GeometryWKT |
|---|---|---|
| 1 | Square Zone | POLYGON((0 0, 0 5, 5 5, 5 0, 0 0)) |
| 2 | Triangle Zone | POLYGON((0 0, 4 0, 2 3, 0 0)) |
| 3 | Route Path | LINESTRING(0 0, 3 4) |
| 4 | Event Point | POINT(2.5 2.5) |
| 5 | Rectangle Zone | POLYGON((0 0, 0 3, 6 3, 6 0, 0 0)) |
Output Data
| ZoneID | ZoneName | GeometryWKT | CentroidPoint | PerimeterLength | CoverageArea |
|---|---|---|---|---|---|
| 1 | Square Zone | POLYGON((0 0, 0 5, 5 5, 5 0, 0 0)) | POINT(2.5 2.5) | 20.00 | 25.00 |
| 2 | Triangle Zone | POLYGON((0 0, 4 0, 2 3, 0 0)) | POINT(2.0 1.0) | 11.21 | 6.00 |
| 3 | Route Path | LINESTRING(0 0, 3 4) | POINT(1.5 2.0) | 5.00 | |
| 4 | Event Point | POINT(2.5 2.5) | POINT(2.5 2.5) | ||
| 5 | Rectangle Zone | POLYGON((0 0, 0 3, 6 3, 6 0, 0 0)) | POINT(3.0 1.5) | 18.00 | 18.00 |
Configuration
Key fields to configure in the Infoveave workflow builder. Full reference available in the documentation.
Geometry Column
Select the column containing WKT geometry strings. The transformation determines the geometry type (POLYGON, LINESTRING, or POINT) for each row and extracts the applicable spatial properties. Mixed geometry types in the same column are handled correctly — POLYGON rows get centroid, length, and area; LINESTRING rows get centroid and length; POINT rows get centroid only.
Centroid Point Column
Enter the name for the column that will store the centroid POINT in WKT format. For POLYGONs, this is the geometric centroid (center of mass). For LINESTRINGs, this is the midpoint of the path. For POINTs, the centroid is the point itself.
Length Column
Enter the name for the column that will store the perimeter length of polygons or the segment length of linestrings as a numeric value. For POINT geometries, this column will be empty.
Area Column
Enter the name for the column that will store the area of polygon geometries as a numeric value. For LINESTRING and POINT geometries, this column will be empty because lines and points have no area dimension.
Frequently asked questions
Everything you need to know about Extract from Geocolumn in Infoveave.
Also in Geospatial — and what runs before & after
Transformations in the same family as Extract from Geocolumn, often chained together in the same Infoveave workflow.
Part of Infoveave Data Automation
80+ transformations. Zero manual steps.
Extract from Geocolumn is one of over 80 transformation activities available inside Infoveave workflows. Chain transformations together — no code, no exports, no waiting for IT.
Ready to see Infoveave in action?
