OGC Requests

OpenGIS® Sensor Observation Service (SOS): Request for Public Comments

Status: 
Please note: This Request is closed. The documents listed below have been adopted by the OGC Technical and Planning Committee. These specifications are under control of the specification Revision Working Group and will be released after the edits and revisions. For the most current version please check our Standards Page.
Description: 

The Open Geospatial Consortium (OGC) is contemplating adoption of a technology called OpenGIS® Sensor Observation Service (SOS). OGC invites public comment on a candidate specification that will soon be presented for approval by OGC members as an OpenGIS(R) Implementation Specification. The purpose of this Request for Public Comment (RFPC) is to obtain comments on the proposal for technologies and needed interfaces required for OpenGIS® Sensor Observation Service (SOS). Documentation of this draft specification can be downloaded here:

Candidate Submission: Thu, 2006-02-02 16:00
Close request period: Fri, 2006-03-10 16:00
TC and PC vote to issue request: Wed, 2006-04-05 16:00
Begin request period: Fri, 2006-05-05 16:00
 

Downloads: 

This document specifies Sensor Observation Service. A Sensor Observation Service provides an API for managing deployed sensors and retrieving sensor data and specifically "observation" data. Whether from in-situ sensors (e.g., water monitoring) or dynamic sensors (e.g., satellite imaging), measurements made from sensor systems contribute most of the geospatial data by volume used in geospatial systems today
Comment: 
Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template.
Subscribe: 
You may wish to be added to the distribution list to receive comments as they are submitted:
Subscribing to the the list will also allow you to view comments already received, which can be found in the List Archives.
OGC Requests: 

OpenGIS® Sensor Planning Service (SPS): Request for Public Comments

Status: 
Please note: This Request is closed. The documents listed below have been adopted by the OGC Technical and Planning Committee. These specifications are under control of the specification Revision Working Group and will be released after the edits and revisions. For the most current version please check our Standards Page.
Description: 

The Open Geospatial Consortium (OGC) is contemplating adoption of a technology called OpenGIS® Sensor Planning Service (SPS). OGC invites public comment on a candidate specification that will soon be presented for approval by OGC members as an OpenGIS(R) Implementation Specification. The purpose of this Request for Public Comment (RFPC) is to obtain comments on the proposal for technologies and needed interfaces required for OpenGIS® Sensor Planning Service (SPS). Documentation of this draft specification can be downloaded here:

Candidate Submission: Tue, 2006-02-21 16:00
Close request period: Fri, 2006-03-10 16:00
TC and PC vote to issue request: Wed, 2006-04-12 16:00
Begin request period: Fri, 2006-05-12 16:00

 

Downloads: 

This OpenGIS® document specifies interfaces for requesting information describing the capabilities of a Sensor Planning Service, for determining the feasibility of an intended sensor planning request, for submitting such a request, for inquiring about the status of such a request, for updating or cancelling such a request, and for requesting information about further OGC Web services that provide access to the data collected by the requested task.
Comment: 
Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template.
Subscribe: 
You may wish to be added to the distribution list to receive comments as they are submitted:


Subscribing to the the list will also allow you to view comments already received, which can be found in the List Archives.
OGC Requests: 

OpenGIS® Transducer Markup Language (TML): Request for Public Comments

Status: 
Please note: This Request is closed. The documents listed below have been adopted by the OGC Technical and Planning Committee. These specifications are under control of the specification Revision Working Group and will be released after the edits and revisions. For the most current version please check our Standards Page.
Description: 

The Open Geospatial Consortium (OGC) is contemplating adoption of a technology called OpenGIS® Transducer Markup Language (TML). OGC invites public comment on a candidate specification that will soon be presented for approval by OGC members as an OpenGIS(R) Implementation Specification. The purpose of this Request for Public Comment (RFPC) is to obtain comments on the proposal for technologies and needed encodings required for OpenGIS® Transducer Markup Language (TML). Documentation of this draft specification can be downloaded here:

Candidate Submission: Fri, 2006-02-03 16:00
Close request period: Fri, 2006-03-10 16:00
TC and PC vote to issue request: Wed, 2006-04-05 16:00
Begin request period: Fri, 2006-05-05 16:00
 

