Skip to content
Novus Examples
geojson1.8 KB

GeoJSON — Legacy 2008 `crs` Member (removed in RFC 7946)

A FeatureCollection carrying the `crs` member from the 2008 GeoJSON specification. RFC 7946 removed it and fixed the CRS as WGS 84, so a modern reader should treat this as an ignorable foreign member — but plenty of exporters still write it and some readers still obey it.

Preview — first 50 linesgeojson
{
  "type": "FeatureCollection",
  "crs": {
    "type": "name",
    "properties": {
      "name": "urn:ogc:def:crs:OGC:1.3:CRS84"
    }
  },
  "features": [
    {
      "type": "Feature",
      "id": "town-KB",
      "properties": {
        "name": "Kestrel Bay",
        "code": "KB",
        "kind": "town",
        "population": 4820,
        "founded": 1786
      },
      "geometry": {
        "type": "Point",
        "coordinates": [
          -12.482,
          47.064
        ]
      }
    },
    {
      "type": "Feature",
      "id": "town-MR",
      "properties": {
        "name": "Marram",
        "code": "MR",
        "kind": "town",
        "population": 1180,
        "founded": 1834
      },
      "geometry": {
        "type": "Point",
        "coordinates": [
          -12.3915,
          47.112
        ]
      }
    },
    {
      "type": "Feature",
      "id": "town-HW",
      "properties": {
        "name": "Holloway",
102 lines total — download for the full file.

Specifications

Format
GeoJSON 2008 style
Features
5
Crs Member
urn:ogc:def:crs:OGC:1.3:CRS84
Rfc7946 Status
the crs member was removed; WGS 84 is assumed
Valid
true
Note
harmless here because CRS84 is what RFC 7946 mandates anyway

Testing contract

Expected to recover
Scenario
Parse the document and check whether the crs member changes how coordinates are interpreted.
Expected result
The member is ignored or preserved as a foreign member; coordinates are read as WGS 84 either way, because CRS84 is exactly what RFC 7946 assumes.

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 — Legacy 2008 `crs` Member (removed in RFC 7946)” is a deterministic Novus Examples fixture for Geospatial, Conversion testing, 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: GeoJSON 2008 style. 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("legacy-crs-member.geojson")
print(gdf.head())
print(gdf.crs)

Generated by generation/geospatial.py. Free for any use, no attribution required — license.