OGC Requests

The OGC requests comments on the OWS Context Encoding Standard

Status: 
Please note: This Request closed on 8 August 2013.
Closing Date: 
Thu, 08/08/2013 - 04:00
Description: 

The Open Geospatial Consortium (OGC®) is seeking comments on the candidate OGC OWS Context Encoding Standard.  This standard is comprised of three documents:

The OGC Web Services Context Document (OWS Context) standard was created to allow a set of configured information resources (service set) to be passed between applications primarily as a collection of services. OWS Context is designed to support limited in-line content as well. The goal is to support use cases such as the distribution of search results and the exchange of a set of resources such as OGC Web Feature Service (WFS), Web Map Service (WMS), Web Map Tile Service (WMTS), Web Coverage Service (WCS) and others in a ‘common operating picture’ supporting situational awareness. Additionally OWS Context can deliver a set of configured processing services (Web Processing Service (WPS)) parameters to allow the processing to be reproduced on different nodes.

This initial call for comment is for two (2) OWS Context documents: A Conceptual Model and the ATOM encoding for the conceptual model. The Conceptual model document describes the use cases, requirements, conceptual data model of the OWS Context encoding standard. The goal of the model is to provide a core model, which is extended and encoded as defined in extensions to this standard. A Context reference is a fully configured service set to be defined and consistently interpreted by clients. The ATOM encoding is the first extension of the core (conceptual model).

The OGC OWS Context Standards Working Group will consider all comments when preparing a final draft of the candidate standard. The comment period ends 8 August 2013.

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] lists.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: 

GML 3.1.1 grid CRSs profile: 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 GML 3.1.1 grid CRSs profile. OGC invites public comment on a candidate profile specification that will soon be presented for approval by OGC members as an OpenGIS(R) Implementation Specification Profile. The purpose of this Request for Public Comment (RFPC) is to obtain comments on the proposal for technologies and needed interfaces required for GML 3.1.1 grid CRSs profile. Documentation of this draft specification can be downloaded here:

Candidate Submission: Tue, 2005-10-11 17:00
Close request period: Fri, 2005-11-11 17:00
TC and PC vote to issue request: Thu, 2005-12-08 17:00
Begin request period: Sat, 2006-01-07 17:00

 

Downloads: 


 
This document defines a profile of the Geography Markup Language (GML) version 3.1.1 for encoding definitions of grid coverage (including image) Coordinate Reference Systems (CRSs) plus related coordinate Transformations. This document also specifies some Universal Resource Names (URNs) for definitions in the "ogc" URN namespace, in addition to those specified in [OGC 05-010]. Additional specific URNs are defined for definitions of the datums, coordinate systems, and coordinate system axes which are often used in definitions of grid and image CRSs.

This profile can be used without a GML Application Schema, and such use is assumed in this document. However, a GML Application Schema that uses this profile could be specified. For example, an Application Schema could specify "GridCRS" as a better name for a DerivedCRS that uses a CartesianCS. Or an Application Schema could allow or require more information to be encoded for an OperationParameter (such as specified in Subclause 14.3.2 and wctsOperationParameter.xsd of OGC Discussion Paper [OGC 05-013]).

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: 

OGC Seeks Comments on “SWE Common” Data Model

Status: 
Please note: This Request is scheduled to close on 14 April 2010.
Description: 

The Open Geospatial Consortium, Inc. (OGC®) seeks public comment on the draft OGC Sensor Web Enablement (SWE) Common Encoding Standard Version 2.0.  The SWE Common standard provides a common data encoding that is used throughout the OGC Sensor Web Enablement (SWE) standards suite. More precisely, the SWE Common model is used to define the representation, nature, structure and encoding of sensor related data.

 

This model is used for describing static data (files) as well as dynamically generated datasets (on-the-fly processing), data subsets, process and web service inputs and outputs and real time streaming data. All categories of sensor observations are in scope ranging from simple in-situ temperature data to satellite imagery and full motion video streamed out of an aircraft.

 

The SWE Common language is an XML implementation of this model and is used by other existing OGC® Sensor Web Enablement standards such as Sensor Model Language (SensorML), Sensor Observation Service (SOS), Sensor Alert Service (SAS) and Sensor Planning Service (SPS).

 

The proposed OGC SWE Common 2.0 standard and information on submitting comments on this document are available below.  The public comment period closes on 14 April 2010.

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: 

The OGC seeks comments on candidate Augmented Reality Markup Language (ARML 2.0) 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 Standards Working Group and will be released after the edits and revisions. For the most current version please check our Standards Page.
Closing Date: 
Sat, 12/01/2012 - 05:00
Description: 

The Open Geospatial Consortium (OGC®) seeks public comment on the candidate OGC Augmented Reality Markup Language (ARML) 2.0 Encoding Standard.

