OGC Requests

The OGC announces Call for Participation in MilOps Geospatial Interoperability Experiment

Status: 
Please note: This Request is closed as of 4 March 2013. 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: 
Mon, 03/04/2013 - 05:00
Description: 

The Open Geospatial Consortium (OGC) has announced a Call for Participation (CFP) in the OGC MilOps Geospatial Interoperability Experiment (MOGIE). The CFP document is available below. 

Command and Control (C2) Core (https://c2core.gtri.org) has been an emerging data exchange capability within Department of Defense over the past three years.  DoD CIO is now moving toward adopting the National Information Exchange Model (NIEM) (http://niem.gov). C2 Core, which is 93% aligned with NIEM technical standards, will be used as the foundation for developing a Military Operations (MilOps) Domain in NIEM. 

The purpose of this experiment is to ensure interoperability of the MilOps Domain with the OGC's geospatial standards and with tools built on those standards. This experiment will demonstrate that the MilOps Domain model and NIEM v2.1 technical concepts work in combination with OGC standards, such as the Geography Markup Language (GML) Encoding Standard and the Web Feature Service (WFS) Web coverage Service (WCS) and Web Mapping Services (WMS) interface standards.

The OGC members that are acting as initiators of the Interoperability Experiment are:

Expressions of interest for participation are due by 4 March 2013.

Contact Frank Klucznik (Frank.Klucznik [at] gtri.gatech.edu) for further details and to register as a participant.

Georgia Tech Research Institute (GTRI) is also one of the organizations that will be participating in the Interoperability Experiment. GTRI and other organizations planning to participate will develop tools, implement and deploy OGC service components or client applications, design a test plan, and prepare reports that contribute to the overall objectives of the experiment.

OGC testbeds, pilot projects and interoperability experiments are part of the OGC's Interoperability Program, a global, hands-on collaborative prototyping program designed to rapidly develop and test candidate specifications and then deliver these proven specifications into the OGC's Standards Program, where they are formalized for public release as OGC standards. These initiatives enable users and providers of geospatial technology to share the costs of developing standards that provide a foundation for "future-proof" enterprise architectures. Providers reduce their costs of developing and maintaining interfaces and encodings while gaining industry recognition, the confidence of an initiative's sponsoring organizations, and the market growth that results from open standards.

An OGC Interoperability Experiment is a rapid, low overhead, formally structured OGC-facilitated activity in which members achieve specific technical objectives that further the OGC Technical Baseline.

OGC Requests: 

The OGC requests comments on the OWS Context Conceptual Model and ATOM Extension Standards

Status: 
Please note: This Request is closed as of 17 February 2013. 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: 
Sun, 02/17/2013 - 05:00
Description: 

18 January 2013 - The Open Geospatial Consortium (OGC®) is seeking comments on the OGC OWS Context Conceptual Model and the associated ATOM Extension document candidate standards.

The OGC OWS Context Conceptual Model describes the use cases, requirements and conceptual data model of an OGC Web Services Context Document. A context document (OWS Context) defines a fully configured set of OGC services to be consistently shared, interpreted and invoked by clients. This standard model is a core model that can be extended and encoded as defined in extensions to the standard, such as the ATOM Extension and the JSON Extension, which has not yet been released.

An OGC Web Services Context Document (OWS Context) enables a set of configured information resources (service set) to be passed between applications as a collection of services. OWS Context supports in-line content as well. This candidate standard supports 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) or others to provide multiple users with a ‘common operating picture’. Additionally OWS Context can deliver a set of configured processing services (Web Processing Service (WPS)) parameters to allow processing to be reproduced on different nodes.

The OGC OWS Context Conceptual Model and the associated ATOM Extension document candidate standards are available for public review and comment below. Comments are due by 17 February 2012.

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 Seeks Comments on Candidate GeoPackage 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: 
Thu, 02/07/2013 - 05:00
Description: 

The Open Geospatial Consortium (OGC®) seeks public comments on the current draft of the candidate OGC GeoPackage (GPKG) Standard. The GPKG Standards Working Group will consider all comments when preparing a final draft of the candidate standard.

Mobile device users who require geospatial application services and associated data and who operate in disconnected or limited network connectivity environments frequently do not have open, available geospatial data to support their applications. Applications include such things as mobile workforce data capture and updates, volunteered geographic information, and real time annotations of map data in an emergency event.

The candidate OGC GeoPackage (GPKG) Standard provides an open, non-proprietary, platform-independent container for distribution and direct use of all kinds of geospatial data. The GeoPackage container and related API will increase the cross-platform interoperability of geospatial applications and web services in the mobile world.  Standard APIs for access and management of GeoPackage data will provide consistent query and update results across such applications and services.  

Future enhancements to the GeoPackage standard, a future GeoPackage Web Service standard, and modifications to existing OGC Web Service (OWS) standards to use GeoPackages as exchange formats will allow OWS to support provisioning of GeoPackages throughout an enterprise or information community.

