Open Geospatial Consortium

From Infogalactic: the planetary knowledge core
(Redirected from Open GIS Consortium)
Jump to: navigation, search

The Open Geospatial Consortium (OGC), an international voluntary consensus standards organization, originated in 1994. In the OGC, more than 500 commercial, governmental, nonprofit and research organizations worldwide collaborate in a consensus process encouraging development and implementation of open standards for geospatial content and services, GIS data processing and data sharing.

History

A predecessor organization, OGF, the Open GRASS Foundation, started in 1992.[1]

From 1994 to 2004 the organization also used the name Open GIS Consortium.

The OGC website gives a detailed history of the OGC.[2]

Standards

Most of the OGC standards depend on a generalized architecture captured in a set of documents collectively called the Abstract Specification, which describes a basic data model for representing geographic features. Atop the Abstract Specification members have developed and continue to develop a growing number of specifications, or standards to serve specific needs for interoperable location and geospatial technology, including GIS.

More information here: http://www.opengeospatial.org/standards

Relationship between clients/servers and OGC protocols

The OGC standards baseline comprises more than 30 standards,[3] including:

  • CSW – Catalog Service for the Web: access to catalog information
  • GML – Geography Markup Language: XML-format for geographical information
  • GeoXACML – Geospatial eXtensible Access Control Markup Language (as of 2009 in the process of standardization)
  • KMLKeyhole Markup Language: XML-based language schema for expressing geographic annotation and visualization on existing (or future) Web-based, two-dimensional maps and three-dimensional Earth browsers
  • Observations and Measurements
  • OGC Reference Model – a complete set of reference models
  • OGC Web Services Context Document defines the application state of an OGC Integrated Client
  • OWS – OGC Web Service Common
  • SOS – Sensor Observation Service[4]
  • SPS – Sensor Planning Service[5]
  • SensorML – Sensor Model Language
  • SensorThings API[6] - an open and unified framework to interconnect IoT devices, data, and applications over the Web. Currently a candidate standard waiting for votes.
  • SFS – Simple Features – SQL
  • SLD - Styled Layer Descriptor
  • WaterML – Information model for the representation of hydrological observation data
  • WCS – Web Coverage Service: provides access, subsetting, and processing on coverage objects
  • WCPS – Web Coverage Processing Service: provides a raster query language for ad-hoc processing and filtering on raster coverages
  • WFS – Web Feature Service: for retrieving or altering feature descriptions
  • WMS – Web Map Service: provides map images
  • WMTS – Web Map Tile Service: provides map image tiles
  • WPS – Web Processing Service: remote processing service
  • GeoSPARQL – Geographic SPARQL Protocol and RDF Query Language:[7] representation and querying of geospatial data for the Semantic Web
  • WTS – Web Terrain Service (WTS)

The design of standards were originally built on the HTTP web services paradigm for message-based interactions in web-based systems, but meanwhile has been extended with a common approach for SOAP protocol and WSDL bindings. Considerable progress has been made in defining Representational State Transfer (REST) web services.

Organization structure

The OGC has three operational units:

  1. the Specification program
  2. the Interoperability Program
  3. Outreach and Community Adoption

Collaboration

The OGC has a close relationship with ISO/TC 211 (Geographic Information/Geomatics). Volumes from the ISO 19100 series under development by this committee progressively replace the OGC abstract specification. Further, the OGC standards Web Map Service, GML, Web Feature Service, Observations and Measurements, and Simple Features Access have become ISO standards.[8]

The OGC works with more than 20 international standards-bodies including W3C, OASIS, WfMC, and the IETF.[9]

See also

References

  1. GRASS Roots, Westervelt, p. 5
  2. http://www.opengeospatial.org/ogc/historylong
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.

External links