OGC Requests

The OGC seeks comment on revised GML in JPEG 2000 Encoding Standard

Status: 
Please note: This Request closed on 19 March 2014.
Open Date: 
Mon, 02/17/2014
Closing Date: 
Wed, 03/19/2014 - 04:00
Description: 

The Open Geospatial Consortium (OGC®) seeks comment on the candidate GML in JPEG 2000 Encoding Standard version 2. This geospatial data encoding standard defines how the Geography Markup Language (GML) is to be used within JPEG 2000 images for adding geographic content to imagery. Once approved, the revised GML in JPEG2000 version 2 candidate standard joins a suite of international open standards that provide a platform for seamless service-based publishing, discovery, assessment, ordering, access and processing of geospatial information.

Version 1.0.0 of this standard was published in January of 2006. The new candidate version 2 of the standard exploits the capabilities of the OGC GML Coverage Application Schema (GMLCOV) and the OGC Web Coverage Service (WCS) 2.0 Interface Standard that have been made available by the OGC since 2006. Version 2 eliminates other shortcomings of Version 1 and also addresses shortcomings of competing methods of using JPEG2000 in geospatial applications.

All OGC standards are free and publicly available on the OGC Standards Page. The candidate GML in JPEG 2000 Encoding Standard version 2 can be downloaded below.

The GML in JPEG 2000 Standards Working Group (GMLJP2 SWG) will consider comments on the candidate GMLJP2 Standard that have been posted through 19 March 2014

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 standard, OGC® OpenSearch Geo and Time Extensions

Status: 
Please note: This Request closed on 13 December 2013. 
Open Date: 
Wed, 11/13/2013
Closing Date: 
Fri, 12/13/2013 - 05:00
Description: 

The Open Geospatial Consortium (OGC®) is seeking comments on the candidate standard, "OGC® OpenSearch Geo and Time Extensions". This document extends the implementation of the popular OpenSearch technologies so that users can take advantage of the geospatial search capabilities enabled by OGC standards. 

Different types of content require different types of search engines. OpenSearch (http://www.opensearch.org) provides a standard way of describing search engine capabilities so that they can be leveraged by search client applications like modern Web browsers. The OGC® OpenSearch Geo and Time Extensions candidate standard provides a very simple way to configure OpenSearch for spatial and temporal queries over distributed repositories of contents having geographic and time properties, and for syndication of these search results in one large index.

Digital resources are becoming more complex and diverse, and this is especially true with respect to sensor data and Web connected sensors. Such data is increasingly becoming discoverable and usable through open interfaces that implement OGC standards (http://www.opengeospatial.org/standards), but most of this data remains undiscoverable via popular search engines. The OGC OpenSearch Geo and Time Extensions candidate standard specifies how to enhance search engines and configure them to access sensor data servers, so that users can query resource URLs through search combinations of time extents, geographic areas or location names, and likely keywords. 

The OGC® OpenSearch Geo and Time Extensions draft standard includes work undertaken within the GENESI-DR (Ground European Network for Earth Science Interoperations - Digital Repositories) project funded by the 7th Framework program of the European (EC Grant Agreement no. 212073) and the follow-up project GENESI-DEC (Ground European Network for Earth Science Interoperations - Digital Earth Community) funded by the same program (Contract nº RI-261623). The document was further supported by the ESA HMA (Heterogeneous Missions Accessibility) initiative and related projects.

The following organizations submitted this document to the Open Geospatial Consortium:

  •    Terradue Srl
  •    FGDC
  •    FortiusOne, Inc.
  •    EDINA
  •    Cubewerx Inc.

Download the candidate OGC OpenSearch Geo and Time Extensions Standard below.  Comments are due by 13 December 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: 

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

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

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

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

Downloads: 

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

Request for Comments (RFC) on Candidate Specification 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 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 membership of the Open Geospatial Consortium, Inc. (OGC) is requesting comments from the public on the candidate OGC Document, "The OGC Specification Model - Writing Modular Specifications".

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

This standard has been referred to as the "core and extension model" due to the insistence on a modular structure throughout all parts of a standard and its implementation. Eventually, all OGC standards will be transitioned to the new structure. This will help standardize the manner in which OGC standards are written and implemented, making implementations easier to test for compliance, thus improving interoperability between and swap-ability between implementations.

The 30 day public comment period begins March 12, 2009 and closes on April 11, 2009. Comments will be reviewed and processed by the OGC Membership. The intent is to edit the Specification Model candidate standard and move the document to be an approved OGC standard. The Specification Model Request for Comment document 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] opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template.
Subscribe: 
You may wish to be added to the distribution list to receive comments as they are submitted:
Subscribing to the the list will also allow you to view comments already received, which can be found in the List Archives.
OGC Requests: 

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

Status: 
Please note: This Request is closed.

 

Description: 


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

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

 

Overview

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

The RFQ/CFP is available below.

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

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

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

The OWS-9 sponsors are:

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

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

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

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

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

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

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

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

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

Downloads: 

 

RESPONSE TEMPLATES (not included in above package)

 

 

 

Questions: Bidder's Conference

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

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

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

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

You must register for this session at:

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

 

Clarifications Document

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

Current clarifications

OGC Requests: 

Request for Comment on CityGML Standard

Status: 
Please note: This Request is closed. The documents listed below have been adopted by the OGC Technical and Planning Committee. These specifications are under control of the specification Revision Working Group and will be released after the edits and revisions. For the most current version please check our Standards Page.
Description: 
The Open Geospatial Consortium, Inc. (OGC) is requesting public comment on the candidate CityGML Encoding Standard. CityGML is a Geography Markup Language 3 (GML3) application schema for the storage and exchange of virtual 3D city models.

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

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


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

OGC Seeks Comment on Geography Markup Language 3.3 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®) seeks public comment on the candidate version 3.3 of the OGC Geography Markup Language (GML). GML 3.3 builds on GML 3.2.1, published by ISO as ISO 19136:2007, and extends GML with additional schema components based on requirements requested by various domains of interest. For example, the 3d modeling community suggest the addition of triangular meshes (TINs) to GML. GML 3.3 is fully backwards compatible with GML 3.2.

