TopoJSON, Intentionally Invalid: Arc Referenced Without Reversal
Intentionally invalid: East Field references the shared arc forwards when it should use the reversed form, so its ring no longer closes. This is the single most common hand-editing mistake in TopoJSON, and it produces a plausible-looking file that renders as a torn shape.
{
"type": "Topology",
"objects": {
"parcels": {
"type": "GeometryCollection",
"geometries": [
{
"type": "Polygon",
"id": "P-010",
"properties": {
"name": "West Field",
"areaHa": 1.31
},
"arcs": [
[
0,
1
]
]
},
{
"type": "Polygon",
"id": "P-011",
"properties": {
"name": "East Field",
"areaHa": 1.31
},
"arcs": [
[
0,
2
]
]
}
]
}
},
"arcs": [
[
[
-12.474,
47.069
],
[
-12.474,
47.06
]
],
[
[Specifications
- Format
- TopoJSON 1.0
- Crs
- WGS 84 (EPSG:4326)
- Encoding
- UTF-8
- Line Endings
- LF
- Objects
- 1
- Polygons
- 2
- Arcs
- 3
- Defect
- intentionally invalid: East Field references arc 0 forward instead of ~0
- Ring Closes
- false
- Valid
- false
Testing contract
Expected to fail- Scenario
- Decode the topology and check that every polygon ring closes.
- Expected result
- West Field closes; East Field does not, because the arc it reuses runs in the wrong direction: a decoder should report the open ring rather than auto-closing it.
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, Intentionally Invalid: Arc Referenced Without Reversal” is a deterministic Testaroo fixture for Geospatial, Error handling, Conversion 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 · intentionally invalid. 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.
Generated by generation/geospatial.py. Free for any use, no attribution required, license.
Related files
- geojsonGeoJSON, Intentionally Invalid: Hole Outside Its ShellIntentionally invalid: the second ring is a whole separate parcel filed as an interior ring of the first, which OGC Simple Features forbids. It is what happens when a MultiPolygon is flattened into a Polygon by concatenating rings.

- geojsonGeoJSON, Intentionally Invalid: Latitude Before LongitudeIntentionally invalid: the five towns with their coordinates written latitude-first. RFC 7946 fixes the order as longitude then latitude, and this is the mistake that arrives via an EPSG-URN-ordered source such as the GML twin in the territory subcategory.

- geojsonGeoJSON, Intentionally Invalid: Self-Intersecting RingIntentionally invalid: a bowtie ring whose two lobes wind in opposite directions, so the shoelace areas nearly cancel. Buffer, intersection and area operations on this geometry return nonsense rather than failing, which is why it belongs in a validation suite.

- geojsonGeoJSON, Intentionally Invalid: Unclosed Polygon RingIntentionally invalid: the parcel's exterior ring omits the repeated closing position that RFC 7946 requires. Many readers close it silently, which hides the producer's bug until a stricter consumer downstream rejects the data.

- geojsonGeoJSON, Intentionally Invalid: Web Mercator Metres in a .geojson FileIntentionally invalid: Web Mercator metres inside a file that claims to be GeoJSON, with a legacy `crs` member as the only hint. RFC 7946 allows exactly one coordinate system, so this file is what a desktop GIS produces when someone exports a projected layer to GeoJSON without reprojecting it first.

- geojsonGeoJSON: Antimeridian Line Split per RFC 7946The same transect cut at the 180th meridian into a two-part MultiLineString, which is what RFC 7946 section 3.1.9 recommends. The split latitude is the linear interpolation of the unsplit twin, so the two files describe the same ground path.