Interoperability of GeoPackage implementations by several participants is being tested and will be demonstrated in the 15 January 2013 OGC Web Services Testbed (OWS-9) Demonstration. The current reference implementation bases, SQLite and SpatiaLite, are open source resources developed by OGC members. The SQLite reference implementation is sponsored in part by the SQLite Consortium, which includes a number of OGC members. SpatiaLite is built on OS-Geo open source libraries by the president of GFOSS.it and others.

The current draft of the candidate OGC GeoPackage (GPKG) Standard 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: 

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: 

The OGC seeks comment on SensorML 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: 
Wed, 12/05/2012 - 05:00
Description: 

The Open Geospatial Consortium (OGC®) seeks public comment on the candidate OGC SensorML 2.0 Encoding Standard.

SensorML is a machine-readable language for describing sensors, actuators, and processes surrounding measurement. SensorML is a key component of the OGC Sensor Web Enablement (SWE) suite of standards.

SensorML 2.0 includes the following changes to the previous version 1.0.1, which was approved in 2007:

  •  Separation of SWE Common Data as a separate standard
  •  More tightly defined rules
  •  Conformance classes allowing for incremental support of SensorML in software and derived encodings
  •  A host of examples provided at initial release of the specification.

 

In addition, SensorML 2.0 includes the following new or improved features:

  •  Support for property extension using external schema
  •  Better-defined support for positions and dynamic state (e.g. location, orientation, velocity, and acceleration)
  •  Better support for inheritance allowing for compact descriptions of deployed devices and processes
  •  Direct access to real-time values and data streams
  •  Better support for multiplexed data streaming (i.e. streams with disparate messages).

SensorML 2.0 supports the descriptions of things within the Internet of Things (IoT) and Web of Things (WoT) by providing a common standard for sensors ("things the measure"), actuators ("things that act"), and processors ("things that calculate"). Efforts are also underway to take advantage of the complementary role that SensorML 2.0 can play with the OGC City Geography Markup Language (CityGML) Encoding Standard and the candidate OGC standard IndoorGML.

The OGC SensorML 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: 

The OGC seeks comment on GML Coverages GeoTIFF extension and WCS 2.0 GeoTIFF extension 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: 
Thu, 11/29/2012 - 05:00
Description: 

The Open Geospatial Consortium (OGC®) seeks comment on a GeoTIFF extension to the OGC GML Coverages (GMLCOV) 1.0 Standard and on a GeoTIFF extension to the OGC Web Coverage Service (WCS) 2.0 Standard, based on the former.

The OGC Geography Markup Language (GML) Encoding Standard is a widely used XML encoding for geospatial data of all types. OGC "coverages", which can be encoded in GML, associate positions within a bounded space to feature attribute values. Examples of these geospatial coverages include Earth images, referenced and non-referenced rasters, curvilinear grids, and point clouds.

The OGC GML 3.2.1 Application Schema – Coverages (GMLCOV), based on OGC Abstract Topic 6 (which is identical to ISO 19123), provides a unified method for encoding OGC coverages in GML, the OGC Sensor Web Enablement (SWE) Common Standard, and the OGC Web Coverage Service (WCS) Interface Standard. As GMLCOV is independent of a particular service definition, it allows coverage data to be exchanged through different types of services that implement these OGC standards.

To provide maximum flexibility in sharing coverage data, the GML Coverages GeoTIFF extension provides a way to encode coverages that are represented in encoding formats other than GML, such as GeoTIFF. The WCS 2.0 GeoTIFF extension binds the former extension to WCS 2.0 to allow usage of GeoTIFF encoded coverages with WCS. The OGC seeks public comment on the OGC documents describing the candidate GMLCOV and WCS extension standards for encoding GeoTIFF data in GMLCOV and using them with WCS. These documents are 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: 

OGC Seeks Comments on "NIL Extension" to Geography Markup Language (GML)

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: 
Fri, 11/23/2012 - 05:00
Description: 

The Open Geospatial Consortium (OGC®) seeks public comment on the candidate "GML-NIL profile" of the OGC Geography Markup Language (GML) Encoding standard. GML is a widely used XML grammar for encoding information about geographical features. The GML-NIL profile provides a way to allow data providers to make a best effort to supply data according to an application schema, even if they do not have values for all feature properties. This is achieved by marking the application schema as a whole as ‘nillable=true’ and using OGC ‘nil’ URIs in links for missing data. This reverses the usual pattern which has a default value of nillable=false.   

 

The GML-NIL pattern of use has been used informally for several years in Earth and environmental science applications, and this candidate standard merely aims to formalize and document the practice. It is expected to be useful in many applications where a heterogeneous community wishes to enable participation by a wide variety of members with different capabilities and data sources. The submission team is composed of members of the GeoSciML project.

 

The candidate OGC GML-NIL standard documents are available for review and comment below.

Downloads: 


 Nillable GML (12-110)   

 



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 comments on Climate and Forecast (CF) extension to NetCDF Core data model 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: 
Fri, 09/21/2012 - 04:00
Description: 

The Open Geospatial Consortium (OGC®) membership seeks comments on an OGC candidate standard, the CF-netCDF Data Model extension to the existing OGC Network Common Data Form (netCDF) Core Encoding Standard version 1.0. 

