The Spatial Summarize agent allows you to group geospatial records into partitions and apply spatial aggregation operations to each group. It is useful when you want to generate summarized spatial outputs such as merged territories, shared overlap zones, bounding extents, center points, polygons, or polylines.
Each aggregation writes its result to a new field, allowing the summarized geometry to be stored alongside or in place of existing analytical outputs.
Configuration Options
Group By
Use Group by to define how records are partitioned before the spatial aggregation is applied. Each unique value, or unique combination of values if multiple fields are added, forms a separate partition. The aggregation operation is then calculated independently within each partition.
Aggregations
Use the Aggregations section to define the spatial summary operation that should be applied to each partition.
Each aggregation includes:
Argument: The geometry-bearing field used in the calculation
Calculation: The spatial aggregation operation to apply
New field: The name of the output field that stores the result
Calculation options include:
Operation | Description | Builder Configuration | Use Cases |
Union Geometries | Combines all geometries in a partition into a single unified geometry, merging overlaps. | Group records by a field such as Region ID, select the geometry field, choose Union Geometries, and save the result to a new output field. | Consolidate territories by region, merge service areas, create one summarized shape per group |
Intersect Geometries | Returns the common overlapping area shared by all geometries in a partition. | Group records by a field such as Market ID, select the geometry field, choose Intersect Geometries, and write the shared overlap geometry to a new field. | Find shared coverage zones, identify common overlap areas, analyze mutually covered regions |
Bounding Box | Returns the rectangular extent that contains all geometries in a partition. | Group records by a business or spatial field, select the geometry field, choose Bounding Box, and create a new field for the extent result. | Generate quick map extents, summarize grouped spatial spread, create lightweight geographic bounds |
Geometric Center | Calculates a center point that represents the grouped geometries in a partition. | Group records by a field such as Region ID, select the geometry field, choose Geometric Center, and store the center point in a new field. | Find regional centers, create representative label points, support downstream distance analysis |
Build Polygon | Connects points in sort order to create a closed polygon. | Group related point records, define a sort field to control point order, choose the point geometry field, select Build Polygon, and save the resulting polygon to a new field. | Trace boundaries from ordered waypoints, build custom territories, create polygons from sequenced point data |
Build Polyline | Connects points in sort order to create an open path or line. | Group related point records, define a sort field such as timestamp or sequence, choose the point geometry field, select Build Polyline, and save the resulting path to a new field. | Build GPS routes, represent delivery tracks, create ordered path-based line outputs |
You can configure multiple summarize calculations in the same agent to generate more than one derived output from the same partitioned data.
Window Sort
Some spatial summarize operations do not depend on row order, while others require a defined sort sequence.
Operations such as Union Geometries, Intersect Geometries, Bounding Box, and Geometric Center do not require ordered input.
Operations such as Build Polygon and Build Polyline require records to be sorted so that points are connected in the intended sequence.
Use Window Sort when an aggregation depends on the order of records within a partition. This is especially important for shape-building operations such as Build Polygon and Build Polyline, where points must be connected in a meaningful sequence.
The current UI includes a Window Sort section with an add control, indicating support for one or more sort fields.
Best Practices
Use Group by fields that reflect the level at which you want the final spatial summary, such as region, market, route, or boundary.
Use a geometry-bearing field in Argument. In the current configuration, geometry is referenced through the Metadata field.
Use Window Sort for sequence-based operations such as Build Polygon and Build Polyline so points are connected in the correct order. The current UI includes a dedicated Window Sort section for this purpose.
Give each output a clear new field name so the summarized geometry is easy to identify in downstream steps. The configuration panel explicitly includes a New field entry for each aggregation.
Use Union Geometries when you want one merged geometry for each partition, such as a single territory or region shape. The current example shows
Union Geometriesapplied toMetadata.Use Intersect Geometries when you want to identify only the shared area common to all geometries in the partition.
Use Bounding Box or Geometric Center when a simplified spatial summary is more useful than a full merged shape.
Validate that grouped records belong together logically before running summarize operations, especially when combining large or overlapping geometries.
For point-based geometry construction, make sure the sort field represents the intended sequence, such as timestamp or waypoint order.
Use descriptive partition fields and output names to make the summarize logic easier to read and maintain.