1 / 13

OpenGIS Catalog Interface RFP Response

This document presents the response of the EO/GEO team to the Open GIS Consortium Catalog Interface RFP. It includes key requirements, existing protocols, proposals, and a plan for convergence.

jmaker
Download Presentation

OpenGIS Catalog Interface RFP Response

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EO/GEO Team Response toOpen GIS ConsortiumCatalog Interface RFP • George Percivall • percivall@harp.gsfc.nasa.gov • February 1999

  2. Main Topics - Agenda • OpenGIS Catalog Interface RFP • Issued by Open GIS Consortium (http://www.opengis.org/) • Issued March 1998 • OpenGIS Project Document Number 98-001 • EO/GEO Team Response to RFP • Based on CEOS CIP and FGDC GEO protocols • Working to Converge Responses • Working with NIMA Catalog Team • Combined response to OGC in May 1999

  3. OGC Catalog RFP - Key Requirements • Specify standard interfaces for geospatial resource discovery and access services, independent of specific distributed computing platforms (DCPs) • Specify specific profiles extending the general interface: CORBA, DCOM, SQL, Others • Provide operations for creating and maintaining collections of geospatial datasets, including a metadata set and metadata entities associated with each stored dataset. • A detailed description of how the profiles support interoperability among catalog services implemented in DCPs • Consistent with other OpenGIS specifications

  4. Data Structure Classes of OpenGIS Catalog Services

  5. Responses to OGC RFP Existing Protocols Proposals to OGC FGDC GEO Profile EO/GEO Team CEOS Catalog Interoperability Protocol (CIP) Joint Submission (DCS and EO/GEO) May 1999 NIMA - Geospatial and Imagery Access Services (GIAS) Distributed Catalog Services (DCS) Nov. 1998

  6. EO/GEO Team • International Collaborative Effort • Industry • Blue Angel Technologies • Hammon, Jensen, Wallen and Associates, Inc. (HJW) • Environmental Systems Research Institute • Government Agencies • FGDC • NASA • CCRS • JRC

  7. EO/GEO Proposal • All messages formed in XML • Search and Retrieval messages from Z39.50 • XML passed over multiple Distributed Computing Platforms (DCPs): HTTP, CORBA, COM • Bridges provide cross-DCP capability, without modifying XML messages • ISO Metadata (15046-15, TC 211) as core for distributed search • Supports search for collection and product metadata through hierarchical collections

  8. Cross DCP Interoperability RM Relational Database INTERNET RM RM RM SQL ODBC CIP Proxy Client Proxy Client LDAPDomain XML CIP Domain CORBA/OGC Gateway CIP/OGC Gateway XML SQL/ ODBC Domain Client OGC Catalog Services GILS Domain OMG Domain GEO Domain CORBA/OGC Gateway COM Domain XML GEO/OGC Gateway Proxy Client XML CORBA Proxy Client GEO Clearinghouse GEO Server GEO Server GEO Server

  9. Approach to Convergence • Two responses presented to OGC in December 98 • Desirable to merge two approaches • Joint assessment of a single approach in January 99 • Results reported Monday (2/8) to OGC • Second unified submission planned for May 99 Global Information Discovery Information Exploitation AltaVista GEO CIP DCS SimpleFeatures

  10. Cross-DCP Approach General Model (UML) XML DTDs for messaging IDL for CORBA MIDL for COM

  11. Catalog Service Interoperability - HTTP-CORBA Example Browsers Client (or webserver) Client OGC HTTP OGC CORBA OGC HTTP OGC CORBA Application Servers Catalog server Bridge Catalog server OGC HTTP OGC CORBA Catalog Server translator Legacy Catalog Server Metadata server Metadata Server

  12. Functional Decomposition of Catalog Services Catalog Service Includes init, close functions Discovery Service (mandatory) Access Service (optional) Management Service (optional) Services Direct Brokered

  13. Conclusion • Combined Submission Feasible • Cross DCP approach using common General Model • Messages and Object approaches • Issues of Interoperability • Compatibility with OGC Simple Features • Query Language for cross DCP Discovery • Metadata Model Independence • Use of XML • Major follow-on activities • Communication of lessons learned to OGC • Develop implementations for demonstrations • Develop commercialization plan • Prepare joint response documents to RFP

More Related