topo-tools
topo-tools is a collection of DuckDB-powered geospatial topology utilities
for cleaning and reconciling administrative boundary polygons. It ships eight
tools, usable from the CLI or as a Python package:
| Tool | What it does | Usage |
|---|---|---|
| edge-extend | Fills gaps around a polygon layer (missing coastline, disputed areas, water bodies) with a Voronoi extension, producing full coverage. | docs/explanation/edge_extend.md |
| edge-clip | Assigns each child to its parent, then clips it to that parent's geometry. | docs/explanation/edge_clip.md |
| edge-stitch | Closes seams in an already-tiled polygon layer with one whole-table coverage-clean pass. | docs/explanation/edge_stitch.md |
| topo-detect | Scans a single polygon layer for gap/overlap coverage defects and reports them, without fixing anything. | docs/explanation/topo_detect.md |
| edge-match | Fits a finer child polygon layer into a coarser parent layer, grouping and extending each child to fill gaps within its own parent. | docs/explanation/edge_match.md |
| edge-mosaic | Re-clips an already-extended child layer into a new/different parent layer, skipping Voronoi extension entirely. | docs/explanation/edge_mosaic.md |
| topo-clean | Detects and fixes gap/overlap defects in a single polygon layer, reporting issues for manual review. | docs/explanation/topo_clean.md |
| change | Compares two versions of a polygon layer and classifies every unit as unchanged, renamed, modified, split, merged, created, or removed. | docs/explanation/change.md |
Installation
uv tool install topo-tools # CLI (recommended)
uv add topo-tools # Python library
Or with pipx:
pipx install topo-tools
Or with pip:
pip install topo-tools
Each linked doc above covers that tool's CLI/Python usage, options, and examples.
Supported Formats
Polygon inputs/outputs: GeoParquet (.parquet), GeoPackage (.gpkg),
Shapefile (.shp), GeoJSON (.geojson). Output format matches input format.
change's tabular changelog is CSV or GeoParquet only; its spatial overlay
layer supports the same four formats as the other tools.
See CONTRIBUTING.md for development setup.
1 maintainer
Release files for topo-tools 0.5.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| topo_tools-0.5.3.tar.gz | 8.2 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| topo_tools-0.5.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.3 MB
Release files / topo_tools-0.5.3.tar.gz
| Download URL | topo_tools-0.5.3.tar.gz |
|---|---|
| Size | 8.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
989f95a7fc276d725085f58fe91f9dc5912b368511066744c3c090aed18a9d7a
|
|
BLAKE2b-256 checksum How to use checksums |
ebcc53739d47cddcffe6abaa12040b1930eadd9cee47850297c1d2e875966b29
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 27, 2026.
Transparency logRelease files / topo_tools-0.5.3-py3-none-any.whl
| Download URL | topo_tools-0.5.3-py3-none-any.whl |
|---|---|
| Size | 118.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5fff7e0d9f6f431cf9cd89596e81f259ca6adae9f2d7d3e2caace5d18407f822
|
|
BLAKE2b-256 checksum How to use checksums |
d7e164754823fceb2f46d6f65d71185d7efa8df2cd13e07293aeb651456aefc3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 27, 2026.
Transparency log
