GeoJSON — Numeric Feature Identifiers
The same five towns keyed by numeric ids. RFC 7946 allows an id to be either a string or a number, and code that assumes one type breaks on the other — usually by stringifying 1 into "1" and then failing to match on a later join.
{
"type": "FeatureCollection",
"features": [
{
"type": "Feature",
"id": 1,
"properties": {
"name": "Kestrel Bay",
"kind": "town",
"code": "KB"
},
"geometry": {
"type": "Point",
"coordinates": [
-12.482,
47.064
]
}
},
{
"type": "Feature",
"id": 2,
"properties": {
"name": "Marram",
"kind": "town",
"code": "MR"
},
"geometry": {
"type": "Point",
"coordinates": [
-12.3915,
47.112
]
}
},
{
"type": "Feature",
"id": 3,
"properties": {
"name": "Holloway",
"kind": "town",
"code": "HW"
},
"geometry": {
"type": "Point",
"coordinates": [
-12.551,
47.018
]
}Specifications
- Format
- GeoJSON (RFC 7946)
- Crs
- WGS 84 (EPSG:4326)
- Coordinate Order
- longitude, latitude
- Encoding
- UTF-8
- Line Endings
- LF
- Features
- 5
- Id Type
- number
- Id Range
- 1-5
- Valid
- true
Testing contract
Expected to pass- Scenario
- Import the collection and compare identifier types with the string-id twin in this family.
- Expected result
- Ids come back as the numbers 1-5, not as strings, and joins against numeric keys succeed.
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 — Numeric Feature Identifiers” is a deterministic Novus Examples fixture for Geospatial, JSON parsing, Metadata 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("feature-id-number.geojson")
print(gdf.head())
print(gdf.crs)Related files
- 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.
- geojsonGeoJSON — bbox on the FeatureCollectionThe five towns with a four-element bounding box on the collection, ordered west, south, east, north as RFC 7946 requires. The values are the true extent of the contained points, so a reader that recomputes the box can be scored against the declared one.
- geojsonGeoJSON — Foreign Members at Every LevelRFC 7946 section 6 allows members it does not define to sit alongside the ones it does, and requires parsers to ignore rather than reject them. This collection carries three such members at the top level.
- topojsonTopoJSON — Geometry Ids Alongside PropertiesFive town geometries that each carry both an `id` member and a `properties` object. TopoJSON keeps these separate, and converters that fold the id into properties (or drop it) break joins against an external attribute table.
- 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 — Empty FeatureCollectionA structurally valid FeatureCollection with an empty `features` array — what a spatial query legitimately returns when nothing matches. It is the standard fixture for the empty-state path of a map component.
Generated by generation/geospatial.py. Free for any use, no attribution required — license.