ESA HMA Catalogue Services for Earth Observation Collection Metadata PV 2013 4.-6. November 2013 ESA-ESRIN Frascati

Uwe Voges con terra GmbH

EO Collection Metadata  Data Collection: series, i.e. a set of dataset sharing the same product specification •

May also cover aggregate collections

 Example EO Collections: •

Series of EO Images of the same satellite (e.g. MSG) and the same sensor (e.g. SEVIRI) at different times (see Figure).

•

GMES datasets: a collection of instances e.g. packaging EO products from Radarsat (collection) and TerraSAR-X (collection) covering a specific area

4.-6. November 2013

PV 2013

2

OGC Catalogue Services – ebRIM Profile  OGC Catalogue Services (CS) ebRIM application profile (AP): •

based on OGC CS framework for implementing GEO catalogues

•

based on the OASIS ebXML Registry Information Model (ebRIM) v3.0

 ebRIM is foundatiion of OASIS ebXML Registries •

information systems managing instances of any electronic content: e.g. XML documents − called RepositoryItems - stored in the Repository

•

standardized metadata that describe the RepositoryItems − called RegistryObjects - stored in the Registry − foundation for search and discovery

•

OASIS ebXML Registry

Registry RegistryObjects: ebXML ebRIM 3.0

ebXML Registry approach is often illustrated with the familiar metaphor of a Local Library: − Repository items are like the Books in the Library − the Registry is like the Card Catalog: − organized to find things quickly − conform to a standard (based on ebRIM)

4.-6. November 2013

PV 2013

UUID

Repository RepositoryItems: e.g. Images, XML Files

3

OGC Catalogue Services – ebRIM Profile

 ebRIM standard provides a set of core RegistryObjects with defined semantic: •

ExtrinsicObjects, the primary metadata class (for a RepositoryItem)

•

Slots, provide a dynamic way to add arbitrary attributes to RegistryObjects

•

Associations, to associate a RegistryObject to other RegistryObjects

•

Classifications, for classifying RegistryObjects. 4.-6. November 2013

PV 2013

4

OGC CS ebRIM Profile – Extension Packages  Extension Packages (EP) meet needs of some application domain •

Set of registry objects that extend the core model

•

Extensibility points include: − new types of ExtrinsicObjects or Associations − additional Classification Schemes /Classification Nodes and Slots

 CS ebRIM AP already includes the Basic (Extension) Package • •

I includes RegistryObjects of general utility in the geomatics domain shall be considered by all OGC EP

CSW-ebRIM Discovery HTTP/XML/SOAP)

can be deployed into existing ebRIM Catalogue

•

allow storage / discovery of defined RegistryObjects

 CS ebRIM profile does not use service interfaces of ebXML CSW-ebRIM Registries

4.-6. November 2013

PV 2013

Registry

ebRIM 3.0 & Basic Package

•

Instead: HTTP protocol binding of the OGC CS

I15 Registry

RegistryObjects:

 EP´s are encoded in XML (called RegistryPackage):

•

OGC CSW AP ebRIM Catalogue

Discovery HTTP/XML/SOAP)

UUID

Repository RepositoryItems: XML Files

I15 Extension Package (EP)  I15 (former: CIM): is Extension Package (EP) for search

OGC CSW AP ebRIM EP I15 Catalogue

/ management of ISO 19115(-2)/19119/19139(-2)

I15 Registry

Dataset-, Collection-, Application- and Service-Metadata

CSW-ebRIM Discovery HTTP/XML/SOAP)

 includes as many ebRIM Objects as required for most

Registry RegistryObjects: ebRIM 3.0 & Basic Package & I15 EP

important discovery use-cases  CIM EP was started in ESA HMA-T (2007-2009), now

UUID

finalized as I15 EP in ESA HMA-S (2013)  accompanied by XML RegistryPackage: can be

Repository

deployed into existing ebRIM Catalogue