ARML 2.0 provides an interchange format for Augmented Reality applications to describe and interact with objects in an AR scene, with a focus on mobile, vision-based AR. The candidate standard describes the virtual objects that are placed into an AR scene, as well as the registration of the virtual objects in the real world, and allows interaction with and dynamic modification of the AR scene using ECMAScript bindings.

ARML 2.0 emerged from ARML 1.0, developed by the creators of the Wikitude World Browser, and was completely remodeled within the OGC ARML 2.0 Standards Working Group to fit existing AR use cases.

The OGC ARML 2.0 Standards Working Group has set a specific focus on a generic way to describe Trackers in an Augmented Reality environment, allowing users to define a multitude of Trackers, such as Marker-Trackers, Face-Trackers, Natural Feature Trackers and even non-vision-based Trackers, to allow a multitude of AR use cases to be implemented with ARML 2.0. The deadline for comments is 2 December 2012.

The OGC ARML 2.0 Encoding Standard Evaluation Package is free and can be downloaded below.

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] lists.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 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: 

OGC Empire Challenge 2009 Pilot: SAS Solicitation

Status: 
Please note: This Request scheduled is closed.
Description: 
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.

Each shall render a verbal report weekly during this teleconference. (In lieu of written reports)

Coordination and Integration Activities

Selected responders will work directly with the sponsor to select test networks, functions and schedules.

Deliverables

1. Online Sensor Alert Service (SAS) using XMPP and KML on at least one of the three networks.
2. SAS Best Practice specification to be used: http://portal.opengeospatial.org/files/?artifact_id=15588
3. Company personnel at designated site (see Demonstration Deployment below) during EC09 Demonstration.

Accreditation

Selected responders shall work directly with the sponsor to coordinate accreditation of the computers and software that they will use to provide the SAS.

Test and Integration

Selected responders shall work directly with the sponsors to conduct Technology Integration Experiments (TIEs).

Demonstration Deployment

Selected responders shall provide an SAS server for deployment at a location identified in negotiations with OGC and sponsor approval.

Submission Documentation (Not to exceed 2 pages)

Company Information

Respondents shall provide an indication of their qualifications to participate.

Financial Information

Respondents shall provide a single $US figure for their reimbursement. WBS breakouts are not required.

Personnel

Respondents shall identify personnel who will work the program and provide a brief summary of their qualifications.

Schedule

17 April RFP/RFQ Reopened - SAS Solicitation announced
27 April 0900, EDT Responses Due to techdesk [at] opengeospatial.org
29 April Selected respondents notified and contract work begins

4 May Kickoff (Teleconference or in person at OGC Office, Herndon, VA)
6 May Security Accreditation Documentation input sent to Sponsor
20 May First Technology Integration Experiment (TIE) conducted

26 June Open Internet TIEs concluded

10 July Demonstration Hardware and software installed at location TBD.
31 July EC09 Field Portion concludes

14 August Final Report information provided to sponsor

Inquiries and Questions

All questions are to be sent to techdesk [at] opengeospatial.org. They will be answered daily as Clarifications and posted to this webpage.


Comment: 
 
OGC Requests: 

OGC Calls for Participation in Climatology-Hydrology Information Sharing Pilot (CHISP-1)

Status: 
Please note: This Request is closed.
Closing Date: 
Fri, 09/14/2012 - 04:00
Description: 

 

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 Climatology-Hydrology Information Sharing Pilot (CHISP), Phase 1 (CHISP-1).

The RFQ/CFP is available at below.

Responses are due by 14 September, 2012.

A bidders’ teleconference was held on 15 August 2012. More information will be available below.

The Point of Contact is Lew Leinenweber (lleinenweber at opengeospatial.org).

The CHISP-1 sponsors are:

  • GeoConnections - Natural Resources Canada and Environment Canada
  • US Geological Survey (USGS)
  • US Environmental Protection Agency (EPA)

Around the world, there is a critical need for improved sharing, accessing, and integration of hydrologic and climatic data.  To meet that need, CHISP-1 will engage leaders in the hydro-climatic community to collaboratively build a duplicable system that uses existing resources – including data portals, standards, technologies, activities, and expertise. These resources are available to stakeholders in all countries.

