KMZ: Nested Folders, a Second KML, and a NetworkLink
A 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.
- doc.kml
- parcels.kml
- survey.png
Specifications
- Format
- KMZ (ZIP-wrapped KML)
- Namespace
- http://www.opengis.net/kml/2.2
- Crs
- WGS 84 (EPSG:4326)
- Coordinate Order
- longitude,latitude[,altitude]
- Encoding
- UTF-8
- Line Endings
- LF
- Members
- 3
- Root Document
- doc.kml
- Linked Documents
- 1
- Network Link Target
- layers/parcels.kml
- Bundled Resources
- 1
- Compression
- deflate
Testing contract
Expected to pass- Scenario
- Load the archive and follow the NetworkLink to the linked document.
- Expected result
- Both KML documents load (the overlay from doc.kml and three parcel polygons from layers/parcels.kml), and the relative href resolves inside the archive rather than over the network.
What is a .kmz file?
KMZ is a ZIP archive containing a KML document and the resources it references. The main document is stored as doc.kml at the archive root, with icons, overlay images, models, and any additional KML files alongside it, so a single file carries an entire map presentation. Google Earth and most GIS tools read KMZ and KML interchangeably.
How to use this file
Use an example .kmz file to test KML readers, map importers, and archive-aware pipelines, verifying that doc.kml is located correctly, that relative resource paths resolve inside the archive, and that styles and overlays survive extraction.
How to use this file for testing
“KMZ: Nested Folders, a Second KML, and a NetworkLink” 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 · KMZ (ZIP-wrapped KML). 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.
- kmlKML: MultiGeometry Mixing Points and a LineStringOne Placemark whose MultiGeometry mixes three Points with a LineString. GeoJSON has no equivalent single type for a heterogeneous set, so this must become a GeometryCollection, and converters that reach for MultiPoint instead lose the line.
- kmlKML: Polygons With innerBoundaryIs HolesTwo 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.
- 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.
