KML is an XML grammar used to encode and transport representations of geographic data for display in an earth browser.  Put simply: KML encodes what to show in an earth browser, and how to show it.  KML uses a tag-based structure with nested elements and attributes and is based on the XML standard.

The KML community is wide and varied.  Casual users create KML Placemarks to identify their homes, describe journeys, and plan cross-country hikes and cycling ventures.  Scientists use KML to provide detailed mappings of resources, models, and trends such as volcanic eruptions, weather patterns, earthquake activity, and mineral deposits.  Real estate professionals, architects, and city development agencies use KML to propose construction and visualize plans.  Students and teachers use KML to explore people, places, and events, both historic and current.  Organizations such as National Geographic, UNESCO, and the Smithsonian have all used KML to display their rich sets of global data.

KML documents and their related images (if any) may be compressed using the ZIP format into KMZ archives.  KML documents and KMZ archives may be shared by e‑mail, hosted locally for sharing within a private internet, or hosted on a web server.

The following are keywords to be used by search engines and document catalogues.

ogcdoc, OGC document, OGC KML 2.3, OGC Keyhole Markup Language 2.3.

This is an OGC Implementation Standard for encoding representations of geographic data for display in an earth browser.

Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. The Open Geospatial Consortium shall not be held responsible for identifying any or all such patent rights.

Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of the standard set forth in this document, and to provide supporting documentation.

The following organizations submitted this Document to the Open Geospatial Consortium (OGC):

Galdos Systems Inc.

Google Inc.

European Union Satellite Centre

All questions regarding this submission should be directed to the editor or the submitters:

1. Scope

KML is an XML grammar used to encode and transport representations of geographic data for display in an earth browser, such as a 3D virtual globe, 2D web browser application, or 2D mobile application.  A KML instance is processed in much the same way that HTML (and XML) documents are processed by web browsers.  Like HTML, KML has a tag-based structure with names and attributes used for specific display purposes.

KML can be used to:

•    Annotate the Earth
•    Specify icons and labels to identify locations on the surface of the planet
•    Create different camera positions to define unique views for KML features
•    Define image overlays to attach to the ground or screen
•    Define styles to specify KML feature appearance
•    Write HTML descriptions of KML features, including hyperlinks and embedded images
•    Organize KML features into hierarchies
•    Locate and update retrieved KML documents from local or remote network locations
•    Define the location and orientation of textured 3D objects

2. Conformance

This standard defines three conformance classes (levels) for KML resources; these indicate the relative importance or priority of a particular set of constraints. The highest level (CL3) indicates full conformance, but a given application or user community may choose to enforce a lower level of conformance.

1. CL1: Includes test cases covering requirements that must be satisfied in all instances.
2. CL2: As for CL1, plus test cases addressing recommended requirements that should be satisfied.
3. CL3: As for CL2, plus test cases for optional constraints that are essentially informative in nature.

A KML resource that conforms to this standard shall satisfy all requirements stipulated in this document. Furthermore, it shall be checked using all applicable tests specified in Annex A (normative). The framework, concepts, and methodology for testing–and the criteria to be achieved to claim conformance–are specified in the OGC Compliance Testing Program Policies and Procedures manual (OGC 08-134r10) and at the OGC compliance testing web site[1].

3. Normative References

The following documents, in whole or in part, are normatively referenced in this document and are indispensable for its application. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.

OGC 14-068,

OGC KML 2.3 – Abstract Test Suite

IETF RFC 4287,

Atom Syndication Format. Available from: http://tools.ietf.org/html/rfc4287

OASIS Extensible Address Language (XAL) 2.0. ,

Available from: http://www.oasis-open.org/committees/ciq/download.html

IETF RFC 3966,

The tel URI for Telephone Numbers. Available from: http://tools.ietf.org/html/rfc3966

ISO 8601:2004,

Data elements and interchange formats — Information interchange — Representation of dates and times

IETF RFC 3986,

Uniform Resource Identifier (URI): Generic Syntax. Available from: http://tools.ietf.org/html/rfc3986

HTML5. ,

Available at http://www.w3.org/TR/html5/

W3C Extensible Markup Language (XML) 1.0. ,

Available from: http://www.w3.org/TR/REC-xml/

W3C Namespaces in XML 1.0. ,

Available from: http://www.w3.org/TR/REC-xml-names/

W3C XML Schema Definition Language (XSD) 1.1 Part 1: Structures. ,

Available at http://www.w3.org/TR/xmlschema11-1/

W3C XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes. ,

Available at http://www.w3.org/TR/xmlschema11-2/

4. Terms and Definitions

This document uses the terms defined in Sub-clause 5.3 of [OGC 06-121r8], which is based on the ISO/IEC Directives, Part 2, Rules for the structure and drafting of International Standards. In particular, the word “shall” (not “must”) is the verb form used to indicate a requirement to be strictly followed to conform to this standard.

For the purposes of this document, the following additional terms and definitions apply.

4.1 application schema

conceptual schema for data required by one or more applications.
[ISO 19101]

4.2 attribute <XML>

name/value pair contained in an element
NOTE:      In this document an attribute is an XML attribute unless otherwise specified

4.3 boundary

set that represents the limit of an entity
[ISO 19107]

4.4 bounding box

minimum volume that encloses a set of objects or data points.

4.5 child element <XML>

immediate descendant element

4.6 complex element <XML>

element of complex content

4.7 coordinate

one of a sequence of n numbers designating the position of a point in n-dimensional space
[ISO 19111]
NOTE:      In a coordinate reference system, the n numbers shall be qualified by units.

4.8 coordinate reference system

coordinate system that is related to an object by a datum
[ISO 19111]

4.9 coordinate system

set of mathematical rules for specifying how coordinates are to be assigned to points
[ISO 19111]

4.10 coordinate tuple

tuple composed of a sequence of coordinates
[ISO 19111]

4.11 data type

specification of a value domain with operations allowed on values in this domain
[ISO/TS 19103]
EXAMPLE:  integer, real, boolean, string, date (conversion of a data into a series of codes).
NOTE:      Data types include primitive predefined types and user-definable types.  All instances of a data types lack identity.

4.12 datum

The set of parameters used by a coordinate reference system that define the position of the origin, the scale, and the orientation of a coordinate system
[ISO 19111]
NOTE:      The datums in used  by the KML coordinate reference system  are a vertical datum based on the geoid earth model and a (horizontal) and a geodetic datum, which specifies the ellipsoid model, area of use, and position of the prime meridian .

4.13 document <XML>

well-formed XML instance

4.14 earth browser

software for displaying and annotating models of the Earth

4.15 element <XML>

basic information item of an XML document containing child elements, attributes and character data
NOTE:      From the XML Information Set:  "Each XML document contains one or more elements, the boundaries of which are either delimited by start-tags and end-tags, or, for empty elements, by an empty-element tag.  Each element has a type, identified by name, sometimes called its ‘generic identifier’ (GI), and may have a set of attribute specifications.  Each attribute specification has a name and a value."

4.16 field

child element of simple content

4.17 field type

XML Schema simple type defined in the KML schema document

4.18 geodetic datum

datum describing the relationship of a 2- or 3-dimensional coordinate system to the Earth
[ISO 19111]

4.19 geographic view

display of geographic KML elements

4.20 interior

set of all points that are on a geometric object but which are not on its boundary

4.21 line string

curve composed of straight-line segments

4.22 list view

display of one or more hierarchies of KML Features

4.23 namespace <XML>

collection of names, identified by a URI reference, which are used in XML documents as element names and attribute names [W3C XML Namespaces]

4.24 plate carrée projection

A simple cylindrical projection in which the target plane has a horizontal axis representing longitude (standard parallel is the Equator) and vertical axis representing latitude. Otherwise known as equi-rectangular, plane chart, or unprojected map projection.

4.25 point

0-dimensional geometric primitive, representing a position
[ISO 19107]
NOTE:      The boundary of a point is the empty set.

4.26 polygon

planar surface defined by 1 exterior boundary and 0 or more interior boundaries

4.27 resource

network data object or service that is identified by a URL

4.28 schema

formal description of a model
[ISO 19101]
NOTE:      In general, a schema is an abstract representation of an object’s characteristics and relationship to other objects.  An XML schema represents the relationship between the attributes and elements of an XML object (for example, a document or a portion of a document)

4.29 schema <XML Schema>

collection of schema components within the same target namespace
EXAMPLE:  Schema components of W3C XML Schema are types, elements, attributes, groups, etc.

4.30 schema document <XML Schema>

XML document containing schema component definitions and declarations
NOTE:      The W3C XML Schema provides an XML interchange format for schema information. A single schema document provides descriptions of components associated with a single XML namespace, but several documents may describe components in the same schema, i.e. the same target namespace.

4.31 simple element <XML>

element of simple content

4.32 tag <XML>

