Skip to content
Novus Examples

Explore the test library

Search files, editable visual templates, and live browser targets from one registry-backed directory. Filtered query views stay crawlable for links but are deliberately noindex; the stable taxonomy pages below remain the canonical search surfaces.

158 results

Page 7 of 7; 24 results per page.

Show the canonical directory
Preview of TopoJSON — Two Parcels Sharing One Arc
topojson
1.2 KB
Actual file preview for TopoJSON — Two Parcels Sharing One Arc

TopoJSON — Two Parcels Sharing One Arc

Two adjacent parcels that share their common boundary as a single arc: West Field references it as 0 and East Field as ~0, the negative-index form that means traverse it backwards. Storing the boundary once is the whole point of TopoJSON, and it is also where naive decoders produce gaps or slivers.

File
TOPOJSON · Topojson · UTF-8
Use case
GeospatialConversion testing+1· Conversion set
Preview of TopoJSON — Zero-Length Arc
topojson
1.5 KB
Actual file preview for TopoJSON — Zero-Length Arc

TopoJSON — Zero-Length Arc

A topology whose fourth arc repeats the same position twice, giving a line of zero length. Quantization produces these routinely when two vertices land in the same grid cell, and simplification code that divides by segment length fails on them.

File
TOPOJSON · Topojson · UTF-8
Use case
GeospatialError handling+1· Conversion set
Preview of WKB — Hex Strings in Both Byte Orders
txt
332 B
Actual file preview for WKB — Hex Strings in Both Byte Orders

WKB — Hex Strings in Both Byte Orders

The same point encoded both ways, plus a polygon, as uppercase hex — the form WKB takes when it travels through a text column or a SQL console. The byte-order flag is the first byte of each string, so the two point encodings differ everywhere after it.

File
TXT · Wkt Wkb · 3 records
Use case
GeospatialSerialization testing+1· Conversion set
Preview of WKB — Raw Little-Endian Point
bin
21 B
Actual file preview for WKB — Raw Little-Endian Point

WKB — Raw Little-Endian Point

Twenty-one raw bytes: a byte-order flag, a little-endian geometry-type code of 1, and two float64 ordinates. This is the wire format PostGIS, GeoPackage and most spatial drivers actually move geometry in.

File
BIN · Wkt Wkb · ASCII
Use case
GeospatialSerialization testing+1· Conversion set
Preview of WKT — All Seven EMPTY Geometry Forms
wkt
126 B
Actual file preview for WKT — All Seven EMPTY Geometry Forms

WKT — All Seven EMPTY Geometry Forms

One EMPTY value for each WKT geometry type, one per line. Empty geometries are what spatial operations return when nothing is left, and round-tripping them is where a database driver usually turns a typed empty into a plain NULL.

File
WKT · Wkt Wkb · 7 records
Use case
GeospatialError handling+1· Conversion set
Preview of WKT — GEOMETRYCOLLECTION
wkt
192 B
Actual file preview for WKT — GEOMETRYCOLLECTION

WKT — GEOMETRYCOLLECTION

A single WKT value for a point, a line and a polygon in one value. WKT nests with bare parentheses and no type tags on the inner parts, so the number and depth of brackets is the only thing that distinguishes a polygon ring from a multipolygon member — which is where hand-written parsers go wrong.

File
WKT · Wkt Wkb · 1 record
Use case
GeospatialSerialization testing+1· Conversion set
Preview of WKT — Intentionally Invalid: Four Malformed Values
wkt
135 B
Actual file preview for WKT — Intentionally Invalid: Four Malformed Values

WKT — Intentionally Invalid: Four Malformed Values

Intentionally invalid: four WKT strings that each break in a different way — a point with one ordinate, a line whose last vertex is ragged, a polygon missing a closing bracket, and a misspelled keyword. Good parsers report which line and which character failed.

File
WKT · Wkt Wkb · 4 records
Use case
GeospatialError handling+1· Conversion set
Preview of WKT — LINESTRING
wkt
80 B
Actual file preview for WKT — LINESTRING

WKT — LINESTRING

A single WKT value for the four-vertex Coast Road. WKT nests with bare parentheses and no type tags on the inner parts, so the number and depth of brackets is the only thing that distinguishes a polygon ring from a multipolygon member — which is where hand-written parsers go wrong.

File
WKT · Wkt Wkb · 1 record
Use case
GeospatialSerialization testing+1· Conversion set
Preview of WKT — M (measured) Geometry
wkt
29 B
Actual file preview for WKT — M (measured) Geometry

WKT — M (measured) Geometry

A point with an M (measure) ordinate rather than a Z. Written without the tag this is indistinguishable from a Z geometry, and a parser that assumes the third ordinate is elevation silently converts a 345-second measure into a 345-metre altitude.

File
WKT · Wkt Wkb · ASCII
Use case
GeospatialSerialization testing+1· Conversion set
Preview of WKT — MULTIPOLYGON
wkt
330 B
Actual file preview for WKT — MULTIPOLYGON

WKT — MULTIPOLYGON

A single WKT value for all three parcels in one geometry. WKT nests with bare parentheses and no type tags on the inner parts, so the number and depth of brackets is the only thing that distinguishes a polygon ring from a multipolygon member — which is where hand-written parsers go wrong.

File
WKT · Wkt Wkb · 1 record
Use case
GeospatialSerialization testing+1· Conversion set
Preview of WKT — POINT
wkt
23 B
Actual file preview for WKT — POINT

WKT — POINT

A single WKT value for the Kestrel Bay town centre. WKT nests with bare parentheses and no type tags on the inner parts, so the number and depth of brackets is the only thing that distinguishes a polygon ring from a multipolygon member — which is where hand-written parsers go wrong.

File
WKT · Wkt Wkb · 1 record
Use case
GeospatialSerialization testing+1· Conversion set
Preview of WKT — POLYGON
wkt
167 B
Actual file preview for WKT — POLYGON

WKT — POLYGON

A single WKT value for the Mill Court parcel and its courtyard. WKT nests with bare parentheses and no type tags on the inner parts, so the number and depth of brackets is the only thing that distinguishes a polygon ring from a multipolygon member — which is where hand-written parsers go wrong.

File
WKT · Wkt Wkb · 1 record
Use case
GeospatialSerialization testing+1· Conversion set
Preview of WKT — Z (three-dimensional) Geometry
wkt
30 B
Actual file preview for WKT — Z (three-dimensional) Geometry

WKT — Z (three-dimensional) Geometry

A point with an explicit Z dimension tag. Some producers write `POINT Z (x y z)` and others write `POINT(x y z)` with no tag at all, so a parser has to cope with the dimension being declared or merely implied by the ordinate count.

File
WKT · Wkt Wkb · ASCII
Use case
GeospatialSerialization testing+1· Conversion set
Preview of WKT — ZM (four-ordinate) Geometry
wkt
89 B
Actual file preview for WKT — ZM (four-ordinate) Geometry

WKT — ZM (four-ordinate) Geometry

A three-vertex line carrying both elevation and a measure, so each position has four ordinates. GeoJSON tops out at three, which makes this the fixture that shows what a WKT-to-GeoJSON conversion has to drop and whether it says so.

File
WKT · Wkt Wkb · ASCII
Use case
GeospatialSerialization testing+1· Conversion set