topo-tools
topo-tools is a collection of DuckDB-powered geospatial topology utilities
for cleaning and reconciling administrative boundary polygons, usable from
the CLI or as a Python package.
Full documentation: https://ocha-dap.github.io/topo-tools-py/
| Tool | Description |
|---|---|
| schema-map | map and apply a source to target schema crosswalk |
| schema-fill | fill down admin-hierarchy columns |
| schema-join | copy a join layer's admin-hierarchy columns onto each input feature |
| topo-clean | detect and fix gap/overlap defects |
| topo-detect | detect gap/overlap defects |
| edge-match | fit an input layer into an overlay layer |
| edge-extend | fill gaps with a Voronoi extension |
| edge-mosaic | re-clip an extended input layer into a new overlay layer |
| edge-clip | clip an input layer to an overlay layer |
| edge-stitch | close seams in a tiled layer |
| change | classify changes between two polygon layer versions |
| package | dissolve, label, and line-ify a layer in one call |
| package-polygons | dissolve a layer into coarser admin levels |
| package-points | one label point per admin unit |
| package-lines | deduplicated admin boundary lines |
Installation
Install with uv (recommended):
uv tool install topo-tools # CLI
uv add topo-tools # Python library
Or with pip/pipx:
pip install topo-tools # CLI or library
pipx install topo-tools # CLI
On macOS/Linux, topo-tools is also available via Homebrew, no Python
tooling required:
brew install OCHA-DAP/topo-tools/topo-tools
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
Metadata
1 maintainer
Release files for topo-tools 0.10.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| topo_tools-0.10.1.tar.gz | 8.4 MB | With provenance | Details for topo_tools-0.10.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| topo_tools-0.10.1-py3-none-any.whl | Python 3 | none | any | Details for topo_tools-0.10.1-py3-none-any.whl |
Total release size: 8.6 MB
Release files / topo_tools-0.10.1.tar.gz
| Download URL | topo_tools-0.10.1.tar.gz |
|---|---|
| Size | 8.4 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d9e3a2ef2889226dfe5c9a1215f16a4d42670e4a87be0a039da0692dbafacf4c
|
|
BLAKE2b-256 checksum How to use checksums |
d5bd1a4619b30adb4e275daae0983e22a200cc96827f902db16d1259f05b17b3
|
| 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 Sep 29, 2026.
Transparency logRelease files / topo_tools-0.10.1-py3-none-any.whl
| Download URL | topo_tools-0.10.1-py3-none-any.whl |
|---|---|
| Size | 182.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b0eb9c2a2dc50fe2861211dc1770104c3d03a02dcefd3302d37a6108a72ab80f
|
|
BLAKE2b-256 checksum How to use checksums |
b662b4664fa78e3550ce8ff2301ca7ab3e23a36e8411dd279baa4daa2c6911a7
|
| 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 Sep 29, 2026.
Transparency logSecurity for topo-tools 0.10.1
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for topo_tools-0.10.1.tar.gz
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 Sep 29, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
