Convert v2 Shapefile Expected GeoJSON
GeoJSON 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.
{
"features": [
{
"geometry": {
"coordinates": [
-12.482,
47.064
],
"type": "Point"
},
"properties": {
"CODE": "KB",
"FOUNDED": 1786,
"NAME": "Kestrel Bay",
"POP": 4820
},
"type": "Feature"
},
{
"geometry": {
"coordinates": [
-12.3915,
47.112
],
"type": "Point"
},
"properties": {
"CODE": "MR",
"FOUNDED": 1834,
"NAME": "Marram",
"POP": 1180
},
"type": "Feature"
},
{
"geometry": {
"coordinates": [
-12.551,
47.018
],
"type": "Point"
},
"properties": {
"CODE": "HW",
"FOUNDED": 1801,
"NAME": "Holloway",
"POP": 2670
},
"type": "Feature"
},Specifications
- Features
- 5
- Geometry Type
- Point
- Crs
- WGS 84
- Delivery Mode
- download-only
- Provider
- converter-v2
- Provenance
- Synthetic deterministic P8 fixture generated by generation/p8_content.py; seed namespace 2026082300
- Fixture Reserve
- convert-v2
Testing contract
Reference control- Scenario
- Convert the four shapefile companions to RFC 7946 GeoJSON and compare feature order and coordinates.
- Expected result
- Five Point features match KB, MR, HW, NP, and QC in source order; all four DBF fields and coordinates match in longitude/latitude order to six decimal places.
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
“Convert v2 Shapefile Expected GeoJSON” is a deterministic Novus Examples fixture for Conversion testing, Geospatial, JSON parsing. The same content exported across many formats and linked as a group, so you can convert one and diff against the expected twin.
Documented properties for this file: GEOJSON · 1,502 bytes. 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("kestrel-bay-towns-expected.geojson")
print(gdf.head())
print(gdf.crs)Related files
- geojsonGeoJSON — Mixed-Geometry FeatureCollectionAll seven RFC 7946 geometry types in a single FeatureCollection. Formats with a single-geometry-type-per-layer model — shapefile, most database tables — cannot hold this in one layer, so it is the fixture that reveals how a converter splits or refuses it.
- geojsonGeoJSON — Three-Element Positions With AltitudeFour positions with a third element, which RFC 7946 defines as height in metres above the WGS 84 ellipsoid. Two-dimensional pipelines commonly truncate the third element without saying so, and this file is what proves whether yours does.
- geojsonGeoJSON Geometry — LineStringA one-feature FeatureCollection holding the four-vertex Coast Road, so a reader can be exercised on LineString in isolation. Coordinates come from the Kestrel Bay territory, so the same shape appears again in every other format in this category.
- geojsonGeoJSON Geometry — MultiLineStringA one-feature FeatureCollection holding all three roads as one geometry, so a reader can be exercised on MultiLineString in isolation. Coordinates come from the Kestrel Bay territory, so the same shape appears again in every other format in this category.
- geojsonGeoJSON Geometry — MultiPointA one-feature FeatureCollection holding three harbour buoys, so a reader can be exercised on MultiPoint in isolation. Coordinates come from the Kestrel Bay territory, so the same shape appears again in every other format in this category.
- geojsonGeoJSON Geometry — MultiPolygonA one-feature FeatureCollection holding the three parcels as one geometry, so a reader can be exercised on MultiPolygon in isolation. Coordinates come from the Kestrel Bay territory, so the same shape appears again in every other format in this category.
Generated by generation/p8_content.py. Free for any use, no attribution required — license.