Русская версия · English
A QGIS plugin for bringing polygon coverages into order - topology check, automatic cleanup, border snapping, insertion of missing nodes, assembly check by attribute and simplification that keeps shared borders shared.
All tools live in the Processing panel and work in models and in batch mode. The input layer is never modified. Every result goes to a new layer.
Interface in English and Russian, chosen by the QGIS locale.
The plugin is free and open source. Support development (Russian bank cards via SBP)
The usual manual routine is to snap a layer to itself with some tolerance, then dissolve without attributes, then inspect the result for discrepancies. It is well known, repeatable and done by hand every time. The plugin does the same thing reproducibly, with a numeric report and with guarantees.
| Tool | What it does | Modifies the layer |
|---|---|---|
| 1.01 Polygon topology check | Finds violations, produces a point layer and a summary | No |
| 1.02 Line topology check | Undershoots, overshoots, dangles | No |
| 1.03 Polygon topology cleanup | Fixes what is technical debris | Yes, into a new layer |
| 1.04 Line topology cleanup | Fixes what is a digitising trace | Yes, into a new layer |
| 1.05 Node and vertex snapping | Brings borders to an exact match | Yes, into a new layer |
| 1.06 Insertion of missing nodes | Adds nodes without changing shape or area | Yes, into a new layer |
| 1.07 Assembly check by attribute | Checks whether groups assemble into one body | No |
| 1.08 Contours into a coverage | Three overlay modes, the cut edge reaches both sides the same | Yes, into a new layer |
| 2.01 Topology-preserving simplify | Thins vertices without tearing shared borders | Yes, into a new layer |
| 2.02 Polygon borders as lines | Outputs borders as separate lines, each one once | No |
| 2.03 Coverage topology model | Breaks a coverage into nodes and arcs | No |
Tool 1.08 puts drawn contours into a coverage. Three overlay modes answer one question, who gets the area under the contour.
| Mode | The new feature | The neighbours | The area of the coverage |
|---|---|---|---|
| Overlay | the whole contour | trimmed | grows by the part beyond the edge |
| Clipping | free space only | lose no area | grows by the same part |
| Cutting in | only what lies inside | trimmed | does not change |
Automation cannot know which of two disputed borders is correct. What it can tell is scale. A centimetre overlap is a digitising error, a hectare one is a disagreement between sources. Behaviour is therefore set by two thresholds, a tolerance in length units and an area threshold. Anything above them is left to the operator and is never fixed automatically under any settings.
- No vertex moves further than the tolerance.
- An edit that takes more than a quarter of an object's area is cancelled.
- Objects narrower than the tolerance are left untouched and serve as anchors.
- A repeat run over the result changes nothing. There is one exception: simplification with smoothing, where every pass cuts the corners again.
- Attributes are preserved. Objects are never deleted without explicit permission.
- Insertion of missing nodes does not change the area at all.
Three plugins solve neighbouring tasks and work together.
- Isoliner - kriging, contour lines and polygons, terrain hydrology, borehole sections. Source
- Isoliner3D - a standalone 3D viewer for surfaces, bed bodies, boreholes and polyhedra, with reserve calculation from a block model. Source
Contours and borders built in Isoliner are put in order by Topoliner, and the result is viewed in Isoliner3D.
From the QGIS plugin repository, or from a ZIP file: Plugins - Manage and Install Plugins - Install from ZIP. Restarting QGIS is not required.
The manual in PDF, topoliner/doc/Topoliner_en.pdf, ships with the plugin.
The Help button in a tool dialog opens it in the interface language.
Sources - doc/MANUAL.en.md, design notes and the classification of violations - doc/DETAILS.en.md.
cd topoliner
python -m unittest discover -s tests -v
QGIS is not needed for the tests. The geometric logic is kept out of QGIS: the core works with plain coordinate lists, and intersection operations go through an adapter that has a Shapely implementation. Shapely uses the same GEOS as QGIS, so the behaviour matches production.
Building the archives:
python tools/build_zip.py
GNU GPL version 3 or later, see LICENSE.