kml2 KB

KML — ExtendedData Untyped Data Elements

Attributes 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.

Geospatial Metadata testing Conversion testing

Preview — first 50 lineskml

<?xml version="1.0" encoding="UTF-8"?>
<kml xmlns="http://www.opengis.net/kml/2.2">
  <Document>
    <name>Kestrel Bay attributes</name>
    <Placemark>
      <name>Kestrel Bay</name>
      <ExtendedData>
        <Data name="code"><value>KB</value></Data>
        <Data name="population"><displayName>Population</displayName><value>4820</value></Data>
        <Data name="founded"><value>1786</value></Data>
      </ExtendedData>
      <Point><coordinates>-12.482,47.064</coordinates></Point>
    </Placemark>
    <Placemark>
      <name>Marram</name>
      <ExtendedData>
        <Data name="code"><value>MR</value></Data>
        <Data name="population"><displayName>Population</displayName><value>1180</value></Data>
        <Data name="founded"><value>1834</value></Data>
      </ExtendedData>
      <Point><coordinates>-12.3915,47.112</coordinates></Point>
    </Placemark>
    <Placemark>
      <name>Holloway</name>
      <ExtendedData>
        <Data name="code"><value>HW</value></Data>
        <Data name="population"><displayName>Population</displayName><value>2670</value></Data>
        <Data name="founded"><value>1801</value></Data>
      </ExtendedData>
      <Point><coordinates>-12.551,47.018</coordinates></Point>
    </Placemark>
    <Placemark>
      <name>Ninepin</name>
      <ExtendedData>
        <Data name="code"><value>NP</value></Data>
        <Data name="population"><displayName>Population</displayName><value>640</value></Data>
        <Data name="founded"><value>1902</value></Data>
      </ExtendedData>
      <Point><coordinates>-12.4402,46.9725</coordinates></Point>
    </Placemark>
    <Placemark>
      <name>Quillan Cross</name>
      <ExtendedData>
        <Data name="code"><value>QC</value></Data>
        <Data name="population"><displayName>Population</displayName><value>310</value></Data>
        <Data name="founded"><value>1877</value></Data>
      </ExtendedData>
      <Point><coordinates>-12.6135,47.0885</coordinates></Point>
    </Placemark>
  </Document>

… 52 lines total — download for the full file.

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: 5
Extended Data Fields: 3
Typed: false
Fields: code, population, founded
Has Display Name: true

Testing contract

Expected to pass

Scenario: Import the file and inspect the resulting attribute types.
Expected result: All five placemarks carry code, population and founded; population and founded are either kept as strings or converted with the inference stated, never coerced silently.

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 — ExtendedData Untyped Data Elements” is a deterministic Novus Examples fixture for Geospatial, Metadata testing, 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 · 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.