The CF-netCDF Data Model is a flexible data model widely used in climate and weather forecast systems as well as for other types of environmental data. The candidate CF-netCDF Data Model extension to the existing OGC Network Common Data Form (netCDF) Core Encoding Standard version 1.0 is the latest step in establishing CF-netCDF as an OGC standard for binary encoding.  This will enable standard delivery of data in binary form via several OGC service interface standards.

The OGC netCDF encoding supports electronic encoding of geospatial data, specifically digital geospatial information representing space- and time-varying phenomena. NetCDF (network Common Data Form) is widely used internationally to communicate and store many kinds of multidimensional data, although it was originally developed for the Earth science community.  The netCDF data model is particularly well suited to providing data in forms familiar to atmospheric and oceanic scientists: namely, as sets of related arrays. 

The conventions for climate and forecast (CF) metadata are designed to promote the processing and sharing of files created with the netCDF API.  The conventions define metadata that provide a definitive description of what the data in each variable represents, and the spatial and temporal properties of the data. This enables users of data from different sources to decide which quantities are comparable, and facilitates building applications with powerful extraction, regridding, and display capabilities.

NetCDF was developed and is maintained and actively supported by the University Corporation for Atmospheric Research (UCAR) (www.ucar.edu). UCAR and other OGC members introduced the first netCDF specification as a candidate OGC standard to encourage broader international use and greater interoperability among clients and servers interchanging data in binary form. 

The candidate CF-netCDF Data Model extension to the existing OGC Network Common Data Form (netCDF) Core Encoding Standard version 1.0 and information about submitting comments on this document are available below. The public comment period closes on September 21, 2012.

Downloads: 
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 Comments on GeoServices REST API Candidate Standard

Status: 
Please note: This Request is closed.
Closing Date: 
Sat, 08/18/2012 - 04:00
Description: 

The Open Geospatial Consortium (OGC®) seeks public comment on the candidate OGC GeoServices REST API standard. The GeoServices REST Application Programming Interface (API) provides a standard way for web clients to communicate with geospatial technologies, such as Geographic Information System (GIS) servers, based on Representational State Transfer (REST) principles.

Using this API, clients, such as a web browser application, issue requests to resources on the server identified by structured Uniform Resource Locators (URLs). The server responds with map images, text-based location details or other representations of geospatial information.  From a services perspective the API offers a mechanism to interact with map, image and feature services and perform geospatial analysis. This JavaScript Object Notation (JSON)-based, RESTful API is intended to make implementing servers instantly usable by developers working with widely used REST-based scripting and programming languages, as well as mobile platforms. End users can then use these developers' Web applications to discover and access the services and use them in their workflows.

In early 2011, Esri contacted the Open Geospatial Consortium about submitting the GeoServices Rest API as a candidate OGC standard. The API was initially developed by Esri and implemented on the ArcGIS for Server platform. This submission was approved through the OGC process and then a Standards Working Group (SWG), composed of many OGC members, performed a detailed review and rewrote the API as an OGC interface standard, removing Esri-specific software references. The OGC’s adoption of this candidate standard will provide the wider Web developer community with additional standards-based choices for leveraging geospatial information.

The candidate OGC GeoServices REST API 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: 

OGC Seeks Comments on NetCDF Enhanced Data Model Extension 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.
Description: 

The Open Geospatial Consortium (OGC®) membership seeks comments on an OGC candidate standard, the Network Common Data Form (NetCDF) NetCDF Enhanced Data Model Extension Encoding Standard. This document specifies an extension to the existing OGC Network Common Data Form (NetCDF) Core Encoding Standard version 1.0.

The OGC netCDF encoding supports electronic encoding of geospatial data, specifically digital geospatial information representing space- and time-varying phenomena. NetCDF (network Common Data Form) is widely used internationally to communicate and store many kinds of multidimensional data, although it was originally developed for the Earth science community. The netCDF data model is particularly well suited to providing data in forms familiar to atmospheric and oceanic scientists: namely, as sets of related arrays. NetCDF was developed and is maintained and actively supported by the Unidata Program Center (http://www.unidata.ucar.edu) of the University Corporation for Atmospheric Research (UCAR).
 
The netCDF classic data model has previously been established as the core OGC CF-netCDF standard. With this extension to the core standard for the enhanced data model, complex data structures can be represented very easily, allowing for more efficient programming. In performance-critical applications, the enhanced model provides significant benefits. Moreover, if existing HDF5 (Hierarchical Data Format, release 5) applications that depend on groups, user-defined types, unsigned types, or strings produce or use these data, the netCDF enhanced data model is required. The recently introduced candidate NetCDF Enhanced Data Model Extension Encoding Standard is the latest step in a longer-term plan for establishing CF-netCDF as an OGC standard for binary encoding, which will enable standard delivery of data in binary form via several OGC service interface standards, including the OGC Web Coverage Service (WCS), Web Feature Service (WFS), and Sensor Observation Service (SOS) Interface Standards.
 
The candidate OGC Network Common Data Form (NetCDF) NetCDF Enhanced Data Model Extension Encoding Standard and information about submitting comments on this document are available below. The public comment period closes on July 1, 2012.
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