1. WGISS 24 October 2007 Slide 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. WGISS 24 October 2007 Slide 2 Enterprise View: Context within GMES

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

4. WGISS 24 October 2007 Slide 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 sar.xsdopt.xsdatm.xsd eop.xsd smXML - gmd (ISO 19139) Catalogue metadata for mission type Catalogue metadata for EO products gml Schema/ namespace for radar missions Schema/ namespaces for optical missions Schema/ namespaces for atmospheric missions Generic and geometric catalogue metadata phr.xsd xyz.xsd Catalogue metadata for specific mission

5. WGISS 24 October 2007 Slide 5 GML observation PropertyDescription within Earth Observation context Content metadaPropertyDescribe general properties such as the data identifier, the downlink and archiving information eop:EarthObservatio nMetadata validTimeDescribe the acquisition duration, i.e. the start and end date of acquisition gml:TimePeriod/gml: beginPosition gml:TimePeriod /gml:endPositio n usingDescribe the Platform/Instrument/Senso r used for the acquisition and the acquisition parameters (i.e. pointing angles, etc.) eop:EarthObservatio nEquipment targetDescribe the observed area on ground i.e. the footprint of acquisition eop:Footprint resultOfDescribe the Earth Observation result composed of the browse, mask and product description eop:EarthObservatio nResult

6. WGISS 24 October 2007 Slide 6 Information Viewpoint 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

7. WGISS 24 October 2007 Slide 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. WGISS 24 October 2007 Slide 8 ISO 19119 Interface Standards Overview 19139 GML Appl Schema OGC CAT ISO extension package (CIM) OrderProgramming OGC SPS ISO 19115 part2 ISO 19115 Discovery Catalogue ebRIM profile EO extension package (ebRIM) OGC WMS OGC WCS

9. WGISS 24 October 2007 Slide 9 Service Viewpoint: 06-131 Catalogue ebRIM Application Profile ebRIM Model CSW (Catalogue Service/Web) HTTP Protocol OGC Catalogue Services 2.0 Catalogue Interface (Abstract) EO Products Extension Package Mapping Discussion paper at the OGC: (06- 131r1_EO_Products_Extension_Package_for_eb RIM_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. WGISS 24 October 2007 Slide 10 GML Appl. Schema for EO Products OGC 06-080 OGC Filter Encoding OGC 04-095 ISO 19143 RIM extension package for EO 2 OGC 06-131 Refers to Catalogue 2.0.1 OGC 04-021 CSW ebRIM AP OGC 05-025 GML 3.2 ISO 19136 OASIS RIM ISO/TS 15000-3 Uses Specification Structure

11. WGISS 24 October 2007 Slide 11 Platform information Taxonomy Acquisition information Additional Information Archiving information Product information EO ebRIM Extension Package Browse information Mask information

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

13. WGISS 24 October 2007 Slide 13 EO Proxy Framework Legacy Catalogue 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) legacy connector EO CS-W Proxy Framework EO ebRIM CS-W EO GML user ebXML

14. WGISS 24 October 2007 Slide 14 Users EO CS-W Proxy Framework EO Proxy Framework request module response modules Decoder legacy format to GML EO Encoder OGC Filter to legacy Filter Decoder legacy format to ebRIM legacy catalog CSW ebRIM operations -GetCapabilities -GetRecords -GetRecordById -GetRepositoryItem legacy connector Web Service Database Proprietary API Any Service

15. WGISS 24 October 2007 Slide 15 EO Proxy Framework Legacy Catalogue 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 legacy connector EO CS-W Proxy Framework EO ebRIM CS-W EO GML user ebXML /** 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. WGISS 24 October 2007 Slide 16 To implement a legacy connector, the developer should build three modules to handle following functionalities: 1.Manage Legacy catalog connection 2.Transform OGC filter into one or more valid legacy queries (request module) request module EO Framework decode OGC filter into java classes translate to legacy query(ies) legacy request GetRecords, GetRecordById or GetRepositoryItem response legacy connector manage connection legacy catalog

17. WGISS 24 October 2007 Slide 17 3.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. response module EO Framework encode ebXML or EO GML response legacy catalog legacy connector manage connection Populate EOProduct with response GetRecords, GetRecordById or GetRepositoryItem response legacy response

18. WGISS 24 October 2007 Slide 18 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 EO CS-W Proxy Framework /** 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. WGISS 24 October 2007 Slide 19 Proxy Alternatives Stylesheet translation Examples prototyped up to now are EOLI-XML (ESA-MUIS) ECHO (NASA-EOSDIS)

20. WGISS 24 October 2007 Slide 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. WGISS 24 October 2007 Slide 21 Conformance tests Context OGC migrates to open-source Test Engine (http://sourceforge.net/projects/t eamengine)http://sourceforge.net/projects/t eamengine Compliance Test Language (CTL), Draft 0.2, Northrop Grumman IT, TASC OWS-4 reimplemented (some) existing conformance tests

22. WGISS 24 October 2007 Slide 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. WGISS 24 October 2007 Slide 23 Conformance tests

24. WGISS 24 October 2007 Slide 24 EXAMPLES

25. WGISS 24 October 2007 Slide 25 Spot Image - DALI

26. WGISS 24 October 2007 Slide 26 Spot - GetRecordByID

27. WGISS 24 October 2007 Slide 27 Eumetsat

28. WGISS 24 October 2007 Slide 28 ESA - MUIS

29. WGISS 24 October 2007 Slide 29 NASA ECHO

30. WGISS 24 October 2007 Slide 30 Multi-catalogue search

31. WGISS 24 October 2007 Slide 31 Service Viewpoint: 07-038 Discovery 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

32. WGISS 24 October 2007 Slide 32 Service Discovery OASIS UDDI v2

33. WGISS 24 October 2007 Slide 33 Collection Discovery Prototype

34. WGISS 24 October 2007 Slide 34 Service Discovery CSW ISO AP & OGC 07-025

35. WGISS 24 October 2007 Slide 35 Service Discovery MUIS2WMS Present

36. WGISS 24 October 2007 Slide 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. WGISS 24 October 2007 Slide 37 Orientations Based on the analysis of the reference documents, the teams 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. WGISS 24 October 2007 Slide 38 Implementations First implementation during FedEO pilot (Ionic) OpenSource implementation now being planned

39. WGISS 24 October 2007 Slide 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. WGISS 24 October 2007 Slide 40 Various other catalogue initiatives

41. WGISS 24 October 2007 Slide 41 GEOSS Registry & Clearinghouse

42. WGISS 24 October 2007 Slide 42 Other ebRIM examples NASA ESG

43. WGISS 24 October 2007 Slide 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. WGISS 24 October 2007 Slide 44 DISCUSSION