Kestrel Bay Territory — KML Twin
The same 14 features as KML Placemarks, with the multi-point buoys expressed as a MultiGeometry and the two holed polygons using innerBoundaryIs. KML orders coordinates longitude-first like GeoJSON, which makes it the least surprising twin in this group.
<?xml version="1.0" encoding="UTF-8"?>
<kml xmlns="http://www.opengis.net/kml/2.2">
<Document>
<name>Kestrel Bay County</name>
<Placemark>
<name>Kestrel Bay</name>
<description>town KB</description>
<Point><coordinates>-12.482,47.064</coordinates></Point>
</Placemark>
<Placemark>
<name>Marram</name>
<description>town MR</description>
<Point><coordinates>-12.3915,47.112</coordinates></Point>
</Placemark>
<Placemark>
<name>Holloway</name>
<description>town HW</description>
<Point><coordinates>-12.551,47.018</coordinates></Point>
</Placemark>
<Placemark>
<name>Ninepin</name>
<description>town NP</description>
<Point><coordinates>-12.4402,46.9725</coordinates></Point>
</Placemark>
<Placemark>
<name>Quillan Cross</name>
<description>town QC</description>
<Point><coordinates>-12.6135,47.0885</coordinates></Point>
</Placemark>
<Placemark>
<name>Coast Road</name>
<description>road R1</description>
<LineString><tessellate>1</tessellate>
<coordinates>-12.482,47.064 -12.451,47.0812 -12.4203,47.0995 -12.3915,47.112</coordinates>
</LineString>
</Placemark>
<Placemark>
<name>Ridge Way</name>
<description>road R2</description>
<LineString><tessellate>1</tessellate>
<coordinates>-12.482,47.064 -12.5115,47.049 -12.551,47.018</coordinates>
</LineString>
</Placemark>
<Placemark>
<name>Ninepin Lane</name>
<description>road R3</description>
<LineString><tessellate>1</tessellate>
<coordinates>-12.482,47.064 -12.4655,47.021 -12.4402,46.9725</coordinates>
</LineString>
</Placemark>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
- KML 2.2
- Placemarks
- 14
- Coordinate Order
- longitude,latitude[,altitude]
- Line Endings
- LF
Testing contract
Expected to pass- Scenario
- Open in a KML reader and compare each Placemark against the master GeoJSON feature of the same name.
- Expected result
- 14 Placemarks with matching names and geometry; the lake and Mill Court parcel each keep one inner boundary.
What is a .kml file?
KML (Keyhole Markup Language) is an XML format for representing geographic features, popularized by Google Earth and Google Maps. It supports placemarks, paths, polygons, styling, and overlays with WGS84 coordinates. It is widely used for sharing annotated maps and 3D geospatial content.
How to use this file
Use an example KML file to test geospatial parsing, placemark and style handling, and converters between KML, GeoJSON, and GPX.
How to use this file for testing
“Kestrel Bay Territory — KML Twin” is a deterministic Novus Examples fixture for Geospatial, Conversion testing, Metadata 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 · KML 2.2. 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
- geojsonGeoJSON — Legacy 2008 `crs` Member (removed in RFC 7946)A FeatureCollection carrying the `crs` member from the 2008 GeoJSON specification. RFC 7946 removed it and fixed the CRS as WGS 84, so a modern reader should treat this as an ignorable foreign member — but plenty of exporters still write it and some readers still obey it.

- gpkgGeoPackage — Features Stored in Web Mercator (EPSG:3857)The same five towns stored as projected metres rather than degrees, with EPSG:3857 registered in gpkg_spatial_ref_sys and stamped into every geometry blob's header. Unlike GeoJSON, GeoPackage genuinely supports this — so it is the clean way to test that your reader honours the declared SRS instead of assuming 4326.

- kmlKML — ExtendedData Untyped Data ElementsAttributes carried in `ExtendedData/Data` elements, which have names and display names but no declared types — every value is a string. Importers must infer that population is a number, and this is where a silently wrong inference starts.

- kmlKML — extrude With Three Different altitudeMode ValuesFour extruded points whose third coordinate means three different things depending on the `altitudeMode` beside it: ignored when clamped, height above terrain when relative, height above the ellipsoid when absolute. Copying the number without the mode changes what the data says.

- kmlKML — Nested Folders (three levels)Eight Placemarks arranged in three levels of Folder, the hierarchy KML uses for layer trees. GeoJSON has nothing equivalent, so a converter must either flatten and record the path or lose the structure entirely — and this file makes which one it did obvious.

- kmlKML — Shared Styles and a normal/highlight StyleMapShared `Style` blocks referenced by `styleUrl`, plus a `StyleMap` pairing normal and highlight states. KML colours are written aabbggrr rather than the usual rrggbbaa, which is why converted maps so often come out with red and blue swapped.

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