Downloads: 

This document describes TML and how it captures necessary information to both understand and process transducer data. Descriptions of how TML captures the actual data and also descriptions of necessary information such as system calibration, transducer behavior, conditions of operation and data collection parameters critical to logical data structure model are all captured within TML. This document specifically describes the TML transducer behavior models and TML data models. It does not describe a service for delivering TML-structured data, but there is a brief discussion of SOA and streaming platform considerations.
Comment: 
Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template.
Subscribe: 
You may wish to be added to the distribution list to receive comments as they are submitted:
Subscribing to the the list will also allow you to view comments already received, which can be found in the List Archives.
OGC Requests: 

OWS-5 Testbed Addendum Released

Status: 
Please note: This Request is closed.
Description: 
RFQ Issuance Date: 7 September, 2007
Clarifications Posted: 17 September, 2007
Proposal Due Date: 5 October, 2007

 


Overview

This document is an addendum to the previously issued OWS-5 RFQ/CFP and includes new requirements to be included in the Agile Geography thread of the ongoing OWS-5 testbed. The requirements within this addendum should be addressed within the overall context of the original OWS-5 RFQ/CFP. It should be noted that schedule information contained within this document supercedes that which was found in the original OWS-5 RFQ/CFP.

The content within this RFQ covers two topics and are described in further detail below:

  1. GeoSynchronization
  2. OWS Core and Extension Experiment

1) GeoSynchronization

GeoSynchronization targets a federated environment comprised of loosely affiliated parties who desire to collaborate on the development and maintenance of a shared geospatial data set. Additionally, technology is enabling new online markets for information sharing and processing to emerge. These too can achieve cost and time benefits from leveraging loosely coupled, industry standards for sharing and synchronization. Solving this interoperability issue is of critical importance to ongoing Spatial Data Infrastructure (SDI) initiatives across the globe, as parties with differing software infrastructures, organizational goals, and legal mandates seek to increase the availability of geospatial information across society without incurring prohibitive costs. While existing OGC technologies have made it easier to publish information in an interoperable manner, creating the potential for effective sharing and collaboration, another level of interoperability technology is required to manage the intricacies of cross-organizational data sharing, which may include acceptance, validation, rejection, and description of operations on information streams.

In this testbed participants will be funded to experiment with solutions that leverage GML-based information models, such as the GML profiles being developed for US framework data sets and the Canadian Geospatial Data Infrastructure. Mass market information models, such as Atom+GeoRSS GML and KML may be considered as well. It is expected that investigations in this area will likely extend the WFS Transactional architecture to accommodate a more loosely coupled approach. However, alternative architectures will be considered as well.

 

2) OWS Core and Extension Experiment

The OGC in general, and the OGC Architecture Board (OAB) in particular, is considering a more formal, modular approach to standards that is described in "OGC Abstract Specification - The Model Specification - Structuring an OGC specification to encourage implementation, version 07-056r2". In support of this effort, this OWS-5 task uses the guidance from this document and applies it to the "OpenGIS® Web Feature Service (WFS) Implementation Specification", "Gazetteer Service - Application Profile of the Web Feature Service Implementation Specification", and the Web Processing Service.


OGC Requests: 

OWS-9 RFQ: OGC Calls for Participation in Major Interoperability Testbed

Status: 
Please note: This Request is closed.

 

Description: 


RFQ Issuance Date:
 22 February 2012
OWS-9 Bidder's Conference: will be held on March 9, 2012, see below.
Proposal Due Date: 5 pm EST on April 6, 2012.

Go Directly to the Request for Quotation Document 
Go Directly to the Bidder's Conference Information Overview 
Go Directly to the Request for Quotation Clarifications

 

Overview

