Kestrel Bay Territory — One WKT Geometry Per Line
Every geometry in the territory as a bare WKT string, one per line and in master order. Attributes are deliberately absent so the file isolates geometry serialisation from attribute mapping.
POINT (-12.482 47.064)
POINT (-12.3915 47.112)
POINT (-12.551 47.018)
POINT (-12.4402 46.9725)
POINT (-12.6135 47.0885)
LINESTRING (-12.482 47.064, -12.451 47.0812, -12.4203 47.0995, -12.3915 47.112)
LINESTRING (-12.482 47.064, -12.5115 47.049, -12.551 47.018)
LINESTRING (-12.482 47.064, -12.4655 47.021, -12.4402 46.9725)
POLYGON ((-12.49 47.06, -12.474 47.06, -12.474 47.069, -12.49 47.069, -12.49 47.06))
POLYGON ((-12.47 47.056, -12.452 47.056, -12.452 47.068, -12.47 47.068, -12.47 47.056), (-12.465 47.06, -12.465 47.064, -12.457 47.064, -12.457 47.06, -12.465 47.06))
POLYGON ((-12.56 47.01, -12.538 47.01, -12.538 47.025, -12.56 47.025, -12.56 47.01))
POLYGON ((-12.52 47.04, -12.495 47.04, -12.488 47.053, -12.506 47.061, -12.529 47.052, -12.52 47.04), (-12.51 47.048, -12.511 47.0525, -12.504 47.053, -12.503 47.047, -12.51 47.048))
MULTIPOINT ((-12.4885 47.0685), (-12.4795 47.0712), (-12.4712 47.0668))
POLYGON ((-12.64 46.95, -12.36 46.95, -12.36 47.14, -12.64 47.14, -12.64 46.95))
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
- OGC Well-Known Text
- Records
- 14
- Coordinate Precision
- 6
- Line Endings
- LF
- Attributes
- false
Testing contract
Expected to pass- Scenario
- Read each line with a WKT parser and compare the geometry to the master GeoJSON feature at the same index.
- Expected result
- 14 geometries parse in order; the Mill Court parcel and Wither Lake each carry a second (interior) ring.
What is a .wkt file?
WKT (Well-Known Text) is the OGC's human-readable encoding for geometry and for coordinate reference systems. Geometry WKT spells out a type and its coordinates — POINT, LINESTRING, POLYGON, and their MULTI and GEOMETRYCOLLECTION forms — while CRS WKT nests PROJCS, GEOGCS, DATUM, and PARAMETER clauses. Its binary counterpart, WKB, encodes the same geometry model compactly.
How to use this file
Use an example .wkt file to test geometry parsers and CRS handling, exercising polygons with interior rings, empty geometries, coordinate precision, and the difference between WKT geometry and WKT coordinate-system definitions.
How to use this file for testing
“Kestrel Bay Territory — One WKT Geometry Per Line” is a deterministic Novus Examples fixture for Geospatial, Conversion testing, Serialization 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: 14 records · UTF-8 · LF. 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
- txtEWKB — PostGIS Hex With an Embedded SRIDPostGIS EWKB, where the SRID is carried by OR-ing 0x20000000 into the geometry-type word and appending the code. A strict OGC WKB reader sees type 0x20000001 instead of 1 and either fails or, worse, reports an unknown geometry type.
- wktEWKT — PostGIS Extended WKT With an SRID PrefixPostGIS's extended WKT, which prefixes the geometry with `SRID=4326;`. It is not part of the OGC standard, so a strict WKT parser rejects the whole string — while a PostGIS-aware one gets the coordinate system for free.
- shpShapefile — Parcels Geometry (.shp, Polygon with a hole)Three Polygon records, one of which has two rings: the Mill Court parcel and its courtyard. Shapefile winds rings the opposite way to GeoJSON — exterior clockwise, holes anticlockwise — and it has no explicit hole marker, so winding is the only signal a reader has.
- shpShapefile — Roads Geometry (.shp, 3 PolyLine records)Three single-part PolyLine records, each carrying its own bounding box, a part index and a run of little-endian coordinate doubles. PolyLine and Polygon share this layout, which is why the shape-type byte in the header is the only thing that distinguishes an open line from a closed ring.
- shpShapefile — Towns Geometry (.shp, 5 Point records)The geometry half of a point shapefile: a 100-byte header carrying the shape type and bounding box, then five 20-byte Point records. The file is useless on its own — attributes live in the .dbf and the coordinate system in the .prj, which is the point of shipping the whole component set.
- binWKB — Raw Little-Endian PointTwenty-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.
Generated by generation/geospatial.py. Free for any use, no attribution required — license.