Skip to content

Ambiguous Engine-dependent Polygon

vectorGeoJSONPolygonEPSG:4326tinybundled

A polygon with a shell and interior ring touching at a single point. This is parseable, but validity interpretation and repair behavior can be engine-dependent across geometry libraries.

Polygon geometry of ambiguous_engine_dependent_polygon, rendered from the case's data
Polygon geometry, rendered from the case's actual geometry. Scale is normalized to the viewport and is not comparable between cases.
Property Value
Case ID ambiguous_engine_dependent_polygon
Category vector
Format GeoJSON
Geometry type Polygon
CRS EPSG:4326
Location Near the origin (synthetic, no real-world location) — 0.00°E, 0.00°N → 6.00°E, 6.00°N
Test tier unit
Size class tiny
Storage class bundled
Redistributable yes
Loader geopandas
Status validated

Use this case

import pytest


@pytest.mark.geocase_case("ambiguous_engine_dependent_polygon")
def test_ambiguous_engine_dependent_polygon(geocase_case) -> None:
    data = geocase_case.load()
    assert data is not None

Use GeoCase in your tests

Install the complete set of vector, raster, and NetCDF dependencies:

pip install "geocase[all]"

View GeoCase on PyPI.

What this case checks

Expose workflows that assume all geometry engines agree on polygon validity and repair output for touching-ring topologies.

Risk types covered

Expected behavior

Assertion Expected
expect_loadable yes
expect_valid_geometry no
expect_crs yes
expected_epsg 4326
expected_geometry_types Polygon

Notes

Polygon with touching shell/interior ring to capture engine-dependent validity behavior.

Required capabilities

  • load
  • geometry-validation
  • repair

Files

Browse this case on GitHub

Source and license

  • Source: geocase-curated
  • License: MIT

Tags

ambiguous engine_dependent invalid polygon topology vector