Exported Content

Strategic Member Advisory Committee

The Strategic Member Advisory Committee is conceived to be a permanent committee within the OGC organization, designed specifically to provide Strategic Members the opportunity to participate in the strategic planning processes of the Consortium, and to support Consortium operations aimed at achieving the corporation's mission as defined in the bylaws.

Technical Committee

The OGC membership process is operationally organized into groups and subgroups, each group having a specified role and level of responsibility. There are three major groups, called Committees: The Technical, the Planning and the Strategic Management Advisory Committees.

The Technical Committee is responsible for all aspects of the formal consensus OGC specification process. This includes:

Planning Committee

The OGC Planning Committee is granted authority to operate by the OGC Bylaws. Principal Membership is provided for organizations that wish to participate in the planning and management of the Consortium's technology development process.

The Planning Committee has ultimate responsibility for approving Technical Committee recommendations for the adoption and release of OGC standards, and for Specification Program planning.

OGC Standards

Below is a list of OGC Implementation Standards.

Implementation Standards are different from the Abstract Specification. They are written for a more technical audience and detail the interface structure between software components. An interface specification is considered to be at the implementation level of detail if, when implemented by two different software engineers in ignorance of each other, the resulting components plug and play with each other at that interface.

Context RWG

This the Revision Working Group for the completion of a new revision to the Web Map Context Implementation The version will be 1.2. Date of the formation of the new RWG was 4/25/07.

The Chair and Vice-Chair are to be elected. The official slate of members is:

  • Martin Daly (CadCorp)
  • Stan Tillman (Intergraph)
  • Ian Turton (Penn State)
  • Arnulf Christl (WhereGroup)
  • Mike Adair, Natural Resources Canada)
  • Tom Kralidis (Geoconnections)
  • Stéphane Nicoll (Ionic)
  • Marcellin Prudham (IGN)

Open Location Services Testbed, Phase 1.1

The OpenLS Testbed was sponsored by Hutchison 3G UK, Sun Microsystems, In-Q-Tel, ESRI with SignalSoft, and Oracle with Webraska.

This testbed yielded Interoperability Program Reports (IPRs) that have become approved OpenGIS® Specifications in support of interoperable Location Based Services to be made available through mobile terminals. The OpenLS Testbed ended with a successful multi-vendor, specification-based mobile demonstration of these interfaces in action.

Sensor Planning Service (SPS)

The OpenGIS® Sensor Planning Service Interface Standard (SPS) defines interfaces for queries that provide information about the capabilities of a sensor and how to task the sensor. The standard is designed to support queries that have the following purposes: to determine the feasibility of a sensor planning request; to submit and reserve/commit such a request; to inquire about the status of such a request; to update or cancel such a request; and to request information about other OGC Web services that provide access to the data collected by the requested task. This is one of the OGC Sensor Web...