RepositoryItems: CSW-ebRIM Discovery HTTP/XML/SOAP)

4.-6. November 2013

PV 2013

ISO19139(-2) XML Files

6

I15 EP – Classifications and Slots (snippet)

4.-6. November 2013

PV 2013

7

I15 EP – Data Dictionary (snippet)  Data Dictionary describes the ExtrinsicObjects (their Slots, Attributes, Classifications and Associations in detail)

4.-6. November 2013

PV 2013

8

I15 EP – relevant parts for DataCollections  Metadata describing data represented by EOs ElementaryDataset or DatasetCollection •

both derived from the abstract ExtrinsicObject DataMetadata

 DataMetadata: having an association to Dataset EO from BP (for BP alignment) class 00 - Ov erv iew

«ExtrinsicObject» I15::SecurityConstraints «classification» + ClassificationCode: ClassificationCode

+

CitedResponsibleParty

«ExtrinsicObject» I15::CitedItem

«ExtrinsicObject» Basic Extension Package::Rights + +

Description [0..1]: InternationalString

Name: InternationalString ExternalIdentifier [0..*]: ExternalIdentifier

«Slot» + Title [0..1]: InternationalString + Created [0..1]: DateTime + Modified [0..*]: DateTime + Issued [0..*]: DateTime + Source [0..*]: URI

0..*

«ClassificationScheme» I15::ThesaurusKeyw ordScheme

Thesaurus 1

+ +

«ExtrinsicObject» I15::LegalConstraints

«ClassificationNode» I15::ThesaurusKeyw ord

«classification» + RestrictionType::access [0..*]: RestrictionCode + RestrictionType::use [0..*]: RestrictionCode

«ExtrinsicObject» I15::ResourceMetadata

ResourceConstraints

«Slot» - Rights [0..*]: InternationalString

+

«ExtrinsicObject» Basic Extension Package:: Image -

«ClassificationScheme» I15::Keyw ordSchemeUntyped

Name: InternationalString Description: InternationalString

Name: InternationalString

GraphicOverview 0..*

classifiedBy 0..*

Description: InternationalString

«Slot» + Format [0..*]: FormatNameAndVersion + Type [0..*]: InternationalString + Envelope [0..*]: gml:EnvelopeType + Language [0..1]: LanguageTag + Coverage [0..*]: IdentifiedItem + Lineage [0..*]: InternationalString + TemporalBegin [0..*]: DateTime + TemporalEnd [0..*]: DateTime «classification» + TopicCategoryCode [0..*]: TopicCategory + CharacterSet [0..*]: CharacterSet

«ClassificationNode» I15::Keyw ordUntyped

classifiedBy 0..* «ExtrinsicObject» I15::ReferenceSpecification Specification

0..*

0..* «Slot» + Conformance: boolean + Explanation: InternationalString

«RegistryObject» ebRIM::Organization + + +

«ExtrinsicObject» I15::DataMetadata «ExtrinsicObject» Basic Extension Package:: Dataset

DatasetDescription 1

0..*

4.-6. November 2013

MetadataPointOfContact +parentMetadata 0..1 ResourceMetadataInformation 1

Subset

«ExtrinsicObject» I15::ElementaryDataset

0..* ParentMetadataInformation

«classification» + SpatialRepresentationType [0..*]: SpatialRepresentationType «Slot» + Resolution [0..*]: gml:MeasureType + ScaleDenominator [0..*]: Integer + SupplementalInformation [0..1]: InternationalString

«ExtrinsicObject» I15::DatasetCollection

PV 2013

Name [0..1]: InternationalString EmailAddress [0..*]: EmailAddress PrimaryContact [0..1]: Person

«ExtrinsicObject» I15::MetadataInformation «Slot» + Date [0..1]: DateTime + Identifier [0..1]: String + ConformsTo[0..1]: MetadataStandardNameAndVersion + Language [0..1]: LanguageTag «classification» + CharacterSet[0..1]: CharacterSet

