1 / 44

Interoperable Catalogues from HMA - FedEO

Interoperable Catalogues from HMA - FedEO. Slides assembled from various sources, with thanks to the contributers to HMA / FedEO A precursor for GMES Data Access and Integration and an overall contribution to GEOSS Jolyon Martin, ESA. Enterprise View: Context within GMES.

powa
Download Presentation

Interoperable Catalogues from HMA - FedEO

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. Interoperable Catalogues from HMA - FedEO Slides assembled from various sources, with thanks to the contributers to HMA / FedEO A precursor for GMES Data Access and Integration and an overall contribution to GEOSS Jolyon Martin, ESA

  2. Enterprise View: Context within GMES

  3. Information Viewpoint main components ISO19115 Collection Metadata ISO 19119 Service Metadata GML Schema for Earth Observation Products Information Viewpoint:Overview

  4. Information Viewpoint:OGC 06-080 Earth Observation Products • A base schema (eop) with specializations for Optical Sensors (opt), Synthetic Aperture Radar (sar), Atmospheric Instruments (atm) and mission specific (e.g. phr) • GML payload aligned with tag names from 19115-part II draft • Based on GML observation • Currently available as best practice paper on OGC web site xyz.xsd phr.xsd Catalogue metadata for specific mission sar.xsd opt.xsd atm.xsd Catalogue metadata for mission type eop.xsd Catalogue metadata for EO products smXML - gmd (ISO 19139) Generic and geometric catalogue metadata gml Schema/namespaces for optical missions Schema/namespaces for atmospheric missions Schema/namespace for radar missions

  5. GML observation

  6. GML Viewers EO Product GML Prospects Radar Altimetery specialisation currently being added CNES Meteo specialisation proposed by Eumetsat Use of the metadata as part of product format within GMLJP2 being explored Information Viewpoint

  7. Service Viewpoint: Overview • Overall Goal: a standardized, harmonized set of interfaces that support a service oriented view of the heterogeneous mission ground segments, which can be implemented in a cost-effective manner; enabling the construction of compound / value added services from basic interfaces. • Discovery (collection, services) • Catalogue (earth observations) [ Order (archive, subscription, on-line access) ] [ Programming (order for acquisitions, mission planning feasibility) ] [ Data Access (wcs, wms) ] [ User Management, Service Orchestration, Monitoring & Control ...]

  8. Interface Standards Overview ISO 19115 OGC CAT OGC SPS ISO 19115 part2 ISO 19119 OGC WMS 19139 ISO extensionpackage(CIM) ebRIM profile Discovery OGC WCS GML Appl Schema EO extensionpackage(ebRIM) Catalogue Order Programming

  9. ebRIM Application Profile EO Products Extension Package ebRIM Model Mapping HTTP Protocol CSW (Catalogue Service/Web) OGC Catalogue Services 2.0 Catalogue Interface (Abstract) Service Viewpoint: 06-131 Catalogue • Discussion paper at the OGC: (06-131r1_EO_Products_Extension_Package_for_ebRIM_Profile_of_CSW_2.0.doc) • Defines a unique way to map the EO metadata type (EO GML) onto the ebRIM model. • Necessary for EO ebRIM Catalogue federations and interoperability.

  10. Specification Structure Catalogue 2.0.1 OGC 04-021 OASIS RIM ISO/TS 15000-3 GML 3.2 ISO 19136 CSW ebRIM AP OGC 05-025 OGC Filter Encoding OGC 04-095ISO 19143 Uses GML Appl. Schemafor EO Products OGC 06-080 RIM extension packagefor EO2 OGC 06-131 Refers to

  11. EO ebRIM Extension Package Additional Information Taxonomy Archivinginformation Platforminformation Productinformation Acquisition information Browseinformation Maskinformation

  12. Catalogue federation OGC EO CAT Proxy Impl. X CAT Legacy Catalog A Legacy native query Legacy native response GetRecords response OGC EO CAT Proxy Impl. Y CAT Legacy Catalog B OGC EO CAT GetRecords request Replicate response response GetRecords OGC EO CAT Standalone Impl. Z response EO GML Harvest  Possible Architectures

  13. EO CS-W Proxy Framework EO Proxy Framework EO ebRIM CS-W Legacy Catalogue user ebXML legacy connector EO GML • IONIC HMA-T objectives: • build an EO proxy framework to allow the implementation of EO CS-W ebRIM proxies in front of legacy catalogs • Productize EO Proxy framework developments (released as library set based on IONIC RedSpider Aug 07)

  14. EO CS-W Proxy Framework EO Proxy Framework request module CSW ebRIM operations -GetCapabilities -GetRecords -GetRecordById -GetRepositoryItem Encoder OGC Filter to legacy Filter legacy catalog legacy connector Users responsemodules Decoder legacy format to ebRIM • Web Service • Database • Proprietary API • Any Service Decoder legacy format to GML EO

  15. EO CS-W Proxy Framework EO Proxy Framework EO ebRIM CS-W Legacy Catalogue user ebXML legacy connector EO GML IONIC EO CS-W Proxy Framework: • proposes simple interfaces • hides ebRIM structure to concentrate on EOProduct structure • manages automatically ebRIM parsing/creation and EO GML creation /** add EOP level metadata */ m_EOProductOHR.setAcquisitionType("NOMINAL"); m_EOProductOHR.setStatus("ACQUIRED"); m_EOProductOHR.setImageQualityDegradation(0); m_EOProductOHR.setAcquisitionStation("TLS"); m_EOProductOHR.setOrbitNumber(12); …

  16. To implement a legacy connector, the developer should build three modules to handle following functionalities: • Manage Legacy catalog connection • Transform OGC filter into one or more valid legacy queries (request module) GetRecords , GetRecordById or GetRepositoryItem response request module legacy catalog legacy connector legacy request EO Framework decode OGC filter into java classes translate to legacy query(ies) manage connection

  17. Populate “EOProduct” Java objects with legacy responses.These “EOProduct” Java objects will then be automatically translated into a compliant ebXML response or EO GML response. (response module) Those modules will have to integrate the IONIC EO CS-W Proxy Framework by implementing well documented interfaces and extending abstract classes. GetRecords, GetRecordById or GetRepositoryItem response response module legacy catalog legacy connector legacy response EO Framework encode ebXML or EO GML response Populate EOProduct with response manage connection

  18. EO CS-W Proxy Framework • Currently OPT/SAR product level metadata are well defined in specifications, but other will come, so … • IONIC EO Proxy Framework is designed to allow extensions: • Ability to define a custom product-level classification (similar to PHR) • Ability to add custom product-level metadata in EOProducts /** create and initialize a Classification of type PHR, child of OHR Classification node */ EOClassification phrclassification = m_EOExtensionPackage.createClassification(PHR_CONCEPT_NAME, PHR_CONCEPT_KEY ,ClassificationId, m_EOProductOHR.getIdentifier(), EOClassification.CLASSIFICATION_TYPE_OHR); /** attach the classification to the EOProduct */ m_EOProductOHR.setEOClassification(phrclassification); /** add PHR level metadata */ m_EOProductOHR.addSlot("cloudCoverQuotationMode", "AUTOMATIC"); m_EOProductOHR.addSlot("imageQualityCodeQuotationMode", "AUTOMATIC"); m_EOProductOHR.addSlot("cloudCoverAssessmentConfidence", 12.34);

  19. Proxy Alternatives • Stylesheet translation • Examples prototyped up to now are • EOLI-XML (ESA-MUIS) • ECHO (NASA-EOSDIS)

  20. Supporting Tools • Currently stand-alone implementations also have been developed (or are in development) • IONIC RedSpider (COTS) • GALDOS IndiCio (COTS) • OpenSource TBC • Main Issue is conformance testing: HMA-T • Permit consolidation/evolution of HMA standards in parallel with implementation. • Permit conformance testing of HMA standards • Permanent testbed based on SOA architecture, located at ESRIN

  21. Conformance tests • Context • OGC migrates to open-source Test Engine (http://sourceforge.net/projects/teamengine) • Compliance Test Language (CTL), Draft 0.2, Northrop Grumman IT, TASC • OWS-4 reimplemented (some) existing conformance tests

  22. Conformance tests (cont'd) • CITE test scripts development for • CSW ebRIM Application Profile (Galdos, OWS-4): OGC 07-049 • ebRIM extension package for EO (Galdos) • Planned delivery soon • Deployment of CITE test environment at ESRIN

  23. Conformance tests

  24. EXAMPLES

  25. Spot Image - DALI

  26. Spot - GetRecordByID

  27. Eumetsat

  28. ESA - MUIS

  29. NASA ECHO

  30. Multi-catalogue search

  31. Use of UDDI for service configuration management, and for COTS tools oriented schema interrogation and service chaining CSW ISO profile found broadly applicable for collection and service metadata discovery providing association between collection and service providing geographic extent to services ESA supporting development of ebRIM extension pacakage for 19115/19119 OGC 07-038 Service Viewpoint: 07-038 Discovery

  32. Service Discovery • OASIS UDDI v2

  33. Collection DiscoveryPrototype

  34. Service Discovery • CSW ISO AP & OGC 07-025

  35. MUIS2WMS“Present” Service Discovery

  36. Reference analysis • Metadata standards • Elements to be included in the registry model • Based on the ISO AP queryables and returnables • 2 main options • Define a simple registry structure with all elements in a single extrinsic object • Valid option, but: • Management of the semantics not compliant with ebRIM CS-W AP • Extensions cannot be processed smoothly • Interest in defining/testing a more complex registry structure • Define a registry structure closer to the ISO structure • More complex queries

  37. Orientations • Based on the analysis of the reference documents, the team’s orientations were to: • Information Model • Repository contains the ISO 19139 instances; Registry contains a subset of ISO 19139 metadata elements. • Keep the registry structure close to the ISO standards • Support the OGC Core queryables and returnables • Support the ISO AP additional queryables and returnables at the summary level • Support INSPIRE Metadata elements (except Conformance) • Reuse and extend the extrinsic objects, associations and slots defined in the Basic Package • Apply the rules defined in the OWS-4 CSW ebRIM Modelling Guidelines IPR • Service • Provide capabilities equivalent to those of the ISO AP • Offer discovery-level search capabilities • Support and refine the service interface semantics defined in the ebRIM AP

  38. Implementations • First implementation during FedEO pilot (Ionic) • OpenSource implementation now being planned

  39. Standardisation Status • CSW 2.0.2 – approved standard • CSW ebRIM profile – v1.0 draft almost ready for internal e-vote (needs alignment to 2.0.2 following final update from public comment period on v0 draft) • CSW EO extension package and CIM (Core Iso Metadata) extension package ready for e-vote, both discussion paper status, but corresponding “standard working group” will be set up to deal with comments towards • Push to do final presentation to next OGC TC (Ispra, December)

  40. Various other catalogue initiatives

  41. GEOSS Registry & Clearinghouse

  42. Other ebRIM examples NASAESG

  43. A possible OGC/ISO view on catalogables • ISO 19110 for feature catalogues • ISO 19111 and ISO 19112 for coordinate systems • ISO 19114 for quality evaluation procedures • ISO 19117 for portrayal information • ISO 19126 for data dictionaries • ISO 19127 for geodetic codes and parameters • ISO 19131 for data product specifications • ISO 19135 for registers • ISO 19138 for data quality measures • … + SENSORS, MODELS, COMPONENTS?? … With differences between catalogue and registry: governance and versioning

  44. DISCUSSION

More Related