GML defines an XML data encoding for geographic data and a grammar to express models of such data using XML Schema. GML has come into wide use since it was first adopted as an OGC standard in 2001 (http://www.ogcnetwork.net/gmlprofiles for examples). GML is the standard that enables information communities and other standards organizations such as the Internet Engineering Task Force (IETF) and OASIS to insert geospatial elements into their standards and be confident that their standards will be compatible with mainstream information infrastructure methods of conveying spatial/temporal information.

Some of the changes between the previous version 3.2.1 and 3.3 are:

  • Support for additional date representations based on ISO 8601 (Representation of dates and times)
  • Support for an additional, compact encoding of commonly used geometry types
  • Support for a new encoding of Triangulated Irregular Networks (TINs)
  • Support for Linear Referencing
  • Extensions to the XML encoding rule
  • Support for grids used by the meteorological and ocean observation communities

All extensions are made in separate XML namespaces to support a modular use of components from the GML schema.

Information on the change requests addressed in GML v3.3 can be found athttp://external.opengeospatial.org/twiki_public/GML/ChangeRequests. The candidate OGC GML v3.3 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 proposal to update ISO 19107:2003 Geographic information – Spatial

Status: 
Please note: This Request closed on 28 November 2013. Any comments submitted prior to 26 November will be fed into the ISO ballot.
Closing Date: 
Thu, 11/28/2013 - 05:00
Description: 

29 October 2013 - The Open Geospatial Consortium (OGC®) is seeking comments on a draft NWIP (New Work Item Proposal) package intended for submission to ISO TC
211 to kick off a project to update ISO 19107:2003 Geographic information – Spatial Schema.

ISO 19107:2003 has been adopted as the OGC Abstract Specification for Geometry. Since this document is the world standard for the representation of geographic geometry, it is used (directly or indirectly) by nearly every specification and standard for geospatial data representations for both ISO and OGC. 19107 is also used by other standards organizations that use OGC standards directly as a cited source or that mimic OGC structures. In updating the Spatial Schema after 10 years of use, ISO TC 211 and the OGC will have to balance the needs for backward compatibility and the needs for new and more appropriate functionality.

This NWIP package was prepared by the OGC Simple Features Standards Working Group in its efforts to update the OGC Simple Features Abstract Specification, which depends heavily on the Spatial Schema.

Comments are due by Thursday, November 28, 2013. All comments received will be submitted by OGC to the ISO and will be adjudicated in the ISO process. The ISO will provide  a formal response to the OGC that will be published before the ISO standard is put to a final vote as an International Standard.

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 Web Services, Phase 5 (OWS-5) Request For Quotation and Call For Participation

Status: 
This Request is Closed.
Description: 
RFQ Issuance Date: 11 May, 2007
OWS-5 Bidder's Conference: 22 May, 2007
Proposal Due Date: 8 June, 2007

 


Overview

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

In January of 2007, the OGC issued a call for sponsors for an OGC OWS-5 Interoperability initiative testbed activity to advance OGC's open framework for interoperability in the geospatial industry. Three meetings were conducted with potential OWS-5 sponsors to review the OGC technical baseline, to discuss OWS-4 results, and to identify OWS-5 requirements. Sponsors have expressed keen interest in advancing standards for geospatial workflow, sensor webs, geospatial digital rights management, GML information communities, and KML. After analyzing the sponsors input, the OGC Interoperability Team recommended to the sponsors that the content of the OWS-5 initiative be organized around the following 6 threads:

  1. Sensor Web Enablement (SWE)
  2. Geo Processing Workflow (GPW)
  3. Information Communities and Semantics (ICS)
  4. Agile Geography
  5. Compliance Testing (CITE)
  6. CAD / GIS / BIM

Introductions to these 6 threads are below.


OWS-5 Sponsors

  • BAE Systems - Network Systems
  • Google
  • Lockheed Martin Integrated Systems & Solutions
  • Northrop Grumman
  • US National Aeronautic and Space Administration (NASA)
  • US National Geospatial-Intelligence Agency (NGA)

OWS-5 Threads

1) Sensor Web Enablement (SWE)

