DOCSLIB-#385690-v1 ... - FTP Directory Listing - Eumetsat

stizzahaddockΛογισμικό & κατασκευή λογ/κού

14 Δεκ 2013 (πριν από 3 χρόνια και 5 μήνες)

606 εμφανίσεις




© EUMETSAT

The copyright of this document is the property of EUMETSAT.





































Doc.No.

:

EUM/OPS/ICD/11/1856

Issue

:

v1

Date

:

8 June 2011

WBS

:



HMA EOP Cata
logue Tailoring ICD
for EUMETSAT




EUMETSAT

Eumetsat
-
Allee 1
, D
-
64295 Darmstadt, Germany

Tel: +49 6151 807
-
7

Fax: +49 6151 807 555

http://www.eumetsat.int


EUM/OPS/ICD/11/1856

v1, 8 June 2011

HMA EOP Catalogue Tailoring

ICD for EUMETSAT




Page
2

of
70


Document Signature Table


Name

Function

Signature

Date

Prepared by:

Michael Schick

Data Access Services
Team Leader



Reviewed by:

Uwe Voges

P
roject Manager / Senior
Geospatial Systems
Consultant at Conterra
GmbH



Reviewed by:

n/a




Approved by:

Graziano Mori

SAG System Authority




Distribution List

Distribution list

Name

No. of Copies

As in Document Signature Table

Electronic Access

ES
A recipients via Author

Signed PDF


Document Change Record

Issue /
Revision

Date

DCN.
No

Summary of Changes

V1

7 June


First formal release






EUM/OPS/ICD/11/1856

v1, 8 June 2011

HMA EOP Catalogue Tailoring

ICD for EUMETSAT




Page
3

of
70


Table of Contents

1

Introduction

................................
................................
................................
................................
..

5

1.1

Purpo
se and Scope

................................
................................
................................
.............

5

1.2

Acronyms and definition

................................
................................
................................
......

5

1.3

List of reference Document

................................
................................
................................
.

6

1.4

List of applicable Document

................................
................................
................................

6

1.5

Document overview

................................
................................
................................
.............

6

2

EUMETSAT HMA EOP Catalogue

................................
................................
...............................

7

2.1

Short overview of OGC O6
-
131r6

................................
................................
.......................

7

2.1.1

Earth Observation schema

................................
................................
.....................

7

2.1.2

CSW ebRIM

................................
................................
................................
............

8

2.2

EUMETSAT HMA EOP Catalogue characteristics

................................
............................

11

2.3

General description of the service

................................
................................
.....................

11

2.3.1

Applicative protocols

................................
................................
.............................

11

2.3.2

Supported ebRim
-
CSW oper
ations

................................
................................
......

12

3

The GetCapabilities Operation

................................
................................
................................
.

13

3.1

GetCapabilities request

................................
................................
................................
.....

13

3.2

GetCapabilities response

................................
................................
................................
..

13

4

The GetRecords operation

................................
................................
................................
........

16

4.1

Brief overview

................................
................................
................................
....................

16

4.2

GetRecords request

................................
................................
................................
..........

16

4.2.1

CSW Request parameters

................................
................................
....................

16

4.2.2

Request filters

................................
................................
................................
.......

18

4.3

GetRecordsResponse

................................
................................
................................
.......

31

4.3.1

CSW Response parameters

................................
................................
.................

31

4.3.2

SearchResult parameters

................................
................................
.....................

31

4.3.3

EUMETSAT HMA EOP Catalogue request’s size limitations

...............................

32

4.3.4

SearchResult content

................................
................................
...........................

32

5

The GetRecordById operation

................................
................................
................................
..

39

5.1

Brief overview

................................
................................
................................
....................

39

5.2

GetRecordById request

................................
................................
................................
.....

39

5.
3

GetRecordByIdResponse

................................
................................
................................
..

40

6

The GetRepositoryItem operation

................................
................................
............................

40

6.1

Brief overview

................................
................................
................................
....................

40

6.2

GetRepositoryItem request

................................
................................
................................

40

6.3

GetRepository
ItemResponse

................................
................................
............................

41

Appendix A

Example Requests/Responses

................................
................................
.........

42

EUM/OPS/ICD/11/1856

v1, 8 June 2011

HMA EOP Catalogue Tailoring

ICD for EUMETSAT




Page
4

of
70



Dublin Core Metadata
1



Title

HMA EOP Catalogue Tailoring ICD for EUMETSAT.

Creator

Dr. Uwe Voges (con terra GmbH)

Issued

14/09/2010

Modified

31
/
05
/201
1

Status

F
inal (Version
1.2
)

Subject

HMA EOP Catalogue Tailoring ICD EUMETSAT “Catalogue
Service Specification 2.0 Extension Package for ebRIM EO Products“
OGC 06
-
131

Publisher

EUMETSAT

Type

Text

Abstract

This document is the HMA E
OP Catalogue Tailoring ICD for
EUMETSAT. It is the tailoring for the “Catalogue Service
Specification 2.0 Extension Package for ebRIM EO Products“ OGC
06
-
131

Contributors

Michael Schick (EUMETSAT), Udo Einspanier, Uwe Voges (con
terra)

Format

MS Word 200
3 (doc)

Source

EUMETSAT EOPortal Document Store

Rights

EUMETSAT

Language

EN

Coverage

Project duration Feb 2009


Dec 2011
)





1

http://www.dublincore.org

EUM/OPS/ICD/11/1856

v1, 8 June 2011

HMA EOP Catalogue Tailoring

ICD for EUMETSAT




Page
5

of
70


1

INTRODUCTION

1.1

Purpose and Scope

This document details the EUMETSAT HMA EOP Catalogue implementation, implementing
the OGC/HMA “
Catalogue Service Specification 2.0 Extension Package for ebRIM EO
Products“ OGC 06
-
131 [1]. It discusses how the EUMETSAT HMA EOP Catalogue
implementation has been performed using OCG 06
-
131:



HMA Service implementation. It describes exceptions, constraint
s and partially
compliances concerning protocol, xml attribute/message contents;



Annex G level of compliance. It describes for the group of EUMETSAT collections
the level of compliance (1,2 or 3) and the limitations concerning: exposed fields,
queryable fi
elds, allowed operators;

In addition an adequate number of examples are provided within this document.

For access via ESA/EO
-
DAIL towards the GMES service projects it gives a concise picture
of the capabilities of the GCM (
GMES Contributing Mission
).

1.2

Acron
yms and definition

AP

Application Profile

API

Application Programming Interface

ATS

Abstract Test Suite

CITE

OGC Compliance & Interoperability Testing & Evaluation

CSW




Catalogue Services for the Web

EO

Earth Observation

EO
-
DAIL

Earth Observation

Data Access Integration Layer

EOP

EO Products Extension Package for ebRIM Profile of CSW, OGC
doc 06
-
131

EPSG

European Petrol Survey Group

ESA

European Space Agency

ESRIN

European Space Research Institute

EU

European Union

GCM

GMES Contributing Mission

GIS

Geographic Information System

GMES

Global Monitoring for Environment and Security

GUI

Graphical User Interface

HMA

Heterogeneous Mission Accessibility

HMA
-
T

