topojson6.9 KB

Kestrel Bay Territory — Unquantized TopoJSON Twin

The territory as TopoJSON with no quantization and no transform, so arc coordinates are the raw WGS 84 positions. Decoding it must reproduce the master GeoJSON exactly — which makes it the reference case before the quantized fixtures introduce rounding.

Geospatial Conversion testing JSON parsing

Preview — first 50 linestopojson

{
  "type": "Topology",
  "objects": {
    "territory": {
      "type": "GeometryCollection",
      "geometries": [
        {
          "type": "Point",
          "properties": {
            "name": "Kestrel Bay",
            "code": "KB",
            "kind": "town",
            "population": 4820,
            "founded": 1786
          },
          "coordinates": [
            -12.482,
            47.064
          ]
        },
        {
          "type": "Point",
          "properties": {
            "name": "Marram",
            "code": "MR",
            "kind": "town",
            "population": 1180,
            "founded": 1834
          },
          "coordinates": [
            -12.3915,
            47.112
          ]
        },
        {
          "type": "Point",
          "properties": {
            "name": "Holloway",
            "code": "HW",
            "kind": "town",
            "population": 2670,
            "founded": 1801
          },
          "coordinates": [
            -12.551,
            47.018
          ]
        },
        {
          "type": "Point",

… 429 lines total — download for the full file.

Specifications

Territory: Kestrel Bay County (invented)
Crs: WGS 84 (EPSG:4326), longitude/latitude order
Features: 14
Geometry Types: Point, MultiPoint, LineString, Polygon
Bbox: -12.64,46.95,-12.36,47.14
Encoding: UTF-8
Format: TopoJSON 1.0
Objects: 1
Arcs: 10
Quantization: none
Transform: false
Line Endings: LF

Testing contract

Reference control

Scenario: Decode the topology to GeoJSON and diff it against the master FeatureCollection.
Expected result: Every coordinate matches the master exactly; there is no quantization error to allow for.

What is a .topojson file?

TopoJSON is an extension of GeoJSON that encodes topology. Shared boundaries are stored once as arcs and referenced by the geometries that use them, coordinates are quantised to an integer grid and delta-encoded, and a transform object records the scale and translation needed to recover real positions. For data with many adjacent polygons — administrative boundaries especially — files are dramatically smaller than the equivalent GeoJSON.

How to use this file

Use an example .topojson file to test TopoJSON readers and GeoJSON converters, verifying that arcs are dereferenced in the right direction, that negative arc indices are handled, and that the quantisation transform is reversed exactly.

How to use this file for testing

“Kestrel Bay Territory — Unquantized TopoJSON Twin” is a deterministic Novus Examples fixture for Geospatial, Conversion testing, 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 · LF · TopoJSON 1.0. 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.