Skip to content
Testaroo
geojson2.5 KB

GeoJSON: bbox on Every Feature

Three 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.

GeospatialJSON parsingMetadata testing
Preview, first 50 linesgeojson
{
  "type": "FeatureCollection",
  "features": [
    {
      "type": "Feature",
      "id": "bb-1",
      "properties": {
        "name": "Harbour Yard",
        "kind": "parcel"
      },
      "geometry": {
        "type": "Polygon",
        "coordinates": [
          [
            [
              -12.49,
              47.06
            ],
            [
              -12.474,
              47.06
            ],
            [
              -12.474,
              47.069
            ],
            [
              -12.49,
              47.069
            ],
            [
              -12.49,
              47.06
            ]
          ]
        ]
      },
      "bbox": [
        -12.49,
        47.06,
        -12.474,
        47.069
      ]
    },
    {
      "type": "Feature",
      "id": "bb-2",
      "properties": {
        "name": "Coast Road",
        "kind": "road"
… 149 lines total: download for the full file.

Specifications

Format
GeoJSON (RFC 7946)
Crs
WGS 84 (EPSG:4326)
Coordinate Order
longitude, latitude
Encoding
UTF-8
Line Endings
LF
Features
3
Bbox Scope
feature
Bbox Length
4
Note
each bbox is the true extent of its own geometry
Valid
true

Testing contract

Reference control
Scenario
Build a bounding-box index from the declared per-feature boxes and compare it with one computed from geometry.
Expected result
All three declared boxes match their geometry exactly, including the holed lake polygon whose interior ring must not affect the extent.

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: bbox on Every Feature” is a deterministic Testaroo 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("bbox-per-feature.geojson")
print(gdf.head())
print(gdf.crs)

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

Related files