GeoJSON — Intentionally Invalid: Coordinates as JSON Strings
Intentionally invalid: the file is perfectly good JSON but the coordinates are quoted strings, which RFC 7946 does not allow. It is exactly what a CSV-to-GeoJSON script produces when it forgets to cast, and a permissive reader will coerce it and hide the bug.
{
"type": "FeatureCollection",
"features": [
{
"type": "Feature",
"id": "bad-type",
"properties": {
"name": "Kestrel Bay",
"defect": "coordinates are strings, not numbers"
},
"geometry": {
"type": "Point",
"coordinates": [
"-12.482",
"47.064"
]
}
}
]
}
Specifications
- Format
- GeoJSON (RFC 7946)
- Crs
- WGS 84 (EPSG:4326)
- Coordinate Order
- longitude, latitude
- Encoding
- UTF-8
- Line Endings
- LF
- Features
- 1
- Coordinate Json Type
- string
- Required Json Type
- number
- Parses As Json
- true
- Valid
- false
- Defect
- intentionally invalid — coordinates must be JSON numbers
Testing contract
Expected to fail- Scenario
- Validate the document against the GeoJSON schema rather than merely parsing it as JSON.
- Expected result
- JSON parsing succeeds but GeoJSON validation fails on the coordinate types; nothing coerces the quoted numbers without reporting it.
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: Coordinates as JSON Strings” is a deterministic Novus Examples 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("coordinates-as-strings.geojson")
print(gdf.head())
print(gdf.crs)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 — 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 — Clockwise Exterior Ring (right-hand rule violated)Both rings of the Mill Court parcel are wound the wrong way round: the exterior clockwise, the interior counter-clockwise. RFC 7946 mandates the right-hand rule, and consumers that rely on winding to tell holes from shells will read this polygon inside out.
- geojsonGeoJSON — Empty GeometryCollectionA GeometryCollection with an empty `geometries` array — structurally valid, semantically the empty geometry. Converters that map a collection onto a multi-geometry type usually emit null here, quietly changing the record's meaning.
Generated by generation/geospatial.py. Free for any use, no attribution required — license.