9

I15 EP – DataQuality and Acquisition Packages class 12 - Detailed Data Quality Information

 Specific packages: •

•

ResourceMetadata «ExtrinsicObject» I15::DataMetadata

Data quality: package to represent the ISO DQ_DataQuality elements

DataQualityInfo

0..* «ExtrinsicObject» I15::DataQuality «Slot» + ScopeLevel: String + ScopeDescription [0..*]: InternationalString + Envelope [0..*]: gml:EnvelopeType + TemporalBegin [0..*]: DateTime + TemporalEnd [0..*]: DateTime

Acquisition (from ISO19115-2) can be described by the EOB´s AquisitionInformation, Platform, Instrument, their slots and associations.

0..1 +

Description: InternationalString

LineageSource

LineageProcessStep

0..* «ExtrinsicObject» I15::Source +

CodeSpace class 14 - Acquisition Information

«ExtrinsicObject» I15::Lineage

DataQualityLineage

Description: InternationalString

«Slot» + ScaleDenominator [0..1]: int + Envelope [0..*]: gml:EnvelopeType + TemporalBegin [0..*]: DateTime SourceReferenceSystem + TemporalEnd [0..*]: DateTime

«ExtrinsicObject» I15::ProcessStep

0..* StepSource

+

0..*

Description: InternationalString

«Slot» + Rationale [0..1]: InternationalString + Date [0..1]: DateTime

0..1 «ExtrinsicObject» I15::IdentifiedItem

ResourceMetadata «ExtrinsicObject» I15::DataMetadata

~

0..1

Processor

SourceCitation

Name: InternationalString 0..1 Authority

«ExtrinsicObject» I15::Instrument + +

AcquiredBy

Description: InternationalString Name: InternationalString

1 + +

«Slot» + Identifier: String

0..*

«ExtrinsicObject» I15::AcquisitionInformation

0..*

«ExtrinsicObject» I15::CitedItem

MountedOn

Name: InternationalString ExternalIdentifier [0..*]: ExternalIdentifier

«Slot» + Title [0..1]: InternationalString + Created [0..1]: DateTime + Modified [0..*]: DateTime + Issued [0..*]: DateTime + Source [0..*]: URI

InstrumentCitation

0..* AcquisitionInstrument

0..*

«ExtrinsicObject» I15::CitedItem

«RegistryObject» ebRIM::Organization

CitedResponsibleParty 0..*

+ + +

Name [0..1]: InternationalString EmailAddress [0..*]: EmailAddress PrimaryContact [0..1]: Person

«RegistryObject» ebRIM::Person + +

PersonName: InternationalString EmailAddress [0..1]: EmailAddress

PlatformCitation 0..*

AcquisitionPlatform 0..*

0..1 «ExtrinsicObject» I15::Platform

+

Description: InternationalString

«Slot» + Identifier: String Sponsor «RegistryObject» ebRIM::Organization

0..* + + +

Name [0..1]: InternationalString EmailAddress [0..*]: EmailAddress PrimaryContact [0..1]: Person

4.-6. November 2013

PV 2013

10

I15 EP - Context  The associations between the main Resource ExtrinsicObjects represent the context − Sophisticated queries are possible based on those associations

•

OperatesOn between ServiceMetadata and DataMetadata

•

IsClientOf between Application and ServiceMetadata

•

Subset between DatasetCollection and the abstract DataMetadata EOB

•

Accesses between Application and DataMetadata class 01 - Context & Resource

«ExtrinsicObject» I15::ResourceMetadata

«ExtrinsicObject» I15::DataMetadata

Subset

OperatesOn

0..*

«ExtrinsicObject» I15::Serv iceMetadata

0..* 0..*

0..*

IsClientOf

Accesses

«ExtrinsicObject» I15::Application

«ExtrinsicObject» I15::DatasetCollection

4.-6. November 2013

«ExtrinsicObject» I15::ElementaryDataset

