Processor Guide

Use this guide to choose the right processor for your use case.

Summary table

Processor Best for Speed Geometry scope Notes
AlignerGeometryProcessor (default) General use Medium Auto-selects by context Recommended default entrypoint
DieussaertGeometryProcessor Polygon-to-polygon alignment Fast Polygon/MultiPolygon focused Usually best first choice for parcel-like workflows
NetworkGeometryProcessor Generic point/line/polygon network behavior Slower Broadest support Use when network-like behavior is required
TopologyProcessor Shared-boundary consistency between neighboring features Slower Topology-aware arc workflow Experimental and specialized
SnapGeometryProcessor Direct vertex/edge snapping behavior Case-dependent Depends on snap strategy Good for explicit snap-driven workflows

Practical recommendation

  1. Start with AlignerGeometryProcessor (default).
  2. If your scenario is polygon-to-polygon and speed matters, prefer DieussaertGeometryProcessor.
  3. Switch to NetworkGeometryProcessor when mixed geometry types or network behavior are required.
  4. Use TopologyProcessor only when preserving shared topology across thematic features is a strict requirement.