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
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:

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

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

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

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 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
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 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
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 Requests

OGC Seeks Comments on GeoServices REST API Candidate Standard

Status: 
Please note: This Request is closed.
Closing Date: 
Sat, 08/18/2012
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:

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 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.
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 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
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.ogc.org/webex_auth.php?AT=JM&MK=798776961&PW=CflSRhNe

      Clarifications

      The most recent clarifications are dated 2012-08-20

      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 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.  The Clarifications Document is here: 

      Current clarifications

      OGC Requests: 
      OGC Requests

      Pages