PV 2013

11

Registration of ISO19139(-2) metadata files  I15 defines the registration of ISO documents as mappings from ISO19139(-2) XPaths to I15: •

How to deduce the main EO (ElementaryDataset, DatasetCollection, Service, Application)

•

How to derive: − the elements for the MetadataInformation EO − the associated RegistryObjects (e.g. Constraints), classifications and slot values − the associations between the main EOs

•

XSLT will be made available in HMA 4.-6. November 2013

PV 2013

12

Registration of ISO19139(-2) metadata files  I15 specification includes examples of ISO19139 documents and their mappings to I15

 Snippet from an example mapping

4.-6. November 2013

PV 2013

13

Sample Request

 I15 Catalogues understand OGC GetRecords filter expressions which use the I15 RegistryObjects.  Sample: •

filters for EO Collections where the data is available in a specified region and acquired by a SEVIRI instrument which is mounted on a Meteosat-9 or -10 satellite.

4.-6. November 2013

PV 2013

14

I15 Conformance Classes  I15 candidate standard defines two level of conformance: •

Core: support of the Core I15 EP RegistryObjects (in Requests and Responses

•

Extension: support of Core + Extension I15 EP RegistryObjects (mainly Quality and Acquisition Information )

•

Inspire (INSPIRE Conformance Class - ICC) : − In Europe: important to retain interoperability with INSPIRE Discovery Service (IDS) − assures semantic interoperability between I15 and IDS − defined in HMA (separate document: OGC 08-197r3) − restricts the use of optional ExtrinsicObjects, Associations, Slots and query capabilities by making some mandatory − includes mappings between IDS and I15 queryables and returnables − Based on ICC - bridges were developed that map between I15/ICC- and IDS − allow integration of HMA I15 collection catalogues into INSPIRE SDI − Vice versa: integration of IDS-Catalogues into ESA HMA SDI

4.-6. November 2013

PV 2013

15

OpenSearch Extension for Earth Observation  OGC OpenSearch Extension for EarthObservation (OGC 13-026) •

simple HTTP/KVP/GET EO (collection) metadata interface

•

developed in HMA-S: extension to OpenSearch Geo/Temporal (OGC 10-032)

CSW-ebRIM Discovery HTTP/XML/SOAP)

•

In a flexible Architecture it should sit on top of I15(/ICC) Cat

•

Disadvantages (in comparison to I15):

OGC CSW AP ebRIM EP I15Catalogue I15 Registry

Registry RegistryObjects: ebRIM 3.0 & Basic Package & I15 EP based

− very limited set ISO elements supported − not suitable for complex (deep) searches with arbitrary structures (filter), where associations between OS EOP HTTP/KVP information objects (joins) involved, e.g. − Search for GMES dataset aggregating Radarsat (collection) and TerraSAR-X (collection) data CSW-ebRIM − Data-/Service-Coupling Scenarios: Discovery HTTP/XML/SOAP) “search for WMS 1.3 services operating on datasets acquired with SEVIRI instrument •

Very limited control on the search process

•

Can´t request specific information: e.g. instrument information

•

not aligned with IDS.

•

no interface for metadata management 4.-6. November 2013

PV 2013

UUID

Repository RepositoryItems: ISO19139(-2) XML Files

16

Status of I15 Spec and Implementations •

•

•

Specification generally finished: •

OGC I15 SWG voted “YES” on the spec to provide to public comment

•

OGC Public Comment Period started one week ago

Last steps: •

Solve comments coming from public comment period

•

OGC TC voting

•

Finalization of Test Environment: ETS

Implementations: •

Dif. Catalogue Server Products (e.g. Buddata, Geonetwork?), Ground Segments (e.g. EUMETSAT via Bridge) and Clients (e.g. ESA/Spacebel) are implementing the I15/CIM.

4.-6. November 2013

PV 2013

17

4.-6. November 2013

PV 2013

18