markup in an XML document delimiting the content of an element
NOTE:      A tag with no forward slash (e.g. <Placemark> ) is called a start-tag (also opening tag), and one with a forward slash (e.g. </Placemark> is called an end-tag (also closing tag).

4.33 tuple

ordered list of values

4.34 Uniform Resource Identifier (URI)

unique identifier for a resource, structured in conformance with IETF RFC 2396
NOTE:      The general syntax is <scheme>::<scheme-specific-part>.  The hierarchical syntax with a namespace is <scheme>://<authority><path>?<query> – see [RFC 2396].

5.    Conventions

5.1       Abbreviated Terms

Some frequently used abbreviated terms:

CRS

                 Coordinate Reference System

CS

                   Coordinate System

CSV

                 Comma Separated Values

CT

                   Coordinate Transformation

EPSG

              European Petroleum Survey Group

GIS

                  Geographic Information System

GML

               Geography Markup Language

HTTP

             Hyper Text Transfer Protocol

IETF

               Internet Engineering Task Force

ISO

                  International Organization for Standardization

KMZ

              KML Archive File

OGC

               Open Geospatial Consortium

RFC

                Request for Comments

URI

                 Uniform Resource Identifier

URL

                Uniform Resource Locator

URN

               Uniform Resource Name

W3C

                World Wide Web Consortium

xAL

                 Extensible Address Language

XML

               Extensible Markup Language

XSD

                XML Schema Definition

0D

                   Zero Dimensional

1D

                   One Dimensional

2D

                   Two Dimensional

3D

                   Three Dimensional

5.2       XML Namespaces

Several namespace bindings are assumed in this document (see Table 1). However, in an instance document the actual prefix bound to a given namespace is not significant; any legal NCName (http://www.w3.org/TR/xml-names/#NT-NCName) may be used.

All components of the KML schema are defined in the namespace with the name identifier "http://www.opengis.net/kml/2.2", for which the prefix kml or the default (no prefix) namespace is used within this Standard. The namespace for KML 2.3 is unchanged from version 2.2, because any KML document valid under the rules of version 2.2 has essentially the same schema assessment semantics under this specification as it did under version 2.2. Users of the KML namespace should be aware that additional backward compatible schema components in this namespace may be defined in future minor revisions of this standard, according to the following rules:

1. New elements or attributes added to previously existing KML elements in a minor revision shall be declared optional.
2. New global elements are permitted in a minor revision, but shall not be required to appear in an instance document.
3. Existing elements/attributes in previous minor versions shall not be removed in a new minor release, but may be labelled ‘deprecated’, meaning that support may no longer exist in the next major release.
4. Any schema components unrecognized by a KML application shall be gracefully ignored.

The atom:author and atom:link components described by the Atom Syndication Format are defined in the namespace with the name identifier "http://www.w3.org/2005/Atom".

The schema components from these namespaces are documented in the XML Schema documents  that accompany this standard, which are hosted in the OGC KML schema repository: http://schemas.opengis.net/kml/.

The xAL:AddressDetails component described by the extensible Address Language is defined in the namespace with the name identifier "urn:oasis:names:tc:ciq:xsdschema:xAL:2.0".

5.3      XML Schema

KML 2.3 uses the W3C XML 1.1 Schema language to describe the grammar of conformant KML data instances.  The KML schema document is hosted in the OGC KML schema repository (http://schemas.opengis.net/kml/) and forms a normative part of this OGC Implementation Standard.

The normative KML schema includes deprecated schema components that KML producers are advised to not use; they may be removed in a subsequent major revision.

5.4       Versioning

Each schema document specifying components of the KML schema shall carry a version attribute as defined in the XML Schema Recommendation.  The format of the version attribute string is x.y.z where x denotes the major version number, y denotes a minor version number, and z denotes a bug fix release for that document. The schema version attribute shall capture the corresponding standard document version and satisfy the compatibility requirements in conformance with OGC standard policy directives (06-135r11, 13.1, 13.2, and 13.4). The target namespace combined with the value of schema/@version uniquely identifies the KML schema.

KML instance documents also carry an version attribute on the root KML element declaring which version of the schema it conforms to. The KML version attribute combined with the KML namespace declared on the root KML element, uniquely identifies the schema that the KML instance conforms to.

5.5       Deprecated parts of previous versions of KML

The verb “deprecate” provides notice that the referenced portion of this Standard is being retained for backwards compatibility with earlier versions but may be removed from a subsequent major revision.

5.6       Documentation

Clauses 7 to 16 specify the content model for each KML element.  The KML content model is defined in terms of child elements and attributes.  Where a child element is defined in a separate subclause, a link is provided to it.

Throughout this document, the following conventions are used:

•   Concrete element and attribute names used within the text are formatted in Courier New and abstract elements in Courier New Italic, except in the case of headings and references to them.
•   A value from an enumerated set is in bold.
•   Child element content is specified within the element subclause whose type declares such children.
•   The prefix “xsd:” is used to identify types that are defined by XML Schema, for example xsd:string.
•   The use of abstract substitution elements within the text refers to the concrete elements that substitute for them.  For example, kml:AbstractContainerGroup refers to the kml:Document and kml:Folder elements that substitute for it.  Element substitution is described for each element where applicable.
•   The term kml:Document is a KML element; the term “KML document” refers to an XML instance of KML.
•   Default values for simple elements are listed under relevant Content subclauses.  Unless otherwise stated, default values for optional elements shall apply when such elements are empty or absent.
•   The term “KML resource” refers to a local or remote KML or KMZ instance.

Each element subclause includes an XML structure section that shows the content model for the described element as a representative XML instance, using the following conventions:

•   The minimum and maximum occurrence of elements and attributes required by its schema type are shown in square brackets, for example [0..1].  Such occurrence requirements are necessary but insufficient in that additional occurrence requirements are asserted within this .
•   Elements are itemized in document order but may appear in any order in an XML instance, since element order is no longer enforced by the KML schema as of version 2.3.
•   Where the type for an element derives by extension from a base type, the elements and attributes that have been added to the base type’s content are shown in bold.

6.      KML Model Overview

6.1       KML Abstract Element Substitution Hierarchy

This section provides an overview of the KML schema type hierarchy.  While element names are used, they represent the schema types that define their content. As KML is an XML grammar, element names are case-sensitive and must appear exactly as specified in the KML schema document.

In KML, some types are derived from a parent type. A derived type typically inherits all of the elements of its parent type and adds some specific element content of its own.  KML also includes abstract elements whose type is also abstract.  Such abstract types are used to establish schema type hierarchies.  Abstract elements may serve as placeholders for elements that substitute for them in the XML Schema sense.

The KML abstract element substitution hierarchy is represented by the following nested list, showing the abstract KML elements that serve as the head of substitution groups. The corresponding types of the abstract elements (shown in brackets) follow an equivalent parallel type  hierarchy.  For example, kml:AbstractContainerGroup substitutes for kml:AbstractFeatureGroup, which in turn substitutes for kml:AbstractObjectGroup. Likewise, kml:AbstractContainerType derives by exenstion from kml:AbstractFeatureType, which in turn derives from kml:AbstractObjectType.

•   kml:AbstractObjectGroup (kml:AbstractObjectType)
  •   kml:AbstractFeatureGroup (kml:AbstractFeatureType)
    •   AbstractContainerGroup (kml:AbstractContainerType)
    •   AbstractOverlayGroup (kml:AbstractOverlayType)
  •   AbstractGeometryGroup (kml:AbstractGeometryType)
  •   AbstractStyleSelectorGroup (kml:AbstractStyleSelectorType)
  •   AbstractSubStyleGroup (kml:AbstractSubStyleType)
    •   AbstractColorStyleGroup (kml:AbstractColorStyleType)
  •   AbstractExtentGroup (kml:AbstractExtentType)
    •   AbstractLatLonBox (kml:AbstractLatLonBoxType)
  •   AbstractViewGroup (kml:AbstractViewType)
  •   AbstractTimePrimitiveGroup (kml:AbstractTimePrimitiveType)
  •   AbstractLinkGroup (kml:AbstractObjectType)
  •   AbstractTourPrimitiveGroup (kml:AbstractTourPrimitiveType)

These abstract elements and their associated base types define the core of the language.

All concrete elements derived from kml:AbstractObjectGroup may have an assigned identifier.

Simple elements are generally referred to as KML fields.  Such elements are of XML Schema simple types or KML field types defined in the KML schema.  KML field types are specified in clause 16 Field Types.

6.2       Coordinate Reference System

Each element that extends the kml:AbstractGeometryGroup element defines a spatial extent of a kml:Placemark.  The spatial extent may include the location of an anchor point on the earth to serve as an origin for a 3D object as in the case of the kml:Model element, or may include the encoding of explicit coordinate tuples in the kml:coordinates element in the case of the kml:Point, kml:LineString, and kml:LinearRing elements.

The KML encoding of every kml:Location and coordinate tuple uses geodetic longitude, geodetic latitude, and altitude (in that order) as defined in Annex B. Note that altitude is measured from the vertical datum, which is the WGS84 EGM96 Geoid. The altitude measurement (orthometric H) is illustrated in Figure 1.

6.3       Geometry Interpolation for 3D Earth Browsers

6.3.1      Interpolated Points

Geometric points which are not explicitly encoded are called interpolated points.  The following subclauses describe the interpolation schemes for the kml:LineString, kml:LinearRing, and kml:Polygon elements.

6.3.2      kml:LineString and kml:LinearRing

The type of interpolation used for the kml:LineString and kml:LinearRing elements depend on the values of the child kml:altitudeMode and kml:tessellate elements.  If the kml:altitudeMode value is not clampToGround then the interpolation between two consecutive control points is a straight line segment in the 3D WGS 84 geocentric coordinate reference system (http://www.opengis.net/def/crs/EPSG/0/4978).  This straight line segment will be referred to as L in Table 2, which summarizes the kml:LineString and kml:LinearRing interpolation scheme for the various combinations of kml:altitudeMode and kml:tessellate values.

For example, in the following KML instance the kml:LineString coordinates element has two control points (–135,30,500000) and (–80,30,500000) of the form (lon,lat,altitude) in the CRS defined in  with gml:id=“LonLat84_5773”.

<kml xmlns=“http://www.opengis.net/kml/2.2”>
  <Document>
    <Placemark>
      <LineString>
        <altitudeMode>absolute</altitudeMode>
        <coordinates>-135,30,500000 -80,30,500000</coordinates>
      </LineString>
    </Placemark>
  </Document>
</kml>

Since the kml:altitudeMode is absolute, the interpolation between these two control points is the straight line segment L shown in Figure 2 in the 3D WGS 84 geocentric CRS, which does not follow the earth’s curvature and cuts through the earth’s terrain.

The line segment L will be projected to the terrain surface if kml:altitudeMode and kml:tessellate are set as in the following kml:LineString instance.  In this case the projected kml:LineString will follow the earth’s curvature as shown in Figure 3

<kml xmlns=“http://www.opengis.net/kml/2.2”>
  <Document>
    <Placemark>
      <LineString>
        <tessellate>true</tessellate>
        <altitudeMode>clampToGround</altitudeMode>
        <coordinates>-135,30,500000 -80,30,500000</coordinates>
      </LineString>
    </Placemark>
  </Document>
</kml>

If kml:altitudeMode and kml:tessellate are set as in the following kml:LineString instance, then the only the control points are projected to the terrain and the interpolation between the projected control points is a straight line segment in the WGS 84 Geocentric CRS as shown in Figure 4.

<kml xmlns=“http://www.opengis.net/kml/2.2”>
  <Document>
    <Placemark>
      <LineString>
        <tessellate>false</tessellate>
        <altitudeMode>clampToGround</altitudeMode>
        <coordinates>-135,30,500000 -80,30,500000</coordinates>
      </LineString>
    </Placemark>
  </Document>
</kml>

6.3.3      kml:Polygon

The type of interpolation used for the kml:Polygon element also depends on the values of the child kml:altitudeMode and kml:tessellate elements.  If the kml:altitudeMode value is not clampToGround then the interpolation of the kml:Polygon boundary comprised of the descendent kml:LinearRing elements is as described previously in Table 2.  The remaining interior points of the kml:Polygon are then filled in linearly in the 3D WGS 84 geocentric CRS, i.e. they must lie on the plane that passes through all the control points of each kml:LinearRing.

The control points of every kml:LinearRing must lie on a common plane.

Table 3 summarizes the kml:Polygon interpolation scheme for the various combination of kml:altitudeMode and kml:tessellate values.

For example, the following kml:Polygon encodes five control points in its outer boundary in the CRS defined in Annex B.

<kml xmlns=“http://www.opengis.net/kml/2.2”>
  <Document>
    <Placemark>
      <Polygon>
        <altitudeMode>absolute</altitudeMode>
        <outerBoundaryIs>
          <LinearRing>
            <coordinates>
-135,50,300000 -135,40,450000 -80,40,450000 -80,50,300000 -135,50,300000
            </coordinates>
          </LinearRing>
        </outerBoundaryIs>
      </Polygon>
    </Placemark>
  </Document>
</kml>

Since the kml:altitudeMode is absolute, the outer boundary points of the polygon that are interpolated between the control points in the kml:LinearRing form a quadrilateral perimeter in the 3D WGS 84 geocentric CRS.  The interior points of this 4 sided polygon are filled in linearly in the 3D WGS 84 geocentric CRS and form the plane region inside the perimeter.  Note that the plane region does not follow the earth’s curvature and cuts through the surface of the earth as shown in Figure 5.

In the following kml:Polygon instance the kml:altitudeMode is set to clampToGround.

<kml xmlns=“http://www.opengis.net/kml/2.2”>
  <Document>
    <Placemark>
      <Polygon>
        <altitudeMode>clampToGround</altitudeMode>
        <outerBoundaryIs>
          <LinearRing>
            <coordinates>-135,78.5,300000 -135,12.5,300000 -45,12.5,300000 -45,78.5,300000 -135,78.5,300000</coordinates>
          </LinearRing>
        </outerBoundaryIs>
      </Polygon>
    </Placemark>
  </Document>
</kml>

The outer boundary points of the polygon that are interpolated between the control points in the kml:LinearRing form a rectangular perimeter in the plate carrée plane.  Then the interior points of the rectangle are filled in linearly in this plane.  Finally each (lon,lat) point of the rectangle is mapped to a (lon,lat,alt) point on the earth terrain surface as shown in Figure 6.

6.3.4      kml:GroundOverlay and kml:Region

The latitude and longitude boundaries for both kml:GroundOverlay and kml:Region are specified by the elements kml:west, kml:east, kml:south, and kml:north. In the case of kml:GroundOverlay constant lines of longitude demarcate the portion of the kml:LatLonBox boundary corresponding to the values of kml:west, kml:east and constant lines of latitude demarcate the portion of the boundary corresponding to the values of kml:south, kml:north. If kml:altitudeMode value is not clampToGround, as in the following KML example, then the altitude of the kml:GroundOverlay is determined by the kml:altitude element.

<kml>
  <GroundOverlay>
    <altitude>500000</altitude>
    <altitudeMode>absolute</altitudeMode>
    <LatLonBox>
      <north>80.0</north>
      <south>60.0</south>
      <east>60.0</east>
      <west>-60.0</west>
    </LatLonBox>
  </GroundOverlay>
</kml>

The KML example above is shown in Figure 7. If kml:altitudeMode value is clampToGround then the kml:GroundOverlay is projected onto the earth’s terrain surface model similar to the case of the kml:Polygon shown on the right hand side of Figure 6.

In the case of kml:Region the values of kml:west, kml:east of kml:LatLonAltBox determine the boundary surfaces of constant longitude and the values of kml:south, kml:north determine the boundary surfaces of constant latitude. The values of kml:minAltitude and kml:maxAltitude in the kml:LatLonAltBox determine the lower and upper bounding surfaces of constant altitude, respectively.

<kml>
  <Region>
    <LatLonAltBox>
      <north>80.0</north>
      <south>60.0</south>
      <east>60.0</east>
      <west>-60.0</west>
      <minAltitude>500000</minAltitude>
      <maxAltitude>2000000</maxAltitude>
      <altitudeMode>absolute</altitudeMode>
    </LatLonAltBox>
  </Region>
</kml>

The spatial extent of the sample kml:Region encoded above is depicted in Figure 8.

6.4       Shared Styles

A kml:Style or kml:StyleMap element contained by a kml:AbstractFeatureGroup element is an “inline style” and shall apply only to the kml:AbstractFeatureGroup that contains it.  When these elements are encoded as the child of a kml:Document element they are called a “shared style.”  A shared style shall have an id value.  A shared style applies to any kml:AbstractFeatureGroup that references the style from its child kml:styleUrl element.

If a kml:AbstractFeatureGroup is associated with both an inline and shared style, the inline style shall take precedence.

Shared styles shall only be encoded within a Document. Shared styles are not inherited by any child kml:AbstractFeatureGroup elements of a kml:Document.

For a kml:Style or kml:StyleMap that applies to a kml:Document, the kml:Document itself must explicitly reference a shared style.  For example:

<Document>
  <Style id=“myPrettyDocument”>
   <ListStyle>…</ListStyle>
 
  </Style>
  <styleUrl#myPrettyDocument">
  …
</Document>

<kml xmlns=“http://www.opengis.net/kml/2.2”>
<Document>
  <name>Document.kml</name>
  <open>1</open>
  <Style id=“exampleStyleDocument”>
    <LabelStyle>
      <color>ff0000cc</color>
    </LabelStyle>
  </Style>
  <Placemark>
    <name>Document Feature 1</name>
    <styleUrl>#exampleStyleDocument</styleUrl>
    <Point>
      <coordinates>-122.371,37.816,0</coordinates>
    </Point>
  </Placemark>
  <Placemark>
    <name>Document Feature 2</name>
    <styleUrl>#exampleStyleDocument</styleUrl>
    <Point>
      <coordinates>-122.370,37.817,0</coordinates>
    </Point>
  </Placemark>
</Document>
</kml>

6.5       Entity Replacement

Entity substitution is employed as a template mechanism within the kml:BalloonStyle kml:text element. Individual values shall be substituted for each instance of the entity, or a null string if no value exists.  The source of values for entity substitution is local to the kml:AbstractFeatureGroup being styled and any kml:Schema elements associated with it.  Entity syntax for identifying a substitution value is as follows:

1. $[element_or_attribute_name], where “element_or_attribute_name” is the name of a field element or attribute of the kml:AbstractFeatureGroup.  This identifies the value of the field element or attribute.
2. $[name_attribute_of_Data_element], where “name_attribute_of_Data_element” is the value of the kml:name attribute of a descendant kml:Data element of the kml:AbstractFeatureGroup.  This identifies the value of the child kml:value element of the kml:Data element.
3. $[name_attribute_of_Data_element/displayName], where “name_attribute_of_Data_element” is the value of the kml:name attribute of a descendant kml:Data element of the kml:AbstractFeatureGroup; “/” is a separator; and “displayName” is the value of the kml:Data/kml:displayName element.
4. $[TYPENAME/TYPEFIELD], where “TYPENAME” is the value of the kml:name attribute of a descendant kml:Schema element of the kml:AbstractFeatureGroup; “/” is a separator; and “TYPEFIELD” is the value of the kml:name attribute of a child kml:SimpleField element of the kml:Schema element .  This identifies the value of a descendant kml:SimpleData element of the kml:AbstractFeatureGroup that references the kml:SimpleField element.
5. $[TYPENAME/TYPEFIELD/displayName], where “TYPENAME” is the value of the kml:name attribute of a descendant kml:Schema element of the kml:AbstractFeatureGroup; “/” is a separator; and “TYPEFIELD” is the value of the kml:name attribute of a child kml:SimpleField element of the kml:Schema element; and “displayName” is the value of the child kml:displayName element of the kml:SimpleField element.  This identifies the value of the kml:displayName element.

For example, the $[name] and $[description] entities in the following kml:BalloonStyle kml:text element shall be replaced by the kml:name and kml:description values of kml:AbstractFeatureGroup elements associated with the kml:BalloonStyle:

<text>This is $[name], whose description is:<br/>$[description]</text>

6.6       Application Profiles

6.6.1      Introduction

An application profile defines a set of elements derived from one or more base standards for the purpose of:

•   promoting interoperability; and
•   meeting the requirements of a particular application domain.

6.6.2      Rules for Authoring KML Application Profiles

A KML profile can restrict or extend KML to the extent permitted by this standard, see 6.7 (Extension Model). The KML schema provides a number of extension points that may be exploited in a profile. While a profile shall not contradict the standard, it may restrict the choice of options or introduce new elements (or do both).

Documents that conform to the KML standard may contain elements and attributes that are not part of the standard but are defined in an application profile. Such elements and attributes—called foreign information items—must not reside within the KML namespace; they shall be placed in another namespace.

Application profiles shall not redefine any KML components (structurally or semantically) within the KML namespace.

Application profiles which extend KML shall:

•   define the XML structure of any new elements and attributes in an application profile document. If the application profile requires the use of newly created schema components (not including elements and attributes that are reused from a third party schema), the newly created components shall be defined in a valid application profile schema that imports the KML schema;
•   add new elements and/or attributes to existing concrete KML elements according to 6.7.2 Extension by Composition, where permitted by the KML schema;
•   derive any new complex types of complex content in the application profile schema by extension according to 6.7.1Extension by Inheritance; from the relevant KML abstract type whose semantics it shares. If the new complex type does not share semantics with any existing KML abstract type, then derive by extension from kml:AbstractObjectType.
  

                          EXAMPLE: a new feature type shall derive from kml:AbstractFeatureType.

•   declare any new elements and attributes in the application profile schema as optional, i.e. minOccurs=“0”, to support the KML update mechanism.  This however does not preclude asserting minimum occurrence constraints as conformance rules within supplementary normative application profile documentation.

Application profiles that extend KML should:

•   place any newly created extension elements and attributes in a “vendor-neutral” namespace to support any future potential integration with the KML standard, and encourage interoperability in general.

An adopted OGC application profile that extends KML should:

•   be based on a source mass market application profile that is supported by running code;
•   preferably maintain or else deprecate the namespace of a source application profile from which it derives, if/where the source profile is in popular use within the mass market.  This is to ensure backwards compatibility with existing instances and consumers of the source profile;
•   provide a structural and semantic mapping between any profile components which have changed from their original source profile.

Authors of application profiles are encouraged to submit their extensions to OGC for standardization.  This does not preclude any resulting OGC application profile from being merged later into the KML standard.

6.7       Extension Model

The KML schema provides several mechanisms to extend KML within application profiles.  All KML extensions shall conform to the application extension profile requirements discussed in 6.6 Application Profiles.

6.7.1      Extension by Inheritance

The KML schema defines abstract base types (e.g. kml:AbstractFeatureType), concrete types (e.g. kml:PlacemarkType), and abstract elements that act as the head of substitution groups (e.g. kml:AbstractFeatureGroup).  While further derivation of all KML concrete complex types is prohibited, new schema types in a KML Application Profile may be derived from the core abstract base types, listed in 6.1.

6.7.2      Extension by Composition

6.7.2.1     Simple Element Substitution

In a KML Application Profile, a simple element (whose type derives from xsd:anySimpleType) may be declared to substitute for a KML abstract head element that is:

•   of type xsd:anySimpleType. Such abstract head elements have a naming convention whereby their local name ends with “SimpleExtensionGroup” (e.g. kml:AbstractFeatureSimpleExtensionGroup).
•   of type kml:enumBaseType. Such abstract head elements have a naming convention whereby the local name begins with “abstract” (e.g. kml:abstractFlyToMode).

Usage examples:

•   a new element whose type validly derives from xsd:anySimpleType and substitutes for kml:AbstractFeatureSimpleExtensionGroup would be available wherever kml:AbstractFeatureSimpleExtensionGroup is permitted; that is, as a child of kml:Document, kml:Folder, kml:GroundOverlay, kml:ScreenOverlay, kml:PhotoOverlay, kml:Placemark, and kml:NetworkLink.
•   a new element whose type defines new enumeration values by deriving by restriction from kml:enumBaseType and substitutes for kml:abstractFlyToMode would be available wherever kml:abstractFlyToMode is permitted; that is, as a child of kml:FlyTo.

6.7.2.2     Complex Element Substitution

In a KML Application Profile, a complex element may be declared to substitute for a KML abstract head element that is:

•   of a core abstract base type (e.g. kml:AbstractFeatureType).
•   of type xsd:anyType and substitutes for kml:AbstractObjectGroup.  Substituting for such an element requires a type definition that derives from kml:AbstractObjectGroup.  All such head elements have a local name that ends with “ObjectExtensionGroup” (e.g. kml:AbstractFeatureObjectExtensionGroup).
•   of type xsd:anyType and declares no substitution group.  These have a local name that ends with “Extension” (e.g. kml:DataExtension).

Usage examples:

•   a new element whose type derives by extension from kml:AbstractFeatureType and substitutes for kml:AbstractFeatureGroup would be available wherever kml:AbstractFeatureGroup is permitted; that is, as a child of kml:Document, kml:Folder, kml:kml or kml:Delete.
•   a new element whose type derives by extension from kml:AbstractObjectType and substitutes for kml:AbstractFeatureObjectExtensionGroup would be available wherever kml:AbstractFeatureObjectExtensionGroup is permitted; that is, as a child of kml:Document, kml:Folder, kml:GroundOverlay, kml:ScreenOverlay, kml:PhotoOverlay, kml:Placemark, and kml:NetworkLink.
•   a new element whose type is of xsd:anyType and substitutes for kml:DataExtension would be available wherever kml:DataExtension is permitted; that is, as a child of kml:Data.

An example of the creation of new extension elements using complex element substitution is provided in Annex D.1 Extension Model Examples.

6.7.2.3     Foreign Wildcard Elements

KML 2.3 makes use of the new defaultOpenContent element introduced in XML Schema 1.1 to optionally allow for any element content from a foreign namespace. This extension mechanism allows for the direct use of XML element content from third-party schemas. Authors of KML Application Profile extensions are now able to experimentally add foreign element content interleaved among existing KML elements at any location in the KML document tree. Further details and examples of this type of extension-by-composition as applied to KML style element extensions are illustrated in Annex D.2 Extension Model Examples.

6.7.2.4     Foreign Wildcard attributes

KML 2.3 also introduces a new extension point for attributes. Any number of ‘wildcard attributes’ from a foreign namespace, which can be utilized on most KML elements, including all elements whose type ultimately derives from any of the types listed in 6.7.2.4.1. The so-called ‘wildcard attributes’ are realized in XML Schema as an xsd:anyAttribute. declaration as follows:

    <anyAttribute namespace=“##other” processContents=“lax”/>

By setting processContents to ‘lax’, wildcard content can be validated if a schema location is supplied in the instance document (i.e. using xsi:schemaLocation); if the schema location is not supplied then validation of the wildcard attributes will not occur. The xsd:anyAttribute is included by reference from all of the types listed in 6.7.2.4.1. An example of the creation of a new extension attribute is provided in Annex D.3 Extension Model Examples.

6.7.2.4.1    KML types declared with the anyAttribute wildcard attribute

•   kml:AbstractObjectType,
•   kml:vec2Type,
•   kml:ExtendedDataType,
•   kml:SchemaDataType,
•   kml:SimpleDataType,
•   kml:SimpleArrayDataType,
•   kml:DataType,
•   kml:KMLType,
•   kml:NetworkLinkControlType,
•   kml:SchemaType,
•   kml:SimpleFieldType,
•   kml:SimpleArrayFieldType,
•   kml:BoundaryType,
•   kml:UpdateType,
•   kml:CreateType,
•   kml:DeleteType,
•   kml:ChangeType.

7      Root Element

7.1       kml

7.1.1      Structure

<kml:kml
 hint=“string [0..1]”
 version=“kml:kmlVersionType [0..1]”
  anyAttribute=“anySimpleType [0..1]”>
    <kml:NetworkLinkControl>…</kml:NetworkLinkControl> [0..1]
    <kml:AbstractFeatureGroup>…</kml:AbstractFeatureGroup> [0..1]
    <kml:KmlSimpleExtensionGroup>…</kml:KmlSimpleExtensionGroup> [0..*]
    <kml:KmlObjectExtensionGroup>…</kml:KmlObjectExtensionGroup> [0..*]
</kml:kml>

7.1.2      Description

The root element of a KML document instance.  It should contain at least one of its child elements.

7.1.3      Content

     kml:NetworkLinkControl

See 13.4 kml:NetworkLinkControl.

     kml:AbstractFeatureGroup

See 9.1 kml:AbstractFeatureGroup.

     kml:KmlSimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

     kml:KmlObjectExtensionGroup

See 6.7.2.2 Complex Element Substitution.

7.1.4      Attributes

     hint

    Description

The hint attribute may be used to provide information on how to process the KML document instance.

    Content

     version

    Description

The version attribute declares which version of the schema the KML instance conforms to.

    Content

     anyAttribute

    Description

The anyAttribute declaration provides a new extension point in KML 2.3, which allows any number of ‘wildcard attributes’ from a foreign namespace (see 6.7.2.4 Foreign Wildcard attributes).

    Content

7.1.5      Assertions

If any of the following descendent elements (or element/attribute combinations) are present then the attribute version value shall be ‘2.3.0’ or later:

•   kml:altitudeOffset
•   kml:balloonVisibility
•   kml:Camera/kml:TimeStamp
•   kml:Camera/kml:TimeSpan
•   kml:Camera/kml:horizFov
•   kml:Create/kml:MultiGeometry
•   kml:Data/@uom
•   kml:Delete/kml:MultiGeometry
•   kml:Delete/kml:Point
•   kml:Delete/kml:LineString
•   kml:Delete/kml:LinearRing
•   kml:Delete/kml:Polygon
•   kml:Delete/kml:Model
•   kml:LatLonQuad
•   kml:LookAt/kml:TimeStamp
•   kml:LookAt/kml:TimeSpan
•   kml:LookAt/kml:horizFov
•   kml:MultiTrack
•   kml:seaFloorAltitudeMode
•   kml:SimpleArrayField
•   kml:SimpleField/@uom
•   kml:Tour
•   kml:Track

7.1.6      Example

<kml xmlns=“http://www.opengis.net/kml/2.2” version=“2.3.0”>
  <NetworkLinkControl>…</NetworkLinkControl>
  <Document>…</Document>
</kml>

8.      Object

8.1       kml:AbstractObjectGroup

8.1.1      Structure

<kml:AbstractObjectGroup
 id=“ID [0..1]”
 targetId=“NCName [0..1]”
 anyAttribute=“anySimpleType [0..1]”>
    <kml:ObjectSimpleExtensionGroup>…</kml:ObjectSimpleExtensionGroup> [0..*]
</kml:AbstractObjectGroup>

8.1.2      Description

The following elements can be used wherever this abstract element is referenced:

8.1.3      Content

     kml:ObjectSimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

8.1.4      Attributes

     id

    Description

The id attribute may be used to specify a unique identifier for the kml:AbstractObjectGroup within the KML document instance.

If an element affiliated with kml:AbstractObjectGroup is not being updated (that is, it is not a descendant of kml:Update) and it is empty then it shall have an id attribute; otherwise it cannot be updated. An object that is not empty should have an identifier to permit future updates.

    Content

     targetId

    Description

The optional targetId attribute may be used to encode the id value of another kml:AbstractObjectGroup.

If a kml:AbstractObjectGroup is being used for update purposes (is a grandchild of kml:Update) then it shall have a targetId attribute referencing the kml:AbstractObjectGroup element to be updated.  Otherwise, outside of an update context targetId has no meaning.

See also 13.5 kml:Update.

    Content

     anyAttribute

See 7.1.4.3 anyAttribute.

9.      Features

9.1       kml:AbstractFeatureGroup

9.1.1      Structure

<kml:AbstractFeatureGroup
 id=“ID [0..1]”
 targetId=“NCName [0..1]”
 anyAttribute=“anySimpleType [0..1]”>
    <kml:ObjectSimpleExtensionGroup>…</kml:ObjectSimpleExtensionGroup> [0..*]
    <kml:name>…</kml:name> [0..1]
    <kml:visibility>…</kml:visibility> [0..1]
    <kml:balloonVisibility>…</kml:balloonVisibility> [0..1]
     <kml:open>…</kml:open> [0..1]
    <atom:author>…</atom:author> [0..1]
    <atom:link>…</atom:link> [0..1]
    <kml:address>…</kml:address> [0..1]
    <xal:AddressDetails>…</xal:AddressDetails> [0..1]
    <kml:phoneNumber>…</kml:phoneNumber> [0..1]
    <kml:snippet>…</kml:snippet> [0..1]
    <kml:description>…</kml:description> [0..1]
    <kml:AbstractViewGroup>…</kml:AbstractViewGroup> [0..1]
    <kml:AbstractTimePrimitiveGroup>…</kml:AbstractTimePrimitiveGroup> [0..1]
    <kml:styleUrl>…</kml:styleUrl> [0..1]
    <kml:AbstractStyleSelectorGroup>…</kml:AbstractStyleSelectorGroup> [0..*]
    <kml:Region>…</kml:Region> [0..1]
    <kml:AbstractExtendedDataGroup>…</kml:AbstractExtendedDataGroup> [0..1]
    <kml:AbstractFeatureSimpleExtensionGroup>…
     </kml:AbstractFeatureSimpleExtensionGroup> [0..*]      
    <kml:AbstractFeatureObjectExtensionGroup>… 
     </kml:AbstractFeatureObjectExtensionGroup> [0..*]
</kml:AbstractFeatureGroup>

9.1.2      Description

This abstract element can be used wherever the following element is referenced:

The following elements can be used wherever this abstract element is referenced:

9.1.3      Content

     kml:name

    Description

Specifies a label for the kml:AbstractFeatureGroup.

    Content

     kml:visibility

    Description

Specifies whether the kml:AbstractFeatureGroup shall be drawn in the geographic view when it is initially loaded (1 or true), or not (0 or false).  In order for a kml:AbstractFeatureGroup to be visible, the kml:visibility tag of all its ancestors shall also be set to 1 or true.

    Content

     kml:balloonVisibility

    Description

Specifies whether the description balloon is opened when loaded or updated.

    Content

     kml:open

    Description

Specifies whether a kml:AbstractContainerGroup appears expanded (1 or true) or collapsed (0 or false) when first loaded into the list view.

See also 12.17 kml:ListStyle.

    Content

     atom:author

    Description

Specifies the author of the kml:AbstractFeatureGroup. See also 9.8 kml:AbstractContainerGroup regarding the inheritance of atom:author within KML feature hierarchies.

    Content

See IETF RFC 4287, 4.2.1.

     atom:link

    Description

Specifies the URL of the source resource that contains the kml:AbstractFeatureGroup.  The URL is encoded as the value of the atom:href attribute.

The atom:link rel attribute shall be present and its value should be related. See also 9.8 kml:AbstractContainerGroup regarding the inheritance of the atom:link within KML feature hierarchies.

    Content

See IETF RFC 4287, 4.2.7.

     kml:address

    Description

A string value representing an unstructured address for the kml:AbstractFeatureGroup such as street, city, state address, and/or a postal code.  This may be used to geocode the location of a kml:AbstractFeatureGroup if it does not contain a kml:AbstractGeometryGroup element.

    Content

     xal:AddressDetails

    Description

A structured address for the kml:AbstractFeatureGroup formatted according to xAL 2.0.  This may be used to geocode the location of a kml:AbstractFeatureGroup if it does not contain a kml:AbstractGeometryGroup element.

    Content

See OASIS Extensible Address Language (XAL) 2.0.

     kml:phoneNumber

    Description

A value representing a telephone number.  The number should be formatted according to IETF RFC 3966.

    Content

    kml:snippet

    Description

Specifies a short description of the kml:AbstractFeatureGroup.  The value of kml:snippet, if present, is used in the list view instead of kml:description.

The text may include HTML content that is encoded as well-formed XML using HTML entity references or by enclosing the HTML within a CDATA section.

The element kml:snippet replaces the deprecated element kml:Snippet, however kml:Snippet may likely be supported by KML software implementations for an indeterminate period of time.

    Content

    kml:description

    Description

Specifies a description of the kml:AbstractFeatureGroup.  This should be displayed in the description balloon.

The text may include HTML content that is encoded as well-formed XML using HTML entity references or by enclosing the HTML within a CDATA section.

If the description includes the HTML <a href=“…” type=“…”> tag, it should have an HTML href and type attribute and be interpreted as follows:

•   The href attribute specifies a URL.
•   If the target of the href is a KML resource, an earth browser should load the resource if the link is activated.

The href may reference another kml:AbstractFeatureGroup if its value is the fragment component of a URL (see 12.13.3.1).  If such a link is activated the geographic view should fly to the kml:AbstractFeatureGroup whose ID matches the fragment.  If this kml:AbstractFeatureGroup has a kml:LookAt or kml:Camera element, it shall be viewed from the specified viewpoint.

Special processing is required for embedded HTML links that append a display directive to the fragment component of the URL; such a directive (e.g. “;flyto”) must be removed from the fragment component in order to obtain the shorthand pointer.  Available directives are:

•   ;flyto (default) – fly to the kml:AbstractFeatureGroup
•   ;balloon – open the kml:AbstractFeatureGroup’s balloon but do not fly to the kml:AbstractFeatureGroup
•   ;balloonFlyto – open the kml:AbstractFeatureGroup’s balloon and fly to the kml:AbstractFeatureGroup

For example, the following code indicates to open the resource CraftsFairs.kml resource, fly to the kml:Placemark whose ID is “Albuquerque,” and open its balloon:

<description>
  <a href=“http://myServer.com/CraftsFairs.kml#Albuquerque;balloonFlyto”>
      One of the Best Art Shows in the West</a>
</description>

The type attribute specifies the MIME type for the target resource.  An earth browser should interpret the target resource according to this specified MIME type when attempting to load it.  To indicate that the target resource is KML specify the following MIME type:

type=“application/vnd.google-earth.kml+xml”

To indicate that the target resource is a KMZ archive specify the following MIME type:

type=“application/vnd.google-earth.kmz”

For example, the type attribute below indicates that an earth browser should attempt to load the target as a KML resource even though the file extension is .php:

<a href=“myserver.com/cgi-bin/generate-kml.php#placemark123”
   type=“application/vnd.google-earth.kml+xml”

    Content

    kml:AbstractViewGroup

An abstract placeholder for a viewpoint (kml:Camera or kml:LookAt).

See 14.1 AbstractViewGroup.

    kml:AbstractTimePrimitiveGroup

An abstract placeholder for a time primitive (kml:TimeStamp or kml:TimeSpan).

See 15.1 kml:AbstractTimePrimitiveGroup.

    kml:styleURL

    Description

Specifies a reference to a kml:Style or kml:StyleMap.  The reference shall be encoded as a URL with a fragment component (see 12.13.3.1).  The value of the fragment shall be the id of a kml:Style or kml:StyleMap defined in a kml:Document.

See also 12.2 kml:Style; 12.3 kml:StyleMap, and 6.4 Shared Styles.

    Content

    Example

To reference a kml:Style or kml:StyleMap in the same document:

<styleUrl>#myIconStyleID</styleUrl>

To reference a kml:Style or kml:StyleMap in a hosted document:

<styleUrl>http://someserver.com/somestylefile.xml#restaurant</styleUrl>

    kml:AbstractStyleSelectorGroup

One or more kml:Styles or kml:StyleMaps used to style the kml:Feature.

See also 12.1 kml:AbstractStyleSelectorGroup and 6.4 Shared Styles.

    kml:Region

Affects the visibility of the kml:AbstractFeatureGroup .

See 9.16 kml:Region.

    kml:AbstractExtendedDataGroup

Allows for the addition of user-defined data.

See 9.2 kml:AbstractExtendedDataGroup.

    kml:AbstractFeatureSimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

    kml:AbstractFeatureObjectExtensionGroup

See 6.7.2.2 Complex Element Substitution.

9.1.4      Examples

     Sample Use of HTML Elements within a Description

<kml xmlns=“http://www.opengis.net/kml/2.2”>
<Placemark>
  <name>Feature.kml</name>
  <snippet>
    The snippet is a way ofproviding an alternative
    description that will beshown in the List view.
  </snippet>
  <description>
    <![CDATA[
      Styles: <i>Italics</i>, <b>Bold</b>, <u>Underlined</u>,
      <s>Strike Out</s>, subscript<sub>subscript</sub>,
      superscript<sup>superscript</sup>, 
      <big>Big</big>, <small>Small</small>, <tt>Typewriter</tt>,
      <em>Emphasized</em>, <strong>Strong</strong>, <code>Code</code>
      <hr />
      Fonts:
      <font color=“red”>red by name</font>,
      <font color=“#408010”>leaf green by hexadecimal RGB</font>,
      <font size=1>size 1</font>, <font size=2>size 2</font>,
      <font size=3>size 3</font>, <font size=4>size 4</font>,
      <font size=5>size 5</font>, <font size=6>size 6</font>,
      <font size=7>size 7</font>,
      <font face=times>Times</font>,
      <font face=verdana>Verdana</font>,
      <font face=arial>Arial</font>
      <br/>
      <hr />
      Links:
      <a href=“http://doc.trolltech.com/3.3/qstylesheet.html”>
      QT Rich Text Rendering
      </a>
      <br />
      <hr />
      Alignment:
      <br />
      <p align=left>left</p><p align=center>center</p>
      <p align=right>right</p>
      <hr />
      Ordered Lists:
      <br />
      <ol><li>First</li><li>Second</li><li>Third</li></ol>
      <ol type=“a”><li>First</li><li>Second</li><li>Third</li></ol>
      <ol type=“A”><li>First</li><li>Second</li><li>Third</li></ol>
      <hr />
      Unordered Lists:
      <br />
      <ul><li>A</li><li>B</li><li>C</li></ul>
      <ul type=“circle”><li>A</li><li>B</li><li>C</li></ul>
      <ul type=“square”><li>A</li><li>B</li><li>C</li></ul>
      <hr />
      Definitions:
      <br />
      <dl>
      <dt>Scrumpy</dt>
      <dd>Hard English cider from the west country</dd>
      <dt>Pentanque</dt>
      <dd>A form of boules where the goal is to throw a metal ball as
      close as possible to a jack</dd>
      </dl>
      <hr />
      Block Quote:
      <br />
      <blockquote>
      We shall not cease from exploration<br />
      And the end of all our exploring<br />
      Will be to arrive where we started<br />
      And know the place for the first time
      </blockquote>
      <br />
      <hr />
      Centered:
      <br />
      <center>See, I have a Rhyme assisting<br />
      my feeble brain,<br />
      its tasks oft-times resisting!</center>
      <hr />
      Headings:
      <br />
      <h1>Header 1</h1>
      <h2>Header 2</h2>
      <h3>Header 3</h3>
      <h3>Header 4</h4>
      <h3>Header 5</h5>
      <hr />
      Images:
      <br />
      <img src=“http://www.opengis.net/images/googleearth.gif” />
      <br />
      <i>Scaled image</i>
      <br />
      <img src=“http://www.opengis.net/images/googleearth.gif”
      width=“100” />
      <br />
      <hr />
      Tables:
      <table border=“1” padding=“3” width=“300”>
      <tr><td>1</td><td>2</td><td>3</td><td>4</td><td>5</td></tr>
      <tr><td>a</td><td>b</td><td>c</td><td>d</td><td>e</td></tr>
      </table>
    ]]>
  </description>
  <Point>
    <coordinates>-122.378927,37.826793,0</coordinates>
  </Point>
</Placemark>
</kml>

     Sample Use of Atom Elements

This example shows use of the atom:author, atom:name and atom:link attribution elements from the Atom namespace.  In this case, atom:author and atom:link apply to both kml:Placemarks.

<kml xmlns=“http://www.opengis.net/kml/2.2”
     xmlns:atom=“http://www.w3.org/2005/Atom”>
  <Document>
    <atom:author>
      <atom:name>J. K. Rowling</atom:name>
    </atom:author>
    <atom:link href=“http://www.harrypotter.com” />
    <Placemark>
      <name>Hogwarts</name>
      <Point>
        <coordinates>1,1</coordinates>
      </Point>
    </Placemark>
    <Placemark>
      <name>Little Hangleton</name>
      <Point>
        <coordinates>1,2</coordinates>
      </Point>
    </Placemark>
  </Document>
</kml>

9.2       kml:AbstractExtendedDataGroup

9.2.1      Structure

<kml:AbstractExtendedDataGroup>…</kml:AbstractExtendedDataGroup>

9.2.2      Description

The following elements can be used wherever this abstract element is referenced:

kml:AbstractExtendedDataGroup is an abstract substitution head element that allows for the addition of user-defined data. Note that the kml:Metadata element was deprecated in KML 2.2, use kml:ExtendedData instead.

See also 9.3 kml:ExtendedData and 6.7.2.2 Complex Element Substitution.

9.2.3      Content

9.3       kml:ExtendedData

9.3.1      Structure

<kml:ExtendedData
 anyAttribute=“anySimpleType [0..1]”>
    <kml:Data>…</kml:Data> [0..*]
    <kml:SchemaData>…</kml:SchemaData> [0..*]
    <xsd:any/> (any element from foreign namespace with lax validation) [0..*]
</kml:ExtendedData>

9.3.2      Description

The kml:ExtendedData element offers three mechanisms for adding user-defined data to a kml:AbstractFeatureGroup.  These mechanisms are:

•   Adding arbitrary name/value data pairs using the kml:Data element (optionally typed using an xsi:type attribute)
•   Adding instances of typed fields defined in the user-defined kml:Schema element
•   Including any XML content defined in namespaces other than the KML namespace and null namespace

These mechanisms can be used concurrently within a single kml:AbstractFeatureGroup or KML document.

Child elements of kml:ExtendedData support entity substitution.  See 6.5 Entity Replacement.

kml:ExtendedData should contain at least one child element outside of an update context, that is when not a descendant of kml:Update.

9.3.3      Content

     kml:Data

An name/value pair with an optional typing mechanism (xsi:type attribute).

See 9.4 kml:Data.

     kml:SchemaData

Encodes an instance of a user-defined data type defined by a referenced kml:Schema

See 9.5 kml:SchemaData.

     xsd:any

    Description

kml:ExtendedData may include any other well-formed, namespace-qualified XML content that is not from the KML namespace "http://www.opengis.net/kml/2.2"

    Content

    Example

The following example demonstrates the encoding of XML content from the "http://www.example.org/app" namespace:

<kml
  xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”
  xmlns=“http://www.opengis.net/kml/2.2”
  xmlns:app=“http://www.example.org/app”
  xmlns:gml=“http://www.opengis.net/gml”>
  <Placemark>
    <name>A road</name>
    <ExtendedData>
      <app:Road>
        <app:numberOfLanes>2</app:numberOfLanes>
        <app:pavement>gravel</app:pavement>
      </app:Road>
    </ExtendedData>
  </Placemark>
</kml>

9.3.4      Attributes

     anyAttribute

See 7.1.4.3 anyAttribute.

9.4       kml:Data

9.4.1      Structure

<kml:Data
 id=“ID [0..1]”
 targetId=“NCName [0..1]”
 anyAttribute=“anySimpleType [0..1]”
 name=“string [0..1]”
 uom=“anyURI [0..1]”>
    <kml:ObjectSimpleExtensionGroup>…</kml:ObjectSimpleExtensionGroup> [0..*]
    <kml:displayName>…</kml:displayName> [0..1]
    <kml:value>…</kml:value> [1]
    <kml:DataExtension>…</kml:DataExtension> [0..*]
</kml:Data>

9.4.2      Description

This element can be used wherever the following element is referenced:

Creates a name/value data pair, where:

•   The data pair is identified by the name attribute
•   The value of the data pair is supplied by kml:value

Both name and kml:value should be encoded.  The value of the name attribute shall be unique within the context of its parent kml:ExtendedData element. Since kml:value has the simple ur-type (xsd:anySimpleType), an xsi:type attribute can be provided on kml:value, to specify a simple datatype. If the xsi:type attribute is present, its value shall be a primitive XML Schema datatype; an XML Schema validator would then be able to enforce that kml:value is consistent with the datatype specified in the xsi:type attribute.

9.4.3      Content

     kml:displayName

    Description

An alternate display name.

    Content

     kml:value

    Description

Value of the data pair.

    Content

     kml:DataExtension

See 6.7.2.2 Complex Element Substitution.

9.4.4      Attributes

     name

    Description

Name of the data pair.

    Content

     uom

    Description

The uom attribute indicates the unit of measure for some measured quantity. If the value is not an absolute URI (that refers to a definition, e.g. ‘http://www.bipm.org/en/publications/si-brochure/metre.html’), it is expected to be a case-sensitive unit symbol (e.g. ‘m’ for meters, ‘s’ for seconds, ‘deg’ for degrees, ‘yd_us’ for US yards) appearing in the Unified Code for Units of Measure (http://unitsofmeasure.org/ucum.html).

    Content

9.4.5      Example

In the following example, an xsi:type attribute is added to two of the kml:value elements and a uom attribute is added to one of the kml:Data elements.

<Placemark>
  <name>Club house</name>
  <ExtendedData>
    <Data name=“holeNumber”>
      <value>1</value>
    </Data>
    <Data name=“holeYardage” uom=“yd_us”>
      <value xsi:type=“xsd:double”>234</value>
    </Data>
    <Data name=“holePar”>
      <value xsi:type=“xsd:positiveInteger”>4</value>
    </Data>
  </ExtendedData>
</Placemark>

9.5       kml:SchemaData

9.5.1      Structure

<kml:SchemaData
 id=“ID [0..1]”
 targetId=“NCName [0..1]”
 anyAttribute=“anySimpleType [0..1]”
 schemaUrl=“anyURI [0..1]”>
    <kml:ObjectSimpleExtensionGroup>…</kml:ObjectSimpleExtensionGroup> [0..*]
    <kml:SimpleData>…</kml:SimpleData> [0..*]
    <kml:SimpleArrayData>…</kml:SimpleArrayData> [0..*]
    <kml:SchemaDataExtension>…</kml:SchemaDataExtension> [0..*]
</kml:SchemaData>

i9.5.2      Description

This element can be used wherever the following element is referenced:

Encodes an instance of a user-defined data type defined by a referenced kml:Schema.

A kml:SchemaData element shall reference a kml:Schema element using the kml:schemaUrl attribute.

9.5.3      Content

     kml:SimpleData

See 9.6 kml:SimpleData.

     kml:SimpleArrayData

See 9.7 kml:SimpleArrayData.

     kml:SchemaDataExtension

See 6.7.2.2 Complex Element Substitution.

9.5.4      Attributes

     schemaUrl

    Description

The value of kml:schemaURL should either be: a full URL, a reference to a kml:Schema id attribute defined in an external KML resource; or a reference to a kml:Schema id defined in the same KML resource.

    Content

    Examples

All of the following URI values are acceptable:

schemaUrl=“http://host.com/PlacesIHaveLived.kml#my-schema-id”

schemaUrl=“AnotherFile.kml#my-schema-id”

schemaUrl=“#schema-id”   <!– same KML document –>

9.6       kml:SimpleData

9.6.1      Structure

<kml:SimpleData
 name=“string [1]”
 anyAttribute=“anySimpleType [0..1]”>
    anySimpleType
</kml:SimpleData>

9.6.2      Description

Encodes an instance of a user-defined field defined by a referenced kml:SimpleField.

The value of kml:SimpleData shall be of the data type specified in the type attribute of the referenced kml:SimpleField ; the enforcement of this rule is possible, but not so simple using XML Schema validation. Methods for automated datatype consistency enforcement for kml:SimpleData values using both Schematron and XML Schema validation are discussed in([10], 8.2 Validate kml:SimpleData for Datatype Consistency),. kml:SimpleData is of complex type that extends from the simple ur-type xsd:anySimpleType, so an xsi:type attribute could optionally be provided to enable datatype enforcement using XML Schema validation. However, unlike the case of kml:value,  the valid values of  the xsi:type attribute would not be simple datatypes, rather they would be complex types that must be validly derived from kml:SimpleDataType (in a schema type definition outside the KML namespace.)

The required name attribute shall be used to identify the kml:SimpleField by name.  The identified kml:SimpleField shall be declared within the kml:Schema element that is referenced from the kml:SchemaURL attribute.

9.6.3      Content

9.6.4      Attributes

     name

    Description

A name value  reference to the corresponding kml:SimpleField. See 9.11.4.2 name.

    Content

     anyAttribute

See 7.1.4.3 anyAttribute.

9.6.5      Example

User-defined data elements are shown in the following example:

<kml xmlns=“http://earth.google.com/kml/2.2”>
  <Document>
    <name>ExtendedData+SchemaData</name>
    <open>1</open>
    <!– Create a balloon template referring to the user-defined type –>
    <Style id=“trailhead-balloon-template”>
      <BalloonStyle>
        <text>
          <![CDATA[
            <h2>My favorite trails!</h2>
            <br/><br/>
            The $[TrailHeadType/TrailHeadName/displayName] is <i>$[TrailHeadType/TrailHeadName]</i>.
            The trail is $[TrailHeadType/TrailLength] miles.<br/>
            The climb is $[TrailHeadType/ElevationGain] meters.<br/><br/>
          ]]>
        </text>
      </BalloonStyle>
    </Style>
 
    <!– Declare the type “TrailHeadType” with 3 fields –>
    <Schema name=“TrailHeadType” id=“TrailHeadTypeId”>
      <SimpleField type=“string” name=“TrailHeadName”>
        <displayName><![CDATA[<b>Trail Head Name</b>]]></displayName>
      </SimpleField>
      <SimpleField type=“double” name=“TrailLength”>
        <displayName><![CDATA[<i>The length in miles</i>]]></displayName>
      </SimpleField>
      <SimpleField type=“int” name=“ElevationGain”>
        <displayName><![CDATA[<i>change in altitude</i>]]></displayName>
      </SimpleField>
    </Schema>
 
 
    <!– Instantiate some Placemarks extended with TrailHeadType fields –>
    <Placemark>
      <name>Easy trail</name>
      <styleUrl>#trailhead-balloon-template</styleUrl>
      <ExtendedData>
        <SchemaData schemaUrl=“#TrailHeadTypeId”>
          <SimpleData name=“TrailHeadName”>Pi in the sky</SimpleData>
          <SimpleData name=“TrailLength”>3.14159</SimpleData>
          <SimpleData name=“ElevationGain”>10</SimpleData>
        </SchemaData>
      </ExtendedData>
      <Point>
        <coordinates>-122.000,37.002</coordinates>
      </Point>
    </Placemark>
    <Placemark>
      <name>Difficult trail</name>
      <styleUrl>#trailhead-balloon-template</styleUrl>
      <ExtendedData>
        <SchemaData schemaUrl=“#TrailHeadTypeId”>
          <SimpleData name=“TrailHeadName”>Mount Everest</SimpleData>
          <SimpleData name=“TrailLength”>347.45</SimpleData>
          <SimpleData name=“ElevationGain”>10000</SimpleData>
        </SchemaData>
      </ExtendedData>
      <Point>
        <coordinates>-121.998,37.0078</coordinates>
      </Point>
    </Placemark>
  </Document>
</kml>

9.7       kml:SimpleArrayData

9.7.1      Structure

<kml:SimpleArrayData
 id=“ID [0..1]”
 targetId=“NCName [0..1]”
 anyAttribute=“anySimpleType [0..1]”
 name=“string [1]”>
     <kml:ObjectSimpleExtensionGroup>…</kml:ObjectSimpleExtensionGroup> [0..*] 
     <kml:value>…</kml:value> [0..*]
     <kml:SimpleArrayDataExtension>…</kml:SimpleArrayDataExtension> [0..*] 
</kml:SimpleArrayData>

9.7.2      Description

Encodes an instance of a user-defined data array defined by a referenced kml:SimpleArrayField.

The kml:value children of kml:SimpleArrayData shall each be of the data type specified in the type attribute of the referenced kml:SimpleArrayField.

The required name attribute shall be used to identify the kml:SimpleArrayField by name.  The identified kml:SimpleArrayField shall be declared within the kml:Schema element that is referenced from the kml:SchemaURL attribute.

9.7.3      Content

     kml:value

See 9.4.3.2 kml:value.

     kml:SimpleArrayDataExtension

See 6.7.2.2 Complex Element Substitution.

9.7.4      Attributes

     name

    Description

A name value  reference to the corresponding kml:SimpleArrayField. See 9.12.4.2 name.

    Content

     anyAttribute

See 7.1.4.3 anyAttribute.

9.7.5      Example

See 10.15.4.2 Example 2 – Extended Data Arrays for an example in the context of kml:Track.

9.8       kml:AbstractContainerGroup

9.8.1      Structure

<kml:AbstractContainerGroup
 id=“ID [0..1]”
 targetId=“NCName [0..1]”
 anyAttribute=“anySimpleType [0..1]”>
    <kml:ObjectSimpleExtensionGroup>…</kml:ObjectSimpleExtensionGroup> [0..*]
    <kml:name>…</kml:name> [0..1]
    <kml:visibility>…</kml:visibility> [0..1]
    <kml:balloonVisibility>…</kml:balloonVisibility> [0..1]
    <kml:open>…</kml:open> [0..1]
    <atom:author>…</atom:author> [0..1]
    <atom:link>…</atom:link> [0..1]
    <kml:address>…</kml:address> [0..1]
    <xal:AddressDetails>…</xal:AddressDetails> [0..1]
    <kml:phoneNumber>…</kml:phoneNumber> [0..1]
    <kml:snippet>…</kml:snippet> [0..1]
    <kml:description>…</kml:description> [0..1]
    <kml:AbstractViewGroup>…</kml:AbstractViewGroup> [0..1]
    <kml:AbstractTimePrimitiveGroup>…</kml:AbstractTimePrimitiveGroup> [0..1]
    <kml:styleUrl>…</kml:styleUrl> [0..1]
    <kml:AbstractStyleSelectorGroup>…</kml:AbstractStyleSelectorGroup> [0..*]
    <kml:Region>…</kml:Region> [0..1]
    <kml:AbstractExtendedDataGroup>…</kml: AbstractExtendedDataGroup> [0..1]
    <kml:AbstractFeatureSimpleExtensionGroup>… 
     </kml:AbstractFeatureSimpleExtensionGroup> [0..*]
    <kml:AbstractFeatureObjectExtensionGroup>… 
     </kml:AbstractFeatureObjectExtensionGroup> [0..*]
    <kml:AbstractContainerSimpleExtensionGroup>…
     </kml:AbstractContainerSimpleExtensionGroup> [0..*]
    <kml:AbstractContainerObjectExtensionGroup>…
     </kml:AbstractContainerObjectExtensionGroup> [0..*]
</kml:AbstractContainerGroup>

9.8.2      Description

This abstract element can be used wherever the following element is referenced:

The following elements can be used wherever this abstract element is referenced:

For convenience in constructing KML feature hierarchies, unless overruled by the presence of such elements locally, the value of the following kml:AbstractFeatureGroup elements shall be inherited by all kml:AbstractFeatureGroup members of a feature hierarchy:

•   atom:author
•   atom:link
•   kml:Region
•   kml:AbstractTimePrimitiveGroup

Thus it is not necessary for a child kml:AbstractFeatureGroup to carry any of these elements where their local value is the same as that of its parent kml:Document or kml:Folder.  Inheritance of these elements continues to any depth of nesting, but if overruled by a local declaration, then the new value is inherited by all its children in turn.  Notwithstanding this rule, such elements may be used locally even if they have the same value as that of a parent kml:Document or kml:Folder.

9.8.3      Content

     kml:AbstractContainerSimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

     kml:AbstractContainerObjectExtensionGroup

See 6.7.2.2 Complex Element Substitution.

9.9       kml:Document

9.9.1      Structure

<kml:Document
 id=“ID [0..1]”
 targetId=“NCName [0..1]”
 anyAttribute=“anySimpleType [0..1]”>
    <kml:ObjectSimpleExtensionGroup>…</kml:ObjectSimpleExtensionGroup> [0..*]
    <kml:name>…</kml:name> [0..1]
    <kml:visibility>…</kml:visibility> [0..1]
    <kml:balloonVisibility>…</kml:balloonVisibility> [0..1]
    <kml:open>…</kml:open> [0..1]
    <atom:author>…</atom:author> [0..1]
    <atom:link>…</atom:link> [0..1]
    <kml:address>…</kml:address> [0..1]
    <xal:AddressDetails>…</xal:AddressDetails> [0..1]
    <kml:phoneNumber>…</kml:phoneNumber> [0..1]
    <kml:snippet>…</kml:snippet> [0..1]
    <kml:description>…</kml:description> [0..1]
    <kml:AbstractViewGroup>…</kml:AbstractViewGroup> [0..1]
    <kml:AbstractTimePrimitiveGroup>…</kml:AbstractTimePrimitiveGroup> [0..1]
    <kml:styleUrl>…</kml:styleUrl> [0..1]
    <kml:AbstractStyleSelectorGroup>…</kml:AbstractStyleSelectorGroup> [0..*]
    <kml:Region>…</kml:Region> [0..1]
    <kml:AbstractExtendedDataGroup>…</kml: AbstractExtendedDataGroup> [0..1]
    <kml:AbstractFeatureSimpleExtensionGroup>…
     </kml:AbstractFeatureSimpleExtensionGroup> [0..*]
    <kml:AbstractFeatureObjectExtensionGroup>…
     </kml:AbstractFeatureObjectExtensionGroup> [0..*]
    <kml:AbstractContainerSimpleExtensionGroup>…
     </kml:AbstractContainerSimpleExtensionGroup> [0..*]
    <kml:AbstractContainerObjectExtensionGroup>…
     </kml:AbstractContainerObjectExtensionGroup> [0..*]
    <kml:Schema>…</kml:Schema> [0..*]
    <kml:AbstractFeatureGroup>…</kml:AbstractFeatureGroup> [0..*]
    <kml:DocumentSimpleExtensionGroup>…</kml:DocumentSimpleExtensionGroup> [0..*]
    <kml:DocumentObjectExtensionGroup>…</kml:DocumentObjectExtensionGroup> [0..*]
</kml:Document>

9.9.2      Description

This element can be used wherever the following element is referenced:

A kml:Document is a container for KML features, shared styles, and user-defined schemas. 

See also 6.4 Shared Styles.

9.9.3      Content

     kml:Schema

Specifies a user-defined schema.

See 9.10 kml:Schema.

     kml:AbstractFeatureGroup

See 9.1 kml:AbstractFeatureGroup.

     kml:DocumentSimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

     kml:DocumentObjectExtensionGroup

See 6.7.2.2 Complex Element Substitution.

9.10    kml:Schema

9.10.1    Structure

<kml:Schema
 name=“string [0..1]”
 id=“ID [0..1]”
 anyAttribute=“anySimpleType [0..1]”>
    <kml:SimpleField>…</kml:SimpleField> [0..*]
    <kml:SimpleArrayField>…</kml:SimpleArrayField> [0..*]
    <kml:SchemaExtension>…</kml:SchemaExtension> [0..*]
</kml:Schema>

9.10.2    Description

Specifies a user-defined schema that is used to add user-defined data encoded within a child kml:ExtendedData element of a kml:AbstractFeatureGroup.  kml:Schema shall have an id so that instances of it (encoded as kml:SchemaData) may reference it.

9.10.3    Content

    kml:SimpleField

See 9.11 kml:SimpleField.

    kml:SimpleArrayField

See 9.12 kml:SimpleArrayField.

    kml:SchemaExtension

See 6.7.2.2 Complex Element Substitution.

9.10.4    Attributes

    id

    Description

Unique identifier of the kml:AbstractObjectGroup within the KML document instance.

    Content

    name

See 9.6.4.1 name.

    anyAttribute

See 7.1.4.3 anyAttribute.

9.10.5    Example

<kml xmlns=“http://www.opengis.net/kml/2.2”>
<Document>
  <Schema name=“TrailHeadType” id=“TrailHeadTypeId”>         
    <SimpleField type=“string” name=“TrailHeadName”>      
      <displayName><![CDATA[<b>Trail Head Name</b>]]></displayName>    
    </SimpleField>    
    <SimpleField type=“double” name=“TrailLength”>      
      <displayName><![CDATA[<i>The length in miles</i>]]></displayName>    
    </SimpleField>     <SimpleField type=“int” name=“ElevationGain”>      
      <displayName><![CDATA[<i>change in altitude</i>]]></displayName>    
    </SimpleField>  
  </Schema>
</Document>
</kml>

9.11    kml:SimpleField

9.11.1    Structure

<kml:SimpleField
 type=“string [0..1]”
 name=“string [0..1]”
 uom=“anyURI [0..1]”
 anyAttribute=“anySimpleType [0..1]”>
    <kml:displayName>…</kml:displayName> [0..1]
    <kml:SimpleFieldExtension>…</kml:SimpleFieldExtension> [0..*]
</kml:SimpleField>

9.11.2    Description

Specifies a user-defined data field.  The name and type attributes shall be specified. The main purpose of kml:SimpleField is to enable KML implementations to efficiently store a data value in memory as a specified data type (e.g. storing an integer value as an integer datatype rather than a string representation of the integer). The datatype information encoded in the type attribute of kml:SimpleField can also be used to enable automated datatype consistency checking between the type attribute and a corresponding kml:SimpleData value. For example, a Schematron assertion can provide such a datatype consistency check as discussed in ([10], 8.2 Validate kml:SimpleData for Datatype Consistency).

9.11.3    Content

    kml:displayName

See 12.8 kml:displayName.

    kml:SimpleFieldExtension

See 6.7.2.2 Complex Element Substitution.

9.11.4    Attributes

    type

    Description

Type of the field.  The type content shall specify a qualified name of an XML Schema simple type. Simple types include the XML Schema primitive datatypes and any type that is validly derived from a simple XML Schema datatype (e.g. kml:angle90Type). The following XML Schema datatypes are also valid example values of type:

    Content

    name

Name that identifies the kml:SimpleField. Used as a reference value in the kml:SimpleData name attribute. See 9.6.4.1 name.

    uom

Unit of measure symbol for a data value representing a measured quantity. See 9.4.4.2 uom.

    anyAttribute

See 7.1.4.3 anyAttribute.

9.12    kml:SimpleArrayField

9.12.1    Structure

<kml:SimpleArrayField
 type=“string [0..1]”
 name=“string [0..1]”
 uom=“anyURI [0..1]”
 anyAttribute=“anySimpleType [0..1]”>
    <kml:displayName>…</kml:displayName> [0..1]
    <kml:SimpleArrayFieldExtension>…</kml:SimpleArrayFieldExtension> [0..*]
</kml:SimpleArrayField>

9.12.2    Description

Specifies a user-defined data field for an array of data (similar to 9.11 kml:SimpleField in both structure and purpose). The name and type attributes shall be specified.

9.12.3    Content

    kml:displayName

See 12.8 kml:displayName.

    kml:SimpleArrayFieldExtension

See 6.7.2.2 Complex Element Substitution.

9.12.4    Attributes

    type

Type of the field. See 9.11.4.1 type.

    name

Name that identifies the kml:SimpleArrayField. Used as a reference value in the kml:SimpleArrayData name attribute.

    uom

Unit of measure symbol for a data value representing a measured quantity.

See 9.4.4.2 uom.

    anyAttribute

See 7.1.4.3 anyAttribute.

9.13    kml:Folder

9.13.1    Structure

<kml:Folder
 id=“ID [0..1]”
 targetId=“NCName [0..1]”
 anyAttribute=“anySimpleType [0..1]”>
    <kml:ObjectSimpleExtensionGroup>…</kml:ObjectSimpleExtensionGroup> [0..*]
    <kml:name>…</kml:name> [0..1]
    <kml:visibility>…</kml:visibility> [0..1]
    <kml:balloonVisibility>…</kml:balloonVisibility> [0..1]
     <kml:open>…</kml:open> [0..1]
    <atom:author>…</atom:author> [0..1]
    <atom:link>…</atom:link> [0..1]
    <kml:address>…</kml:address> [0..1]
    <xal:AddressDetails>…</xal:AddressDetails> [0..1]
    <kml:phoneNumber>…</kml:phoneNumber> [0..1]
    <kml:snippet>…</kml:snippet> [0..1]
    <kml:description>…</kml:description> [0..1]
    <kml:AbstractViewGroup>…</kml:AbstractViewGroup> [0..1]
    <kml:AbstractTimePrimitiveGroup>…</kml:AbstractTimePrimitiveGroup> [0..1]
    <kml:styleUrl>…</kml:styleUrl> [0..1]
    <kml:AbstractStyleSelectorGroup>…</kml:AbstractStyleSelectorGroup> [0..*]
    <kml:Region>…</kml:Region> [0..1]
    <kml:AbstractExtendedDataGroup>…</kml: AbstractExtendedDataGroup> [0..1]
    <kml:AbstractFeatureSimpleExtensionGroup>…
     </kml:AbstractFeatureSimpleExtensionGroup> [0..*]
    <kml:AbstractFeatureObjectExtensionGroup>…
     </kml:AbstractFeatureObjectExtensionGroup> [0..*]
    <kml:AbstractContainerSimpleExtensionGroup>…
     </kml:AbstractContainerSimpleExtensionGroup> [0..*]
    <kml:AbstractContainerObjectExtensionGroup>…
     </kml:AbstractContainerObjectExtensionGroup> [0..*]
    <kml:AbstractFeatureGroup>…</kml:AbstractFeatureGroup> [0..*]
    <kml:FolderSimpleExtensionGroup>…</kml:FolderSimpleExtensionGroup> [0..*]
    <kml:FolderObjectExtensionGroup>…</kml:FolderObjectExtensionGroup> [0..*]
</kml:Folder>

9.13.2    Description

This element can be used wherever the following element is referenced:

A kml:Folder is used to organize kml:AbstractFeatureGroup elements hierarchically.  Contains zero or more kml:AbstractFeatureGroup elements and allows the creation of one or more nested hierarchies of KML features.

kml:Folder should contain at least one child element outside of an update context, that is when not a descendant of kml:Update.

9.13.3    Content

    kml:AbstractFeatureGroup

See 9.1 kml:AbstractFeatureGroup.

    kml:FolderSimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

    kml:FolderObjectExtensionGroup

See 6.7.2.2 Complex Element Substitution.

9.13.4    Example

<kml xmlns=“http://www.opengis.net/kml/2.2”>
<Folder>
  <name>Folder.kml</name>
  <open>1</open>
  <description>
    A folder is a container that can hold multiple other objects
  </description>
  <Placemark>
    <name>Folder object 1 (Placemark)</name>
    <Point>
      <coordinates>-122.377588,37.830266,0</coordinates>
    </Point>
  </Placemark>
  <Placemark>
    <name>Folder object 2 (Polygon)</name>
    <Polygon>
      <outerBoundaryIs>
        <LinearRing>
          <coordinates>
            -122.377830,37.830445,0
            -122.377576,37.830631,0
            -122.377840,37.830642,0
            -122.377830,37.830445,0
          </coordinates>
        </LinearRing>
      </outerBoundaryIs>
    </Polygon>
  </Placemark>
  <Placemark>
    <name>Folder object 3 (Path)</name>
    <LineString>
      <tessellate>1</tessellate>
      <coordinates>
        -122.378009,37.830128,0 -122.377885,37.830379,0
      </coordinates>
    </LineString>
  </Placemark>
</Folder>
</kml>

9.14    kml:Placemark

9.14.1    Structure

<kml:Placemark
 id=“ID [0..1]”
 targetId=“NCName [0..1]”
 anyAttribute=“anySimpleType [0..1]”>
    <kml:ObjectSimpleExtensionGroup>…</kml:ObjectSimpleExtensionGroup> [0..*]
    <kml:name>…</kml:name> [0..1]
    <kml:visibility>…</kml:visibility> [0..1]
    <kml:balloonVisibility>…</kml:balloonVisibility> [0..1]
    <kml:open>…</kml:open> [0..1]
    <atom:author>…</atom:author> [0..1]
    <atom:link>…</atom:link> [0..1]
    <kml:address>…</kml:address> [0..1]
    <xal:AddressDetails>…</xal:AddressDetails> [0..1]
    <kml:phoneNumber>…</kml:phoneNumber> [0..1]
    <kml:snippet>…</kml:snippet> [0..1]
    <kml:description>…</kml:description> [0..1]
    <kml:AbstractViewGroup>…</kml:AbstractViewGroup> [0..1]
    <kml:AbstractTimePrimitiveGroup>…</kml:AbstractTimePrimitiveGroup> [0..1]
    <kml:styleUrl>…</kml:styleUrl> [0..1]
    <kml:AbstractStyleSelectorGroup>…</kml:AbstractStyleSelectorGroup> [0..*]
    <kml:Region>…</kml:Region> [0..1]
    <kml:AbstractExtendedDataGroup>…</kml: AbstractExtendedDataGroup> [0..1]
    <kml:AbstractFeatureSimpleExtensionGroup>…
     </kml:AbstractFeatureSimpleExtensionGroup> [0..*]
    <kml:AbstractFeatureObjectExtensionGroup>…
     </kml:AbstractFeatureObjectExtensionGroup> [0..*]
    <kml:AbstractGeometryGroup>…</kml:AbstractGeometryGroup> [0..1]
    <kml:PlacemarkSimpleExtensionGroup>…
     </kml:PlacemarkSimpleExtensionGroup> [0..*]
    <kml:PlacemarkObjectExtensionGroup>…
     </kml:PlacemarkObjectExtensionGroup> [0..*]
</kml:Placemark>

9.14.2    Description

This element can be used wherever the following element is referenced:

A kml:Placemark is a kml:AbstractFeatureGroup with an associated kml:AbstractGeometryGroup.

A kml:Placemark with a kml:Point geometry should be drawn with an icon to mark the kml:Placemark in the geographic view.  The point itself determines the position of the kml:Placemark’s name and display icon.

kml:Placemark should contain a kml:AbstractGeometryGroup element outside of an update context, that is when not a descendant of kml:Update.

9.14.3    Content

    kml:AbstractGeometryGroup

See 10.1 kml:AbstractGeometryGroup.

    kml:PlacemarkSimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

    kml:PlacemarkObjectExtensionGroup

See 6.7.2.2 Complex Element Substitution.

9.14.4    Example

<Placemark>
  <name>New Placemark</name>
  <description>Some Descriptive text.</description>
  <LookAt>
    <longitude>-90.86879847669974</longitude>
    <latitude>48.25330383601299</latitude>
    <range>440.8</range>
    <tilt>8.3</tilt>
    <heading>2.7</heading>
  </LookAt>
  <Point>
    <coordinates>-90.86948943473118,48.25450093195546,0</coordinates>
  </Point>
</Placemark>

9.15    kml:NetworkLink

9.15.1    Structure

<kml:NetworkLink
 id=“ID [0..1]”
 targetId=“NCName [0..1]”
 anyAttribute=“anySimpleType [0..1]”>
    <kml:ObjectSimpleExtensionGroup>…</kml:ObjectSimpleExtensionGroup> [0..*]
    <kml:name>…</kml:name> [0..1]
    <kml:visibility>…</kml:visibility> [0..1]
    <kml:balloonVisibility>…</kml:balloonVisibility> [0..1]
    <kml:open>…</kml:open> [0..1]
    <atom:author>…</atom:author> [0..1]
    <atom:link>…</atom:link> [0..1]
    <kml:address>…</kml:address> [0..1]
    <xal:AddressDetails>…</xal:AddressDetails> [0..1]
    <kml:phoneNumber>…</kml:phoneNumber> [0..1]
    <kml:snippet>…</kml:snippet> [0..1]
    <kml:description>…</kml:description> [0..1]
    <kml:AbstractViewGroup>…</kml:AbstractViewGroup> [0..1]
    <kml:AbstractTimePrimitiveGroup>…</kml:AbstractTimePrimitiveGroup> [0..1]
    <kml:styleUrl>…</kml:styleUrl> [0..1]
    <kml:AbstractStyleSelectorGroup>…</kml:AbstractStyleSelectorGroup> [0..*]
    <kml:Region>…</kml:Region> [0..1]
    <kml:AbstractExtendedDataGroup>…</kml: AbstractExtendedDataGroup> [0..1]
    <kml:AbstractFeatureSimpleExtensionGroup>…
     </kml:AbstractFeatureSimpleExtensionGroup> [0..*]
    <kml:AbstractFeatureObjectExtensionGroup>…
     </kml:AbstractFeatureObjectExtensionGroup> [0..*]
    <kml:refreshVisibility>…</kml:refreshVisibility> [0..1]
    <kml:flyToView>…</kml:flyToView> [0..1]
    <kml:Link>…</kml:Link> [0..1]
    <kml:NetworkLinkSimpleExtensionGroup>…
     </kml:NetworkLinkSimpleExtensionGroup> [0..*]
    <kml:NetworkLinkObjectExtensionGroup>…
     </kml:NetworkLinkObjectExtensionGroup> [0..*]
</kml:NetworkLink>

9.15.2    Description

This element can be used wherever the following element is referenced:

References a KML resource on a local or remote network.  kml:NetworkLink elements may be used in combination with kml:Region elements to efficiently load and display large datasets.

9.15.3    Content

    kml:refreshVisibility

    Description

Specifies the control over the visibility of any kml:AbstractFeatureGroup elements within the referenced KML resource.

A value of 0 or false shall leave the visibility of any referenced kml:AbstractFeatureGroup elements in the geographic view within the control of the earth browser user.

A value of 1 or true shall require any referenced kml:AbstractFeatureGroup elements to be visible within the geographic view whenever such kml:AbstractFeatureGroup elements are refreshed.

    Content

    kml:flyToView

    Description

Specifies whether to adjust the geographic view upon kml:NetworkLink activation.

A value of 0 or false indicates that the geographic view shall remain unchanged.  A value of 1 or true indicates that the geographic view shall be displayed according to the kml:AbstractViewGroup specified by either:

•   a kml:NetworkLinkControl
•   a child kml:AbstractFeatureGroup of kml:kml

if they exist in the referenced KML resource.  The kml:AbstractViewGroup of the kml:NetworkLinkControl shall take precedence over the kml:AbstractViewGroup of the kml:AbstractFeatureGroup if they both exist.  If neither exists then the view shall remain unchanged.

    Content

    kml:Link

Specifies the location of the KML resource fetched by kml:NetworkLink. Note that kml:Link replaces the kml:Url element, which was deprecated in KML 2.2.

See 13.1 kml:Link, kml:Icon (kml:LinkType).

    kml:NetworkLinkSimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

    kml:NetworkLinkObjectExtensionGroup

See 6.7.2.2 Complex Element Substitution.

9.15.4    Example

<Document>
  <visibility>1</visibility>
  <NetworkLink>
    <name>NE US Radar</name>
    <refreshVisibility>1</refreshVisibility>
    <flyToView>1</flyToView>
    <Link>…</Link>
  </NetworkLink>
</Document>

9.16    kml:Region

9.16.1    Structure

<kml:Region
 id=“ID [0..1]”
 targetId=“NCName [0..1]”
 anyAttribute=“anySimpleType [0..1]”>
    <kml:ObjectSimpleExtensionGroup>…</kml:ObjectSimpleExtensionGroup> [0..*]
    <kml:AbstractExtentGroup>…</kml:AbstractExtentGroup> [0..1]
    <kml:Lod>…</kml:Lod> [0..1]
    <kml:RegionSimpleExtensionGroup>…</kml:RegionSimpleExtensionGroup> [0..*]
    <kml:RegionObjectExtensionGroup>…</kml:RegionObjectExtensionGroup> [0..*]
</kml:Region>

9.16.2    Description

This element can be used wherever the following element is referenced:

Affects the visibility of the kml:AbstractFeatureGroup.  A kml:AbstractFeatureGroup associated with a kml:Region is drawn only when the kml:Region is active.

A kml:Region affects visibility of a kml:AbstractFeatureGroup.  kml:Regions define both culling and level-of-detail control over the display of the kml:AbstractFeatureGroup.  A region shall specify a kml:LatLonAltBox element that describes an area of interest defined by geographic coordinates and altitudes.  In addition, a kml:Region contains a kml:Lod element that defines a validity range of the associated kml:Region in terms of projected screen size.

Regions are inherited through a kml:AbstractFeatureGroup hierarchy and affect the visibility of kml:AbstractFeatureGroup elements that are defined lower in the hierarchy.

A kml:Region is said to be “active” when the bounding box is within the user’s view and the LOD requirements are met.  kml:AbstractFeatureGroup elements associated with a kml:Region are drawn only when the kml:Region is active.  When the kml:viewRefreshMode is onRegion, the kml:Link or kml:Icon is loaded only when the kml:Region is active.  In a kml:AbstractContainerGroup or kml:NetworkLink hierarchy, this calculation uses the kml:Region that is the closest ancestor in the hierarchy. See also 9.8 kml:AbstractContainerGroup regarding the inheritance of kml:Region within KML feature hierarchies.

kml:Region shall contain the kml:LatLonAltBox and kml:Lod child elements outside of an update context, that is when not a descendant of kml:Update.

9.16.3    Content

    kml:AbstractExtentGroup

An abstract placeholder for kml:LatLonAltBox in the context of kml:Region.

See 9.17 kml:AbstractExtentGroup and 9.19 kml:LatLonAltBox.

    kml:Lod

See 9.22 kml:Lod.

    kml:RegionSimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

    kml:RegionObjectExtensionGroup

See 6.7.2.2 Complex Element Substitution.

9.16.4    Example

<Region>
  <LatLonAltBox>
    <north>50.625</north>
    <south>45</south>
    <east>28.125</east>
    <west>22.5</west>
    <minAltitude>10</minAltitude>
    <maxAltitude>50</maxAltitude>
  </LatLonAltBox>
  <Lod>
    <minLodPixels>128</minLodPixels>
    <maxLodPixels>1024</maxLodPixels>
    <minFadeExtent>128</minFadeExtent>
    <maxFadeExtent>128</maxFadeExtent>
  </Lod>
</Region>

9.17    kml:AbstractExtentGroup

9.17.1    Structure

<kml:AbstractExtentGroup
 id=“ID [0..1]”
 targetId=“NCName [0..1]”
 anyAttribute=“anySimpleType [0..1]”>
    <kml:ObjectSimpleExtensionGroup>…</kml:ObjectSimpleExtensionGroup> [0..*] 
    <kml:AbstractExtentSimpleExtensionGroup>…   
     </kml:AbstractExtentSimpleExtensionGroup> [0..*]   
    <kml:AbstractExtentObjectExtensionGroup>…
     </kml:AbstractExtentObjectExtensionGroup> [0..*]
</kml:AbstractExtentGroup>

9.17.2    Description

This element can be used wherever the following element is referenced:

The following elements can be used wherever this abstract element is referenced:

9.17.3    Content

    kml:AbstractExtentSimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

    kml:AbstractExtentObjectExtensionGroup

See 6.7.2.2 Complex Element Substitution.

9.18    kml:AbstractLatLonBoxGroup

9.18.1    Structure

<kml:AbstractLatLonBoxGroup
 id=“ID [0..1]”
 targetId=“NCName [0..1]”
 anyAttribute=“anySimpleType [0..1]”>
    <kml:ObjectSimpleExtensionGroup>…</kml:ObjectSimpleExtensionGroup> [0..*] 
    <kml:AbstractExtentSimpleExtensionGroup>…   
     </kml:AbstractExtentSimpleExtensionGroup> [0..*]   
    <kml:AbstractExtentObjectExtensionGroup>…
     </kml:AbstractExtentObjectExtensionGroup> [0..*]
    <kml:north>…</kml:north> [0..1]
    <kml:south>…</kml:south> [0..1]
    <kml:east>…</kml:east> [0..1]
    <kml:west>…</kml:west> [0..1]
    <kml:AbstractLatLonBoxSimpleExtensionGroup>…
     </kml:AbstractLatLonBoxSimpleExtensionGroup> [0..*]
    <kml:AbstractLatLonBoxObjectExtensionGroup>…
     </kml:AbstractLatLonBoxObjectExtensionGroup> [0..*]
</kml:AbstractLatLonBoxGroup>

9.18.2    Description

This element can be used wherever the following element is referenced:

The following elements can be used wherever this abstract element is referenced:

The kml:AbstractLatLonBoxGroup element represents a bounding box, which is spanned by latitude and longitude values satisfying: kml:south ≤ latitude ≤ kml:north and kml:west ≤ longitude ≤ kml:east.

9.18.3    Content

    kml:north

    Description

Specifies the latitude of the north edge of the bounding box, in decimal degrees in the interval: -180 < latitude ≤ 180. Note that the value of kml:north ≠ -180 because it must be strictly greater than the value of kml:south.  Note also that values of |latitude| > 90 are atypical, but allowed for backwards compatibility with KML 2.2. The default value of kml:north is 90 (changed from the default value of 180 in KML 2.2). See Section 9.14.3.7 for additional information on value constraints.

    Content

    kml:south

    Description

Specifies the latitude of the south edge of the bounding box, in decimal degrees  in the interval: -180 ≤ latitude < 180. Note that the value of kml:south ≠ 180 because it must be strictly less than the value of kml:north. Note also that values of |latitude| > 90 are atypical, but allowed for backwards compatibility with KML 2.2. The default value of kml:south is -90 (changed from the default value of -180 in KML 2.2).See Section 9.14.3.7 for additional information on value constraints.

    Content

    kml:east

    Description

Specifies the longitude of the east edge of the bounding box, in decimal degrees in the interval: -360 < longitude ≤ 360. Note that the value of kml:east ≠ -360 because it must be strictly greater than the value of kml:west. See Section 9.14.3.7 for additional information on value constraints.

    Content

    kml:west

    Description

Specifies the longitude of the west edge of the bounding box, in decimal degrees in the interval: -360 < longitude < 360. Note that the value of kml:west ≠ 360 because it must be strictly less than the value of kml:east and also kml:west ≠ -360, because of the uniqueness and non-self-overlap constraints. See Section 9.14.3.7 for additional information on value constraints.

    Content

    kml:AbstractLatLonBoxSimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

    kml:AbstractLatLonBoxObjectExtensionGroup

See 6.7.2.2 Complex Element Substitution.

    Constraints

In KML 2.3, the allowed value range in decimal degrees used by kml:east and kml:west is extended by a factor of 2 (from ±180 in KML 2.2) to ±360. This was done in order to accommodate bounding boxes anywhere on the earth, including overlaps of the anti-meridian, and of any size up to full global coverage. With the extension of the longitude range, all degree values, except -360 = 0 = 360 (mod 360), have exactly two equivalent choices modulo 360, e.g. -359 = 1 (mod 360). The latitude range for kml:north and kml:south remain the same as in KML 2.2 and the following constraints C1 (i.e. the non-trivial latitude interval constraint) and C2 (i.e. the non-trivial longitude interval constraint) are unchanged:

New constraints in KML 2.3 are introduced with the longitude range extension to avoid self overlaps and to preserve uniqueness of longitude interval values:

The constraint C3 ensures that the longitude interval does not overlap itself. The constraint C4 ensures the choice of the kml:west and kml:east values are unique for every longitude interval. Examples of allowed and prohibited pairs of kml:west and kml:east values are shown in Figure 9.

Additional examples of valid longitude intervals with full global coverage, starting and ending at different longitude values are shown in Figure 10.

9.19    kml:LatLonAltBox

9.19.1    Structure

<kml:LatLonAltBox
 id=“ID [0..1]”
 targetId=“NCName [0..1]”
 anyAttribute=“anySimpleType [0..1]”>
    <kml:ObjectSimpleExtensionGroup>…</kml:ObjectSimpleExtensionGroup> [0..*]
    <kml:AbstractExtentSimpleExtensionGroup>…
     </kml:AbstractExtentSimpleExtensionGroup> [0..*]    
    <kml:AbstractExtentObjectExtensionGroup>…
     </kml:AbstractExtentObjectExtensionGroup> [0..*]
    <kml:north>…</kml:north> [0..1]
    <kml:south>…</kml:south> [0..1]
    <kml:east>…</kml:east> [0..1]
    <kml:west>…</kml:west> [0..1]
    <kml:AbstractLatLonBoxSimpleExtensionGroup>…
     </kml:AbstractLatLonBoxSimpleExtensionGroup> [0..*]
    <kml:AbstractLatLonBoxObjectExtensionGroup>…
     </kml:AbstractLatLonBoxObjectExtensionGroup> [0..*]
    <kml:minAltitude>…</kml:minAltitude> [0..1]
    <kml:maxAltitude>…</kml:maxAltitude> [0..1]
    <kml:altitudeMode>…</kml:altitudeModeGroup> [0..1]
    <kml:seaFloorAltitudeMode>…</kml:seaFloorAltitudeMode> [0..1]
    <kml:AltitudeModeSimpleExtensionGroup>…
     </kml:AltitudeModeSimpleExtensionGroup> [0..1]
    <kml:AltitudeModeObjectExtensionGroup>…
     </kml:AltitudeModeObjectExtensionGroup> [0..1]
    <kml:LatLonAltBoxSimpleExtensionGroup>…
     </kml:LatLonAltBoxSimpleExtensionGroup> [0..*]
    <kml:LatLonAltBoxObjectExtensionGroup>…
     </kml:LatLonAltBoxObjectExtensionGroup> [0..*]
</kml:LatLonAltBox>

9.19.2    Description

This element can be used wherever the following element is referenced:

The schema type for kml:LatLonAltBox derives by extension from the schema type for kml:AbstractLatLonAltBoxGroup, even though it does not substitute for it.

Specifies the extent of a 3D bounding box, such that:

•   kml:north is greater than kml:south;
•   kml:east is greater than kml:west;
•   kml:minAltitude is less than or equal to kml:maxAltitude;
•   if kml:minAltitude and kml:maxAltitude are both present, kml:altitudeMode shall not have a value of clampToGround.

9.19.3    Content

    minAltitude

    Description

Specified in meters above the vertical datum (and is affected by the kml:altitudeMode specification).

    Content

    maxAltitude

    Description

Specified in meters above the vertical datum (and is affected by the kml:altitudeMode specification).

    Content

    kml:altitudeMode

See 9.20 kml:altitudeMode.

    kml:seaFlooraltitudeMode

See 9.21 kml:seaFloorAltitudeMode.

    kml:AltitudeModeSimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

    kml:AltitudeModeObjectExtensionGroup

See 6.7.2.2 Complex Element Substitution.

    kml:LatLonAltBoxSimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

    kml:LatLonAltBoxObjectExtensionGroup

See 6.7.2.2 Complex Element Substitution.

9.19.4    Example

<LatLonAltBox>
  <north>43.374</north>
  <south>42.983</south>
  <east>-0.335</east>
  <west>-1.423</west>
  <minAltitude>0</minAltitude>
  <maxAltitude>0</maxAltitude>
</LatLonAltBox>

9.20    kml:altitudeMode

9.20.1    Structure

<kml:altitudeMode>…</kml:altitudeMode>

9.20.2    Description

Specifies how the altitude components are interpreted in kml:coordinates, kml:coord and kml:altitude elements. The allowed values of kml:altitudeMode are:

•   clampToGround- (default) The altitude value is ignored and the position is projected onto the ground.
•   relativeToGround - Sets the altitude of the element relative to the actual ground elevation of a particular location. For example, if the ground elevation of a location is exactly at sea level and the altitude for a point is set to 9 meters, then the elevation for the icon of a point placemark elevation is 9 meters with this mode. However, if the same coordinate is set over a location where the ground elevation is 10 meters above sea level, then the elevation of the coordinate is 19 meters above sea level.
•   absolute- Sets the altitude of the coordinate relative to sea level, regardless of the actual elevation of the terrain beneath the element. For example, if you set the altitude of a coordinate to 10 meters with an absolute altitude mode, the icon of a point placemark will appear to be at ground level if the terrain beneath is also 10 meters above sea level. If the terrain is 3 meters above sea level, the placemark will appear elevated above the terrain by 7 meters.

If kml:altitudeMode is set to relativeToGround or absolute then the associated altitude component(s) should be present within the element to which it applies.

See also 6.3 Geometry Interpolation for 3D Earth Browsers.

9.20.3    Content

9.21    kml:seaFloorAltitudeMode

9.21.1    Structure

<kml:seaFloorAltitudeMode>…</kml:seaFloorAltitudeMode>

9.21.2    Description

Specifies how the altitude components are interpreted in kml:coordinates, kml:coord and kml:altitude elements. The allowed values of kml:seaFloorAltitudeMode are:

• relativeToSeaFloor - Interprets the altitude as a value in meters above the sea floor. If the point is above land rather than sea, the altitude will be interpreted as being above the ground.
• clampToSeaFloor – The specified altitude value is ignored, and the point will be projected onto the sea floor. If the point is on land rather than at sea, the point will be positioned on the ground.

9.21.3    Content

9.22    kml:Lod

9.22.1    Structure

<kml:Lod
 id=“ID [0..1]”
 targetId=“NCName [0..1]”
 anyAttribute=“anySimpleType [0..1]”>
    <kml:ObjectSimpleExtensionGroup>…</kml:ObjectSimpleExtensionGroup> [0..*]
    <kml:minLodPixels>…</kml:minLodPixels> [0..1]
    <kml:maxLodPixels>…</kml:maxLodPixels> [0..1]
    <kml:minFadeExtent>…</kml:minFadeExtent> [0..1]
    <kml:maxFadeExtent>…</kml:maxFadeExtent> [0..1]
    <kml:LodSimpleExtensionGroup>…</kml:LodSimpleExtensionGroup> [0..*]
   <kml:LodObjectExtensionGroup>…</kml:LodObjectExtensionGroup> [0..*]
</kml:Lod>

9.22.2    Description

This element can be used wherever the following element is referenced:

Specifies the level of detail to use when displaying a kml:Region.

An earth browser should calculate the size of the kml:Region when projected onto screen space then compute the square root of the kml:Region’s area.  For example, if an untiled kml:Region is square and the viewpoint is directly above the kml:Region, this measurement is equal to the width of the projected kml:Region.  If this measurement falls within the limits defined by kml:minLodPixels and kml:maxLodPixels, and if the kml:LatLonAltBox is in view, then the kml:Region should be activated.  If this limit is not reached, the associated geometry should not be drawn since it would be too far from the user’s viewpoint to be visible.

kml:minLodPixels shall be less than kml:maxLodPixels (where a value of -1 = infinite).  It is also advised that kml:minFadeExtent + kml:maxFadeExtent is less than or equal to kml:maxLodPixels - kml:minLodPixels.

The following diagram demonstrates how kml:Lod is used in the determination of the visibility of a region:

In the following diagram, if P=the calculated projected pixel size, the circled numbers indicate the following:

if (P < minLodPixels)
  opacity=0                                 //#1 in diagram
else if(P < minLodPixels + minFadeExtent)
  opacity=(P - minLodPixels)/minFadeExtent  //#2 in diagram
else if (P < maxLodPixels - maxFadeExtent)
  opacity=1                                 //#3 in diagram
else if (P < maxLodPixels)
  opacity=(maxLodPixels-P)/maxFadeExtent    //#4 in diagram
else
  opacity=0                                 //#5 in diagram

kml:Lod shall contain the kml:minLodPixels outside of an update context, that is when not a descendant of kml:Update.

See also 9.16 kml:Region.

9.22.3    Content

    kml:minLodPixels

    Description

Measurement in screen pixels that represents the minimum limit of the visibility range for a given kml:Region.

    Content

    kml:maxLodPixels

    Description

Measurement in screen pixels that represents the maximum limit of the visibility range for a given kml:Region.  The default value of −1.0 indicates “active to infinite size.”

    Content

    kml:minFadeExtent

    Description

Distance over which the geometry fades, from fully opaque to fully transparent.  This ramp value, expressed in screen pixels, is applied at the minimum end of the LOD (visibility) limits.

    Content

    kml:maxFadeExtent

    Description

Distance over which the geometry fades, from fully transparent to fully opaque.  This ramp value, expressed in screen pixels, is applied at the maximum end of the LOD (visibility) limits.

    Content

    kml:LodSimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

    kml:LodObjectExtensionGroup

See 6.7.2.2 Complex Element Substitution.

9.22.4    Example

<Region>
  <LatLonAltBox>
    <north>50.625</north>
    <south>45</south>
    <east>28.125</east>
    <west>22.5</west>
    <minAltitude>10</minAltitude>
    <maxAltitude>50</maxAltitude>
  </LatLonAltBox>
  <Lod>
    <minLodPixels>128</minLodPixels>
    <maxLodPixels>1024</maxLodPixels>
    <minFadeExtent>128</minFadeExtent>
    <maxFadeExtent>128</maxFadeExtent>
  </Lod>
</Region>

9.23    kml:Tour

9.23.1    Structure

<kml:Tour
 id=“ID [0..1]”
 targetId=“NCName [0..1]”
 anyAttribute=“anySimpleType [0..1]”> 
    <kml:ObjectSimpleExtensionGroup>…</kml:ObjectSimpleExtensionGroup> [0..*]
    <kml:name>…</kml:name> [0..1]
    <kml:visibility>…</kml:visibility> [0..1]
    <kml:balloonVisibility>…</kml:balloonVisibility> [0..1]
    <kml:open>…</kml:open> [0..1]
    <atom:author>…</atom:author> [0..1]
    <atom:link>…</atom:link> [0..1]
    <kml:address>…</kml:address> [0..1]
    <xal:AddressDetails>…</xal:AddressDetails> [0..1]
    <kml:phoneNumber>…</kml:phoneNumber> [0..1] 
    <kml:AbstractSnippetGroup>…</kml:AbstractSnippetGroup> [0..1]
    <kml:description>…</kml:description> [0..1]
    <kml:AbstractViewGroup>…</kml:AbstractViewGroup> [0..1]
    <kml:AbstractTimePrimitiveGroup>…</kml:AbstractTimePrimitiveGroup> [0..1]
    <kml:styleUrl>…</kml:styleUrl> [0..1]
    <kml:AbstractStyleSelectorGroup>…</kml:AbstractStyleSelectorGroup> [0..*]
    <kml:Region>…</kml:Region> [0..1]
    <kml:AbstractExtendedDataGroup>…</kml:AbstractExtendedDataGroup> [0..1]   
    <kml:AbstractFeatureSimpleExtensionGroup>…
    </kml:AbstractFeatureSimpleExtensionGroup> [0..*]   
    <kml:AbstractFeatureObjectExtensionGroup>…
    </kml:AbstractFeatureObjectExtensionGroup> [0..*]
    <kml:Playlist>…</kml:Playlist> [0..1]
    <kml:TourSimpleExtensionGroup>…</kml:TourSimpleExtensionGroup> [0..*]
    <kml:TourObjectExtensionGroup>…</kml:TourObjectExtensionGroup> [0..*]
</kml:Tour>

9.23.2    Description

A kml:Tour specifies a controlled flight through a series of geographic locations. The aspects of the flight that can be controlled include: the duration between locations, the mode of flight (smooth or bounce), what and when sound tracks should be played, and how KML features are updated throughout the tour. The kml:Tour is comprised of a playlist, which contains tour primitives, such as fly-to viewpoints, flight durations, pauses, sound cues, and KML updates. The tour primitives can be played in series or in parallel and are used to specify the behavior of the KML browser along different segments of the tour timeline. 

9.23.3    Content

    kml:Playlist

Contains any number of tour primitives.

See 9.24 kml:Playlist.

    kml:TourSimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

    kml:TourObjectExtensionGroup

See 6.7.2.2 Complex Element Substitution.

9.23.4    Example

<kml xmlns=“http://www.opengis.net/kml/2.2”>
   <Document>
     <name>A tour and some features</name>
     <open>1</open>
     <Tour>
       <name>Play me!</name>
       <Playlist>
         <FlyTo>
           <duration>5.0</duration>
           <!– bounce is the default flyToMode –>
           <Camera>
             <longitude>170.157</longitude>
             <latitude>-43.671</latitude>
             <altitude>9700</altitude>
             <heading>-6.333</heading>
             <tilt>33.5</tilt>
           </Camera>
         </FlyTo>
         <Wait>
           <duration>1.0</duration>
         </Wait>
         <FlyTo>
           <duration>6.0</duration>
           <Camera>
             <longitude>174.063</longitude>
             <latitude>-39.663</latitude>
             <altitude>18275</altitude>
             <heading>-4.921</heading>
             <tilt>65</tilt>
             <altitudeMode>absolute</altitudeMode>
           </Camera>
         </FlyTo>
         <FlyTo>
           <duration>3.0</duration>
           <flyToMode>smooth</flyToMode>
           <LookAt>
             <longitude>174.007</longitude>
             <latitude>-39.279</latitude>
             <altitude>0</altitude>
             <heading>112.817</heading>
             <tilt>68.065</tilt>
             <range>6811.884</range>
             <altitudeMode>relativeToGround</altitudeMode>
           </LookAt>
         </FlyTo>
         <FlyTo>
           <duration>3.0</duration>
           <flyToMode>smooth</flyToMode>
           <LookAt>
             <longitude>174.064</longitude>
             <latitude>-39.321</latitude>
             <altitude>0</altitude>
             <heading>-48.463</heading>
             <tilt>67.946</tilt>
             <range>4202.579</range>
             <altitudeMode>relativeToGround</altitudeMode>
           </LookAt>
         </FlyTo>
         <Wait>
           <duration>6.0</duration>
         </Wait>
       </Playlist>
     </Tour>
     <Folder>
       <name>Points and polygons</name>
       <Style id=“pushpin”>
         <IconStyle>
           <Icon>
             <href>http://maps.google.com/mapfiles/kml/pushpin/ylw-pushpin.png</href>
           </Icon>
         </IconStyle>
       </Style>
       <Placemark id=“mountainpin1”>
         <name>New Zealand’s Southern Alps</name>
         <styleUrl>#pushpin</styleUrl>
         <Point>
           <coordinates>170.144,-43.605,0</coordinates>
         </Point>
       </Placemark>
       <Placemark id=“polygon1”>
         <name>Polygon</name>
         <Polygon>
           <tessellate>1</tessellate>
           <outerBoundaryIs>
             <LinearRing>
               <coordinates> 175.365,-36.522,0 175.366,-36.530,0 175.369,-36.529,0 175.366,-36.521,0
                 175.365,-36.522,0 </coordinates>
             </LinearRing>
           </outerBoundaryIs>
         </Polygon>
       </Placemark>
     </Folder>
   </Document>
 </kml>

9.24 kml:Playlist

9.24.1   Structure

<kml:Playlist
 id=“ID [0..1]” 
  targetId=“NCName [0..1]”
 anyAttribute=“anySimpleType [0..1]”>
    <kml:ObjectSimpleExtensionGroup>…</kml:ObjectSimpleExtensionGroup> [0..*]
    <kml:AbstractTourPrimitiveGroup>…</kml:AbstractTourPrimitiveGroup> [0..*]
    <kml:PlaylistSimpleExtensionGroup>…</kml:PlaylistSimpleExtensionGroup> [0..*]
    <kml:PlaylistObjectExtensionGroup>…</kml:PlaylistObjectExtensionGroup> [0..*]
</kml:Playlist>

9.24.2    Description

The kml:Playlist element contains any number of tour primitives, i.e. elements that substitute for kml:AbstractTourPrimitiveGroup. There can be at most one kml:Playlist element contained within a kml:Tour element. 

9.24.3    Content

    kml:AbstractTourPrimitiveGroup

An abstract placeholder for the following instantiable elements: kml:FlyTo, kml:AnimatedUpdate, kml:TourControl, kml:Wait, and kml:SoundCue.

See 9.25 kml:AbstractTourPrimitiveGroup.

    kml:PlaylistSimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

    kml:PlaylistObjectExtensionGroup

See 6.7.2.2 Complex Element Substitution.

9.25   kml:AbstractTourPrimitiveGroup

9.25.1    Structure

<kml:AbstractTourPrimitiveGroup
 id=“ID [0..1]”
 targetId=“NCName [0..1]”
  anyAttribute=“anySimpleType [0..1]”>
  <kml:ObjectSimpleExtensionGroup>…</kml:ObjectSimpleExtensionGroup> [0..*]
  <kml:AbstractTourPrimitiveSimpleExtensionGroup>…
   </kml:AbstractTourPrimitiveSimpleExtensionGroup> [0..*]
  <kml:AbstractTourPrimitiveObjectExtensionGroup>…
   </kml:AbstractTourPrimitiveObjectExtensionGroup> [0..*]
</kml:AbstractTourPrimitiveGroup>

9.25.2    Description

The kml:AbstractTourPrimitiveGroup is an abstract placeholder for the following instantiable elements: kml:FlyTo, kml:AnimatedUpdate, kml:TourControl, kml:Wait, and kml:SoundCue. Some of these primitives are played series and some can be played in parallel with others.

The primitives: kml:FlyTo, kml:Wait, and kml:TourControl are played sequentially, and must be fully complete before the playlist moves on to the next primitive. So only one of these series-type primitives can take place at a time – no new kml:SoundCue or kml:AnimatedUpdate primitives can be started while a series-type primitive is taking place.

The primitives: kml:AnimatedUpdate and kml:SoundCue can be played in parallel with other primitives. These primitives are cued when they appear in the playlist. Once they are started, the playlist immediately moves on to the next primitive, without waiting for the kml:SoundCue or kml:AnimatedUpdate to complete. This means that:

• any number of sound cues and/or animated updates can take place at the same time, by cueing them one after the other in the playlist
• sound cues and/or animated updates can continue while series-type primitives are playing (though they can not be started while series-type primitives are playing)

The diagram below illustrates this behavior.

The diagram shows that each kml:FlyTo takes a specific amount of time to complete, which is specified by its kml:duration element. After the duration has elapsed, the tour proceeds to the next primitive.

On the other hand, the kml:SoundCue, takes place in parallel. The next primitive (the second kml:FlyTo) in the playlist is executed immediately after the sound track begins playing. The sound track continues until the end of the file is reached, or the end of the tour, whichever occurs first. If the tour ends before the sound file does, the sound track is truncated. Any number of sound tracks can be played at any given time, as each is loaded into its own timeline track.

Animated updates behave in a similar way. If a placemark’s icon is set to increase in size over a 5 second duration, it does so while the subsequent primitives in the playlist take place.

9.25.3    Content

    kml:AbstractTourPrimitiveSimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

    kml: AbstractTourPrimitiveObjectExtensionGroup

See 6.7.2.2 Complex Element Substitution.

9.25.4    Example

<Tour xmlns=“http://www.opengis.net/kml/2.2”>
   <Playlist>
     <FlyTo>
       <duration>5</duration>
       <flyToMode>bounce</flyToMode>
       <LookAt>
         <longitude>-79.387</longitude>
         <latitude>43.643</latitude>
         <altitude>0</altitude>
         <heading>-172.3</heading>
         <tilt>10</tilt>
         <range>1200</range>
         <altitudeMode>relativeToGround</altitudeMode>
       </LookAt>
     </FlyTo>
     <TourControl>
       <playMode>pause</playMode>
     </TourControl>
     <SoundCue>
       <href> http://dev.keyhole.com/codesite/cntowerfacts.mp3 </href>
       <!– this file is ten seconds long –>
     </SoundCue>
     <Wait>
       <duration>10.0</duration>
     </Wait>
   </Playlist>
 </Tour>

9.26    kml:AnimatedUpdate

9.26.1    Structure

<kml:AnimatedUpdate 
 id=“ID [0..1]” 
  targetId=“NCName [0..1]”
 anyAttribute=“anySimpleType [0..1]”>
   <kml:ObjectSimpleExtensionGroup>…</kml:ObjectSimpleExtensionGroup> [0..*]
    <kml:AbstractTourPrimitiveSimpleExtensionGroup>…
    </kml:AbstractTourPrimitiveSimpleExtensionGroup> [0..*]      
   <kml:AbstractTourPrimitiveObjectExtensionGroup>…
    </kml:AbstractTourPrimitiveObjectExtensionGroup> [0..*]
   <kml:duration>…</kml:duration> [0..1]
    <kml:Update>…</kml:Update> [0..1]
    <kml:delayedStart>…</kml:delayedStart> [0..1] 
   <kml:AnimatedUpdateSimpleExtensionGroup>… 
    </kml:AnimatedUpdateSimpleExtensionGroup> [0..*]
    <kml:AnimatedUpdateObjectExtensionGroup>…
    </kml:AnimatedUpdateObjectExtensionGroup> [0..*]
</kml:AnimatedUpdate>

9.26.2    Description

kml:AnimatedUpdate controls changes to KML Features (e.g. balloon open/close) during a tour using kml:Update.

9.26.3    Content

kml:AnimatedUpdate should contain a kml:duration value to specify the length of time in seconds over which the update takes place. Integer, float, and color values are animated by interpolating from the original to the new value over the duration; boolean, string, and other values not amenable to interpolation, are updated at the end of the duration.

    kml:duration

    Description

Specifies the length of time, in seconds, over which the update takes place.

    Content

    kml:Update

See section 13.5 kml:Update. If the objects to be updated all occur in the same document as the parent kml:AnimatedUpdate element then the kml:Update/kml:targetHref element may be empty.

    kml:delayedStart

    Description

Specifies the number of seconds to wait (after the inline start position) before applying the update.

    Content

    kml:AnimatedUpdateSimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

    kml:AnimatedUpdateObjectExtensionGroup

See 6.7.2.2 Complex Element Substitution.

9.26.4    Example

<kml xmlns=“http://www.opengis.net/kml/2.2”>
   <Document>
     <name>AnimatedUpdate example</name>
     <Style id=“pushpin”>
       <IconStyle id=“mystyle”>
         <Icon>
           <href>http://maps.google.com/mapfiles/kml/pushpin/ylw-pushpin.png</href>
           <scale>1.0</scale>
         </Icon>
       </IconStyle>
     </Style>
     <Placemark id=“mountainpin1”>
       <name>Pin on a mountaintop</name>
       <styleUrl>#pushpin</styleUrl>
       <Point>
         <coordinates>170.1435558771009,-43.60505741890396,0</coordinates>
       </Point>
     </Placemark>
     <Tour>
       <name>Play me!</name>
       <Playlist>
         <FlyTo>
           <flyToMode>bounce</flyToMode>
           <duration>3</duration>
           <Camera>
             <longitude>170.157</longitude>
             <latitude>-43.671</latitude>
             <altitude>9700</altitude>
             <heading>-6.333</heading>
             <tilt>33.5</tilt>
           </Camera>
         </FlyTo>
         <AnimatedUpdate>
           <duration>5</duration>
           <Update>
             <targetHref/>
             <Change>
               <IconStyle targetId=“mystyle”>
                 <scale>10.0</scale>
               </IconStyle>
             </Change>
           </Update>
         </AnimatedUpdate>
         <Wait>
           <duration>5</duration>
         </Wait>
       </Playlist>
     </Tour>
   </Document>
 </kml>

9.27     kml:FlyTo

9.27.1    Structure

<kml:FlyTo
 id=“ID [0..1]” 
  targetId=“NCName [0..1]”
 anyAttribute=“anySimpleType [0..1]”> 
    <kml:ObjectSimpleExtensionGroup>…</kml:ObjectSimpleExtensionGroup> [0..*]
    <kml:AbstractTourPrimitiveSimpleExtensionGroup>… 
    </kml:AbstractTourPrimitiveSimpleExtensionGroup> [0..*]   
   <kml:AbstractTourPrimitiveObjectExtensionGroup>…
    </kml:AbstractTourPrimitiveObjectExtensionGroup> [0..*]
   <kml:duration>…</kml:duration> [0..1]
    <kml:abstractFlyToMode>…</kml:abstractFlyToMode> [0..1]
    <kml:AbstractViewGroup>…</kml:AbstractViewGroup> [0..1]
    <kml:FlyToSimpleExtensionGroup>…</kml:FlyToSimpleExtensionGroup> [0..*]
    <kml:FlyToObjectExtensionGroup>…</kml:FlyToObjectExtensionGroup> [0..*]
</kml:FlyTo>

9.27.2    Description

kml:FlyTo specifies a point in space to which the browser will fly during a tour. It must contain an abstract view (e.g. kml:LookAt or kml:Camera), and should contain kml:duration and kml:flyToMode elements, which specify the time it takes to fly to the specified point and the method of flight, respectively.

9.27.3    Content

    kml:duration

Specifies the length of time, in seconds, over which the flight takes place.

See 9.26.3.1 kml:duration.

    kml:abstractFlyToMode

    Description

An abstract placeholder for kml:flyToMode and an extension point for fly-to mode enumerations. See also 9.28 kml:flyToMode and 6.7.2.1 Simple Element Substitution.

    Content

    kml:AbstractViewGroup

An abstract placeholder for a viewpoint (kml:Camera or kml:LookAt).

See 14.1 AbstractViewGroup.

    kml:FlyToSimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

    kml:FlyToObjectExtensionGroup

See 6.7.2.2 Complex Element Substitution.

9.27.4    Example

<FlyTo>
   <duration>2.55</kml:duration>
   <flyToMode>smooth</kml:flyToMode>
   <Camera>
     <longitude>-113.084448</longitude>
     <latitude>36.567081</latitude>
     <altitude>41277.571403</altitude>
     <heading>116.150227</heading>
     <altitudeMode>absolute</altitudeMode>
   </Camera>
 </FlyTo>

9.28    kml:flyToMode

9.28.1    Structure

<kml:flyToMode>…</kml:flyToMode>

9.28.2    Description

Specifies the mode of flight using an enumerated value; smooth or bounce:

1. smooth mode allows for an unbroken flight from point to point. An unbroken series of smooth FlyTos will begin and end at zero velocity, and will not slow at each intermediate point. A sequence of smooth FlyTos will be broken by either of the following elements:
   •    <kml:flyToMode>bounce</kml:flyToMode>
   •   kml:Wait

   This means that the velocity will approach zero immediately preceding either of the above elements during a smooth FlyTo. A sequence of smooth FlyTos is not broken by kml:AnimatedUpdate elements.

2. bounce mode alwaysbegins and ends at zero velocity.

9.28.3    Content

9.29    kml:SoundCue

9.29.1    Structure

<kml:SoundCue
 id=“ID [0..1]”
 targetId=“NCName [0..1]”
 anyAttribute=“anySimpleType [0..1]”>
  <kml:ObjectSimpleExtensionGroup>…</kml:ObjectSimpleExtensionGroup> [0..*]
   <kml:AbstractTourPrimitiveSimpleExtensionGroup>…
   </kml:AbstractTourPrimitiveSimpleExtensionGroup> [0..*]  
  <kml:AbstractTourPrimitiveObjectExtensionGroup>…
   </kml:AbstractTourPrimitiveObjectExtensionGroup> [0..*]
  <kml:href>…</kml:href>[0..1]
  <kml:delayedStart>…</kml:delayedStart>[0..1]
  <kml:SoundCueSimpleExtensionGroup>…
   </kml:SoundCueSimpleExtensionGroup>[0..*]
  <kml:SoundCueObjectExtensionGroup>…
   </kml:SoundCueObjectExtensionGroup> [0..*]
</kml:SoundCue>

9.29.2    Description

Contains a kml:href element to reference a sound track. The kml:SoundCue element does not contain a duration. The sound file plays in parallel to the rest of the tour, meaning that the next tour primitive takes place immediately after the kml:SoundCue tour primitive is reached. If another sound file is cued before the first has finished playing, the files are mixed. The kml:delayedStart element specifies to delay the start of the sound for a given number of seconds before playing the file.

9.29.3    Content

    kml:href

Specfies a URI reference to a sound track (e.g. MP3, M4A, or AAC format).

See 12.13.3.1 kml:href.

    kml:delayedStart

Specifies the number of seconds to wait before playing the sound track.

See 9.26.3.3 kml:delayedStart.

    kml:SoundCueSimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

    kml:SoundCueObjectExtensionGroup

See 6.7.2.2 Complex Element Substitution.

9.29.4    Example

<Tour>
   <Playlist>
     <SoundCue>
      <!– 15 second audio clip –>
      <href>http://www.example.com/audio/trumpets.mp3</href>
      <delayedStart>1</kml:delayedStart>
     </SoundCue>
     <FlyTo>
       <duration>5</duration>
       <flyToMode>bounce</flyToMode>
       <LookAt>
         <longitude>-79.387</longitude>
         <latitude>43.643</latitude>
         <altitude>0</altitude>
         <range>1200</range>
         <tilt>10</tilt>
         <heading>-172.3</heading>
         <altitudeMode>relativeToGround</altitudeMode>
       </LookAt>
     </FlyTo>
     <SoundCue>
       <href> http://dev.keyhole.com/codesite/cntowerfacts.mp3 </href>
       <!– 10 second audio clip –>
     </SoundCue>
     <Wait>
       <duration>10</duration>
       <!– continues the tour for 10 seconds while audio clip plays –>
     </Wait>
   </Playlist>
 </Tour>

9.30    kml:TourControl

9.30.1    Structure

<kml:TourControl
 id=“ID [0..1]”
 targetId=“NCName [0..1]”
 anyAttribute=“anySimpleType [0..1]”>
  <kml:ObjectSimpleExtensionGroup>…</kml:ObjectSimpleExtensionGroup> [0..*]
   <kml:AbstractTourPrimitiveSimpleExtensionGroup>…
   </kml:AbstractTourPrimitiveSimpleExtensionGroup> [0..*]    
  <kml:AbstractTourPrimitiveObjectExtensionGroup>…
   </kml:AbstractTourPrimitiveObjectExtensionGroup> [0..*] 
   <kml:abstractPlayMode>…</kml:abstractPlayMode> [0..1]
  <kml:TourControlSimpleExtensionGroup>…
   </kml:TourControlSimpleExtensionGroup> [0..*]
  <kml:TourControlObjectExtensionGroup>…
   </kml:TourControlObjectExtensionGroup> [0..*]
 </kml:TourControl>

9.30.2    Description

kml:TourControl allows a kml:playMode element, enabling the tour to be paused until a user takes action to continue the tour.

9.30.3    Content

    kml:abstractPlayMode

    Description

An abstract placeholder for kml:playMode and an extension point for play mode enumerations. See also 9.31 kml:playMode and 6.7.2.1 Simple Element Substitution.

    Content

    kml:TourControlSimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

    kml:TourControlObjectExtensionGroup

See 6.7.2.2 Complex Element Substitution.

9.30.4   Example

<TourControl id=“TC001”>
   <playMode>pause</playMode>
 </TourControl>

9.31    kml:playMode

9.31.1    Structure

<kml:playMode>…</kml:playMode>

9.31.2    Description

Specifies the play mode using an enumerated value.

9.31.3    Content

9.32    kml:Wait

9.32.1    Structure

<kml:Wait
 id=“ID [0..1]” 
  targetId=“NCName [0..1]”
 anyAttribute=“anySimpleType [0..1]”> 
    <kml:ObjectSimpleExtensionGroup>…</kml:ObjectSimpleExtensionGroup> [0..*]
    <kml:AbstractTourPrimitiveSimpleExtensionGroup>…
    </kml:AbstractTourPrimitiveSimpleExtensionGroup> [0..*]   
   <kml:AbstractTourPrimitiveObjectExtensionGroup>… 
    </kml:AbstractTourPrimitiveObjectExtensionGroup> [0..*]
   <kml:duration>…</kml:duration> [0..1]
    <kml:WaitSimpleExtensionGroup>…</kml:WaitSimpleExtensionGroup> [0..*]
    <kml:WaitObjectExtensionGroup>…</kml:WaitObjectExtensionGroup> [0..*]
</kml:Wait>

9.32.2    Description

The kml:Wait element holds the camera still, at the last-defined abstract view, for the number of seconds specified in its kml:duration element before playing the next tour primitive. Note that kml:Wait does not pause the tour timeline – sound files and animated updates will continue to play while the camera is waiting.

9.32.3    Content

    kml:duration

Specifies the length of time, in seconds, to wait while holding the camera still at the last defined abstract view.

See 9.26.3.1 kml:duration.

    kml:WaitSimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

    kml:WaitObjectExtensionGroup

See 6.7.2.2 Complex Element Substitution.

10.    Geometries

10.1    kml:AbstractGeometryGroup

10.1.1    Structure

<kml:AbstractGeometryGroup
 id=“ID [0..1]”
 targetId=“NCName [0..1]”
 anyAttribute=“anySimpleType [0..1]”>
   <kml:ObjectSimpleExtensionGroup>…</kml:ObjectSimpleExtensionGroup> [0..*]   
   <kml:AbstractGeometrySimpleExtensionGroup>…
    </kml:AbstractGeometrySimpleExtensionGroup> [0..*]   
   <kml:AbstractGeometryObjectExtensionGroup>…
    </kml:AbstractGeometryObjectExtensionGroup> [0..*]
</kml:AbstractGeometryGroup>

10.1.2    Description

This abstract element can be used wherever the following element is referenced:

The following elements can be used wherever this abstract element is referenced:

10.1.3    Content

    kml:AbstractGeometrySimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

    kml:AbstractGeometryObjectExtensionGroup

See 6.7.2.2 Complex Element Substitution.

10.2    kml:MultiGeometry

10.2.1    Structure

<kml:MultiGeometry
 id=“ID [0..1]”
 targetId=“NCName [0..1]”
 anyAttribute=“anySimpleType [0..1]”>
    <kml:ObjectSimpleExtensionGroup>…</kml:ObjectSimpleExtensionGroup> [0..*]
    <kml:AbstractGeometrySimpleExtensionGroup>…
     </kml:AbstractGeometrySimpleExtensionGroup> [0..*]
    <kml:AbstractGeometryObjectExtensionGroup>…
     </kml:AbstractGeometryObjectExtensionGroup> [0..*]
    <kml:AbstractGeometryGroup>…</kml:AbstractGeometryGroup> [0..*]     
    <kml:MultiGeometrySimpleExtensionGroup>…
     </kml:MultiGeometrySimpleExtensionGroup> [0..*]
    <kml:MultiGeometryObjectExtensionGroup>…
     </kml:MultiGeometryObjectExtensionGroup> [0..*]
</kml:MultiGeometry>

10.2.2    Description

This element can be used wherever the following element is referenced:

A container for zero or more geometry elements associated with the same KML feature.

A kml:MultiGeometry element should contain more than one kml:AbstractGeometryGroup element outside of an update context, that is when not a descendant of kml:Update.

10.2.3    Content

    kml:AbstractGeometryGroup

See 10.1 kml:AbstractGeometryGroup.

    kml:AbstractGeometrySimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

    kml:AbstractGeometryObjectExtensionGroup

See 6.7.2.2 Complex Element Substitution.

10.2.4    Example

<Placemark>
  <name>SF Marina Harbor Master</name>
  <visibility>0</visibility>
  <MultiGeometry>
    <LineString>
      <!– north wall –>
      <coordinates>
        -122.4425587930444,37.80666418607323,0
        -122.4428379594768,37.80663578323093,0
      </coordinates>
    </LineString>
    <LineString>
      <!– south wall –>
      <coordinates>
        -122.4425509770566,37.80662588061205,0
        -122.4428340530617,37.8065999493009,0
      </coordinates>
    </LineString>
  </MultiGeometry>
</Placemark>

10.3    kml:Point

10.3.1    Structure

<kml:Point
 id=“ID [0..1]”
 targetId=“NCName [0..1]”
 anyAttribute=“anySimpleType [0..1]”>
    <kml:ObjectSimpleExtensionGroup>…</kml:ObjectSimpleExtensionGroup> [0..*]
    <kml:AbstractGeometrySimpleExtensionGroup>…
     </kml:AbstractGeometrySimpleExtensionGroup> [0..*]
    <kml:AbstractGeometryObjectExtensionGroup>…
     </kml:AbstractGeometryObjectExtensionGroup> [0..*]
    <kml:extrude>…</kml:extrude> [0..1]
    <kml:altitudeMode>…</kml:altitudeModeGroup> [0..1]
    <kml:seaFloorAltitudeMode>…</kml:seaFloorAltitudeMode> [0..1]
    <kml:AltitudeModeSimpleExtensionGroup>…
     </kml:AltitudeModeSimpleExtensionGroup> [0..1]
    <kml:AltitudeModeObjectExtensionGroup>…
     </kml:AltitudeModeObjectExtensionGroup> [0..1]
    <kml:coordinates>…</kml:coordinates> [0..1]
    <kml:PointSimpleExtensionGroup>…</kml:PointSimpleExtensionGroup> [0..*]
    <kml:PointObjectExtensionGroup>…</kml:PointObjectExtensionGroup> [0..*]
</kml:Point>

10.3.2    Description

This element can be used wherever the following element is referenced:

A geographic location defined by a single geodetic longitude, geodetic latitude, and (optional) altitude coordinate tuple.

10.3.3    Content

    kml:extrude

Specifies whether to connect the point to the ground with a line when displayed in the geographic view.

See 10.4 kml:extrude.

    kml:altitudeMode

See 9.20 kml:altitudeMode.

    kml:seaFlooraltitudeMode

See 9.21 kml:seaFloorAltitudeMode.

    kml:AltitudeModeSimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

    kml:AltitudeModeObjectExtensionGroup

See 6.7.2.2 Complex Element Substitution.

    kml:coordinates

    Description

A single coordinate tuple.

    Content

    kml:PointSimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

    kml:PointObjectExtensionGroup

See 6.7.2.2 Complex Element Substitution.

10.3.4    Example

<Point>
  <coordinates>-90.86948943473118,48.25450093195546</coordinates>
</Point>

10.4    kml:extrude

10.4.1    Structure

<kml:extrude>…</kml:extrude>

10.4.2    Description

Specifies whether to connect a geometry to the ground.  To extrude a geometry, the kml:altitudeMode shall be either relativeToGround or absolute, and the altitude component within the kml:coordinates element should be greater than 0 (that is, in the air). The geometry is extruded toward the Earth’s center of mass.

See also 6.3 Geometry Interpolation for 3D Earth Browsers.

10.4.3    Content

10.5    kml:LinearRing

10.5.1    Structure

<kml:LinearRing
 id=“ID [0..1]”
 targetId=“NCName [0..1]”
 anyAttribute=“anySimpleType [0..1]”>
    <kml:ObjectSimpleExtensionGroup>…</kml:ObjectSimpleExtensionGroup> [0..*]
    <kml:AbstractGeometrySimpleExtensionGroup>…
     </kml:AbstractGeometrySimpleExtensionGroup> [0..*]
    <kml:AbstractGeometryObjectExtensionGroup>…
     </kml:AbstractGeometryObjectExtensionGroup> [0..*]
     <kml:extrude>…</kml:extrude> [0..1]
     <kml:tessellate>…</kml:tessellate> [0..1]
     <kml:altitudeMode>…</kml:altitudeModeGroup> [0..1]
     <kml:seaFloorAltitudeMode>…</kml:seaFloorAltitudeMode> [0..1]
     <kml:AltitudeModeSimpleExtensionGroup>…
      </kml:AltitudeModeSimpleExtensionGroup> [0..1]
     <kml:AltitudeModeObjectExtensionGroup>…
      </kml:AltitudeModeObjectExtensionGroup> [0..1]
     <kml:coordinates>…</kml:coordinates> [0..1]
     <kml:altitudeOffset>…</kml:altitudeOffset> [0..1]
      <kml:LinearRingSimpleExtensionGroup>…
      </kml:LinearRingSimpleExtensionGroup> [0..*]
     <kml:LinearRingObjectExtensionGroup>…
      </kml:LinearRingObjectExtensionGroup> [0..*]
</kml:LinearRing>

10.5.2    Description

This element can be used wherever the following element is referenced:

Defines a closed line string that should not cross itself.

kml:extrude, kml:tessellate, kml:altitudeMode and kml:seaFloorAltitudeMode elements should not be specified when kml:LinearRing is used to define a boundary for a kml:Polygon.

10.5.3    Content

    kml:extrude

See 10.4 kml:extrude.

    kml:tessellate

See 10.6 kml:tessellate.

    kml:altitudeMode

See 9.20 kml:altitudeMode.

    kml:seaFlooraltitudeMode

See 9.21 kml:seaFloorAltitudeMode.

    kml:AltitudeModeSimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

    kml:AltitudeModeObjectExtensionGroup

See 6.7.2.2 Complex Element Substitution.

    kml:coordinates

    Description

A list of four or more coordinate tuples where the first and last coordinate tuples must be the same.

    Content

    kml:altitudeOffset

    Description

Modifies how the altitude values are rendered. The value of kml:altitudeOffset shifts the entire geometry up or down as a unit. Units are in meters.

    Content

    kml:LinearRingSimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

    kml:LinearRingObjectExtensionGroup

See 6.7.2.2 Complex Element Substitution.

10.5.4    Example

<kml xmlns=“http://www.opengis.net/kml/2.2”>
<Placemark>
  <name>LinearRing.kml</name>
  <Polygon>
    <outerBoundaryIs>
      <LinearRing>
        <coordinates>
          -122.365662,37.826988,0
          -122.365202,37.826302,0
          -122.364581,37.82655,0
          -122.365038,37.827237,0
          -122.365662,37.826988,0
        </coordinates>
      </LinearRing>
    </outerBoundaryIs>
  </Polygon>
</Placemark>
</kml>

10.6    kml:tessellate

10.6.1    Structure

<kml:tessellate>…</kml:tessellate>

10.6.2    Description

Specifies whether to drape a geometry over the terrain.  A value of 1 or true specifies to drape; a value of 0 or false specifies not to drape.  To enable tessellation, the value for kml:altitudeMode shall be clampToGround.

See also 6.3 Geometry Interpolation for 3D Earth Browsers.

10.6.3    Content

10.7    kml:LineString

10.7.1    Structure

<kml:LineString
 id=“ID [0..1]”
 targetId=“NCName [0..1]”
 anyAttribute=“anySimpleType [0..1]”>
    <kml:ObjectSimpleExtensionGroup>…</kml:ObjectSimpleExtensionGroup> [0..*]
    <kml:AbstractGeometrySimpleExtensionGroup>…
     </kml:AbstractGeometrySimpleExtensionGroup> [0..*]
    <kml:AbstractGeometryObjectExtensionGroup>…
     </kml:AbstractGeometryObjectExtensionGroup> [0..*]
    <kml:extrude>…</kml:extrude> [0..1]
    <kml:tessellate>…</kml:tessellate> [0..1]
    <kml:altitudeMode>…</kml:altitudeModeGroup> [0..1]
    <kml:seaFloorAltitudeMode>…</kml:seaFloorAltitudeMode> [0..1]
    <kml:AltitudeModeSimpleExtensionGroup>…
     </kml:AltitudeModeSimpleExtensionGroup> [0..1]
    <kml:AltitudeModeObjectExtensionGroup>…
     </kml:AltitudeModeObjectExtensionGroup> [0..1]
    <kml:coordinates>…</kml:coordinates> [0..1]
    <kml:altitudeOffset>…</kml:altitudeOffset> [0..1]
     <kml:LineStringSimpleExtensionGroup>…
     </kml:LineStringSimpleExtensionGroup> [0..*]
    <kml:LineStringObjectExtensionGroup>…
     </kml:LineStringObjectExtensionGroup> [0..*]
</kml:LineString>

10.7.2    Description

This element can be used wherever the following element is referenced:

Defines a list of one or more contiguous line segments.

10.7.3    Content

    kml:extrude

Specifies whether to extend the kml:LineString to the ground when displayed in the geographic view.  When a kml:LineString is extruded, the points of each line segment are extended to the terrain toward the Earth’s center of mass, forming a polygon resembling a wall or fence.

See 10.4 kml:extrude.

    kml:tessellate

See 10.6 kml:tessellate.

    kml:altitudeMode

See 9.20 kml:altitudeMode.

    kml:seaFlooraltitudeMode

See 9.21 kml:seaFloorAltitudeMode.

    kml:AltitudeModeSimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

    kml:AltitudeModeObjectExtensionGroup

See 6.7.2.2 Complex Element Substitution.

    kml:coordinates

    Description

Two or more coordinate tuples.

    Content

    kml:altitudeOffset

See 10.5.3.8 kml:altitudeOffset.

    kml:LineStringSimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

    kml:LineStringObjectExtensionGroup

See 6.7.2.2 Complex Element Substitution.

10.7.4    Example

<kml xmlns=“http://www.opengis.net/kml/2.2”>
<Document>
  <name>LineString.kml</name>
  <open>1</open>
  <LookAt>
    <longitude>-122.36415</longitude>
    <latitude>37.824553</latitude>
    <altitude>0</altitude>
    <range>150</range>
    <tilt>50</tilt>
    <heading>0</heading>
  </LookAt>
  <Placemark>
    <name>unextruded</name>
    <LineString>
      <extrude>0</extrude>
      <tessellate>1</tessellate>
      <coordinates>
        -122.364383,37.824664,0 -122.364152,37.824322,0
      </coordinates>
    </LineString>
  </Placemark>
  <Placemark>
    <name>extruded</name>
    <LineString>
      <extrude>1</extrude>
      <tessellate>1</tessellate>
      <altitudeMode>relativeToGround</altitudeMode>
      <coordinates>
        -122.364167,37.824787,50 -122.363917,37.824423,50
      </coordinates>
    </LineString>
  </Placemark>
</Document>
</kml>

10.8    kml:Polygon

10.8.1    Structure

<kml:Polygon
 id=“ID [0..1]”
 targetId=“NCName [0..1]”
 anyAttribute=“anySimpleType [0..1]”>
    <kml:ObjectSimpleExtensionGroup>…</kml:ObjectSimpleExtensionGroup> [0..*]
    <kml:AbstractGeometrySimpleExtensionGroup>…
     </kml:AbstractGeometrySimpleExtensionGroup> [0..*]
    <kml:AbstractGeometryObjectExtensionGroup>…
     </kml:AbstractGeometryObjectExtensionGroup> [0..*]
    <kml:extrude>…</kml:extrude> [0..1]
    <kml:tessellate>…</kml:tessellate> [0..1]
    <kml:altitudeMode>…</kml:altitudeModeGroup> [0..1]
    <kml:seaFloorAltitudeMode>…</kml:seaFloorAltitudeMode> [0..1]
    <kml:AltitudeModeSimpleExtensionGroup>…
     </kml:AltitudeModeSimpleExtensionGroup> [0..1]
    <kml:AltitudeModeObjectExtensionGroup>…
     </kml:AltitudeModeObjectExtensionGroup> [0..1]
    <kml:outerBoundaryIs>…</kml:outerBoundaryIs> [0..1]
    <kml:innerBoundaryIs>…</kml:innerBoundaryIs> [0..*]
    <kml:PolygonSimpleExtensionGroup>…
     </kml:PolygonSimpleExtensionGroup> [0..*]
    <kml:PolygonObjectExtensionGroup>…
     </kml:PolygonObjectExtensionGroup> [0..*]
</kml:Polygon>

10.8.2    Description

This element can be used wherever the following element is referenced:

A kml:Polygon shall have an outer boundary ring outside of an update context, that is when not a descendant of kml:Update.  It may have 0 or more inner boundary rings.  Each ring is defined by a kml:LinearRing.  It is advised that the rings not cross each other.

10.8.3    Content

    kml:extrude

    Description

Specifies whether to connect the kml:Polygon to the ground when displayed in the geographic view.

When a kml:Polygon is extruded, each boundary point is extended to the terrain toward the earth’s center of mass, which gives the appearance of a building or a box.

Only the kml:Polygon boundary is extruded, not the kml:Polygon interior (for example, a rectangle turns into a box with five faces).

See 10.4 kml:extrude.

    kml:tessellate

See 10.6 kml:tessellate.

    kml:altitudeMode

See 9.20 kml:altitudeMode.

    kml:seaFlooraltitudeMode

See 9.21 kml:seaFloorAltitudeMode.

    kml:AltitudeModeSimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

    kml:AltitudeModeObjectExtensionGroup

See 6.7.2.2 Complex Element Substitution.

    kml:outerBoundaryIs

Specifies the exterior boundary of the kml:Polygon defined by a kml:LinearRing element.

See 10.5 kml:LinearRing.

    kml:innerBoundaryIs

Specifies an inner boundary of the kml:Polygon defined by a kml:LinearRing element.

See 10.5 kml:LinearRing.

    kml:PolygonSimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

    kml:PolygonObjectExtensionGroup

See 6.7.2.2 Complex Element Substitution.

10.8.4    Example

<kml xmlns=“http://www.opengis.net/kml/2.2”>
<Document>
  <name>Polygon.kml</name>
  <open>0</open>
  <Placemark>
    <name>hollow box</name>
    <Polygon>
      <extrude>1</extrude>
      <altitudeMode>relativeToGround</altitudeMode>
      <outerBoundaryIs>
        <LinearRing>
          <coordinates>
            -122.366278,37.818844,30
            -122.365248,37.819267,30
            -122.365640,37.819861,30
            -122.366669,37.819429,30
            -122.366278,37.818844,30
          </coordinates>
        </LinearRing>
      </outerBoundaryIs>
      <innerBoundaryIs>
        <LinearRing>
          <coordinates>
            -122.366212,37.818977,30
            -122.365424,37.819294,30
            -122.365704,37.819731,30
            -122.366488,37.819402,30
            -122.366212,37.818977,30
          </coordinates>
        </LinearRing>
      </innerBoundaryIs>
    </Polygon>
  </Placemark>
</Document>
</kml>

10.9    kml:Model

10.9.1    Structure

<kml:Model
 id=“ID [0..1]”
 targetId=“NCName [0..1]”
 anyAttribute=“anySimpleType [0..1]”>
    <kml:ObjectSimpleExtensionGroup>…</kml:ObjectSimpleExtensionGroup> [0..*]
    <kml:AbstractGeometrySimpleExtensionGroup>…
     </kml:AbstractGeometrySimpleExtensionGroup> [0..*]
    <kml:AbstractGeometryObjectExtensionGroup>…
     </kml:AbstractGeometryObjectExtensionGroup> [0..*]
    <kml:altitudeMode>…</kml:altitudeModeGroup> [0..1]
    <kml:seaFloorAltitudeMode>…</kml:seaFloorAltitudeMode> [0..1]
    <kml:AltitudeModeSimpleExtensionGroup>…
     </kml:AltitudeModeSimpleExtensionGroup> [0..1]
    <kml:AltitudeModeObjectExtensionGroup>…
     </kml:AltitudeModeObjectExtensionGroup> [0..1]
    <kml:Location>…</kml:Location> [0..1]
    <kml:Orientation>…</kml:Orientation> [0..1]
    <kml:Scale>…</kml:Scale> [0..1]
    <kml:Link>…</kml:Link> [0..1]
    <kml:ResourceMap>…</kml:ResourceMap> [0..1]
    <kml:ModelSimpleExtensionGroup>…
     </kml:ModelSimpleExtensionGroup> [0..*]
    <kml:ModelObjectExtensionGroup>…
     </kml:ModelObjectExtensionGroup> [0..*]
</kml:Model>

10.9.2    Description

This element can be used wherever the following element is referenced:

Specifies the location and orientation of a textured 3D object resource.  The structure and appearance of the textured 3D object are not defined in this specification.

A local earth-fixed frame (X’-Y’-Z’) is defined as follows.

The Z’-axis is defined by the local surface normal (local to the tangent plane at the location point), the Y’-axis is defined by the intersection of the meridian plane defined by the longitude of the location point, and the tangent plane, and the X’-axis is chosen so that X’-Y’-Z’ form a right handed orthogonal frame.

A model-fixed frame (X-Y-Z) is defined as follows.  The Y-axis is +ve through the front of the model.  The Z-axis is +ve through the top of the model and the X-axis is chosen so that X-Y-Z forms a right handed orthogonal frame.

The orientation of the model is then defined by the orientation of the model-fixed frame (X-Y-Z) relative to the local earth-fixed frame (X’-Y’-Z’) as follows:

Roll – rotation about the model Y-axis

Tilt – rotation about the model X-axis

Heading – Rotation about the model Z-axis

kml:Model:

•   shall contain kml:Link and kml:Location elements;
•   shall contain a kml:ResourceMap element that has a kml:Alias element for each texture file, if the target resource has texture files;

outside of an update context, that is when not a descendant of kml:Update.

10.9.3    Content

    kml:altitudeMode

See 9.20 kml:altitudeMode.

    kml:seaFlooraltitudeMode

See 9.21 kml:seaFloorAltitudeMode.

    kml:AltitudeModeSimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

    kml:AltitudeModeObjectExtensionGroup

See 6.7.2.2 Complex Element Substitution.

    kml:Location

    Description

Specifies the coordinates of the kml:Model’s origin.

See 10.10 kml:Location.

    kml:Orientation

    Description

Specifies the orientation of the model coordinate axes relative to a local earth-fixed reference frame.

See 10.11 kml:Orientation.

    kml:Scale

    Description

Scales a model along the x, y, and z axes in the model’s coordinate space.

See 10.12 kml:Scale.

    kml:Link

    Description

Specifies the location of a textured 3D object resource such as a COLLADA file.

See 13.1 kml:Link, kml:Icon (kml:LinkType).

    kml:ResourceMap

    Description

Specifies 0 or more kml:Alias elements, each of which is a mapping for the texture file path from the original textured 3D object file to the KML or KMZ resource that contains the kml:Model.

See 10.13 kml:ResourceMap.

    kml:ModelSimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

    kml:ModelObjectExtensionGroup

See 6.7.2.2 Complex Element Substitution.

10.9.4    Example

<Model id=“khModel543”>
  <altitudeMode>relativeToGround</altitudeMode>
  <Location>
    <longitude>39.55375305703105</longitude>
    <latitude>-118.9813220168456</latitude>
    <altitude>1223</altitude>
  </Location>
  <Orientation>
    <heading>45.0</heading>
    <tilt>10.0</tilt>
    <roll>0.0</roll>
  </Orientation>
  <Scale>
    <x>1.0</x>
    <y>1.0</y>
    <z>1.0</z>
  </Scale>
  <Link>
    <href>house.dae</href>
  </Link>
  <ResourceMap>
    <Alias>
      <targetHref>../files/CU-Macky—Center-StairsnoCulling.jpg</targetHref>
      <sourceHref>CU-Macky—Center-StairsnoCulling.jpg</sourceHref>
    </Alias>
    <Alias>
      <targetHref>../files/CU-Macky-4sideturretnoCulling.jpg</targetHref>
      <sourceHref>CU-Macky-4sideturretnoCulling.jpg</sourceHref>
    </Alias>
    <Alias>
      <targetHref>../files/CU-Macky-Back-NorthnoCulling.jpg</targetHref>
      <sourceHref>CU-Macky-Back-NorthnoCulling.jpg</sourceHref>
    </Alias>
  </ResourceMap>
</Model>

10.10    kml:Location

10.10.1    Structure

<kml:Location
 id=“ID [0..1]”
 targetId=“NCName [0..1]”
 anyAttribute=“anySimpleType [0..1]”>
    <kml:ObjectSimpleExtensionGroup>…</kml:ObjectSimpleExtensionGroup> [0..*]
    <kml:longitude>…</kml:longitude> [0..1]
    <kml:latitude>…</kml:latitude> [0..1]
    <kml:altitude>…</kml:altitude> [0..1]
    <kml:LocationSimpleExtensionGroup>…</kml:LocationSimpleExtensionGroup> [0..*]
    <kml:LocationObjectExtensionGroup>…</kml:LocationObjectExtensionGroup> [0..*]
</kml:Location>

10.10.2    Description

This element can be used wherever the following element is referenced:

Specifies the coordinates of a location.

A kml:Location element shall contain the kml:longitude, kml:latitude child elements outside of an update context, that is when not a descendant of kml:Update.

10.10.3    Content

    kml:latitude

    Description

Geodetic latitude of origin in decimal degrees.

    Content

    kml:longitude

    Description

Geodetic longitude of origin in decimal degrees.

    Content

    kml:altitude

    Description

Altitude of origin measured in meters and interpreted according to kml:altitudeMode.

    Content

    kml:LocationSimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

    kml:LocationObjectExtensionGroup

See 6.7.2.2 Complex Element Substitution.

10.10.4    Example

<Location>
  <longitude>39.55375305703105</longitude> 
  <latitude>-118.9813220168456</latitude>
  <altitude>1223</altitude>
</Location>

10.11    kml:Orientation

10.11.1    Structure

<kml:Orientation
 id=“ID [0..1]”
 targetId=“NCName [0..1]”
 anyAttribute=“anySimpleType [0..1]”>
    <kml:ObjectSimpleExtensionGroup>…</kml:ObjectSimpleExtensionGroup> [0..*]
    <kml:heading>…</kml:heading> [0..1]
    <kml:tilt>…</kml:tilt> [0..1]
    <kml:roll>…</kml:roll> [0..1]
    <kml:OrientationSimpleExtensionGroup>…
     </kml:OrientationSimpleExtensionGroup> [0..*]
    <kml:OrientationObjectExtensionGroup>…
     </kml:OrientationObjectExtensionGroup> [0..*]
</kml:Orientation>

10.11.2    Description

This element can be used wherever the following element is referenced:

Specifies the orientation of the model coordinate axes relative to a local earth-fixed reference frame.

kml:Orientation should contain at least one child element outside of an update context, that is when not a descendant of kml:Update.  It is advised that kml:heading, kml:tile and kml:roll all be specified.

10.11.3    Content

    kml:heading

    Description

Rotation about the z axis.  A value of 0 equals North.  A positive rotation is counter clockwise around the positive z axis, looking along the z-axis away from the origin, and specified in decimal degrees from 0 to ±180.

    Content

    kml:tilt

    Description

Rotation about the x axis.  A positive rotation is counter clockwise around the positive x axis and specified in decimal degrees from 0 to ±180.

    Content

    kml:roll

    Description

Rotation about the y axis.  A positive rotation is counter clockwise around the positive y axis and specified in decimal degrees from 0 to ±180.

    Content

    kml:OrientationSimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

    kml:OrientationObjectExtensionGroup

See 6.7.2.2 Complex Element Substitution.

10.11.4    Defining Orientation

This diagram illustrates the initial orientation of a model’s axes:

10.11.5    Example

<Orientation>
  <heading>45.0</heading>
  <tilt>10.0</tilt>
  <roll>0.0</roll>
</Orientation>

10.12    kml:Scale

10.12.1    Structure

<kml:Scale
 id=“ID [0..1]”
 targetId=“NCName [0..1]”
 anyAttribute=“anySimpleType [0..1]”>
    <kml:ObjectSimpleExtensionGroup>…</kml:ObjectSimpleExtensionGroup> [0..*]
    <kml:x>…</kml:x> [0..1]
    <kml:y>…</kml:y> [0..1]
    <kml:z>…</kml:z> [0..1]
    <kml:ScaleSimpleExtensionGroup>…</kml:ScaleSimpleExtensionGroup> [0..*]
    <kml:ScaleObjectExtensionGroup>…</kml:ScaleObjectExtensionGroup> [0..*]
</kml:Scale>

10.12.2    Description

This element can be used wherever the following element is referenced:

Scales a model along the x, y, and z axes in the model’s coordinate space.

kml:Scale should contain at least one child element outside of an update context, that is when not a descendant of kml:Update.  It is advised that kml:x, kml:y, and kml:z all be specified.

10.12.3    Content

    x

    Description

Scale factor along x axis.

    Content

    y

    Description

Scale factor along y axis.

    Content

    z

    Description

Scale factor along z axis.

    Content

    kml:ScaleSimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

    kml:ScaleObjectExtensionGroup

See 6.7.2.2 Complex Element Substitution.

10.12.4    Example

<Scale>
   <x>2.5</x>
   <y>2.5</y>
   <z>3.5</z>
 </Scale>

10.13    kml:ResourceMap

10.13.1    Structure

<kml:ResourceMap
 id=“ID [0..1]”
 targetId=“NCName [0..1]”
 anyAttribute=“anySimpleType [0..1]”>
    <kml:ObjectSimpleExtensionGroup>…</kml:ObjectSimpleExtensionGroup> [0..*]
    <kml:Alias>…</kml:Alias> [0..*]
    <kml:ResourceMapSimpleExtensionGroup>…
     </kml:ResourceMapSimpleExtensionGroup> [0..*]
    <kml:ResourceMapObjectExtensionGroup>…
     </kml:ResourceMapObjectExtensionGroup> [0..*]
</kml:ResourceMap>

10.13.2    Description

This element can be used wherever the following element is referenced:

Should specify at least one or more kml:Alias elements outside of an update context, that is when not a descendant of kml:Update.  Each kml:Alias element is a mapping for the texture file path from the original textured 3D object file to the KML or KMZ resource that contains the kml:Model.  This element allows texture files to be moved and renamed without having to update the original textured 3D object file that references those textures.  One kml:ResourceMap element can contain multiple mappings from different source textured object files into the same target resource.

Each child kml:Alias element should have a unique child kml:sourceHref element .

10.13.3    Content

    kml:Alias

See 10.14 kml:Alias.

    kml:ResourceMapSimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

    kml:ResourceMapObjectExtensionGroup

See 6.7.2.2 Complex Element Substitution.

10.14    kml:Alias

10.14.1    Structure

<kml:Alias
 id=“ID [0..1]”
 targetId=“NCName [0..1]”
 anyAttribute=“anySimpleType [0..1]”>
    <kml:ObjectSimpleExtensionGroup>…</kml:ObjectSimpleExtensionGroup> [0..*]
    <kml:targetHref>…</kml:targetHref> [0..1]
    <kml:sourceHref>…</kml:sourceHref> [0..1]
    <kml:AliasSimpleExtensionGroup>…</kml:AliasSimpleExtensionGroup> [0..*]
    <kml:AliasObjectExtensionGroup>…</kml:AliasObjectExtensionGroup> [0..*]
</kml:Alias>

10.14.2    Description

This element can be used wherever the following element is referenced:

Contains a mapping from kml:sourceHref to kml:targetHref.  Both should be specified ouside of an update context, that is when not a descendant of kml:Update.

10.14.3    Content

    targetHref

    Description

Specifies the textured 3D object file to be fetched by an earth browser.  This reference can be a relative reference to an image file within a KMZ file, or it can be an absolute reference to the file (for example, a URL).

    Content

    sourceHref

    Description

Specifies the path for the texture file within the textured 3D object.

    Content

    kml:AliasSimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

    kml:AliasObjectExtensionGroup

See 6.7.2.2 Complex Element Substitution.

10.14.4    Example

<Alias>
  <targetHref>../images/foo.jpg</targetHref>
  <sourceHref>in-geometry-file/foo.jpg</sourceHref>
</Alias>

10.15    kml:Track

10.15.1    Structure

<kml:Track
 id=“ID [0..1]” 
 targetId=“NCName [0..1]”
 anyAttribute=“anySimpleType [0..1]”> 
    <kml:ObjectSimpleExtensionGroup>…
    </kml:ObjectSimpleExtensionGroup> [0..*]
    <kml:AbstractGeometrySimpleExtensionGroup>…
    </kml:AbstractGeometrySimpleExtensionGroup> [0..*]   
   <kml:AbstractGeometryObjectExtensionGroup>…
    </kml:AbstractGeometryObjectExtensionGroup> [0..*]
   <kml:extrude>…</kml:extrude> [0..1]
    <kml:tessellate>…</kml:tessellate> [0..1]
    <kml:altitudeMode>…</kml:altitudeModeGroup> [0..1]
   <kml:seaFloorAltitudeMode>…</kml:seaFloorAltitudeMode> [0..1]
   <kml:AltitudeModeSimpleExtensionGroup>…
    </kml:AltitudeModeSimpleExtensionGroup> [0..1]
   <kml:AltitudeModeObjectExtensionGroup>…
    </kml:AltitudeModeObjectExtensionGroup> [0..1]
   <kml:when>…</kml:when> [0..*]
    <kml:coord>…</kml:coord> [0..*]
    <kml:angles>…</kml:angles> [0..*]
    <kml:Model>…</kml:Model> [0..1]
    <kml:ExtendedData>…</kml:ExtendedData> [0..1]
    <kml:TrackSimpleExtensionGroup>…</kml:TrackSimpleExtensionGroup> [0..*]
    <kml:TrackObjectExtensionGroup>…</kml:TrackObjectExtensionGroup> [0..*]
</kml:Track>

10.15.2    Description

A kml:Track element captures the path of a moving object over a specified period of time. Either an icon or a model can be used to visually represent the time-stamped positions of the track. The time positions of a kml:Track are captured in an array of kml:when elements and the space coordinates are captured in an equal-length array of kml:coord elements. Additional data arrays of equal-length containing: angle/orientation data (kml:angles) or arbitrary data values (kml:ExtendedData) may accompany the kml:when and kml:coord arrays. Note that the time-varying properties of a kml:Track (kml:when, kml:coord, kml:angles) may occur in any order. However, these elements must be treated as an implicit, parallel array in which document order is significant. That is, the property values that correspond to the same index are implicitly the fields of a single tuple: (kml:when[i], kml:coord[i], kml:angles[i]).  

A kml:Track is essentially a univariate or multivariate time-series (using the terminology of statistics) with either a uniform or non-uniform sampling. If the time values of the kml:when array are at regular intervals, the sampling is uniform, otherwise the sampling is non-uniform. If the kml:whenarray is accompanied by more than one other data array (e.g. kml:coord, kml:angles, and kml:ExtendedData arrays), the time-series is multivariate, otherwise if accompanied by a single data array (e.g. kml:coord) the time-series is univariate.

Note: KML versions prior to 2.3 allowed a user to associate a time element with any KML Feature (placemark, ground overlay, etc.). However, only one time element could be associated with a given Feature. The kml:Track provides a compact encoding of time series data by associating a single object with multiple time elements. The kml:Track element also provides additional functionality than the earlier mechanism, for example, interpolation of position along the track. With this new functioality, browser implementations can display graphs of elevation and speed (plus additional data, if provided) for the object over time.

    Missing Data

Missing data values for positions on the track, can be accommodated by empty kml:coord(i.e. <kml:coord></kml:coord>) or kml:angles values. Any element except kml:when can be empty and may be used to represent missing data to balance the size of the kml:when, kml:coord, and kml:anglesarrays, since the data array sizes must be equal. Missing numerical data, for example represented by an empty kml:coord or kml:angles, can be estimated by linear interpolation between two well-specified data points nearby. Such interpolation can also be applied to missing numerical data arrays in kml:ExtendedData for a track.

10.15.3    Content

    kml:extrude

See 10.4 kml:extrude.

    kml:tessellate

See 10.6 kml:tessellate.

    kml:altitudeMode

See 9.20 kml:altitudeMode.

    kml:seaFlooraltitudeMode

See 9.21 kml:seaFloorAltitudeMode.

    kml:AltitudeModeSimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

    kml:AltitudeModeObjectExtensionGroup

See 6.7.2.2 Complex Element Substitution.

    kml:when

    Description

Specifies a time value that corresponds to a spatial location(specified in by the kml:coordelement). The number of kml:when elements in a kml:Track must be equal to the number of kml:coord elements (and kml:angles elements, if included).

    Content

    kml:coord

    Description

Specifies a coordinate value consisting of three single-space delimited floating point values for longitude, latitude, and altitude, with (no comma separators). For example:

<kml:coord>-122.207881 37.371915 156.000000</kml:coord>

Note that the syntax for the kml:coord element is different from kml:coordinates, which uses comma separators between the longitude, latitude, and altitude components.

    Content

    kml:angles

    Description

Specifies additional heading, tilt, and roll values to the icon or model for each time/position within the track. The three floating point values are listed without comma separators and represent degrees of rotation. If kml:anglesis not specified, then the heading, tilt, and roll values of the object can be interpolated from its track.The number of kml:angles elements specified should equal the number of kml:when and kml:coord elements. An example encoding of kml:angles is as follows:

  <kml:angles>45.54676 66.2342 77.0</kml:angles>

    Content

    kml:Model

If specified, the kml:Model replaces the point icon used to indicate the current position on the track. When a kml:Model is specified within a kml:Track, the child elements of kml:Model function as follows:

•   The kml:Location element is ignored.
•   The kml:altitudeMode element is ignored.
•   The kml:Orientation value is combined with the orientation of the track as follows. First, the kml:Orientation rotation is applied, which brings the model from its local (x, y, z) coordinate system to a right-side-up, north-facing orientation. Next, a rotation is applied that corresponds to the interpolation of the kml:angles values that affect the heading, tilt, and roll of the model as it moves along the track. If no angles are specified, the heading and tilt are inferred from the movement of the model.

See 10.9 kml:Model.

    kml:ExtendedData

Custom data elements may also be defined in the instance by kml:Schema and may be useful to associate with each time/position on a track. For example, tracks representing hikes or bicycle rides could include data for heart rate, cadence, and power, as shown in 10.15.4.2 Example 2 – Extended Data Arrays. In kml:Schema, a kml:SimpleArrayField is defined for each custom data type. Then, for each data type, a kml:SimpleArrayData element in included containing a kml:value array corresponding to, and of equal length as, the kml:when and kml:coord arrays of the track.

See 9.3 kml:ExtendedData.

    kml:TrackSimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

    kml:TrackObjectExtensionGroup

See 6.7.2.2 Complex Element Substitution.

10.15.4    Examples

The first example shows how to create parallel “arrays” of values for kml:when and kml:coord. The number of time and position values must be equal.

    Example 1 – Basic Time and Position Arrays

<kml xmlns=“http://www.opengis.net/kml/2.2”>
  <Folder>
    <Placemark>
      <Track>
        <when>2010-05-28T02:02:09Z</when>
        <when>2010-05-28T02:02:35Z</when>
        <when>2010-05-28T02:02:44Z</when>
        <when>2010-05-28T02:02:53Z</when>
        <when>2010-05-28T02:02:54Z</when>
        <when>2010-05-28T02:02:55Z</when>
        <when>2010-05-28T02:02:56Z</when>
        <coord>-122.207881 37.371915 156.000000</coord>
        <coord>-122.205712 37.373288 152.000000</coord>
        <coord>-122.204678 37.373939 147.000000</coord>
        <coord>-122.203572 37.374630 142.199997</coord>
        <coord>-122.203451 37.374706 141.800003</coord>
        <coord>-122.203329 37.374780 141.199997</coord>
        <coord>-122.203207 37.374857 140.199997</coord>
      </Track>
    </Placemark>
  </Folder>
</kml>

    Example 2 – Extended Data Arrays

The boldface type in this example highlights the elements used to define and specify custom data for a bike ride. The custom data fields are internally named heartrate, cadence, and power. The kml:Schema element specifies an additional display name (using kml:displayName) for each set of values (Heart Rate, Cadence, and Power) and specifies the data type for each new field (xsd:int, xsd:int, and xsd:float, respectively).

This example provides a richer presentation of a track, with custom icons and separate icon and line styles for highlight and normal modes. Note, however, that the example only demonstrates seven sets of data values. The original example includes tens of thousands of values (data courtesy of Sean Broeder). This data was collected with a Garmin Edge 705 with associated heart rate monitor and power meter.

<kml xmlns=“http://www.opengis.net/kml/2.2”>
   <Document>
     <name>GPS record of bike ride</name>
 
     <!– Normal track style –>
     <LookAt>
       <TimeSpan>
         <begin>2010-05-28T02:02:09Z</begin>
         <end>2010-05-28T02:02:56Z</end>
       </TimeSpan>
       <longitude>-122.205544</longitude>
       <latitude>37.373386</latitude>
       <range>1300.000000</range>
     </LookAt>
     <Style id=“track_n”>
       <IconStyle>
         <scale>.5</scale>
         <Icon>
           <href>http://earth.google.com/images/kml-icons/track-directional/track-none.png</href>
         </Icon>
       </IconStyle>
       <LabelStyle>
         <scale>0</scale>
       </LabelStyle>
 
     </Style>
     <!– Highlighted track style –>
     <Style id=“track_h”>
       <IconStyle>
         <scale>1.2</scale>
         <Icon>
           <href>http://earth.google.com/images/kml-icons/track-directional/track-none.png</href>
         </Icon>
       </IconStyle>
     </Style>
     <StyleMap id=“track”>
       <Pair>
         <key>normal</key>
         <styleUrl>#track_n</styleUrl>
       </Pair>
       <Pair>
         <key>highlight</key>
         <styleUrl>#track_h</styleUrl>
       </Pair>
     </StyleMap>
     <!– Normal multiTrack style –>
     <Style id=“multiTrack_n”>
       <IconStyle>
         <Icon>
           <href>http://earth.google.com/images/kml-icons/track-directional/track-0.png</href>
         </Icon>
       </IconStyle>
       <LineStyle>
         <color>99ffac59</color>
         <width>6</width>
       </LineStyle>
 
     </Style>
     <!– Highlighted multiTrack style –>
     <Style id=“multiTrack_h”>
       <IconStyle>
         <scale>1.2</scale>
         <Icon>
           <href>http://earth.google.com/images/kml-icons/track-directional/track-0.png</href>
         </Icon>
       </IconStyle>
       <LineStyle>
         <color>99ffac59</color>
         <width>8</width>
       </LineStyle>
     </Style>
     <StyleMap id=“multiTrack”>
       <Pair>
         <key>normal</key>
         <styleUrl>#multiTrack_n</styleUrl>
       </Pair>
       <Pair>
         <key>highlight</key>
         <styleUrl>#multiTrack_h</styleUrl>
       </Pair>
     </StyleMap>
     <!– Normal waypoint style –>
     <Style id=“waypoint_n”>
       <IconStyle>
         <Icon>
           <href>http://maps.google.com/mapfiles/kml/pal4/icon61.png</href>
         </Icon>
       </IconStyle>
     </Style>
     <!– Highlighted waypoint style –>
     <Style id=“waypoint_h”>
       <IconStyle>
         <scale>1.2</scale>
         <Icon>
           <href>http://maps.google.com/mapfiles/kml/pal4/icon61.png</href>
         </Icon>
       </IconStyle>
     </Style>
     <StyleMap id=“waypoint”>
       <Pair>
         <key>normal</key>
         <styleUrl>#waypoint_n</styleUrl>
       </Pair>
       <Pair>
         <key>highlight</key>
         <styleUrl>#waypoint_h</styleUrl>
       </Pair>
     </StyleMap>
     <Style id=“lineStyle”>
       <LineStyle>
         <color>99ffac59</color>
         <width>6</width>
       </LineStyle>
     </Style>
     <Schema id=“schema”>
       <SimpleArrayField name=“heartrate” type=“xsd:int”>
         <displayName>Heart Rate</displayName>
       </SimpleArrayField>
       <SimpleArrayField name=“cadence” type=“xsd:int”>
         <displayName>Cadence</displayName>
       </SimpleArrayField>
       <SimpleArrayField name=“power” type=“xsd:float”>
         <displayName>Power</displayName>
       </SimpleArrayField>
     </Schema>
     <Folder>
       <name>Tracks</name>
       <Placemark>
         <name>2010-05-28T01:16:35.000Z</name>
         <styleUrl>#multiTrack</styleUrl>
         <Track>
           <when>2010-05-28T02:02:09Z</when>
           <when>2010-05-28T02:02:35Z</when>
           <when>2010-05-28T02:02:44Z</when>
           <when>2010-05-28T02:02:53Z</when>
           <when>2010-05-28T02:02:54Z</when>
           <when>2010-05-28T02:02:55Z</when>
           <when>2010-05-28T02:02:56Z</when>
           <coord>-122.207881 37.371915 156.000000</coord>
           <coord>-122.205712 37.373288 152.000000</coord>
           <coord>-122.204678 37.373939 147.000000</coord>
           <coord>-122.203572 37.374630 142.199997</coord>
           <coord>-122.203451 37.374706 141.800003</coord>
           <coord>-122.203329 37.374780 141.199997</coord>
           <coord>-122.203207 37.374857 140.199997</coord>
           <ExtendedData>
             <SchemaData schemaUrl=“#schema”>
               <SimpleArrayData name=“cadence”>
                 <value>86</value>
                 <value>103</value>
                 <value>108</value>
                 <value>113</value>
                 <value>113</value>
                 <value>113</value>
                 <value>113</value>
               </SimpleArrayData>
               <SimpleArrayData name=“heartrate”>
                 <value>181</value>
                 <value>177</value>
                 <value>175</value>
                 <value>173</value>
                 <value>173</value>
                 <value>173</value>
                 <value>173</value>
               </SimpleArrayData>
               <SimpleArrayData name=“power”>
                 <value>327.0</value>
                 <value>177.0</value>
                 <value>179.0</value>
                 <value>162.0</value>
                 <value>166.0</value>
                 <value>177.0</value>
                 <value>183.0</value>
               </SimpleArrayData>
             </SchemaData>
           </ExtendedData>
        </Track>
       </Placemark>
     </Folder>
   </Document>
 </kml>

10.16    kml:MultiTrack

10.16.1    Structure

<kml:MultiTrack
 id=“ID [0..1]” 
  targetId=“NCName [0..1]”
 anyAttribute=“anySimpleType [0..1]”> 
    <kml:ObjectSimpleExtensionGroup>…</kml:ObjectSimpleExtensionGroup> [0..*]
    <kml:AbstractGeometrySimpleExtensionGroup>…
    </kml:AbstractGeometrySimpleExtensionGroup> [0..*]    
   <kml:AbstractGeometryObjectExtensionGroup>…
    </kml:AbstractGeometryObjectExtensionGroup> [0..*]
    <kml:altitudeMode>…</kml:altitudeModeGroup> [0..1]
    <kml:seaFloorAltitudeMode>…</kml:seaFloorAltitudeMode> [0..1]
    <kml:AltitudeModeSimpleExtensionGroup>…
     </kml:AltitudeModeSimpleExtensionGroup> [0..1]
    <kml:AltitudeModeObjectExtensionGroup>…
     </kml:AltitudeModeObjectExtensionGroup> [0..1]
    <kml:interpolate>…</kml:interpolate> [0..1]
    <kml:Track>…</kml:Track> [0..*]
    <kml:MultiTrackSimpleExtensionGroup>…
    </kml:MultiTrackSimpleExtensionGroup> [0..*]
    <kml:MultiTrackObjectExtensionGroup>…
    </kml:MultiTrackObjectExtensionGroup> [0..*]
</kml:MultiTrack>

10.16.2    Description

A kml:MultiTrack element is used to collect multiple tracks into one conceptual unit with an associated icon (or model) that moves along the track. The kml:MultiTrack encoding is optimized for multiple tracks for the same real-world object.

10.16.3    Content

    kml:altitudeMode

See 9.20 kml:altitudeMode.

    kml:seaFlooraltitudeMode

See 9.21 kml:seaFloorAltitudeMode.

    kml:AltitudeModeSimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

    kml:AltitudeModeObjectExtensionGroup

See 6.7.2.2 Complex Element Substitution.

    kml:interpolate

    Description

Specifies a boolean value indicating whether to interpolate between the tracks in a multi-track or not. If the boolean value is 0 (or ‘false’), then the point icon or model stops at the end of one track and skips to the start of the next one. For example, if a single placemark is needed to represent your path over two separate days, and the GPS unit used to record position was turned off for four hours during this period, a discontinuity between the points where the unit was turned off and then on again will be captured. If the value for kml:interpolate is 1 (or ‘true’), the values between the end of the first track and the beginning of the next track are joined by linearly interpolated points to form a single continuous path.

    Content

    kml:Track

Specifies a kml:Track member of the kml:MultiTrack collection.

See 10.15 kml:Track.

    kml:MultiTrackSimpleExtensionGroup

See 6.7.2.1 Simple Element Substitution.

    kml:MultiTrackObjectExtensionGroup

See 6.7.2.2 Complex Element Substitution.

10.16.4    Example

<kml xmlns=“http://www.opengis.net/kml/2.2”>
     <Folder>
       <Placemark>
         <MultiTrack>
           <interpolate>1</interpolate>
          <Track>
             <when>2010-05-28T02:02:09Z</when>
             <when>2010-05-28T02:02:35Z</when>
             <when>2010-05-28T02:02:44Z</when>
             <when>2010-05-28T02:02:53Z</when>
             <when>2010-05-28T02:02:54Z</when>
             <when>2010-05-28T02:02:55Z</when>
             <when>2010-05-28T02:02:56Z</when>
             <coord>-122.203208 37.374857 140.199997</coord>
             <coord>-122.203330 37.374780 141.199997</coord>
             <coord>-122.203452 37.374706 141.800003</coord>
             <coord>-122.203573 37.374630 142.199997</coord>
             <coord>-122.204679 37.373939 147.000000</coord>
             <coord>-122.205713 37.373288 152.000000</coord>
             <coord>-122.207882 37.371915 156.000000</coord>
           </Track>
           <Track>
             <when>2010-05-28T02:02:57Z</when>
             <when>2010-05-28T02:02:58Z</when>
             <when>2010-05-28T02:02:59Z</when>
             <when>2010-05-28T02:03:00Z</when>
             <when>2010-05-28T02:03:01Z</when>
             <when>2010-05-28T02:03:02Z</when>
             <when>2010-05-28T02:03:03Z</when>
             <coord>-122.207881 37.371915 156.000000</coord>
             <coord>-122.205712 37.373288 152.000000</coord>