GeoJSON, Intentionally Invalid: Latitude Outside -90 to 90
Intentionally invalid: latitude 95, five degrees past the north pole. This is the value that appears when longitude and latitude have been swapped somewhere upstream, so catching it early usually finds an axis-order bug rather than a data-entry one.
{
"type": "FeatureCollection",
"features": [
{
"type": "Feature",
"id": "bad-lat",
"properties": {
"name": "Impossible position",
"defect": "latitude 95 is outside the valid range"
},
"geometry": {
"type": "Point",
"coordinates": [
-12.482,
95.0
]
}
}
]
}
Specifications
- Format
- GeoJSON (RFC 7946)
- Crs
- WGS 84 (EPSG:4326)
- Coordinate Order
- longitude, latitude
- Encoding
- UTF-8
- Line Endings
- LF
- Features
- 1
- Latitude
- 95
- Valid Range
- -90 to 90
- Valid
- false
- Defect
- intentionally invalid: latitude out of range
Testing contract
Expected to fail- Scenario
- Run coordinate-range validation, then check whether the pair is a swapped longitude/latitude.
- Expected result
- Latitude 95 is rejected; the pair is recognisable as an axis-order mistake because 95 is a legal longitude but never a legal latitude.
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: Latitude Outside -90 to 90” is a deterministic Testaroo fixture for Geospatial, Error handling, Schema validation. 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("latitude-out-of-range.geojson")
print(gdf.head())
print(gdf.crs)Generated by generation/geospatial.py. Free for any use, no attribution required, license.
Related files
- geojsonGeoJSON, Intentionally Invalid: Ring With Only Three PositionsIntentionally invalid: a ring of three positions that closes back on itself and therefore encloses nothing. RFC 7946 requires at least four positions for a linear ring, and this is the shape a simplification pass produces when it over-thins a small polygon.

- wktWKT, Intentionally Invalid: Four Malformed ValuesIntentionally invalid: four WKT strings that each break in a different way, a point with one ordinate, a line whose last vertex is ragged, a polygon missing a closing bracket, and a misspelled keyword. Good parsers report which line and which character failed.

- geojsonGeoJSON, Intentionally Invalid: Hole Outside Its ShellIntentionally invalid: the second ring is a whole separate parcel filed as an interior ring of the first, which OGC Simple Features forbids. It is what happens when a MultiPolygon is flattened into a Polygon by concatenating rings.

- geojsonGeoJSON, Intentionally Invalid: Self-Intersecting RingIntentionally invalid: a bowtie ring whose two lobes wind in opposite directions, so the shoelace areas nearly cancel. Buffer, intersection and area operations on this geometry return nonsense rather than failing, which is why it belongs in a validation suite.

- geojsonGeoJSON, Intentionally Invalid: Unclosed Polygon RingIntentionally 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.

- 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.
