Exported Content

This term indicates that the page contains imported content from the portal and therefore should not be edited.

The Catalog Domain Working Group is responsible for collection of requirements, technology discussions, presentations, and other activities related to OGC work on interface specifications for Catalogs. Catalogs enable the collection, maintenance, and access of content and service metadata for the dynamic discovery of resources. The Catalog Working Group is also the...The Catalog Working Group is responsible for collection of requirements, technology discussions, presentations, and other activities related to OGC work on interface specifications for Catalogs. Catalogs enable the collection, maintenance, and access of content and service metadata for the dynamic discovery of resources.

The following is the official slate of members for the OWS Common 1.2**
RWG.

  • Arliss Whiteside (BAE). Chair of the RWG
  • Rüdiger Gartmann (con terra). Vice Chair of the RWG
  • Peter Vretanos (CubeWerx)
  • Peter Schut (NR Canada/Geoconnections)
  • Stan Tillman (Intergraph)
  • Andreas Matheus (University of the ...

The central purpose of the Coverages DWG is to promote and oversee development of OGC Implementation Specifications for exploitation of, and accessing, coverage data, including images and other grid coverages. Secondary purposes include promoting use of these specifications, and refining the OGC Abstract Specification as may be needed to better support these specifications.

The DocTeam is a subcommittee of the OGC Technical Committee. The DocTeam will work with OGC staff and OGC members to define, enforce and educate on documentation guidelines (format, templates, style) within the OGC. It will work with OGC staff and OGC members to maintain strong linkages between the Implementation Specifications and the Abstract Specification with the goal of maintaining a core model upon which all OG...The DocTeam will work with OGC staff and OGC members to define, enforce and educate on documentation guidelines (format, templates, style) within the OGC.

The OpenGIS® Web Map Service Interface Standard (WMS) provides a simple HTTP interface for requesting geo-registered map images from one or more distributed geospatial databases. A WMS request defines the geographic layer(s) and area of interest to be processed. The response to the request is one or more geo-registered map images (returned as JPEG, PNG, etc) that can be displayed in a browser application. The interface also supports the ability to specify whether the returned images should be transparent so that layers from multiple servers can be combined or not.

NOTE: WMS 1.3 and ISO 1912...

The OpenGIS® Styled Layer Descriptor (SLD) Profile of the OpenGIS® Web Map Service (WMS) Encoding Standard [http://www.opengeospatial.org/standards/wms] defines an encoding that extends the WMS standard to allow user-defined symbolization and coloring of geographic feature[http://www.opengeospatial.org/ogc/glossary/f] and coverage[http://www.opengeospatial.org/ogc/glossary/c] data. SLD addresses the need for users and software to be able to control the visual portrayal of the geospatial data. The ability to define styling rules requires a styling language that the client and server can bo...
The OpenGIS® Open Location Services Interface Standard (OpenLS) specifies interfaces that enable companies in the Location Based Services (LBS) value chain to “hook up” and provide their pieces of applications such as emergency response (E-911, for example), personal navigator, traffic information service, proximity service, location recall, mobile field service, travel directions, restaurant finder, corporate asset locator, concierge, routing, vector map portrayal and interaction, friend finder, and geography voice-graphics. These applications are enabled by interfaces that implement OpenLS s...
Syndicate content