Heterogeneous Mission Accessibility Testbed

HTML

Hyper Text Markup Language

HTTP

Hyper Text
Transfer Protocol

ICD

Interface Control Document

ISO

International Standardization Organization

IT

Information Technology

JDK

Java Development Kit

JVM

Java Virtual Machine

OASIS

Advancing Open Standards for the Information Society

OGC




Open Geospatia
l Consortium

OGC

Open Geospatial Consortium

OWS

OGC Web Service

EUM/OPS/ICD/11/1856

v1, 8 June 2011

HMA EOP Catalogue Tailoring

ICD for EUMETSAT




Page
6

of
70


PDF

Portable Document Format

SOA

Service Oriented Architecture

SOAP

Simple Object Access Protocol

SSE

Service Support Environment

TCP/IP

Transmission Control Protocol / Internet Protocol

UML

Unified Modelling Language

WAN

Wide Area Network

XML

eXtensible Markup Langua
ge

XSL




eXtensible Stylesheet Language


1.3

List of reference Document

[1]


EO Products Extension Package for ebRIM Profile of CSW, Version 2.0.2, OGC doc
06
-
131r6, V0.2.4

[2]


GML 3.1.1 Application Schema for Earth Observation O Products, OGC doc 06
-
080r,
V.0.9.3

[3]


OGC OWS Common Implementation Specification 1.0 [OGC 05
-
008c1]

[
4
]


OGC Web Registry Service (WRS)
-

Part 1: ebRIM profile of CSW, OGC doc 07
-
110

[
5
]


OGC Web
Registry Service


Part 2: Basic extension package, OGC doc 07
-
144

[
6
]


OGC Catalogue Services Specification, Version 2.0.2, OGC doc 07
-
006

1.4

List of applicable Document

[1]


EO Portal


High Level Architectural Design, v3B, EUMETSAT doc
EUM/OPS/TEN/08/067
6.

[2]


EO Portal and Clearing House
-

Technology Analysis (Trade
-
Off), v1B, EUMETSAT
doc EUM/OPS/TEN/08/0675.

[
3
]: Object Management Group (OMG): Unified Modelling Language Specification (version
2.0), "Infrastructure", ptc/05
-
07
-
05, and "Superstructure"
, ptc/05
-
07
-
06

1.5

Document overview

In chapter 2 a short overview of the EO Products Extension Package for ebRIM Profile of
CSW [1] is given. Then, general information is provided (supported protocols and operations)
on the EUMETSAT implementation (EUMETSAT H
MA EOP Catalogue).

Chapter 3
-
6 provide the details how the EUMETSAT HMA EOP Catalogue supports the
following EOP operations:

-

GetCapabilities

-

GetRecords

-

GetRecordById

-

GetRepositoryItem

The Annex describes examples of operation requests and responses.

EUM/OPS/ICD/11/1856

v1, 8 June 2011

HMA EOP Catalogue Tailoring

ICD for EUMETSAT




Page
7

of
70


2

EUMET
SAT HMA EOP CATALOGU
E

2.1

Short overview of OGC O6
-
131r6

In the following a short synthesis of the
OGC
/HMA

Catalogue Services Specification 2.0

Extension Package for ebRIM Application Profile:

Earth Observation Products (short:
HMA
EOP

Catalogue)
General Speci
fication is given.

2.1.1

Earth Observation schema

The central document of the HMA EOP CATALOGUE specification is OGC 06
-
131 [1].
This document describes how earth observation products and their metadata are implemented.
This implementation is based on the follow
ing object/association schema:



Figure 1: Earth Observation schema
2





2

See [1] for the actual and complete schema

EUM/OPS/ICD/11/1856

v1, 8 June 2011

HMA EOP Catalogue Tailoring

ICD for EUMETSAT




Page
8

of
70


EOProducts are also classified in optical (OPT), radar (SAR) or atmospheric (ATM)
products. This classification permits to add specific information shared between products of
the same t
ype.


An EOProduct with all its attributes, associations and associated Extrinsic Objects is packed
in an entity called RegistryPackage. So each record returned in a result will correspond to a
RegistryPackage containing an EOProduct and all its metadata.


The complete Earth Observation schema can be found in OGC 06
-
080 [2]. Nevertheless, in
HMA scope,
the list of metadata that is exposed by the EUMETSAT
HMA
EOP
C
atalogue
can be found in paragraph 4.3.4.3.


2.1.2

CSW ebRIM

The XML representation of this schema is

made using ebRIM. The complete representation
of EOProducts in ebRIM can be found in OGC O6
-
131 [1].
All representative acquisition
parameters are available (as
fields or
slots) for
the
extended search
.

The list of slots for each
type of object is defined

as follows:
3



<!
--

Meta
-
registryObjcts to list allowed slots by objectType
--
>


<
rim
:
RegistryObject

objectType
="
urn:x
-
ogc:specification:csw
-
ebrim:ObjectType:EO:EOProduct
">


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:acquisitionType
"
sl
otType
="
string
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:acquisitionStation
"
slotType
="
string
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:acquisitionSubType
"
slotType
="
string
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:O
GC
-
06
-
131:acrossTrackPointingAngle
"
slotType
="
double
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:alongTrackPointingAngle
"
slotType
="
double
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:antennaLookDirection
"
slotType
="
string
"/>



<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:beginPosition
"
slotType
="
dateTime
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:centerOf
"
slotType
="
geometry
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:cloudCoverPercentage
"
slotType
="
double
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:doi
"
slotType
="
string
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:dopplerFrequency
"
slotType
="
double
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:end
Position
"
slotType
="
dateTime
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:extentOf
"
slotType
="
geometry
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:illuminationAzimuthAngle
"
slotType
="
double
"/>


<
rim
:
Slot

name
="
urn:ogc:def:
ebRIM
-
Slot:OGC
-
06
-
131:illuminationElevationAngle
"
slotType
="
double
"/>




<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:imageQualityDegradation
"
slotType
="
double
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:imageQualityDegradationQuot
ationMode
"
slotType
="
string
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:lastOrbitNumber
"
slotType
="
int
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:maximumIncidenceAngle
"
slotType
="
double
"/>


<
rim
:
Slot

name
="
urn:ogc:def:eb
RIM
-
Slot:OGC
-
06
-
131:minimumIncidenceAngle
"
slotType
="
double
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:orbitDirection
"
slotType
="
string
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:orbitNumber
"
slotType
="
int
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:parentIdentifier
"
slotType
="
string
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:pitch
"
slotType
="
int
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:polarisationChannels
"
slotType
="
string
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:polarisationMode
"
slotType
="
string
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:productType
"
slotType
="
string
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:roll
"
slotType
="
int
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:snowCoverPercentage
"
slotType
="
double
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:status
"
slotType
="
string
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:vendorSpecif
icAttributes
"
slotType
="
string
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:vendorSpecificValues
"
slotType
="
string
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:yaw
"
slotType
="
int
"/>


</
rim
:
RegistryObject
>






<
rim
:
Reg
istryObject

objectType
="
urn:x
-
ogc:specification:csw
-
ebrim:ObjectType:EO:EOAcquisitionPlatform
">


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:instrumentShortName
"
slotType
="
string
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:platfor
mOrbitType
"
slotType
="
string
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:platformSerialIdentifier
"
slotType
="
string
"/>