The Sensor Web subtask will continue to mature the existing set of SWE work items to enable the federation of sensors, platforms and management infrastructure into a single sensor enterprise. In OWS-5,interoperability engineering activities will focus on integration and demonstration of physical sensors and simulators within a realistic operating environment. In addition, progress is expected on enhancements to the SWE specifications as described in the "Future work" clauses of the respective baseline documents.

Emphasis for SWE during this phase of the OWS project will be on:

  • Leveraging results of OWS-4 to extend and integrate those specifications and implementations.
  • Demonstrating SWE's ability to meet the geospatial needs of large enterprise system by integrating SWE into realistic enterprise workflow scenarios supported by Use Cases.
  • Continuing previous test-bed efforts to integrate IEEE 1451 sensor into SWE
  • Establishing cross thread collaboration with CGB by integrating sensors into 3D models.
  • Harmonizing SWE concepts and specifications with other OGC specifications and initiatives.
  • Developing compliance test for SWE specification to accelerate adoption

2) Geo Processing Workflow (GPW)

No geo-process is an island, or more exactly no geo-process should be an island. By interconnecting geo-processes through service chaining and orchestration to meet workflow requirements, creation of valued-added enterprise systems is possible that demonstrate the power of interoperability and service oriented architectures. The OWS-2 Image Handling for Decision Support (IH4DS) thread extended the baseline of OWS service types with image processing services. OWS-3 Common Architecture activities built on that work by applying the services developed in OWS-2 to the SWE and GeoDSS environments. OWS-4 furthered workflow service development by investigating the patterns for building general purpose geo-processing services and prototyping a feature editing scenario.

OWS-5 will further mature geoprocessing workflows by bringing together more services in real-world image processing scenarios, developing a SOAP/WSDL framework for all OGC services, and incorporating rights-based access to resources. The GPW thread in this testbed is organized into the following inter-related work areas:

  • Enterprise integration and refinement of OGC Web Service architecture
  • Enterprise integration of OGC Web Services using service chaining and workflow to implement the full service life cycle for the Publish-Find-Bind pattern
  • Integrate GeoRM services and components in the workflow with focus on Identity, Authorization, Authentication and Trust model

3) Information Communities and Semantics (ICS)

The ICS thread seeks to advance the understanding and use of complex geographic information types within an interoperability architecture. A variety of geospatial data types will be modeled in UML and converted into GML using the UGAS ShapeChange tool. Information about these data and the services provisioning them will be registered in a number of catalogs and utilized in workflows developed in the GPW thread.

This activity will test the ability of OGC standards to facilitate one of the core scenarios in any spatial data infrastructure-information publication.

4) Agile Geography

This testbed focuses on process integration and ‘right-sizing' of services to demonstrate the power of interoperability and service-oriented architectures using OGC Web Services. The Agile Geography thread explores this goal through two distinct activities.

The first explores the future of KML, OWS Context, and lightweight payloads of geospatial information on the Web in general, applying the concepts of links, bookmarks and Web pages to digital cartography and geospatial information management. Participants will explore the harmonization of KML and OWS Context XML encodings and prototype client and server software that exploits these document types.

The second activity-GeoSynchronization and Sharing-extends the WFS-Transactional architecture to target a federated environment comprised of loosely affiliated parties who desire to collaborate, in full or in part, on the maintenance of a shared geospatial data set.

5) Compliance Testing (CITE)

