KML — LineString Placemarks With tessellate
The three roads as LineString Placemarks with `tessellate` set, which tells a globe renderer to drape the line over terrain rather than drawing it as a straight chord. Converters that drop the flag produce lines that tunnel through hills.
<?xml version="1.0" encoding="UTF-8"?>
<kml xmlns="http://www.opengis.net/kml/2.2">
<Document>
<name>Kestrel Bay roads</name>
<Placemark>
<name>Coast Road</name>
<description>primary road, 9.4 km, reference 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>secondary road, 8.1 km, reference 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>track road, 10.6 km, reference R3</description>
<LineString><tessellate>1</tessellate>
<coordinates>-12.482,47.064 -12.4655,47.021 -12.4402,46.9725</coordinates>
</LineString>
</Placemark>
</Document>
</kml>
Specifications
- Format
- KML 2.2
- Namespace
- http://www.opengis.net/kml/2.2
- Crs
- WGS 84 (EPSG:4326)
- Coordinate Order
- longitude,latitude[,altitude]
- Encoding
- UTF-8
- Line Endings
- LF
- Placemarks
- 3
- Geometry
- LineString
- Tessellate
- 1
- Total Vertices
- 10
- Styled
- false
Testing contract
Expected to pass- Scenario
- Convert to GeoJSON and check both geometry and the tessellate flag.
- Expected result
- Three LineStrings are produced with 4, 3 and 3 vertices; the tessellate setting is either preserved as a property or reported as unmappable.
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
“KML — LineString Placemarks With tessellate” is a deterministic Novus Examples fixture for Geospatial, Conversion testing, Data import. 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
- kmzKMZ — Bundled Icon Referenced by a Relative PathA KMZ whose style points at `files/markers/town.png` inside the same archive. Resolving that relative href against the archive rather than the filesystem is the whole job of a KMZ reader, and it is where extract-then-parse implementations break.

- kmzKMZ — Single doc.kml, No ResourcesThe minimal KMZ: a ZIP holding exactly one `doc.kml` at the archive root and nothing else. Readers are supposed to open the first .kml they find, and most look for the conventional name — this file satisfies both rules.

- gpkgGeoPackage — Aspatial Attributes Table (no geometry column)A GeoPackage holding an `attributes` table with no geometry at all — the standard's own answer to a lookup table you want to ship alongside your layers. Its gpkg_contents row has null bounds and a null SRS, which is what readers that assume every row is spatial trip over.

- gpkgGeoPackage — Three Feature Layers in One SQLite ContainerThe territory as an OGC GeoPackage: an ordinary SQLite database with the three required metadata tables and three feature layers whose geometry columns hold GeoPackage binary blobs. Unlike a shapefile it carries several geometry types, long column names and real typed columns in one file.

- gpxGPX — Route (rte) Rather Than a TrackA `rte` element: an ordered list of waypoints describing a planned route, with no timestamps because it has not been travelled yet. Many importers only look for `trk` and report this perfectly valid file as empty.

- gpxGPX — Standalone Waypoints OnlyFive `wpt` elements for the towns of the territory, with names, symbols and descriptions but no track or route. It is the GPX equivalent of a point layer, and the third of the three top-level GPX content types.

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