KML and KMZ: geographic documents for map presentation
See how KML describes geographic features and presentation, and why KMZ is a packaged form rather than a different geometry model.
Why this matters
KML is still common in shared map files, field planning, Google Earth workflows, and exported GIS content. Knowing its structure makes migrations and conversions less mysterious.
Learn it
KML is an XML-based geographic format standardized by OGC. It can describe placemarks, geometry, styles, folders, overlays, and other presentation-oriented content. KMZ is a ZIP-based package that usually contains a KML document plus related resources such as images. When moving KML into another system, preserve geometry and meaningful attributes while deciding what presentation-specific information should map to styles or metadata.
Work through an example
A KML Placemark may contain a name and Point geometry. The same feature in GeoJSON would place geometry in a Feature and non-geometric values in properties.
<Placemark>
<name>Example station</name>
<Point>
<coordinates>-122.3321,47.6062,0</coordinates>
</Point>
</Placemark>Practice
- 1Read the KML sample and identify the document, placemark, geometry, and coordinate order.
- 2Sketch how you would represent the same placemark as GeoJSON.
- 3List which KML style information your destination actually needs to preserve.
What to watch for
KML coordinate tuples are longitude,latitude[,altitude]. Do not assume the conversational latitude/longitude order.
Where this takes you
This knowledge helps with KML imports, GIS migration, field planning, and moving map content between tools.