Coordinate Precision — 1 Decimal Place
The same harbour light written to 1 decimal place — enough to identify which country you are in. The ladder exists because coordinate precision is almost always chosen by accident, and shipping six unnecessary digits multiplies the size of every geometry in a tileset.
{
"type": "FeatureCollection",
"features": [
{
"type": "Feature",
"id": "harbour-light-1dp",
"properties": {
"name": "Kestrel Bay harbour light",
"decimalPlaces": 1,
"maxGroundErrorMetres": 5559.75
},
"geometry": { "type": "Point", "coordinates": [-12.5, 47.1] }
}
]
}
Specifications
- Format
- GeoJSON (RFC 7946)
- Features
- 1
- Decimal Places
- 1
- Longitude
- -12.5
- Latitude
- 47.1
- Max Ground Error Metres Latitude
- 5559.754012
- Max Ground Error Metres Longitude
- 3787.190054
- Meaning
- which country you are in
- Encoding
- UTF-8
- Line Endings
- LF
- Note
- coordinates written literally, not reformatted by a JSON encoder
Testing contract
Reference control- Scenario
- Parse the file and compute the worst-case ground error implied by 1 decimal places.
- Expected result
- Latitude resolves to within 5559.75 m and longitude to within 3787.19 m at this latitude; the digits in the file are exactly as written, not re-rounded by the parser.
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
“Coordinate Precision — 1 Decimal Place” is a deterministic Novus Examples fixture for Geospatial, JSON parsing, Serialization 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 · GeoJSON (RFC 7946). 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("coordinate-precision-01dp.geojson")
print(gdf.head())
print(gdf.crs)Related files
- geojsonCoordinate Precision — Float64 Round-Trip HazardsFive features whose coordinates are the values that break naive JSON number handling: 17-significant-digit doubles, the classic 0.1 + 0.2 artefact, the largest float64 below 180, a 1e-7 offset, and coordinates written in exponent form. Re-serialising this file is where a parser quietly loses or gains a digit.
- geojsonConvert v2 Shapefile Expected GeoJSONGeoJSON semantic target for the five-town shapefile set, preserving point order, CODE/NAME/POP/FOUNDED attributes, and longitude/latitude coordinates; the omitted .cpg is safe because every copied DBF value is ASCII. Stable P8 artifact p8-convert-shapefile-geojson.
- txtEWKB — PostGIS Hex With an Embedded SRIDPostGIS EWKB, where the SRID is carried by OR-ing 0x20000000 into the geometry-type word and appending the code. A strict OGC WKB reader sees type 0x20000001 instead of 1 and either fails or, worse, reports an unknown geometry type.
- wktEWKT — PostGIS Extended WKT With an SRID PrefixPostGIS's extended WKT, which prefixes the geometry with `SRID=4326;`. It is not part of the OGC standard, so a strict WKT parser rejects the whole string — while a PostGIS-aware one gets the coordinate system for free.
- geojsonGeoJSON — Bare Geometry Object (no Feature)A top-level Geometry object with no Feature or FeatureCollection around it. This is legal GeoJSON and is what PostGIS `ST_AsGeoJSON` returns, but a surprising number of importers only accept a FeatureCollection.
- geojsonGeoJSON — bbox on Every FeatureThree features that each carry their own bbox. Spatial indexes are often built from these declared boxes instead of the geometry, so a wrong or stale one produces a query that silently misses features.
Generated by generation/geospatial.py. Free for any use, no attribution required — license.