KML

Overview

Google submitted KML (formerly Keyhole Markup Language) to the Open Geospatial Consortium (OGC) to be evolved within the OGC consensus process with the following goal: KML Version 2.2 has been adopted as an OGC implementation standard. Future versions may be harmonized with relevant OGC standards that comprise the OGC standards baseline. There are four objectives for this standards work:

• That there be one international standard language for expressing geographic annotation and visualization on existing or future web-based online and mobile maps (2d) and earth browsers (3d).
• That KML be aligned with international best practices and standards, thereby enabling greater uptake and interoperability of earth browser implementations.
• That the OGC and Google will work collaboratively to ensure that the KML implementer community is properly engaged in the process and that the KML community is kept informed of progress and issues.
• That the OGC process will be used to ensure proper life-cycle management of the KML Standard, including such issues as backwards compatibility.

The OGC has developed a broad Standards Baseline. Google and the OGC believe that having KML fit within that family will encourage broader implementation and greater interoperability and sharing of earth browser content and context.

KML is an XML language focused on geographic visualization, including annotation of maps and images. Geographic visualization includes not only the presentation of graphical data on the globe, but also the control of the user’s navigation in the sense of where to go and where to look.

From this perspective, KML is complementary to most of the key existing OGC standards including GML (Geography Markup Language), WFS (Web Feature Service) and WMS (Web Map Service). Currently, KML 2.2 utilizes certain geometry elements derived from GML 2.1.2. These elements include point, line string, linear ring, and polygon.

The OGC and Google have agreed that there can be additional harmonization of KML with GML (e.g. to use the same geometry representation) in the future. The Mass Market Geo Working Group (MMWG) in the OGC will establish such additional harmonization activities. OGC specifications such as Context and Styled Layer Descriptor (SLD) may be considered.

OGC Standards

• 3D Tiles
• 3dP
• ARML2.0
• Cat: ebRIM App Profile: Earth Observation Products
• Catalogue Service
• CDB
• CityGML
• CityJSON
• COG
• Coordinate Transformation
• CoverageJSON
• CQL2
• EO-GeoJSON
• Filter Encoding
• GGXF
• GML in JPEG 2000
• GeoAPI
• GeoPackage
• GeoPose
• GeoSciML
• GeoSPARQL
• Geography Markup Language
• GeoRSS
• GeoXACML
• Geospatial User Feedback (GUF)
• GeoTiff
• GroundwaterML
• HDF5
• I3S
• Indoor Mapping Data Format (IMDF)
• IndoorGML
• KML
• LandInfra/InfraGML
• LAS
• Location Services (OpenLS)
• Moving Features
• MUDDI
• NetCDF
• Observations, Measurements, and Samples
• OGC API – EDR
• OGC API – Common
• OGC API – Features
• OGC API – Maps
• OGC API – Processes
• OGC API – Tiles
• Open GeoSMS
• OpenMI
• OpenSearch
• Ordering Services Framework for Earth Observation Products
• OWS Context
• OWS Security
• PipelineML
• PubSub
• PUCK
• SWE Common Data Model
• SWE Service Model
• Sensor Model Language
• Sensor Observation Service
• Sensor Planning Service
• SensorThings
• Semantic Sensor Network (SSN)
• STAplus
• Symbology Core
• Simple Features
• Simple Features CORBA
• Simple Features OLE/COM
• Simple Features SQL
• Styled Layer Descriptor
• Symbology Encoding
• Table Joining Service
• Time Ontology in OWL
• TimeseriesML (tsml)
• TrainingDML for AI
• Two Dimensional Tile Matrix Set
• WaterML
• Web Coverage Processing Service
• Web Coverage Service
• Web Feature Service
• Web Map Context
• Web Map Service
• Web Map Tile Service
• Web Processing Service
• Web Service Common
• WKT CRS