GIS Tools - Polygon Overlap Checker

What Is Polygon Overlap Detection?

Polygon overlap detection identifies places where polygon features in a layer (or between two layers) overlap each other. In a topologically clean polygon layer, features should tile without gaps or overlaps: no two polygons should share interior area. Real-world data rarely meets this ideal. Digitizing errors, data migration artifacts, and imperfect joins all produce unwanted overlaps — sometimes large, often tiny "sliver polygons" a few centimeters wide where two boundaries should have matched exactly.

The Polygon Overlap Checker on gis.tools detects and reports overlap areas between polygons. Drop in a single polygon layer to find internal overlaps (pairs of features that shouldn't share area), or drop in two layers to find overlaps between them. The output is a polygon layer of overlap areas, each tagged with the IDs of the overlapping parent features. Everything runs in your browser.

Overlap detection is essential for cadastral data validation, land use inventory cleanup, administrative boundary harmonization, and any situation where polygon coverage is expected to be non-overlapping. It's the companion tool to sliver polygon detection in data QA workflows.

How Polygon Overlap Detection Works

The algorithm:

Build a spatial index on the polygon layer (R-tree or STR-tree)
For each polygon, use the index to find candidate neighbors with overlapping bounding boxes
For each candidate pair, compute ST_Intersection of the two polygons
If the intersection has non-zero area, report it as an overlap

The intersection area is the geometric basis for both detection and reporting. The output polygon represents the shared area, not the parent features.

Sliver Detection

Slivers are tiny overlap polygons (often under 1 m²) that result from floating-point precision or near-miss digitizing. The tool optionally filters overlaps by minimum area to focus on meaningful overlaps while hiding precision noise, or does the opposite — filters to tiny slivers to highlight cleanup targets.

Containment vs Overlap

Containment (one polygon entirely inside another) is a special case of overlap. Most detection tools report both, but the distinction matters for data interpretation: a contained polygon is a hole or nested feature, while a partial overlap is usually a digitizing error.

Key Parameters and Options

Single Layer or Two Layer Mode

Single-layer mode compares each feature against every other feature in the same layer. Two-layer mode compares features across two different layers.

Minimum Area Filter

Ignore overlaps smaller than a threshold (e.g., 0.1 m²) to hide precision noise.

Maximum Area Filter

Ignore overlaps larger than a threshold to find only slivers.

Include Attribute Join

Each overlap output feature can carry the IDs and attributes of both parents.

Practical Applications

Cadastral Data Validation

Parcel boundaries in cadastral datasets must not overlap. Detection identifies pairs of parcels that share area, flagging data entry errors or conflicting surveys that need resolution.

Land Use Inventory

Land use and zoning layers are supposed to tile. Overlap detection finds places where two zones claim the same ground — an error to be resolved by municipal staff.

Sliver Cleanup After Overlay

After a union or intersect operation, small sliver polygons inevitably appear along near-parallel boundaries. Overlap detection identifies them so they can be merged into their largest neighbor.

Conservation Easement Management

Conservation easements should not overlap other protection designations without explicit coordination. Overlap detection flags cases needing legal review.

Building Footprint Quality Control

Building footprint layers sometimes contain duplicate or near-duplicate features. Overlap detection helps dedupe.

Utility Service Territory Conflicts

Electric, gas, and water service territories should not overlap. When they do, it's a contractual or regulatory issue.

Historical Boundary Reconciliation

Digitized historical boundaries from multiple sources often disagree in subtle ways. Overlap detection quantifies and locates the discrepancies.

Step-by-Step Workflow in gis.tools

Open the Polygon Overlap Checker
Drop in one or two polygon layers
Choose the mode
Set minimum and maximum area filters as needed
Click "Check Overlaps"
Inspect the resulting overlap polygons on the map
Each output polygon carries parent feature IDs
Export as GeoJSON for follow-up cleanup

Worked Example

A county GIS team recently migrated its parcel layer from an old system and wants to verify that no parcels overlap. They drop the parcel shapefile (62,000 features) into the Polygon Overlap Checker in single-layer mode with a minimum area filter of 0.5 m² to ignore noise. The tool reports 147 overlaps, of which 112 are between adjacent parcels with 1-5 m² overlaps (likely digitizing errors) and 35 are larger overlaps (up to 300 m²) that represent genuine boundary disputes or encroachments. The team exports the output and sends it to the cadastral unit for field verification.

Common Pitfalls and Gotchas

Expected vs unexpected overlaps: nested polygons, parking lots inside parcels, and buildings inside lots are all legal overlaps in some layers. Filter by semantic expectation.
Coordinate precision: features stored with different decimal precision can produce phantom slivers. Normalize precision first with Coordinate Precision Reducer.
CRS mismatch between two layers produces wrong overlap geometries.
Topology errors in the input can produce exceptions; fix with Geometry Repair first.
Self-overlapping polygons (self-intersections) can produce unexpected results. Check validity first.
Performance: single-layer checking of 100,000 polygons can be slow even with spatial indexes.
Overlap vs containment: decide whether nested polygons should be reported. Some tools treat containment as a special overlap case.
Duplicate reporting: A overlaps B is the same as B overlaps A. Dedupe the output pairs.

Tips for Best Results

Reproject to an equal-area CRS first for meaningful area calculations
Use Geometry Repair to fix invalid geometries before checking
Set a minimum area filter to ignore precision noise
Pair with the GIS Dissolve Tool (Merge by Field) to merge slivers into their largest neighbor
Export overlap points (use Centroid / Point-on-Surface on the overlap output) for efficient navigation in desktop GIS

Comparison with Other GIS Approaches

PostGIS uses ST_Overlaps and ST_Intersects with self-joins. QGIS offers Polygon Overlap under the Topology Checker plugin. ArcGIS has the Topology tools that detect overlap as a topology rule violation. The browser-based gis.tools tool is the fastest way to get an overlap report on moderate-sized layers without setup.

Performance Considerations

Single-layer overlap checking is O(n log n) with a spatial index in typical cases. Very dense layers (thousands of overlaps per feature) can slow things down.

Data Privacy and Browser-Based Processing

Cadastral data, parcel ownership, and contested boundary information can be confidential. Processing runs entirely in your browser.

Related GIS Concepts

Sliver polygon is a thin overlap polygon from precision errors, typically under 1 m². Topology rules in ArcGIS and QGIS formalize constraints like "must not overlap" and report violations. MAUP (Modifiable Areal Unit Problem) is indirectly related because overlapping polygons produce ambiguous attribute values. Coverage is the data model where polygons tile the plane without gaps or overlaps.

Frequently Asked Questions

How do I find overlapping polygons in a single layer?

Drop the layer into the tool in single-layer mode and click Check Overlaps.

How do I filter out tiny slivers?

Set a minimum area filter (e.g., 0.5 m² or larger).

How do I find only slivers (the opposite)?

Set a maximum area filter at the sliver threshold.

Does containment count as overlap?

Yes — a contained polygon fully overlaps the containing one, and the tool reports it.

Can I detect overlaps between two different layers?

Yes — switch to two-layer mode.

Use Cases