TopoJSON — Quantized to a 10,000-Step Grid
The full territory quantized onto a 10,000-step grid with a transform block and delta-encoded arc positions — the default TopoJSON encoding. Rounding is bounded by the grid spacing, which over this 0.28-degree extent is about 2.2 m.
{
"type": "Topology",
"transform": {
"scale": [
2.8002800280028116e-05,
1.9001900190018776e-05
],
"translate": [
-12.64,
46.95
]
},
"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",Specifications
- Format
- TopoJSON 1.0
- Crs
- WGS 84 (EPSG:4326)
- Encoding
- UTF-8
- Line Endings
- LF
- Objects
- 1
- Arcs
- 10
- Quantization
- 10000
- Transform
- true
- Max Position Error Metres
- 2.2
- Delta Encoded
- true
Testing contract
Expected to pass- Scenario
- Decode the topology and compare each position with the unquantized territory twin.
- Expected result
- Every decoded position lands within about 2.2 m of the reference; no position is dropped and arc deltas accumulate without drift.
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
“TopoJSON — Quantized to a 10,000-Step Grid” 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.
Related files
- geojsonConvert v2 Shapefile Expected GeoJSONGeoJSON 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.

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

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