GeoJSON Sample
A GeoJSON FeatureCollection with a point, a line, and a polygon — for testing map tools and geo importers.
{
"type": "FeatureCollection",
"features": [
{ "type": "Feature", "properties": { "name": "City Hall" }, "geometry": { "type": "Point", "coordinates": [-0.1276, 51.5074] } },
{ "type": "Feature", "properties": { "name": "Route" }, "geometry": { "type": "LineString", "coordinates": [[-0.13, 51.50], [-0.12, 51.51], [-0.11, 51.52]] } },
{ "type": "Feature", "properties": { "name": "Zone" }, "geometry": { "type": "Polygon", "coordinates": [[[-0.14, 51.50], [-0.10, 51.50], [-0.10, 51.53], [-0.14, 51.53], [-0.14, 51.50]]] } }
]
}
Specifications
- Format
- GeoJSON
- Features
- 3
- Geometry Types
- Point, LineString, Polygon
- Crs
- WGS84 (EPSG:4326)
- Encoding
- UTF-8
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 Sample” is a deterministic Novus Examples fixture for Geospatial, JSON parsing. 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 · GeoJSON. 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.
Data fixtures document their exact quirks — delimiters, encodings, null handling, schema, and row counts — in the spec table. Point your parser or importer at the file and assert it handles the documented edge cases; clean and deliberately-messy siblings make before/after diffs straightforward.
Code examples
import geopandas as gpd
gdf = gpd.read_file("sample.geojson")
print(gdf.head())
print(gdf.crs)Related files
- 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.
- geojsonCoordinate Precision — 1 Decimal PlaceThe 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.
- geojsonCoordinate Precision — 15 Decimal PlacesThe same harbour light written to 15 decimal places — enough to identify beyond what a float64 can hold for a coordinate at all. 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.
- geojsonCoordinate Precision — 2 Decimal PlacesThe same harbour light written to 2 decimal places — enough to identify which town 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.
- geojsonCoordinate Precision — 4 Decimal PlacesThe same harbour light written to 4 decimal places — enough to identify which building 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.
- geojsonCoordinate Precision — 6 Decimal PlacesThe same harbour light written to 6 decimal places — enough to identify which doorway you are standing 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.
Generated by generation/data_formats.py. Free for any use, no attribution required — license.