3

See [1] for the actual and complete
list of slots

EUM/OPS/ICD/11/1856

v1, 8 June 2011

HMA EOP Catalogue Tailoring

ICD for EUMETSAT




Page
9

of
70



<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:sensorOperationalMode
"
slotType
="
string
"/>


<
rim
:
Slot

name
="
u
rn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:sensorResolution
"
slotType
="
double
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:
sensorType
"
slotType
="
string
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:swathIdentifier
"
slotType
="
string
"/>


</
rim
:
RegistryObject
>




<
rim
:
RegistryObject

objectType
="
urn:x
-
ogc:specification:csw
-
ebrim:ObjectType:EO:EOProductInformation
">


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:fileName
"
slotType
="
anyURI
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:referenceSystemIdentifier
"
slotType
="
string
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:size
"
slotType
="
int
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:version
"
slotType
="
string
"/>


</
rim
:
RegistryObject
>




<
rim
:
RegistryObject

objectType
="
urn:x
-
ogc:specification:csw
-
ebrim:ObjectType:EO:EOBrowseInformation
">


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:fileName
"
slotType
="
anyURI
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:referenc
eSystemIdentifier
"
slotType
="
string
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:subType
"
slotType
="
string
"/>


</
rim
:
RegistryObjet
>



<
rim
:
RegistryObject

objectType
="
urn:x
-
ogc:specification:csw
-
ebrim:ObjectType:EO:EOMaskInformation
">



<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:fileName
"
slotType
="
anyURI
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:referenceSystemIdentifier
"
slotType
="string"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:format
"
slotT
ype
="
string
"/>


</
rim
:
RegistryObject
>




<
rim
:
RegistryObject

objectType
="
urn:x
-
ogc:specification:csw
-
ebrim:ObjectType:EO:EOArchivingInformation
">


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:archivingDate
"
slotType
="
dateTime
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:archivingIdentifier
"
slotType
="
string
"/>


</
rim
:
RegistryObject
>




<
rim
:
RegistryObject

objectType
="
urn:x
-
ogc:specification:csw
-
ebrim:ObjectType:EO:EODataLayer
">


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot
:OGC
-
06
-
131:algorithmName
"
slotType
="
string
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:algorithmVersion
"
slotType
="
string
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:highestLocation
"
slotType
="
double
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:lowestLocation
"
slotType
="
double
"/>


<
rim
:
Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:unit
"
slotType
="
string
"/>


</
rim
:
RegistryObject
>


Due to restrictions in the HMA EOP Catalogue implementations it is often the
case that not
all of these slots are queryable. Sometimes the Catalogues does not have all this metadata and
do only allow few of them as criteria in its requests. The complete list of queryables for the
EUMETSAT HMA EOP Catalogue is provided in
paragraph
4.2.2.


Every queryable has a type: String, Geometry, Boolean, Long, Integer, Float, Double, Date,
anyURI, Short. To use a queryable in a request, different operators are available
corresponding to the type of the slot. These operators can be
PropertyIsEqu
alTo
,
PropertyIsGreaterThan, PropertyIsLessThan and PropertyIsBetween
f
or simple types

like
String, Long and Date, and

BBOX, Overlaps
for type Geometry.
The complete list of types
and operators supported by the
EUMETSAT HMA EOP Catalogue
is provided in par
agraph
4.2.2.


The ebRIM representation of EOProducts
allow queries like:

-


Give me all EO Product instances intersecting this footprint, measured after this
date and acquired with an Accross
-
Track Pointing Angle less than x degrees
”.


More formally:

-


Giv
e me all ExtrinsicObjects with the objectType equals to ‘
urn:x
-
ogc:specification:csw
-
ebrim:ObjectType:EO:EOProduct
’, the
extentOf

slot value


a
geometry


intersecting this box, the
beginPosition
value


a ISO 8601 date
-

greater
than this date and the a
longTrackPointingAngle slot value



a double
-


less than x
”.

EUM/OPS/ICD/11/1856

v1, 8 June 2011

HMA EOP Catalogue Tailoring

ICD for EUMETSAT




Page
10

of
70




Using the CSW ebRIM request syntax:


<?xml version="1.0" encoding="UTF
-
8"?>

<
csw
:
GetRecords


xmlns
:csw
="
http://www.opengis.net/cat/csw/2.0.2
"


xmlns
:ogc
="
http://www.opengis.net/ogc
"


xmlns
:
gml
="
http://www.opengis.net/gml
"

xmlns
:wrs
="
http://www.opengis.net/cat/wrs/1.0
"


xmlns
:rim
="
urn:oasis:names:tc:ebxml
-
regrep:xsd:rim:3.0
"


outputSchema
="
urn:oasis:names:tc:ebxml
-
regrep:xsd:rim:3.0
"

service
="
CSW
"


version
="
2.0.2
"


resultType
="
results
"


startPosition
="
1
"


maxRecords
="
20
">


<
csw
:
Query

typeNames
="
rim:ExtrinsicObject
">


<
csw
:
ElementSetName

typeNames
="
rim:
RegistryPackage
">
full
</
csw
:
ElementSetName
>


<
csw
:
Constraint

version
="
1.1.0
">


<
ogc
:
Filter
>


<
ogc
:
And
>



<!
--

This clau
se means “returned ExtrinsicObjects must represent EOProduct”
--
>



<
ogc
:
PropertyIsEqualTo
>



<
ogc
:
PropertyName
>
/rim:ExtrinsicObject/@objectType
</
ogc
:
PropertyName
>



<
ogc
:
Literal
>
urn:x
-
ogc:specification:csw
-
ebrim:ObjectType:EO:EOProduct
</
ogc
:
Literal
>



</
ogc
:
PropertyIsEqualTo
>



<!
--

This clause mean “ExtrinsicObject’s extentOf slot value must intersect with this box”
--
>



<
ogc
:
BBOX
>



<
ogc
:
PropertyName
>
/rim:ExtrinsicObject/rim:Slot[@name=’urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:multiExtentOf’]/wrs
:ValueList/wrs:AnyValue
</
ogc
:
PropertyName
>



<
gml
:
Envelope
>



<
gml
:
lowerCorner
>
48.86
-
124.18
</
gml
:
lowerCorner
>



<
gml
:
upperCorner
>
51.72
-
111.64
</
gml
:
upperCorner
>



</
gml
:
Envelope
>



</
ogc
:
BBOX
>



<!
--

This clause means “ExtrinsicObject’s
acquisition beginPosition slot value must be greater than that date”
--
>



<
ogc
:
PropertyIsGreaterThan
>



<
ogc
:
PropertyName
>
/rim:ExtrinsicObject/rim:Slot[@name=’urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:beginPosition’]/rim:ValueList/rim:Value
</
ogc
:
PropertyName
>



<
ogc
:
Literal
>
2006
-
07
-
15T00:00:00Z
</
ogc
:
Literal
>



</
ogc
:
PropertyIsGreaterThan
>



<!
--

This clause means “ExtrinsicObject’s acquisitionAlongTrackPointingAngle must be equal to that value”
--
>



