Spatial Match (Intersect / Unmatched)
Description
Section titled “Description”The Spatial Match (Intersect / Unmatched) step pairs each target geometry with the universe geometries it relates to and can emit either the intersection geometry of each matched pair (IntersectPoly) or the Unmatched target rows. It complements the SQL Spatial Match step, which covers the plain matched-pairs case; this executor-backed step covers the two outputs that cannot be expressed in database SQL.
Sources & Options
Section titled “Sources & Options”- Target Table / Universe Table — the geometries to match and the candidates to match against.
- Output Table — where the result is written.
- Target geometry / Universe geometry — the WKT geometry column on each side.
- Relationship — intersects, within, contains, touches, crosses, overlaps, equals, or disjoint. Equals matches only topologically equal geometries, and disjoint matches pairs that share no point; a null geometry never matches disjoint.
- Multiple Rules — a match can relate several target and universe geometry columns at once, each rule with its own relationship. The
joinersetting is whether a pair must satisfy every rule (and, the default) or any rule (or). Savant conversion produces multi-rule matches. An unknown relationship or joiner fails the step by name instead of running as intersects. - Also emit the intersection geometry (IntersectPoly) — add the overlap geometry of each matched pair as a column.
- Output — Matched pairs or Unmatched target rows.
Target & Universe Mapping
Section titled “Target & Universe Mapping”Each input has a mapping tab listing its columns, used to drive the geometry pickers and to pass columns through to the output.