CHISP-1 will create a virtual observatory system for water resources observations and forecasts in parts of the U.S. and Canada, building on current networks and capabilities to support:

  1. Hydrologic modeling of Milk River and Souris River for historical, current and future streamflow and inundation conditions.
  2. Modeling and assessment of nutrient flux into the Great Lakes, which requires accessing and integrating water quality data from multiple agencies

    Advantages of creating this system in an OGC Pilot Project include:

    • Management by a neutral organization
    • Use of a mature and trusted vendor-neutral process led by experienced administrative and technical project managers
    • Design and development best practices (iterative, agile approach to building a SOA-based system)
    • Inclusive process, with open, international call for participation from potential sponsors, and recruiting of industry's best and brightest to staff the development team.

      CHISP-1 will exercise OGC encoding and service standards, including the OGC WaterML 2.0 Encoding Standard, the OGC Sensor Observation Service (SOS) standard and others.

      CHISP-1 offers many benefits. In addition to leveraging the large body of existing related activities, those activities, and others like them around the world, will be enhanced by and benefit from the pilot outcomes. By pooling resources to accomplish a shared objective, the sponsors and participants in CHISP-1 reduce their development risks and leverage their investment. In addition to identifying and clarifying what is possible, the pilot will identify the key technical and non-technical barriers to continued progress in sharing and integrating hydrologic and climatic information. Because it is an international project with broad industry participation, it will promote understanding and strengthen ties within the existing hydro-climatic community.

      Bidder's Conference

      -------------------------------------------------------
      CHISP-1 Bidders Teleconference Dial-in:

      +1 415 363 0833 passcode:665541

      WebEx Information:

      Host: Leinenweber, Lewis

      Start Time: 08/15/2012 : 11:00 AM - 02:00 PM [EDT - US/Eastern]
      Duration: 180 minutes
      Meeting URL: https://portal.opengeospatial.org/webex_auth.php?AT=JM&MK=798776961&PW=C...

      Clarifications

      The most recent clarifications are dated 2012-08-20

      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] lists.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: 

      WCS 1.1.2 Processing extension Request for Comment

      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 Standards 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) 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 WCPS Extension adds a raster expression language to WCS which allows analysis and processing of multi-dimensional grid coverage data over the World Wide Web. Resulting coverages can be transmitted directly or made available for download by URLs communicated to the client.

      The Request for Comments (RFC) document can be downloaded from http://www.opengeospatial.org/standards/requests/49 . Comments are due by July 30, 2008.

      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] lists.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: 

      OGC Seeks Comment on candidate GeoSPARQL 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 Standards 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®) seeks public comment on the candidate OGC “GeoSPARQL: A Geographic Query Language for RDF Data” Standard. The candidate OGC GeoSPARQL standard defines spatial extensions to the W3C's SPARQL protocol and RDF query language. 

      SPARQL is a protocol and query language for the Semantic Web. SPARQL is defined in terms of the W3C's RDF data model and will work for any data source that can be mapped into RDF, which potentially includes sources of geospatial data. The OGC GeoSPARQL standard supports representing and querying geospatial data on the Semantic Web. GeoSPARQL provides the foundational geospatial vocabulary for linked data involving location and defines extensions to SPARQL for processing geospatial data. This standard serves as a common target for vendors to implement and provides rich functionality for building geospatial applications.

      GeoSPARQL follows a modular design. A core component defines top-level RDFS/OWL classes for spatial objects. A geometry component defines RDFS data types for serializing geometry data, RDFS/OWL classes for geometry object types, geometry-related RDF properties, and non-topological spatial query functions for geometry objects. A geometry topology component defines topological query functions. A topological vocabulary component defines RDF properties for asserting topological relations between spatial objects, and a query rewrite component defines rules for transforming a simple triple pattern that tests a topological relation between two features into an equivalent query involving concrete geometries and topological query functions.

      The candidate OGC GeoSPARQL Standard documents are available for review and comment below.

      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] lists.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: 

      The OGC requests comment on the candidate "I15" standard providing ebRIM extension to OGC Catalog Services Interface Standard

      Status: 
      Please note: This Request closed on 30 November 2013. 
      Closing Date: 
      Sat, 11/30/2013 - 05:00
      Description: 

      The Open Geospatial Consortium (OGC®) is seeking comments on the candidate OGC standard, "OGC I15 (ISO19115 Metadata) Extension Package of the OGC Catalogue Services 2.0 (CS-W) ebRIM Profile."

      The OGC Catalogue Services Standard establishes a general framework for implementing catalogue services used for publishing and discovering geospatial data and geoprocessing services.

      The candidate I15 standard provides an extension package aligned with the ebRIM application profile of CS-W for the cataloguing of data and services whose metadata implements ISO geospatial metadata standards. The I15 Extension Package defines mechanisms that allow an ebRIM catalogue to manage and search ISO conformant metadata in ways that enable arbitrary, complex and deep searches involving multiple metadata elements. 

      The draft standard was initially produced during the ESA HMA (Heterogeneous Missions Accessibility) initiative (HMA) and related projects. The OGC OWS-9 testbed initiative tested the draft standard and provided input.

      Download the candidate OGC I15 (ISO19115 Metadata) Extension Package of the OGC Catalogue Services 2.0 (CS-W) ebRIM Profile below:

      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] lists.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