KML: Polygons With innerBoundaryIs Holes
Two polygons that each carry an `innerBoundaryIs` ring: a parcel with a courtyard and a lake with an island. KML names its rings explicitly instead of relying on winding order, so converting to GeoJSON means deciding the winding rather than copying it.
<?xml version="1.0" encoding="UTF-8"?>
<kml xmlns="http://www.opengis.net/kml/2.2">
<Document>
<name>Kestrel Bay areas</name>
<Placemark>
<name>Mill Court</name>
<description>Residential parcel with a courtyard</description>
<Polygon>
<outerBoundaryIs><LinearRing>
<coordinates>-12.47,47.056 -12.452,47.056 -12.452,47.068 -12.47,47.068 -12.47,47.056</coordinates>
</LinearRing></outerBoundaryIs>
<innerBoundaryIs><LinearRing>
<coordinates>-12.465,47.06 -12.465,47.064 -12.457,47.064 -12.457,47.06 -12.465,47.06</coordinates>
</LinearRing></innerBoundaryIs>
</Polygon>
</Placemark>
<Placemark>
<name>Wither Lake</name>
<description>Lake with a wooded island</description>
<Polygon>
<outerBoundaryIs><LinearRing>
<coordinates>-12.52,47.04 -12.495,47.04 -12.488,47.053 -12.506,47.061 -12.529,47.052 -12.52,47.04</coordinates>
</LinearRing></outerBoundaryIs>
<innerBoundaryIs><LinearRing>
<coordinates>-12.51,47.048 -12.511,47.0525 -12.504,47.053 -12.503,47.047 -12.51,47.048</coordinates>
</LinearRing></innerBoundaryIs>
</Polygon>
</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
- 2
- Geometry
- Polygon
- Inner Boundaries
- 2
- Outer Boundaries
- 2
- Styled
- false
Testing contract
Expected to pass- Scenario
- Convert to GeoJSON and inspect ring order and winding.
- Expected result
- Each polygon has its outer ring first and its inner ring second, and the exterior is rewound counter-clockwise as RFC 7946 requires.
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: Polygons With innerBoundaryIs Holes” is a deterministic Testaroo fixture for Geospatial, Conversion testing, Error handling. 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.
Generated by generation/geospatial.py. Free for any use, no attribution required, license.
Related files
- kmlKML: GroundOverlay and ScreenOverlayA georeferenced GroundOverlay pinned to the territory's bounding box and a ScreenOverlay anchored to a pixel position. Both reference images that are not present, which is the normal state for a bare .kml and the reason KMZ exists.
- kmzKMZ: Nested Folders, a Second KML, and a NetworkLinkA KMZ that contains a second KML in a subdirectory, reached through a `NetworkLink` with a relative href, plus an overlay image two directories deep. Readers that only load `doc.kml` show the overlay but none of the three parcels.
- geojsonGeoJSON, Intentionally Invalid: Hole Outside Its ShellIntentionally invalid: the second ring is a whole separate parcel filed as an interior ring of the first, which OGC Simple Features forbids. It is what happens when a MultiPolygon is flattened into a Polygon by concatenating rings.
- geojsonGeoJSON, Intentionally Invalid: Latitude Before LongitudeIntentionally invalid: the five towns with their coordinates written latitude-first. RFC 7946 fixes the order as longitude then latitude, and this is the mistake that arrives via an EPSG-URN-ordered source such as the GML twin in the territory subcategory.
- geojsonGeoJSON, Intentionally Invalid: Self-Intersecting RingIntentionally invalid: a bowtie ring whose two lobes wind in opposite directions, so the shoelace areas nearly cancel. Buffer, intersection and area operations on this geometry return nonsense rather than failing, which is why it belongs in a validation suite.
- geojsonGeoJSON, Intentionally Invalid: Unclosed Polygon RingIntentionally invalid: the parcel's exterior ring omits the repeated closing position that RFC 7946 requires. Many readers close it silently, which hides the producer's bug until a stricter consumer downstream rejects the data.
