OGC Requests

The members of the Open Geospatial Consortium, Inc. (OGC®) request comments to a revision to the OpenGIS® Web Services Common Standard. This document specifies many of the aspects that are common to multiple OGC Web Service (OWS) interface Implementation Standards. These common aspects are primarily parameters and data structures used in operation requests and responses. Examples of common usage are how to handle bounding boxes, exception processing, URL requests, URN expressions, key value encoding, and so forth.

The primary use of OWS Common is as a normative reference for other OWS standards. Those standards currently include the OpenGIS Web Map Service (WMS), Web Feature Service (WFS), and Web Coverage Service (WCS) Standards. Rather than continuing to repeat this material in each Implementation Standard, each standard normatively references each relevant part of OWS Common.

Due to the short turn around and limited scope of the request many of the work items that are normally included in a Statement of Work for an OGC pilot will not be performed. Nor will it be necessary for a responder to provide the detailed information outlined in the original EC'09 CFP/ RFQ. This SAS Solicitation document describes the work to be performed, the schedule required, the reports and attendance requirements for responding. Please submit using the ‘Submission Documentation' directions below - DO NOT use the detailed template listed in the orginal CFP/RFQ.

Initiative Conduct

Meetings and Teleconferences

Selected responders will participate in the Kickoff Teleconference and weekly progress teleconferences.

The membership of the Open Geospatial Consortium, Inc. (OGC) is requesting comments from the public on the candidate OGC Document, "The OGC Specification Model - Writing Modular Specifications".

This document, prepared by the Policy 1.0 Standards Working Group, derives from the collective experience of members in developing and implementing OGC standards, geospatial applications, platforms and services. It provides a logical model and template for candidate standards to assure their internal logic and conformance to accepted software development procedures and the OGC's policy and rules regarding the structure of standards and the types of information that they must provide. The policy guidance will make implementation of OGC standards and the construction of compliance tests easier through enforced traceability of requirements to implementation tests, and it will make modularization of both standards and implementations more explicit and consistent across dependent standards and implementations.

The membership of the Open Geospatial Consortium, Inc. (OGC®) is requesting comments from the public on the candidate OpenGIS® Web Map Tiling Service (WMTS) Interface Standard.

The candidate WMTS Interface Standard is much like the OGC's popular Web Map Server (WMS) Interface Standard, but it enables better server performance in applications that involve many simultaneous requests. To improve performance, instead of creating a new image for each request, it returns small pre-generated images (e.g., PNG or JPEG) or reuses identical previous requests that follow a discrete set of tile matrices. This proposed standard provides support for multiple architectural patterns - KVP, REST and SOAP.

The membership of the Open Geospatial Consortium, Inc. (OGC) is requesting comments on the candidate standard OpenGIS(R) GeoLinking Service (GLS) Interface.

The candidate GLS standard defines an interface for services that provide the ability to "link" data that contain information about geographic objects, such as census tract population statistics, with data in another repository that contains the actual geometry (points, lines, polygons). For example, a table of populations of cities on one server may not contain the geometry information that describes the cities' locations and boundaries, while a second server may house the cities' geometry. The candidate GLS standard describes a set of interfaces for both servers that lets the city name be used as a "common geographic identifier" to join the population data to its geometry, so the user can create a map or perform geospatial analysis on the linked data.

The members of the Open Geospatial Consortium, Inc. (OGC) have submitted a Request for Comments (RFC) on version 0.2.2 of the Earth Observation (EO) Products Extension Package for ebRIM (ISO/TS 15000-3) Profile of CSW 2.0 (OGC document 06-131). (ebRIM is the electronic business Registry Information Model from the OASIS standards organization. CSW (“Catalog Services - Web”) is an OGC standard that specifies a catalogue application profile based on ISO19115:2003/ISO19119:2005 metadata with support for XML encoding per ISO/CD TS 19139  and HTTP protocol binding.)

Overview

OWS testbeds are part of OGC's Interoperability Program, a global, hands-on and collaborative prototyping program designed to rapidly develop, test and deliver proven candidate specifications into OGC's Specification Program, where they are formalized for public release. In OGC's Interoperability Initiatives, international teams of technology providers work together to solve specific geoprocessing interoperability problems posed by the Initiative's sponsoring organizations. OGC Interoperability Initiatives include test beds, pilot projects, interoperability experiments and interoperability support services - all designed to encourage rapid development, testing, validation and adoption of OGC standards.

The Open Geospatial Consortium, Inc. (OGC) membership approved a 30 day public comment period for a revision to the OpenGIS® Web Coverage Service (WCS) Interface Standard. The revision includes two extensions to WCS: the WCS 1.1 Transaction Extension and the Web Coverage Processing Service Processing (WCPS) Extension.

The WCS Interface Standard (http://www.opengeospatial.org/standards/wcs) specifies an application programming interface (API) for requesting coverage data, such as imagery, from one or more distributed sources.

The WCS 1.1 Transaction Extension defines how WCS clients can request that a WCS server import one or more new coverages into that server, update existing coverages, and/or delete existing coverages.

The Open Geospatial Consortium, Inc. (OGC) is requesting public comment on the candidate CityGML Encoding Standard. CityGML is a Geography Markup Language 3 (GML3) application schema for the storage and exchange of virtual 3D city models.

CityGML is a common information model for the representation of 3D urban objects. It defines the classes and relations for the most relevant topographic objects in cities and regional models with respect to their geometrical, topological, semantical and appearance properties. Included are generalization hierarchies between thematic classes, aggregations, relations between objects, and spatial properties. These thematic information go beyond graphic exchange formats and allow to employ virtual 3D city models for sophisticated analysis tasks in different application domains like simulations, urban data mining, facility management, and thematic inquiries.

Slides for the Bidders Conference on 16 January are now available.

The Open Geospatial Consortium, Inc. (OGC) has issued a Request For Quotations and Call for Participation (RFQ/CFP) to solicit proposals in response to requirements for the Empire Challenge 08 Pilot (EC08 OGC Pilot).

The EC08 OGC Pilot is sponsored by a US agency which will provide cost-sharing funds to offset expenses associated with the initiative. The sponsor and the OGC intend to involve as many participants in the initiative as possible and thus are soliciting proposals that will enhance and/or make use of the initiative outcomes. This RFQ/CFP is soliciting partners to provide and deploy hardware / software and to collaborate on the final technology design for the pilot network. Personnel without clearances will be able to install and maintain software on the network. Responses are due by January 24, 2008 and the Pilot Kickoff Meeting will be held the week of February 26-28, 2008, in the Washington, DC area. Technology deployments will be complete by June 27, 2008, followed by a four-week demonstration phase in July.