<
ogc
:
PropertyIs
LessThan
>




<
ogc
:
PropertyName
>
/rim:Ex
trinsicObject/rim:Slot[@name=’urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:alongTrackPointingAngle’]/rim:ValueList/rim:Value



</
ogc
:
PropertyName
>



<
ogc
:
Literal
>
15.3
</
ogc
:
Literal
>



</
ogc
:
PropertyIsLessThan
>


</
ogc
:
And
>


</
ogc
:
Filter
>


</
csw
:
Co
nstraint
>


</
csw
:
Query
>

</
csw
:
GetRecords
>


More information about CSW ebRIM representation of Earth Observation Products and the
mapping with GML metadata is available in document OGC 06
-
131 [1].






EUM/OPS/ICD/11/1856

v1, 8 June 2011

HMA EOP Catalogue Tailoring

ICD for EUMETSAT




Page
11

of
70


2.2

EUMETSAT HMA EOP Catalogue characteristics

The
EUMET
SAT HMA EOP Catalogue implements
the
HMA EOP CATALOGUE

[1
][2]

S
earch Adaptor
and
allows search and discovery of targeted EUMETSAT EO Products
(which are of predefined Product Types

/
Collections
4
)
5
. The
HMA EOP Catalogue
Search
Adaptor is part of the EUMET
SAT Clearinghouse and sits on top of EUMETSATs Legacy
Catalogue “Data Centre” (UMARF).

2.3

General description of the service

2.3.1

Applicative protocols

The aim of
HMA EOP CATALOGUE
is to provide a single interface for all earth
observation catalogues in order to s
implify access to different catalogues for clients using the
Internet.

The
EUMETSAT HMA

EOP
catalogue

supports the target protocol: SOAP 1.2 over HTTP
POST. SOAP 1.1 messages are accepted
as well
but the SOAP
action
is totally ignored.
Discovery via both p
rotocols is not protected, which means that
no
WS
-
S
ecurity
based
token
coming in from
the
outside will be checked
.

Only SOAP messaging (via HTTP/POST) with docum
ent/literal style shall be used
.

You have below a request/response sample with the SOAP envelop
e information.


Request:

POST /daliproxy/wrs/DALIPROXYLAZY HTTP/1.0

Content
-
Type: text/xml; charset=utf
-
8