The OGC Interoperability Program and the OGC Specification Program have achieved a great deal of momentum as a result of the multiple OGC Web service specifications that have recently been published. Key consumers in the geospatial industry are modernizing their enterprises and realizing spatial data infrastructures (SDIs) based on the applicability and interoperability of OGC web services.

The major geospatial industry consumers require verifiable proof of compliance with OGC specifications in order to reach the desirable outcome of interoperability. In OWS-5 the CITE thread advances testing for Web Coverage Service and Catalog Service for the Web to versions 1.1 and 2.0.2 respectively. OWS-5 also initiates Sensor Web compliance testing, with the first Sensor Observation Service and Sensor Planning Service tests.

Also included in the requirements are reference implementations of these specifications. A reference implementation is an open source, fully functional implementation of a specification in reference to which other implementations can be evaluated. The OGC provides open source reference implementations to ensure maximum transparency of its specifications for both vendors and customers.

6) CAD / GIS / BIM (CGB)

NOTE: Work items within the CAD/GIS/BIM thread are provided for comment -- with the anticipation that CGB will be conducted in Phase 2. Comments on CGB are solicited now to support a future RFQ/CFP for Phase 5.2 as defined in Master Schedule.

The CGB activities in the OWS program are directed toward bridging the information models and workflows of the various communities involved with the representation of the built environment in three dimensions. Standards for interoperable exchange of information about buildings and standards for representing and exchanging information about cities at broad-scale are beginning to enable owners, administrators and toolmakers to make investments in developing assets based on these standards. Applications of integrated city models are emerging in the mass-market sphere, witness Google Earth and Microsoft Local Live. One can imagine the extension of these tools into the domains of location-based services to emergency preparedness and response. These applications will require the integration of semantically rich authoritative information that is likely to be created in a highly distributed fashion. This thread of OWS-5 focuses on developing a services-based architecture that will bring the necessary information together, and to make it accessible in a secure way.

Downloads: 

Proposals for cost reimbursement are due by June 8, 2007.

Click a link to download the .zip archive:
DOWNLOAD COMPLETE PACKAGE
Complete OGC Web Services, Phase 5 (OWS-5) RFQ (zip format)

OGC Web Services, Phase 5 (OWS-5) Bidder's Conference Information


A Bidder's Conference is currently scheduled for May 22.
Time: 15:00 UTC, 5:00 PM CEST, 11:00 AM EDT, 8:00 AM PDT
Phone line: +1 512-225-3050 passcode:36429#.

Clarifications to OWS-5 RFQ/CFP

The following clarifications apply to the Request for Quotation/Call for Participation in OGC Web Services, Phase 5 (OWS-5) as issued on 11 May 2007. This list will be updated as additional clarifications are needed. The most current list will always be posted here:

Download OWS-5 RFQ/CFP Clarifications

 


OGC Requests: 

OGC Calls for Participation in FAA Information Dissemination Pilot

Status: 
Please note: This Request is scheduled to close on 18 October 2010 at 9:00 PM EDT.
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 Special Activity Airspace (SAA) Dissemination Pilot, sponsored by the US Federal Aviation Administration (FAA).

 

The RFQ/CFP is below. Responses are due by October 18, 2010. A bidders’ teleconference will be held on October 4, 2010. The Point of Contact for the SAA SWIM Pilot is Nadine Alameh nalameh [at] opengeospatial.org.

 

The FAA SAA Dissemination Pilot will extend the SAA SWIM Services to enable the dissemination of SAA information (including updates and schedule changes) to National Airspace System (NAS) stakeholders and other external users via services that implement OGC Web Services (OWS) standards.

 

In support of the Next Generation Air Transportation System (NextGen), the FAA SWIM program seeks to achieve systems interoperability and information management for diverse Air Traffic Management (ATM) systems using Service-Oriented Architectures (SOA). The FAA SWIM capabilities include supporting the exchange of SAA information between operational ATM systems. SAAs include Special Use Airspaces (SUA) - regions of airspace designated for use by the military ensuring no other traffic uses that airspace during scheduled times.

 

The FAA SAA DisseminationPilot shall build on SAA SWIM Services leveraging the OGC Web Feature Service (WFS), the OGC Feature Portrayal Service (FPS), the (draft) Event Service and the Aeronautical Information Exchange Model (AIXM), Support the filtering, access and portrayal of SAA information as well as the notification to subscribed users of SAA updates and schedule changes,and support the evolution towards end-to-end automated information flow from the US Department of Defense (DoD) - originators of SAA activation requests - to airlines and other NAS stakeholders.

OGC Requests: 

Pages