The Open Geospatial Consortium (OGC®) has issued a Request for Quotations/Call for Participation (RFQ/CFP) to solicit proposals in response to requirements for the OGC Web Services, Phase 9 (OWS-9) Testbed (http://www.opengeospatial.org/projects/initiatives/ows-9).

The RFQ/CFP is available below.

Responses are due by 5 pm EST on April 6, 2012.

A bidders’ teleconference will be held on March 9, 2012. More information will be available below.

The Point of Contact is Nadine Alameh: techdesk [at] opengeospatial.org.

The OWS-9 sponsors are:

  • AGC (Army Geospatial Center, US Army Corps of Engineers)
  • CREAF-GeoViQua-EC (CREAF is the European Center for Research in Ecology and Forestry Applications)
  • EUROCONTROL
  • FAA (US Federal Aviation Administration)
  • GeoConnections - Natural Resources Canada
  • Lockheed Martin Corporation
  • NASA (US National Aeronautics and Space Administration)
  • NGA (US National Geospatial-Intelligence Agency)
  • USGS (US Geological Survey)

OWS-9 builds on the outcomes of prior OGC initiatives (http://www.opengeospatial.org/resource/demos) and is organized around the following threads:

-   Aviation: Develop and demonstrate the use of the Aeronautical Information Exchange Model (AIXM) and the Weather Information Exchange Model (WXXM) in an OGC Web Services environment, focusing on support for several Single European Sky ATM Research (SESAR) project requirements as well as the FAA's Aeronautical Information Management (AIM) and Aircraft Access to SWIM (System Wide Information Management) (AAtS) requirements.

-   Cross-Community Interoperability (CCI): Build on the CCI work accomplished in OWS–8 by increasing interoperability within communities sharing geospatial data, focusing on semantic mediation, query results delivery, data provenance and quality and Single Point of Entry Global Gazetteer 

-   Security and Services Interoperability (SSI): Investigate 5 main activities: Security Management, OGC Geography Markup Language (GML) Encoding Standard Application Schema UGAS (UML to GML Application Schema) Updates, Web Services Façade, Reference Architecture Profiling, and Bulk Data Transfer.

-   OWS Innovations: Explore topics that represent either new areas of work for the Consortium (such as GPS and Mobile Applications), a desire for new approaches to existing technologies to solve new challenges (such as the OGC Web Coverage Service (WCS) work), or some combination of the two.

-   Compliance & Interoperability Testing & Evaluation (CITE): Develop a suite of compliance test scripts for testing and validation of products with interfaces implementing the following OGC standards: Web Map Service (WMS) 1.3 Interface Standard, Web Feature Service (WFS) 2.0 Interface Standard, Geography Markup Language (GML) 3.2.1 Encoding Standard, OWS Context 1.0 (candidate encoding standard), Sensor Web Enablement (SWE) standards, Web Coverage Service for Earth Observation (WCS-EO) 1.0 Interface Standard, and TEAM (Test, Evaluation, And Measurement) Engine Capabilities.

The RFQ/CFP includes details of these threads as well as details on participation eligibility, selection process and kickoff workshop information.

OGC testbeds, pilot projects and interoperability experiments are part of the OGC Interoperability Program, a global, hands-on collaborative prototyping program designed to rapidly develop, test and deliver proven candidate standards into the OGC Specification Program, where they are formalized for public release.

Downloads: 

 

RESPONSE TEMPLATES (not included in above package)

 

 

 

Questions: Bidder's Conference

 A Bidder's Conference (webinar) was be held on March 9, 2012

A second bidder's conference will be held on March 19, 2012 

Date and Time:
Monday, March 19, 2012 10:00 pm, GMT
Monday, March 19, 2012 5:00 pm, Central Daylight Time (Chicago, GMT-05:00)
Tuesday, March 20, 2012 7:00 am, Japan Time (Tokyo, GMT+09:00)
Monday, March 19, 2012 7:00 pm, Eastern Daylight Time (New York, GMT-04:00)
Tuesday, March 20, 2012 11:00 pm, Europe Time (Berlin, GMT+01:00)

This telecon will originate from a F2F meeting as part of OGC TC meetings.

You must register for this session at:

  https://ogc-meeting.webex.com/ogc-meeting/onstage/g.php?t=a&d=668037249

 

Clarifications Document

All Q&A, updates, and other information about OWS-9 from the Bidder’s Conference and other communications will be collected into a Clarifications document, and posted here for public access. Subsequent questions may be directed by email to techdesk [at] opengeospatial.org (techdesk [at] opengeospatial.org).  The Clarifications Document is here: 

Current clarifications

OGC Requests: 

Request for Comment on CityGML Standard

Status: 
Please note: This Request is closed. The documents listed below have been adopted by the OGC Technical and Planning Committee. These specifications are under control of the specification Revision Working Group and will be released after the edits and revisions. For the most current version please check our Standards Page.
Description: 
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.

Activities that would benefit from the richness of CityGML data include city planning, real estate, insurance, architectural design, environmental simulation, mobile telecommunication, disaster management, homeland security, facilities management, vehicle and pedestrian navigation, training simulators and others. CityGML will play an important role in the use of Building Information Models (BIM) to improve interoperability among the information systems used in the many domains of activity that involve design, construction, ownership and operation of buildings and capital projects.


Comment: 
Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template.
Subscribe: 
You may wish to be added to the distribution list to receive comments as they are submitted:
Subscribing to the the list will also allow you to view comments already received, which can be found in the List Archives.
OGC Requests: 

Request for Comment on Geospatial eXtensible Access Control Markup Language (GeoXACML)

Status: 
Please note: This Request is closed. The documents listed below have been adopted by the OGC Technical and Planning Committee. These specifications are under control of the specification Revision Working Group and will be released after the edits and revisions. For the most current version please check our Standards Page.
Description: 

The Open Geospatial Consortium (OGC) is contemplating adoption of a technology called Geospatial eXtensible Access Control Markup Language (GeoXACML). OGC invites public comment on a candidate specification that will soon be presented for approval by OGC members as an OpenGIS(R) Implementation Specification.

The OpenGIS Geospatial eXtensible Access Control Markup Language (GeoXACML) Draft Implementation Specification (OGC Document 07-026) defines a geo-specific extension to the eXtensible Access Control Markup Language (XACML) OASIS standard. "Access control systems" enable management of access to information only until it is obtained by the user and stored locally, as opposed to "rights management systems" that remain in force regardless of where the content of the original resource is located or reproduced.

The purpose of this Request for Public Comment (RFPC) is to obtain comments on the proposal for technologies and needed interfaces required for GeoXACML. Documentation of this draft specification can be downloaded below:

Candidate Submission: Thur, 2007-03-22
TC and PC vote to issue request: Fri, 2007-04-20
Begin request period: Tue, 2007-05-15
Close request period: Thu, 2007-06-14

Comment: 
Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template.
Subscribe: 
You may wish to be added to the distribution list to receive comments as they are submitted:
Subscribing to the the list will also allow you to view comments already received, which can be found in the List Archives.
OGC Requests: 

Request for Comment on Image Geopositioning Service (IGS)

Status: 
Please note: This Request is closed. The documents listed below have been adopted by the OGC Technical and Planning Committee. These specifications are under control of the specification Revision Working Group and will be released after the edits and revisions. For the most current version please check our Standards Page.
Description: 

The Open Geospatial Consortium (OGC) is contemplating adoption of a technology called OpenGIS Image Geopositioning Service (IGS). OGC invites public comment on a candidate specification that will soon be presented for approval by OGC members as an OpenGIS(R) Implementation Specification.

The OpenGIS Image Geopositioning Service (IGS) Draft Implementation Specification defines an Image Geopositioning Service (IGS) interface to services that perform triangulation. (NOTE: The name of this service has not yet been formally agreed upon.) Accompanying this draft specification is a separate OpenGIS Image Geopositioning Metadata Geography Markup Language (GML) Draft Application Schema, which is structured to provide consistency between the IGS and other OGC Web Services (OWS) specifications.

The purpose of this Request for Public Comment (RFPC) is to obtain comments on the proposal for technologies and needed interfaces required for the IGS. Documentation of this draft specification can be downloaded below:

Candidate Submission: Thur, 2007-03-22
TC and PC vote to issue request: Fri, 2007-04-20
Begin request period: Tue, 2007-05-15
Close request period: Thu, 2007-06-14

Comment: 
Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template.
Subscribe: 
You may wish to be added to the distribution list to receive comments as they are submitted:
Subscribing to the the list will also allow you to view comments already received, which can be found in the List Archives.
OGC Requests: 

Request for Comment on KML 2.2

Status: 
Please note: This Request is closed. The documents listed below have been adopted by the OGC Technical and Planning Committee. These specifications are under control of the specification Revision Working Group and will be released after the edits and revisions. For the most current version please check our Standards Page.
Description: 

The Open Geospatial Consortium (OGC) is contemplating adoption of the KML 2.2 candidate standard. The OGC invites public comment on this candidate standard. All comments will be collated and used in the evaluation of KML 2.2 as an OGC standard. In late first quarter 2008, the OGC committee working on the KML 2.2 candidate standard will seek approval by OGC members for KML 2.2 an OpenGIS(R) Encoding Standard.

The OpenGIS Candidate Implementation Standard specifies XML grammar used to encode and transport representations of geographic data for display in an earth browser. Put simply: KML encodes what to show in an earth browser, and how to show it. KML uses a tag-based structure with nested elements and attributes and is based on the XML standard.

The purpose of this Request for Public Comment (RFPC) is to obtain comments on the proposal for KML 2.2. Documentation of this draft standard can be downloaded below:

Candidate Submission: Thur, 2007-08-30
TC and PC vote to issue request: Fri, 2007-09-21
Begin request period: Tue, 2007-12-4
Close request period: Thu, 2008-01-03

Comment: 
Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] opengeospatial.org?SUBJECT=KML%202.2%20Comment&BODY=Part%20A%20to%20be%20completed%20once.%20%20Iterate%20Part%20B%20as%20needed.%0D%0DPART%20A%0D%0D1.%20Evaluator:%20%5BCONTACT%20INFORMATION%5D%0D%0D2.%20Submission:%20%5BOpenGIS%20Project%20Document%20Number,%20Name%5D%0D%0DPART%20B%0D%0D1.%20Requirement:%20%5BGeneral,%20#%5D%0D%0D2.%20Implementation%20Specification%20Section%20number:%20%5BGeneral,%20#%5D%0D%0D3.%20Criticality:%20%5BMajor,%20Minor,%20Editorial,%20etc.%5D%0D%0D4.%20Comments/justifications%20for%20changes:%20%5BComments%5D%0D%0D">Click here to submit comments The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template.
Subscribe: 
You may wish to be added to the distribution list to receive comments as they are submitted:
Subscribing to the the list will also allow you to view comments already received, which can be found in the List Archives.
OGC Requests: 

Request for Comment on Sensor Alert Service

Status: 
Please note: This Request is closed. The documents listed below have been adopted by the OGC Technical and Planning Committee. These specifications are under control of the specification Revision Working Group and will be released after the edits and revisions. For the most current version please check our Standards Page.
Description: 

The Open Geospatial Consortium (OGC) is contemplating adoption of a technology called OpenGIS Sensor Alert Service (SAS). OGC invites public comment on a candidate specification that will soon be presented for approval by OGC members as an OpenGIS(R) Implementation Specification.

The OpenGIS Sensor Alert Service (SAS) Draft Implementation Specification specifies interfaces for requesting information describing the capabilities of a Sensor Alert Service, for determining the nature of offered alerts, the protocols used, and the options to subscribe to specific alert types.

The purpose of this Request for Public Comment (RFPC) is to obtain comments on the proposal for technologies and needed interfaces required for the SAS. Documentation of this draft specification can be downloaded below:

Candidate Submission: Thur, 2007-06-15
TC and PC vote to issue request: Fri, 2007-07-13
Begin request period: Wed, 2007-11-15
Close request period: Fri, 2007-12-15

Comment: 
Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template.
Subscribe: 
You may wish to be added to the distribution list to receive comments as they are submitted:
Subscribing to the the list will also allow you to view comments already received, which can be found in the List Archives.
OGC Requests: 

Pages