Accept: application/soap+xml, application/dime, multipart/related, text/*

User
-
Agent: Axis/#axisVersion#

Host: dev.isoft.com

Cache
-
Control: no
-
cache

P
ragma: no
-
cache

SOAPAction: "http://www.opengis.net/cat/csw/2.0.2/requests#GetRecords"

Content
-
Length: 4121

Connection: close


<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:x
si="http://www.w3.org/2001/XMLSchema
-
instance">




<soapenv:Body>




.... // Any CSW Request


</soapenv:Body>

</soapenv:Envelope>


Response:

<soap:Envelope xmlns:soap="http://sch
emas.xmlsoap.org/soap/envelope/">


<soap:Body>


…. // Any CSW Response


</soap:Body>

</soap:Envelope>


Error response:




4

The Collections can be searched and discovered with the EUM
ETSAT Product Navigator
(navigator.eumetsat.int).

5

The HMA EOP Catalogue Search Adaptor was developed by con terra GmbH.

EUM/OPS/ICD/11/1856

v1, 8 June 2011

HMA EOP Catalogue Tailoring

ICD for EUMETSAT




Page
12

of
70


<?xml version="1.0" encoding="UTF
-
8"?>

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://ww
w.w3.org/2001/XMLSchema
-
instance"
xsi:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/ ../../schemas/soap/envelope.xsd">


<soap:Body>


<soap:Fault>


<soap:faultc
ode>soap:Server</soap:faultcode>


<soap:faultstring>A server exception was encountered.</soap:faultstring>


<soap:detail>



<ows:ExceptionReport version="1.2.0" xmlns:ows="http://www.opengis.net/ows"
xmlns:xsi="http://www.w3.org/2001/XMLSchema
-
instance" xsi:schemaLocation="http://www.opengis.net/ows
../../schemas/hma/catalogue/0.2.1/ows/1.0.0/owsExceptionReport.xsd">


<ows:Exception exceptionCode="wrs:InvalidRequest" locator="The
optional locator attribute may be used to indicate where an exception was encountered in the request that generated
th
e error">


<ows:ExceptionText>Message describing the occurred
error.</ows:ExceptionText>


</ows
:Exception>


</ows:ExceptionReport>


</soap:detail>


</soap:Fault>


</soap:Body>

</soap:Envelope>



The WSDL 2.
0 Doc in the annex of the OGC AP ebRIM base specification

[4][5]

is only
informative. Therefore th
e

WSDL of the OGC CSW 2.0.2 specification

[6] is considered as
foundation for the SOAP implementation. The WSDL can be found here:
http://schemas.opengis.net/csw/2.0.2/examples/wsdl/2.0.2
.


Only simple
HTTP GET with KVP payload is supported for GetCapabilities and
GetRepositoryItem.

For the handling of HTTP errors, standard HTTP error co
des will be returned.


The following
is
the EUMETSAT EOP endpoint:

http://veoportal.eumetsat.int:80/cswSOAP/ProductDiscovery


2.3.2

Supported ebRim
-
CSW operations


The
EUMETSAT HMA EOP CAT
ALOGUE
provides the following main functionalities:

1.

To present its capabilities (
getCapabilities

operation)


2.

To search among existing legacy catalogue scenes according user defined criteria
(
getRecords

operation)

3.

To retrieve ebRIM based metadata of one or

several products by
the ebRIM ID (ID of
the RegistryPackage / EOProduct
-
ExtrinsicObject) that contains the EO Product
(
getRecordById

operation)

4.

To retrieve the
EO GML document

by the ebRIM ID
(ID of the RegistryPackage /
EOProduct
-
ExtrinsicObject)
(
getRe
positoryItem
).


The CSW
-
ebRim operations

/ protocol bindings

that are supported by the
EUMETSAT HMA EOP Catalogue are described in the table below.


EUM/OPS/ICD/11/1856

v1, 8 June 2011

HMA EOP Catalogue Tailoring

ICD for EUMETSAT




Page
13

of
70


Operation

SOAP 1.1 + 1.2 over
HTTP POST

HTTP GET with KVP
payload

GetCapabilities

Supported

Supported

De
scribeRecord

Not supported

Not supported

GetDomain

Not supported

Not supported

GetRecords

Supported

Not supported

GetRecordById

Supported

Not supported

Harvest

Not supported

Not supported

Transaction

Not supported

Not supported

GetRepositoryItem

Not
supported

Supported


Table
1
:
Supported CSW
-
ebRim operations / protocol bindings


3

THE GETCAPABILITIES
OPERATION

The GetCapabilities operation allows clients to retrieve service metadata from a

server. The
response to a GetCapabilit
ies request should be an XML document

containing service
metadata about the server
. The HMA EOP CATALOGUE

[1] S
earch Adaptor
directly
handles the getCapabilities operation, which is hard wired.

3.1

GetCapabilities request

Implemented as described in [
3
] withou
t support for the optional parameters “Sections”,
“updateSequence” and “AcceptFormats”.

HTTP GET/KVP is implemented for
GetCapabilities
.
The value of the mandatory
service

parameter
can

be

CSW
’ (returning CSW Capabilities) or ‘
CSW
-
ebRIM
’ (returning
WRS/e
bRIM Capabilities)
.

HTTP/POST
is not
supported as it is optional in the spec (see 8.2 of
[4]).

A GET/KVP request containing a GetCapabilities request:


http://veoportal.eumetsat.int/cswHTTP/ProductDiscovery?service=CSW
-
ebRIM&verison=2.0.2&request=GetCapabilities

3.2

GetCapabilities response

In the
“CSW” case
, the server responds as defined in the baseline CSW specification. In the
"CS
W
-
ebRIM"
case, the server responds as defined in
[4]
.

“…The response shall advertise supported parentIdentifier (collection name) values in a
CSW service capabilities document, through the use of the ows:ExtendedCapabilities element
(
provides an open exte
nsibility point.
Any supplementary operational metadata may be
added.
) and the parentiIdentifier slot” [1], as demonstrated in the example below:


<?xml version="1.0" encoding="UTF
-
8"?>

<!
--

=================================================================
=======

* Topic:


CSW Capabilities document for the CSW 2.0.2 AP ebRIM EP CIM
-

EUMETSAT 2.0 EO Product
Service

* Date:




14.07.2009


EUM/OPS/ICD/11/1856

v1, 8 June 2011

HMA EOP Catalogue Tailoring

ICD for EUMETSAT




Page
14

of
70


* Update:


16.12.2009 (Added SOAP operation constraint and GetCapabilities/GetRepositoryItem operations)

* Author:

Dr. Uwe Voges, con terra GmbH








============================
===============================================
--
>

<
wrs:Capabilities

xmlns:wrs
="
http://www.opengis.net/cat/wrs/1.0
"

xmlns:csw
="
http://www.opengis.net/cat/csw/2.0.2
"

xmlns:gml
="
http://www.opengis.net/gml
"

xmlns:dc
="
http://purl.org/dc/elements/1.1/
"

xmlns:d
ct
="
http://purl.org/dc/terms/
"

xmlns:ows
="
http://www.opengis.net/ows
"

xmlns:ogc
="
http://www.opengis.net/ogc
"

xmlns:rim
="
urn:oasis:names:tc:ebxml
-
regrep:xsd:rim:3.0
"

xmlns:xlink
="
http://www.w3.org/1999/xlink
"

xmlns:xsi
="
http://www.w3.org/2001/XMLSchema
-
inst
ance
"

version
="
1.0.1
"

xsi:schemaLocation
="
http://www.opengis.net/cat/wrs/1.0
http://schemas.opengis.net/csw/2.0.2/profiles/ebrim/1.0/csw
-
ebrim.xsd
">


<
ows:ServiceIdentification
>



<
ows:Title
>
EUMETSAT OGC Catalogue Service for EO Products
</
ows:Title
>



<
ows
:Abstract
>
EUMETSAT HMA Implementation 2.0
-

OGC Web based Catalogue Service (OGC CSW 2.0.2)
for EO Products (AP ebRIM EP EO 0.2.4) based on U
-
MARF
</
ows:Abstract
>



<
ows:Keywords
>




<
ows:Keyword
>
CSW
</
ows:Keyword
>




<
ows:Keyword
>
EUMETSAT
</
ows:Keyword
>




<
ows:Keyword
>
Catalogue Service
</
ows:Keyword
>




<
ows:Keyword
>
HMA
</
ows:Keyword
>




<
ows:Keyword
>
Registry
</
ows:Keyword
>




<
ows:Keyword
>
ESA
</
ows:Keyword
>




<
ows:Keyword
>
EO Products
</
ows:Keyword
>




<
ows:Keyword
>
Metadata
</
ows:Keyword
>




<
ows:Keyword
>
Meteosat
</
ows:Keyword
>




<
ows:Keyword
>
MetOp
</
ows:Keyword
>




<
ows:Keyword
>
MSG
</
ows:Keyword
>




<
ows:Keyword
>
EPS
</
ows:Keyword
>




<
ows:Keyword
>
MTP
</
ows:Keyword
>




<
ows:Type

codeSpace
="
http://www.conterra.de
">
theme
</
ows:Type
>



</
ows:Keywords
>



<
ows:ServiceType

c
odeSpace
="
http://www.opengeospatial.org/ogcna
">
urn:ogc:serviceType:CatalogueService:2.0.2:HTTP:ebRIM
</
ows:ServiceT
ype
>



<
ows:ServiceTypeVersion
>
1.0.1
</
ows:ServiceTypeVersion
>



<
ows:Fees
>
NONE
</
ows:Fees
>



<
ows:AccessConstraints
>
NONE
</
ows:AccessConstraints
>


</
ows:ServiceIdentification
>


<
ows:ServiceProvider
>



<
ows:ProviderName
>
EUMETSAT
</
ows:ProviderName
>



<
ows:ProviderSite

xlink:type
="
simple
"

xlink:href
="
http://www.eumetsat.int
"/>



<
ows:ServiceContact
>




<
ows:IndividualName
/>




<
ows:PositionName
/>




<
ows:ContactInfo
>





<
ows:Phone
>






<
ows:Voice
>
+49
-
6151
-
807447
</
ows:Voice
>






<
ows:Facsimile
>
+49
-
6151
-
807 0
</
ows:Facsimile
>





</
ows:Phone
>





<
ows:Address
>






<
ows:DeliveryPoint
>
EUMETSAT Allee 1
</
ows:DeliveryPoint
>






<
ows:City
>
Darmstadt
</
ows:C
ity
>






<
ows:AdministrativeArea
>
Hessen
</
ows:AdministrativeArea
>






<
ows:PostalCode
>
64295
</
ows:PostalCode
>






<
ows:Country
>
Germany
</
ows:Country
>






<
ows:ElectronicMailAddress
>
Michael.Schick@eumetsat.int
</
ows:ElectronicMailAddress
>





</
ows:Address
>





<
ows:OnlineResource

xlink:href
="
mailto:Michael.Schick@eumetsat.int
"/>




</
ows:ContactInfo
>



</
ows:ServiceContact
>


</
ows:ServiceProvider
>


<
ows:OperationsMetadata
>



<
ows:Operation

name
="
GetCapabilities
">




<
ows:DCP
>





<
ows:HTTP
>






<
ows:Get

xl
ink:href
="
http://veoportal.eumetsat.int:80/cswHTTP/ProductDiscovery
"/>





</
ows:HTTP
>




</
ows:DCP
>



</
ows:Operation
>



<
ows:Operation

name
="
GetRecords
">




<
ows:DCP
>





<
ows:HTTP
>






<
ows:Post

xlink:href
="
http://veoportal.eumetsat.int:80/cswSOAP/Prod
uctDiscovery
">

EUM/OPS/ICD/11/1856

v1, 8 June 2011

HMA EOP Catalogue Tailoring

ICD for EUMETSAT




Page
15

of
70








<
ows:Constraint

name
="
PostEncoding
">








<
ows:Value
>
SOAP
</
ows:Value
>







</
ows:Constraint
>






</
ows:Post
>





</
ows:HTTP
>




</
ows:DCP
>




<
ows:Parameter

name
="
typeNames
">





<
ows:Value
>
rim:RegistryObject
</
ows:Value
>




</
ows:P
arameter
>




<
ows:Parameter

name
="
outputFormat
">





<
ows:Value
>
text/xml
</
ows:Value
>





<
ows:Value
>
application/xml
</
ows:Value
>




</
ows:Parameter
>




<
ows:Parameter

name
="
outputSchema
">





<
ows:Value
>
urn:oasis:names:tc:ebxml
-
regrep:xsd:rim:3.0
</
ows:Value
>




</
ows:Parameter
>




<
ows:Parameter

name
="
resultType
">





<
ows:Value
>
hits
</
ows:Value
>





<
ows:Value
>
results
</
ows:Value
>




</
ows:Parameter
>




<
ows:Parameter

name
="
ElementSetName
">





<
ows:Value
>
brief
</
ows:Value
>





<
ows:Value
>
summary
</
ows:Value
>





<
ows:Value
>
full
</
ows:Value
>




</
ows:Parameter
>




<
ows:Parameter

name
="
CONSTRAINTLANGUAGE
">





<
ows:Value
>
Filter
</
ows:Value
>




</
ows:Parameter
>



</
ows:Operation
>



<
ows:Operation

name
="
GetRecordById
">




<
ows:DCP
>





<
ows:HTTP
>






<
ows:Post

xlink
:href
="
http://veoportal.eumetsat.int:80/cswSOAP/ProductDiscovery
">







<
ows:Constraint

name
="
PostEncoding
">








<
ows:Value
>
SOAP
</
ows:Value
>







</
ows:Constraint
>






</
ows:Post
>





</
ows:HTTP
>




</
ows:DCP
>




<
ows:Parameter

name
="
ElementSetName
">





<
ows:Value
>
brief
</
ows:Value
>





<
ows:Value
>
summary
</
ows:Value
>





<
ows:Value
>
full
</
ows:Value
>




</
ows:Parameter
>



</
ows:Operation
>



<
ows:Operation

name
="
GetRepositoryItem
">




<
ows:DCP
>





<
ows:HTTP
>






<
ows:Get

xlink:href
="
http://veoportal.eu
metsat.int:80/cswHTTP/ProductDiscovery
"/>





</
ows:HTTP
>




</
ows:DCP
>



</
ows:Operation
>



<
ows:ExtendedCapabilities
>




<
rim:Slot

name
="
urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:parentIdentifier
"

slotType
="
urn:oasis:names:tc:ebxml
-
regrep:DataType:String
">





<
rim:Value
>
urn:ogc:def:EOP:EUM:HMA.M02:ASCxxx1A
</
rim:Value
>





<
rim:Value
>
urn:ogc:def:EOP:EUM:HMA.M02:AVHxxx1B
</
rim:Value
>





<
rim:Value
>
urn:ogc:def:EOP:EUM:HMA.M02:MHSxxx1B
</
rim:Value
>





<
rim:Value
>
urn:ogc:def:EOP:EUM:HMA.MSG1:MSG15
</
rim:Value
>





<
ri
m:Value
>
urn:ogc:def:EOP:EUM:HMA.MSG1:MSGAMVE
</
rim:Value
>





<
rim:Value
>
urn:ogc:def:EOP:EUM:HMA.MSG2:MSG15
</
rim:Value
>





<
rim:Value
>
urn:ogc:def:EOP:EUM:HMA.MSG2:MSGAMVE
</
rim:Value
>





<
rim:Value
>
urn:ogc:def:EOP:EUM:HMA.N18:AVHGAC1B
</
rim:Value
>





<
rim:
Value
>
urn:ogc:def:EOP:EUM:HMA.N19:AVHGAC1B
</
rim:Value
>




</
rim:Slot
>



</
ows:ExtendedCapabilities
>


</
ows:OperationsMetadata
>


<
ogc:Filter_Capabilities
>



<
ogc:Spatial_Capabilities
>




<
ogc:GeometryOperands
>





<
ogc:GeometryOperand
>
gml:Envelope
</
ogc:Geom
etryOperand
>




</
ogc:GeometryOperands
>

EUM/OPS/ICD/11/1856

v1, 8 June 2011

HMA EOP Catalogue Tailoring

ICD for EUMETSAT




Page
16

of
70





<
ogc:SpatialOperators
>





<
ogc:SpatialOperator

name
="
BBOX
"/>




</
ogc:SpatialOperators
>



</
ogc:Spatial_Capabilities
>



<
ogc:Scalar_Capabilities
>




<
ogc:LogicalOperators
/>




<
ogc:ComparisonOperators
>





<
ogc:C
omparisonOperator
>
EqualTo
</
ogc:ComparisonOperator
>





<
ogc:ComparisonOperator
>
Like
</
ogc:ComparisonOperator
>




</
ogc:ComparisonOperators
>



</
ogc:Scalar_Capabilities
>



<
ogc:Id_Capabilities
>




<
ogc:FID
/>



</
ogc:Id_Capabilities
>


</
ogc:Filter_Capabilitie
s
>

</
wrs:Capabilities
>



4

THE GETRECORDS OPERA
TION

4.1

Brief overview

The GetRecords operation is the service for searching products by filters. It is implemented
within the SOAP
-
part of the HMA EOP Catalogue
Adaptor
(which is part of the
EUMETSAT Clearinghou
se).
This
SOAP
-
part is
responsible for the HMA EOP SOAP
interface (getRecords, getRecordById).
T
he
EOCatalogue Adaptor
calls the
UMARF
legacy
system

from within the Clearinghouse.

A d
istributed EO
-
Search
via
HMA services
is
not supported within the first v
ersion of the
Clearinghouse
.

4.2

GetRecords request

Examples of requests can be found in the Annex.

4.2.1

CSW Request parameters

When in the following table a parameter is flagged as ignored, it means the server
ignores the paramter but
does not return an error mes
sage if it is present in the
request. When the value is
“fixed”, “mandatory”

or
“only supported value”
, error
message
or wrong results w
ill be returned if the value of the parameter is invalid.
Parameters and values are case sensitive.


Parameter

Value

Opt
ional /

Mandatory

service

Fixed value of ‘CSW‘
=
䵡湤n瑯ty
=
癥牳楯r
=
Fixed value of ‘2.0.2‘
=
䵡湤n瑯ty
=
牥煵q獴fd
=
-
=
f杮g牥d
=
牥獵汴qype
=
佮ly⁳異灯牴=搠da汵敳l
=


‘hits‘ (default value),
=


‘results‘
=
佰瑩潮慬
=
潵瑰畴c潲浡t
=
佮ly⁳異灯牴=搠da汵敳l
=



‘application/xml‘ (
摥晡u汴⁶=汵攩=
=


‘text/xml’
=
f杮g牥d
=
潵瑰畴pc桥浡
=
c楸e搠癡汵攺
=


‘urn:oasis:names:tc:ebxml
-
regrep:xsd:rim:3.0‘
佰瑩潮慬
=
EUM/OPS/ICD/11/1856

v1, 8 June 2011

HMA EOP Catalogue Tailoring

ICD for EUMETSAT




Page
17

of
70


(default)



‘http://www.opengis.net/cat/csw/2.0.2‘

startPosition

Default Value is 1.

Optional

maxRecords

Default Value is 10.

Optional

t
ypeName
s

For the attribute of the Element “query” and for the
attribute of the Element “ElementSetName“ s
ee chapter
4.2.1.3

s
ee
4.2.1.3

elementSetName



‘brief‘,



‘summ
ary‘ (default value)



‘full‘

If another value than one of these three is provided, it will
be ignored and the default value (summary) will be used.
.

Optional

Constraint

See chapter
4.2.2

(only Filter Encoding supported)

Mandato
ry

SortBy

Ignored if present in the request

Ignored

DistributedSearch

Ignored if present in the request

Ignored

HopCount

Ignored if present in the request

Ignored

ResponseHandler

Ignored if present in the request

Ignored

Table
2

: CSW GetRecords request parameters.

4.2.1.1

resultType

The only supported values for the
resultType

parameter are “
hits
” and “
results
”.

For ‘
hits’

mode, the only relevant returned information is the “
numberOfRecordsMatched
”.



4.2.1.2

OutputSchema

The supported values

for the O
utputSchema

parameter are:




urn:oasis:names:tc:ebxml
-
regrep:xsd:rim:3.0




‘http://www.opengis.net/cat/csw/2.0.2‘


4.2.1.3

TypeName

The attribute “typeNames” of
the
ElementSetName
element
is ignored. A RegistryPackage
will be returned including all those R
egistryObjects which are defined to be included for the
specified ElementSetName (brief, summary, full).


As defined in
[1] the server implementation
assumes the
typeName identifiers

of the Query
element are fixed (i.e. have the
exact values

as shown in t
he example above in red/italic) and
these elements
are ignored.
Means aliases are fixed!



Description

CONFORMANCE

In Annex G of [1] chapter “Request
handling”:



Server can assume that the typeName
identifiers in the above request are fixed
(i.e.
have the
exact values

as shown in the
example above in red/italic) and these
LEVEL 1 & 2 : C

LEVEL 3 : NC

EUM/OPS/ICD/11/1856

v1, 8 June 2011

HMA EOP Catalogue Tailoring

ICD for EUMETSAT




Page
18

of
70


elements could possibly be ignored.
(LEVEL 1 and 2)



Server should be able to handle variable
typeNames identifiers, thus has to interpret
the red/italic section in the request above.
(LEVE
L 3)


4.2.1.4

ElementSetName

All values for the
ElementSetName
are supported.
A RegistryPackage will be returned
including
exactly those
RegistryObjects which are defined to be included for the specified
ElementSetName (brief, summary
, full)

(see [3]):







Brief’
: identification information (id, lid and status) of
ExtrinsicObject
s of
objectType
urn:x
-
ogc:specification:csw
-
ebrim:ObjectType:EO:EOProduct
.



‘Summary’
: summary information (brief
-
content plus Name, Description, Slots,
Externa
lIdentifier) of
ExtrinsicObject
s of objectType
urn:x
-
ogc:specification:csw
-
ebrim:ObjectType:EO:EOProduct

.




Full

: full information (full set of RegistryObjects (including Associations, etc)

If another value than one of these three is provided, it will be
ignored and the default value
(summary) will be used.


4.2.1.5

SortBy

Sorting is not supported. If provided within a request it is ignored.
The default order will be
by ascending
EUMETSAT product name (product id) of the UMARF legacy catalogue
.


4.2.1.6

Pagination

startPo
sition and maxRecords allow using pagination. startPosition is the index of first record
requested and maxRecords represents the number of records needed. So the index of final
record returned will be startPosition + maxRecords if there are enough records
to satisfy the
request, in the other case the index of final record returned will be startPosition +
numberOfRecordsReturned (see chapter 4.3.2).


4.2.2

Request filters

The filter is composed of different parts contained in an <ogc:And> structure

(see Annex G
in

[1])
:


<csw:GetRecords xmlns:csw="http://www.opengis.net/cat/csw/2.0.2"
xmlns:ogc="http://www.opengis.net/ogc" xmlns:gml="http://www.opengis.net/gml"
xmlns:wrs="http://www.opengis.net/cat/wrs/1.0" xmlns:rim="urn:oasis:names:tc:ebxml
-
regrep:xsd:rim:3.0" ve
rsion="2.0.2" outputSchema="urn:oasis:names:tc:ebxml
-
regrep:xsd:rim:3.0" resultType="
results
" service="CSW"
outputFormat="application/xml" maxRecords="
10
" startPosition="
1
">


<csw:Query typeNames="
rim:RegistryPackage

rim:ExtrinsicObject
rim:ExtrinsicObjec
t_acquisitionPlatform rim:ExtrinsicObject_dataLayer
EUM/OPS/ICD/11/1856

v1, 8 June 2011

HMA EOP Catalogue Tailoring

ICD for EUMETSAT




Page
19

of
70


rim:Association_acquisitionPlatAsso rim:Association_dataLayerAsso rim:Classification
rim:ClassificationNode
"
>



<csw:ElementSetName typeNames="rim:

RegistryPackage">full</csw:ElementSetName>



<csw:Constr
aint version="1.1.0">




<ogc:Filter>





<ogc:And>


<ogc:PropertyIsEqualTo>


<ogc:PropertyName>

/rim:RegistryPackage/rim:RegistryObjectList[*]/rim:RegistryObject/@id


</ogc:PropertyName>



<ogc:PropertyName>/rim:ExtrinsicObject/@id


</ogc:PropertyName>


</ogc:PropertyIsEqualTo>







<ogc:PropertyIsEqualTo>





<ogc:PropertyName>/rim:ExtrinsicObject/@obje
ctType</ogc:PropertyName>






<ogc:Literal>
urn:x
-
ogc:specification:csw
-
ebrim:ObjectType:EO:EOProduct
</ogc:Literal>






</ogc:PropertyIsEqualTo>


<<PART 1>>

<<PART 2>>

<<PART 3>>

<<PART 4>>





</ogc:And>




</ogc:Filter>



</csw:Constraint>


</csw:Qu
ery>

</csw:GetRecords>


As defined in
[1]
the implementation
assume
s

the
csw:Query@typeName

identifiers

are
fixed (i.e. have the exact values as shown in the example above in red/italic) and these
elements
are ignored
6
.
Means aliases are fixed!


4.2.2.1

<<Part 1>
>: EUMETSAT Collections

The implementation supports what has to be supported for CL (Conformance Level) 1 and
CL2

(see table below)
. This means
the server is able to handle
multi
-
mission requests:
it is
possible
to
define
more than one collection for a sea
rch

(resulting that the
“parentIdentifier”
is
“or” connected
)
.


Description

CONFORMANCE

06
-
131r5 Annex G chapter “Request handling


The
Collections”:

The server shall be able to handle single mission requests. (LEVEL
1)

LEVEL 1 : C

LEVEL 2 : C

LEVEL 1 & 2 : C




6

Only checked if fixed values are provided otherwise an exception is raised

EUM/OPS/ICD/11/1856

v1, 8 June 2011

HMA EOP Catalogue Tailoring

ICD for EUMETSAT




Page
20

of
70


The server shall be able to handle

multi
-
mission requests (LEVEL
2).

Servers receiving unknown parentIdentifiers shall return an empty
response for this unknown collection as if no products for this
collection were found. (LEVEL 1 & 2)


Currently di
fferent collections are defined for EUMETSAT
7
.

Examples:



urn:ogc:def:EOP:EUM:acronym:MSG15:fileid:EO:EUM:DAT:METOP:HRSEVIRI



urn:ogc:def:EOP:EUM:acronym:AVHxxx1B:satellite:M02:fileid:EO:EUM:DAT:MET
OP:AVHRRL1



4.2.2.2

<<Part 2>>: Area of Interest

This part is opti
onal in a request.

The implementation supports (as required for CL1, see table below)
only
a Bounding Box
(BBOX) as
comparator as
the EUMETSAT legacy UAPI only allows BBOX filters with
support of the urn:ogc:def:crs:EPSG:6.3:4326

(i.e WGS 84) common coordi
nates reference
system. The coordinates are expressed in Latitude Longitude.
The
coordinate reference
system shorthand
is
“urn:ogc:def:crs:EPSG:6.3:4326”.



Description

CONFORMANCE

06
-
131r5 Annex G chapter “Request handling


Area of
Interest”:

Supports o
nly BBOX with EPSG:4326, i.e; WGS 84 (LEVEL 1).

Supports also the following geometries:

Circle, Polygon. (LEVEL 2)

LEVEL 1: C

LEVEL 2 : NC


The
queryable is
multiExtentOf

as defined in [1].
It must be embedded in a <ogc:BBOX>
tag.

Example:


<!

This examp
le is not a complete request

>

<ogc:BBOX>


<ogc:PropertyName>/rim:ExtrinsicObject/rim:Slot[@name="urn:ogc:def:ebRIM
-
Slot:OGC
-
06
-
131:multiExtentOf"]/wrs:ValueList/wrs:AnyValue[1]</ogc:PropertyName>


<Envelope xmlns="http://www.opengis.net/gml" srsName="
u
rn:ogc:def:crs:EPSG:6.3:4326">



<lowerCorner>
35.1940
-
22.5672
</lowerCorner>



<upperCorner>
63.1343 25.2537
</upperCorner>


</Envelope>

</ogc:BBOX>






7

The number will most likely be changed in the future.

EUM/OPS/ICD/11/1856

v1, 8 June 2011

HMA EOP Catalogue Tailoring

ICD for EUMETSAT




Page
21

of
70


Remark
s
:



The
supported operator

is
listed in the service capabilities document within the
Filter_Capabil
ities section.



If a filter expression contains an unsupported operator the service return
s

an exception
with code wrs:NotSuppported.



No support for Polygons and Circles
8


4.2.2.3

<<Part 3>>: Support for Common EOP Queryables

This part is optional in a request.

Gen
eral remark concerning the implementation of the
request
´s

filter handling policy within
the
EUMETSAT HMA EOP Catalogue
(full view being the

reference for the exposed slots):

-

a search parameter on a not relevant slot (i.e. not queryable and not exposed) is

ignored;

-

a search parameter on an exposed but not queryable slot raises an ExceptionReport;

-

a search parameter with an unsupported operation on an exposed and queryable slot
raises an ExceptionReport;

-

if a slot has a fixed value (e.g.
productType

always e
qual
s

to ‘IMAGE’), nothing is
returned when the value is different from the fixed one;

-

all queryables are considered as optional.



Description

CONFORMANCE

06
-
131r5 Annex G chapter “Request handling”:



CONFORMANCE LEVEL 1 and 2: A server shall implement a
“lazy” behaviour and ignore EO extension package attributes in a
filter expression which are not supported by the requested
selection.
The Catalogue component shall ignore, whenever
possible, search parameters that are not relevant.

However, the Catalogue
component shall not offend in its
response the search parameters included in the query (i.e. a
response shall not expose a slot whose value contradicts a search
parameter targeting that slot).

As a consequence (full view being the reference for the exposed

slots):

-

a search parameter on a not relevant slot (i.e. not queryable and
not exposed) shall be ignored

-

a search parameter on an exposed but not queryable slot shall
raise an ExceptionReport

-

a search parameter with an unsupported operation on an exp
osed
and queryable slot shall raise an ExceptionReport


LEVEL 1 and 2 : C

LEVEL 3 : NC




8

Maybe in a later
release it may be
possible to have convert Circle and Polygon geometries into “bounding”
BBOX


EUM/OPS/ICD/11/1856

v1, 8 June 2011

HMA EOP Catalogue Tailoring

ICD for EUMETSAT




Page
22

of
70




CONFORMANCE LEVEL 3: A server shall implement a “strict”
behaviour and implement exception handling as in the
specification OGC 06
-
131 when receiving EO extension package
attributes in a filter expres
sion which are not supported by the
requested selection.



The comparators
for the different data types which have to be supported for Conformance
Level 1 are visualized in the table below.


Type

Comparators supported

Strin
g

PropertyIsEqualTo

Double, int

(
PropertyIsEqualTo,
)
9

PropertyIsGreaterThanOrEqualTo,
PropertyIsLessThanOrEqualTo

Date

(
PropertyIsEqualTo,
)
9

PropertyIsGreaterThanOrEqualTo,
PropertyIsLessThanOrEqualTo

Geomet
ry

BBOX

Table
3
:Comparators depending on the type for level 1
Conformance


The supported comparators of the
EUMETSAT HMA EOP Catalogue
are visualized in the
table below.


Type

Comparators supported

String

PropertyIsEqualTo

Double
, int

PropertyIsGreaterThanOrEqualTo,
PropertyIsLessThanOrEqualTo

Date

PropertyIsGreaterThanOrEqualTo,
PropertyIsLessThanOrEqualTo

Geometry

BBOX

Table
4
:Comparators depending on the type
implemented in EUMETSAT HMA EOP
CATALOGUE


If a queryable deviates from this behaviour this is described in one of the following tables
(giving details on the queryables).

The implementation only supports
“and” connected expressions of
queryable/comparator/value triples.

An Exception is thrown if


or
” connected
expressions
are
included in a query (outside parentIdentifier


see <<Part1 >>)
.

The following table
s

show the supported queryables and their corresponding supported
comparators
.

Th
ese
important table
s

describe for each queryable if is
real
ly
supported
as
queryable (
or not
)
, the
corresponding
supported
comparator, the level of compliance to which



9

Not clear, if mandatory

EUM/OPS/ICD/11/1856

v1, 8 June 2011

HMA EOP Catalogue Tailoring

ICD for EUMETSAT




Page
23

of
70


support of the queryable belongs to, and the relative degree of compliance (C=full,
PC=partially)
.




Queryable

Supported
Comparators

Comment


Addi
tional
EUMETSAT
Implementatio
n Comment

Annex G

Conforman
ce Level

rim:Name

-

Will be returned
-
> but it
is not queryable
(ignored)




doi

-

Not queryable., ignored.
Will not be returned.




parentIdentifier

PropertyIsEqualTo