OGC Testbed 10
OGC Testbed 10
Reduced Risk - More Choices - New Technologies - Lower Cost
Interested? Read on!!
On July 15, 2013, 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 Testbed 10.
The RFQ/CFP is available at http://www.opengeospatial.org/standards/requests/103.
- Responses are due by 5 pm EST on 26 August 2013.
- An IP Program and Testbed 10 Q&A Webinar will be held on 6 August 2013. More information will be available at the URL above.
We invite you to follow us on twitter, Linkedin or Facebook to stay updated on the the Q&A Webinar, clarifications to requirements, kickoff details, etc.
The OGC Testbed 10 Kickoff workshop for the CCI and Open Mobility threads (see below) will be held 7-9 October 2013 in Washington, DC. The Aviation thread kickoff will be held 27 September in Frascati, Italy during the week of the OGC Technical Committee Meeting in Frascati.
The Point of Contact is Lew Leinenweber: techdesk [at] opengeospatial [dot] org.
The OWS-10 sponsors are:
- AGC (Army Geospatial Center, US Army Corps of Engineers)
- ESA (European Space Agency)
- FAA (US Federal Aviation Administration)
- GeoConnections - Natural Resources Canada
- Harris Corporation
- Lockheed Martin Corporation
- NGA (US National Geospatial-Intelligence Agency)
- NOAA National Weather Service
- USGS (US Geological Survey)
- UK DSTL (UK Defence Science and Technology Lab)
OGC Testbed 10 builds on the outcomes of prior OGC initiatives (http://www.opengeospatial.org/resource/demos) and is organized around the following threads:
- Cross-Community Interoperability (CCI): Increase Geospatial community interoperability by building on CCI OWS-9 work in semantic mediation, volunteer geographic information (VGI), provenance and data quality, and Global Gazetteer. Explore the potential of interoperability in the hydrology domain and utilizing ontologies to more easily share and visualize geospatial data.
- Open Mobility: Explore the geospatial standards requirements needed to support the growing emerging mobile environment where client applications are mobile, information services are mobile, and increasingly distributed across cloud infrastructures. The Open Mobility thread will address these requirements while leveraging on the work achieved in the OWS-9 Testbed in the areas of Geopackages and Geopackaging services and new OWS Context encodings.
- Aviation: Develop and demonstrate the use of the Aeronautical Information Exchange Model (AIXM) and the Flight Information Exchange Model (FIXM), building on the work accomplished in prior testbeds to advance the applications of OGC Web Services standards in next generation air traffic management systems to support European and US aviation modernization programs.
The RFQ/CFP includes details of these threads as well as details on participation eligibility, selection process and kickoff workshop information.
OWS testbeds are part of OGC's Interoperability Program, a global, hands-on and collaborative prototyping program designed to rapidly develop, test and deliver proven candidate specifications into OGC's Standards Program, where they are formalized for public release. 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 OGC standards.
In the OGC Interoperability Program, organizations collaborate to:
- Reduce technology risk by aligning vendors to produce standards and best practices to address interoperability challenges. Vendors are motivated to develop these standards with their own resources.
- Expand the market and improve choice by encouraging industry adoption of new standards and best practices, ensuring market availability of interoperable solutions
- Mobilize new technologies by facilitating broad industry influence and early adoption of newly available standards
- Reduce lifecycle costs by reducing or eliminating the need for custom integration