Explanation
Understanding-oriented design rationale for each tool: why it works the way it does, stage by stage, including tradeoffs and rejected alternatives.
docs/explanation/ states why each tool is built the way it is.
docs/reference/ states what it currently does; docs/adr/ records the
one-off decisions behind both.
-
assign
Assign each child to a parent, majority vote or per-child plurality.
-
change
Compare an old/new polygon layer pair and classify every unit.
-
Code
code, code-refactor, code-update: the shared code leaf and its two tools.
-
Edge
edge-clip, edge-extend, edge-match, edge-mosaic, edge-stitch: fit and stitch boundary layers together.
-
Package
package, package-lines, package-points, package-polygons: cartographic outputs for a web map.
-
performance
Thread-scaling benchmarks and the RTREE experiment.
-
Schema
schema-crosswalk, schema-fill, schema-map, schema-refactor: crosswalk and fill a column schema.
-
Topo
topo-clean, topo-detect: detect and fix single-layer coverage defects.
-
topology
The SPATIAL_JOIN memory bug and other topology-cleaning notes.
-
voronoi-memory
Per-file resampling distance and memory ceilings for large countries.