- Google KML Reader/Writer
- Google KML Quick Facts
- Resource Traversal
- Reader Parameters
- Writer Parameters
- Feature Types
- Writer Pipelines
- Atom Metadata
- Style Management and Common Styles
- Document Element Omission
- Raw Text
- Update Mode
- Feature Representation
- KML Dataset Structure
- File Structure
- Identifying Elements
- Documents and Folders
- Tours
- Extended Data
- User Defined Schema
- Layers and Feature Type Fanout
- Feature Attributes
- Geometry
- 3D
- Fixed Schema
- Common Element Attributes
- Common Format Attributes
- NetworkLinkControl
- Document
- Folder
- Placemark
- ScreenOverlay
- GroundOverlay
- PhotoOverlay
- NetworkLink
- Style
- StyleMap
- Tour
- AnimatedUpdate
- FlyTo
- SoundCue
- TourControl
- Wait
Update Item Order
Geo browsers, such as Google Earth, process each child element of the <Update> element in sequential order. As a result it is important to ensure that dependencies between individual update items are respected. For example, it is important to ensure that the “Create” for a parent Folder is executed prior to the “Create” for a Placemark. The writer sorts the contents of <Update> element in the following order:
- Update items are grouped according to their update mode in the following order: Delete, Create, Change
- Operations on parent nodes are executed prior to those on child nodes
- Operations on containers are executed prior to those on non-containers.
- By order of kml_id, where none of the above apply.