GeoJSON — Intentionally Invalid: Unclosed Polygon Ring
Intentionally invalid: the parcel's exterior ring omits the repeated closing position that RFC 7946 requires. Many readers close it silently, which hides the producer's bug until a stricter consumer downstream rejects the data.
{
"type": "FeatureCollection",
"features": [
{
"type": "Feature",
"id": "bad-open",
"properties": {
"name": "Harbour Yard",
"defect": "first position != last"
},
"geometry": {
"type": "Polygon",
"coordinates": [
[
[
-12.49,
47.06
],
[
-12.474,
47.06
],
[
-12.474,
47.069
],
[
-12.49,
47.069
]
]
]
}
}
]
}
Specifications
- Format
- GeoJSON (RFC 7946)
- Crs
- WGS 84 (EPSG:4326)
- Coordinate Order
- longitude, latitude
- Encoding
- UTF-8
- Line Endings
- LF
- Features
- 1
- Ring Positions
- 4
- Closed
- false
- Spec Section
- RFC 7946 section 3.1.6
- Valid
- false
- Defect
- intentionally invalid — ring is not closed
Testing contract
Expected to fail- Scenario
- Validate the polygon against RFC 7946.
- Expected result
- A strict validator reports an unclosed ring; a lenient reader closes it and must say so rather than staying quiet.
What is a .geojson file?
GeoJSON is a JSON-based format for encoding geographic data structures such as points, lines, and polygons, along with their properties. It uses WGS84 longitude-latitude coordinates and standard feature and feature-collection objects. It is a common interchange format for web mapping and GIS.
How to use this file
Use an example GeoJSON file to test geometry parsing, coordinate handling, and mapping libraries or GIS pipelines that render or analyze spatial features.
How to use this file for testing
“GeoJSON — Intentionally Invalid: Unclosed Polygon Ring” is a deterministic Novus Examples fixture for Geospatial, Error handling, Conversion testing. GeoJSON, GPX, and KML files with points, lines, polygons, and tracks — for testing map tools, route parsers, and geo importers.
Documented properties for this file: UTF-8 · LF · intentionally invalid. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.
Geospatial fixtures publish one invented territory across formats, with the coordinate reference system and feature counts documented in specs. Convert or reproject and diff against the twin in the same group; edge-case geometries state exactly which assumption they are built to break.
Code examples
import geopandas as gpd
gdf = gpd.read_file("ring-unclosed.geojson")
print(gdf.head())
print(gdf.crs)Related files
- geojsonGeoJSON — Antimeridian Line Split per RFC 7946The same transect cut at the 180th meridian into a two-part MultiLineString, which is what RFC 7946 section 3.1.9 recommends. The split latitude is the linear interpolation of the unsplit twin, so the two files describe the same ground path.
- geojsonGeoJSON — Antimeridian Polygon Split into a MultiPolygonThe straddling block cut at 180 into two polygons that share an edge on the meridian — the interoperable form. Use it as the expected output when testing an antimeridian-splitting routine against the unsplit twin.
- geojsonGeoJSON — LineString Crossing the Antimeridian (unsplit)A two-point line whose longitudes step from 179.6 to -179.7. Interpolating naively draws a 359.3-degree line all the way back around the world instead of the 0.7-degree hop across the 180th meridian — the classic antimeridian artefact.
- geojsonGeoJSON — LineString Passing Over the North PoleA flight path that goes up one meridian, touches the pole, and comes down the antipodal meridian — so longitude jumps by exactly 180 degrees at the middle vertex. Renderers that interpolate in longitude draw a horizontal streak across the whole map instead.
- geojsonGeoJSON — Longitude Written Beyond 180The same transect with its eastern end written as 180.3 rather than the normalised -179.7. Producers that accumulate longitudes across the antimeridian emit this constantly; RFC 7946 restricts longitude to -180..180, so a strict reader must reject or normalise it.
- geojsonGeoJSON — Points Exactly at the PolesThree points at exactly plus or minus 90 degrees latitude, two of which are the same physical place written with different longitudes. Web Mercator cannot represent either pole — latitude 90 projects to infinity — so this is the fixture that catches divide-by-zero and NaN in a reprojection path.
Generated by generation/geospatial.py. Free for any use, no attribution required — license.