Open Geospatial Consortium
Posted Date: 2012-11-16
Approval Date: 2012-12-21
Publication date: 2013-03-26
External identifier of this OGC® document: http://www.opengis.net/doc/bp/eo-product-collection
Reference number of this document: OGC 11-035r1
Version: 1.0
Category: OGC® Best Practice
Editors: Frédéric Houbie, Steven Smolders

EO Product Collection, Service and Sensor Discovery
using the CS-W ebRIM Catalogue

Copyright © 2013 Open Geospatial Consortium
To obtain additional rights of use, visit http://www.opengeospatial.org/legal
This document defines an OGC Best Practices on a particular technology orapproach related to an OGC standard. This document is not an OGC Standard
and may not be referred to as an OGC Standard. This document is subject tochange without notice. This document is an official position of the OGC
membership on this particular technology topic

Document type:
Document subtype:
Document stage:
Document language:

OGC® Best Practice Paper
NA
Approved for publication
EnglishOGC 11-035

License Agreement
Permission is hereby granted by the Open Geospatial Consortium, ("Licensor"), free of charge and subject to the terms set forth
below, to any person obtaining a copy of this Intellectual Property and any associated documentation, to deal in the Intellectual
Property without restriction (except as set forth below), including without limitation the rights to implement, use, copy, modify,
merge, publish, distribute, and/or sublicense copies of the Intellectual Property, and to permit persons to whom the Intellectual
Property is furnished to do so, provided that all copyright notices on the intellectual property are retained intact and that each
person to whom the Intellectual Property is furnished agrees to the terms of this Agreement.
If you modify the Intellectual Property, all copies of the modified Intellectual Property must include, in addition to the above
copyright notice, a notice that the Intellectual Property includes modifications that have not been approved or adopted by
LICENSOR.
THIS LICENSE IS A COPYRIGHT LICENSE ONLY, AND DOES NOT CONVEY ANY RIGHTS UNDER ANY PATENTSTHAT MAY BE IN FORCE ANYWHERE IN THE WORLD.
THE INTELLECTUAL PROPERTY IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE, AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. THE COPYRIGHT HOLDER ORHOLDERS INCLUDED IN THIS NOTICE DO NOT WARRANT THAT THE FUNCTIONS CONTAINED IN THE
INTELLECTUAL PROPERTY WILL MEET YOUR REQUIREMENTS OR THAT THE OPERATION OF THE
INTELLECTUAL PROPERTY WILL BE UNINTERRUPTED OR ERROR FREE. ANY USE OF THE INTELLECTUAL
PROPERTY SHALL BE MADE ENTIRELY AT THE USER’S OWN RISK. IN NO EVENT SHALL THE COPYRIGHTHOLDER OR ANY CONTRIBUTOR OF INTELLECTUAL PROPERTY RIGHTS TO THE INTELLECTUAL PROPERTYBE LIABLE FOR ANY CLAIM, OR ANY DIRECT, SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY
DAMAGES WHATSOEVER RESULTING FROM ANY ALLEGED INFRINGEMENT OR ANY LOSS OF USE, DATA OR
PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR UNDER ANY OTHER LEGAL THEORY,ARISING OUT OF OR IN CONNECTION WITH THE IMPLEMENTATION, USE, COMMERCIALIZATION ORPERFORMANCE OF THIS INTELLECTUAL PROPERTY.
This license is effective until terminated. You may terminate it at any time by destroying the Intellectual Property together withall copies in any form. The license will also terminate if you fail to comply with any term or condition of this Agreement. Except
as provided in the following sentence, no such termination of this license shall require the termination of any third party end-user
sublicense to the Intellectual Property which is in force as of the date of notice of such termination. In addition, should theIntellectual Property, or the operation of the Intellectual Property, infringe, or in LICENSOR’s sole opinion be likely to infringe,
any patent, copyright, trademark or other right of a third party, you agree that LICENSOR, in its sole discretion, may terminate
this license without any compensation or liability to you, your licensees or any other party. You agree upon termination of any
kind to destroy or cause to be destroyed the Intellectual Property together with all copies in any form, whether held by you or by
any third party.
Except as contained in this notice, the name of LICENSOR or of any other holder of a copyright in all or part of the Intellectual
Property shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Intellectual Property
without prior written authorization of LICENSOR or such copyright holder. LICENSOR is and shall at all times be the sole
entity that may authorize you or any third party to use certification marks, trademarks or other special designations to indicatecompliance with any LICENSOR standards or specifications.
This Agreement is governed by the laws of the Commonwealth of Massachusetts. The application to this Agreement of theUnited Nations Convention on Contracts for the International Sale of Goods is hereby expressly excluded. In the event any
provision of this Agreement shall be deemed unenforceable, void or invalid, such provision shall be modified so as to make itvalid and enforceable, and as so modified the entire Agreement shall remain in full force and effect. No decision, action or
inaction by LICENSOR shall be construed to be a waiver of any rights or remedies available to it.

iiCi ht © 2013 O

G

ti l Cti

OGC 11-035r1

Abstract
This is an OGC Best Practice document describing the relations that exist between
several metadata conceptual models (EO Product, EO Product Collections, Sensors
and Services). The specification of the linking between different artifacts is important
for the process of cataloguing and discovering those artifacts.

Keywords
ogcdoc, ogc document, csw, catalogue, ebrim, sensors, discovery, eoCi ht © 2013 O

G

ti l C

ti

iii

OGC 11-035

Contents1	
  INTRODUCTION ................................................................................................................. 1	
  
1.1	
  
Document contributor contact points .................................................................. 1	
  

1.2	
  

Revision history .................................................................................................. 1	
  

1.3	
  

Future work ......................................................................................................... 2	
  

1.4	
  

Forward ............................................................................................................... 2	
  

2	
  

REFERENCES ...................................................................................................................... 2	
  

3	
  

TERMS AND DEFINITIONS .............................................................................................. 4	
  

4	
  

CONVENTIONS .................................................................................................................... 5	
  Abbreviated terms ............................................................................................... 5	
  

4.1	
  
4.2	
  

UML notation...................................................................................................... 5	
  

5	
  

INTRODUCTION ................................................................................................................. 5	
  

6	
  

METADATA MODELS ........................................................................................................ 7	
  
6.1	
  
EO Product Collection minimal information model ........................................... 7	
  6.1.1	
   EO Product Collection information model ..................................................... 7	
  6.1.2	
   Non ISO 19115 elements for eo product collection discovery ..................... 14	
  
6.2	
  

EO Services minimal information model ......................................................... 17	
  6.2.1	
   EO Services information model .................................................................... 18	
  6.2.2	
   INSPIRE mapping notes ............................................................................... 25	
  
6.3	
  

SensorML minimal information model ............................................................ 25	
  6.3.1	
   SensorML Discovery Profile ........................................................................ 25	
  
7	
  

DISCOVERY STRATEGY IN EO COMMUNITY ......................................................... 26	
  EO Community Metadata model ...................................................................... 26	
  

7.1	
  

7.1.1	
   Link between EO product metadata and the acquiring sensor ...................... 27	
  7.1.2	
   Link between EO product metadata and the metadata of thecorresponding EO Product Collection ...................................................................... 31	
  7.1.3	
   Link between the EO Product Collection metadata and the sensors
information ................................................................................................................ 31	
  iCi ht © 2013 O

G

ti l Cti

OGC 11-035r1

7.1.4	
   Identifier definition ....................................................................................... 32	
  
7.2	
  

Metadata cataloguing ........................................................................................ 32	
  7.2.1	
   How to link different extension packages in a CSW ebRIM catalog ........... 33	
  7.2.1.1	
   LINK BY ASSOCIATION ........................................................................................................................ 33	
  7.2.1.2	
   LINK BY EQUIVALENT SLOT ................................................................................................................ 33	
  7.2.2	
   Link between EO Product and EO Product Collection metadata ................. 34	
  7.2.3	
   Link between EO Product and Sensor metata............................................... 34	
  7.2.4	
   Link between Collection and Sensor ............................................................ 35	
  Ci ht © 2013 O

G

ti l Cti

OGC 11-035

List of figures
Figure 1 EO Product Collection metadata (Simplified UML class diagram – using
ISO19115 elements only – not all dataTypes/codelists included)........................................ 7	  Figure 2 EO Product Collection metadata (Simplified UML class diagram – using
ISO19115 -2 extension for Platform & Instrument elements only) .................................. 15	  Figure 3 : EO Data Models and what they describe .................................................................. 27	
  List of tables

Page

Table 1 Metadata entity set information (EO Product Collection Mandatory elementsonly) .......................................................................................................................................... 8	
  Table 2 CI_ResponsibleParty (EO Product Collection Mandatory elements only) ................. 9	
  Table 3 DataIdentification Information (EO Product Collection Mandatory elementsonly) ........................................................................................................................................ 10	
  Table 4 CI_Citation (EO Product Collection Mandatory elements only) ............................... 11	
  Table 5 CI_Date (EO Product Collection Mandatory elements only) ..................................... 11	
  Table 6 MD_resolution (EO Product Collection Mandatory elements only) ......................... 11	
  Table 7 MD_Keywords ................................................................................................................ 12	
  Table 8 DQ_DataQuality ............................................................................................................. 12	
  Table 9 DQ_Element .................................................................................................................... 12	
  Table 10 DQ_Result ..................................................................................................................... 13	
  Table 11 LI_Lineage..................................................................................................................... 13	
  Table 12 MD_Constraints/LegalConstraints ............................................................................. 14	
  Table 14 CI_ResponsibleParty (EO Services Collection Mandatory elements only) ............. 20	
  Table 15 ServiceIdentification Information ............................................................................... 22	
  Table 16 SV_CoupledResource ................................................................................................... 22	
  Table 17 SV_OperationMetadata ............................................................................................... 22	
  Table 18 MD_StandardOrderProcess ........................................................................................ 23	
  Table 19 CI_Citation .................................................................................................................... 23	
  Table 20 CI_Date .......................................................................................................................... 24	
  Table 21 MD_Keywords .............................................................................................................. 24	
  Table 22 MD_Constraints/LegalConstraints ............................................................................. 25	
  

i

C

i ht © 2013 O

G

ti l Cti

OGC® Discussion Paper

OGC 11-035

EO Product Collection and Service Discovery using the
CS-W ebRIM Catalogue

1

Introduction

This document is created within the SMAAD (Semantic-web Mediated AccessAcross Domains) project. This European Project aims at validating the technicalchoices concerning metadata and discovery within the Earth Observation domain
made within the Heterogeneous Mission Accessibility series of projects.
This document proposes a technical guideline for implementing the discovery of EO
Product Collections, EO Services and EO Sensors.
This document contains an analysis of the minimal EO Product collection and EO
Services metadata that is to be supplied for meaningful and concise descriptions of
EO Product Collections and EO Services and documents the effects on the existingCIM extension Package of the ebRIM Application Profile of CSW.
1.1

Document contributor contact points

All questions regarding this document should be directed to the editor or thecontributors:
Name

Organization

Frédéric Houbie
Philippe Mougnaud
Steven Smolders

1.2

Intergraph
ESA
GIM

Revision history
Date

Release

EditorPrimary clauses
modified

Description

2011-10-06

1.0

S. Smolders,F. Houbie

All

Initial version

2012-03-30

1.1

F. HoubieAll

Add Sensor linking information

1

OGC 11-035
1.3

Future work

This document is a description of the relations that exist between different metadata
models and their cataloguing process. Evolutions in the metadata models or
catalogue specifications could have impact on the content of this document.
1.4

ForwardAttention is drawn to the possibility that some of the elements of this document may
be the subject of patent rights. The Open Geospatial Consortium shall not be held
responsible for identifying any or all such patent rights.
Recipients of this document are requested to submit, with their comments,
notification of any relevant patent claims or other intellectual property rights ofwhich they may be aware that might be infringed by any implementation of thestandard set forth in this document, and to provide supporting documentation.
2

References

The following documents provide background reference. In the body of the text
these documents are referenced as listed below.
[RD01] ISO 19115:2003 Geographic Information – Metadata[RD02] ISO 19119, Geographic Information – Services (ISO 19119:2005)
21/06/2006,
http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?cs
number=39890[RD03] ISO 19139, Geographic Information – Metadata XML (ISO 19139:2007),
http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?cs
number=32557[RD04] OGC 09-163r2, OGC Catalogue Services Specification 2.0, Extension
Package for ebRIM Application Profile: SensorML, Version 0.0.3,
02/04/2010.
[RD05] OGC 06-131r6, OGC Catalogue Services Specification 2.0, Extension
Package for ebRIM Application Profile: Earth Observation Products,
Version 1.0.0, 10/02/2010
http://portal.opengeospatial.org/files/?artifact_id=28152[RD06] OGC 07-038r3, OGC Cataloguing of ISO Metadata (CIM) – Using theebRIM profile of CS-W, Version 0.1.12[RD07] OGC 07-045, OpenGIS Catalogue Services Specification 2.0.2 – ISO
Metadata Application Profile, Version 1.0, 19/07/2007,
http://portal.opengeospatial.org/files/?artifact_id=21460

2

Copyright © 2013 Open Geospatial Consortium

OGC 11-035r1[RD08] DRAFT HMA EO Product Collection and Service Discovery using the ISO
Metadata Application Profile of CSW 2.0.1, OGC 07-025 (not published)[RD09] OGC 04-038r4 OpenGIS Catalogue Services Specification 2.0.1 (withCorrigendum) ISO Metadata Application Profile[RD10] OGC 10-168 DRAFT, OGC SensorML Encoding Standard, Version 2.0.0,
2011-06-27[RD11] ISO 19115/Cor.1:2006, Geographic information – Metadata, TechnicalCorrigendum 1[RD12] INSPIRE Metadata Implementing Rules: Technical Guidelines based on
EN ISO 19115 and EN ISO 19119, INSPIRE Drafting Team Metadata andEuropean Commission Joint Research Centre, V. 1.2, 2010-06-16[RD13] ISO 19119:2005/PDAM 1 - Extensions of the service metadata model
http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?cs
number=44268[RD14] INSPIRE Metadata Regulation, 03/12/2008, COMMISSIONREGULATION (EC) No 1205/2008 of 3 December 2008 implementing
Directive 2007/2/EC of the European Parliament and of the Council as
regards metadata, http://eurlex.europa.eu/LexUriServ/LexUriServ.do?uri=CELEX:32008R1205:EN:N
OT[RD15] Corrigendum to INSPIRE Metadata Regulation 15.12.200, Corrigendum to
INSPIRE Metadata Regulation published in the Official Journal of theEuropean Union, L 328, page 83, http://eurlex.europa.eu/LexUriServ/LexUriServ.do?uri=CELEX:32008R1205R%28
02%29:EN:NOT[RD16] ISO 19115-2:2009 - Geographic information -- Metadata -- Part 2:
Extensions for imagery and gridded data
[RD17] ISO 19139-2, Geographic Information – Metadata – XML Schema
Implementation – Part 2: Extensions for imagery and gridded data –DRAFT[RD18] OGC 11-043 DRAFT, Sensor Model Language 2.0 Extensions for Earth
Observation Instruments and Platforms, Version: 1.0.0, 2011-04-15[RD19] OGC 08-167 Semantic Annotation of OGC standards, Version 2.1 201107-27[RD20] OGC 10-157 Earth Observation Metadata profile of Observations &Measurements, Version 1.0.0, 2011-06-02

Copyright © 2013 Open Geospatial Consortium

3

OGC 11-035

3

Terms and definitions

datasetidentifiable collection of data (ISO19115)
dataset series
collection of datasets sharing the same product specification (ISO19115)
EO product collection
An EO product collection is equivalent to a dataset series as defined within the ISO
19XXX series of standards. It is a collection of datasets sharing the same productspecification.
In the Earth Observation context, a collection typically corresponds to datasets (i.e.
products) derived from data acquired by a single sensor onboard a satellite or seriesof satellites and having the same operation mode. Examples of EO ProductCollections are “TerraSAR-X spotlight mode ” or “ESA ENVISAT MERIS Full
Resolution L1+2”
EO Service
Web Service that operates on the above mentioned EO product collections.
Examples of such services include catalogue services that allow discovery of EO
data products, EO Product Collections, EO Sensors and EO Services, EO Feasibility
Analysis services, EO Ordering services, on-line EO data access services and EO
Web Map Services.
interface
named set of operations that characterize the behaviour of an entity (ISO19119)
metadata
data about data (ISO19115)
metadata element
discrete unit of metadata (ISO19115)
metadata entity
set of metadata elements describing the same aspect of data (ISO19115)
model
abstraction of some aspects of a universe of discourse (ISO19115)
operation
specification of a transformation or query that an object may be called to execute(ISO19119)
resource
asset or means that fulfils a requirement (ISO19115)

4

Copyright © 2013 Open Geospatial Consortium

OGC 11-035r1

servicedistinct part of the functionality that is provided by an entity through interfaces([ISO/IEC TR 14252])
service interface
shared boundary between an automated system or human being and anotherautomated system or human being [ISO 19101]
4

Conventions

4.1

Abbreviated terms

AP

Application Profile

CIM

Cataloguing of ISO Metadata

CSW

Catalogue Services for the Web

DLR

Deutsches Zentrum für Luft- und Raumfahrt

ebRIM

eBusiness Registry Information Model

EO

Earth Observation

ESA

European Space Agency

HMA

Heterogeneous Missions Accessibility

INSPIRE

Infrastructure for Spatial Information in Europe

ISO

International Organisation for Standardisation

OGC

Open Geospatial Consortium

TBC

To Be Confirmed

TBD

To Be Defined

UML

Unified Modelling LanguageXMLeXtensible Markup Language

4.2

UML notation

Most diagrams that appear in this standard are presented using the Unified
Modeling Language (UML) static structure diagram, as described in Subclause 5.2of [OGC 06-121r3].
5

Introduction

During the Heterogeneous Missions Accessibility (HMA) series of Projects
managed by the European Space Agency (ESA), the HMA stakeholders defined aminimal set of metadata elements that are required to describe a Collection of Earth
Observation Products.

Copyright © 2013 Open Geospatial Consortium

5OGC 11-035

This EO Production Collection metadata information model was based on the ISO
19115 metadata model which was adapted for use in the EO/HMA Context in thefollowing manner:
It was constrained by making some optional ISO1915 elements mandatory(e.g. fileIdentifier)
It was constrained by fixing the values for some elements (e.g.
hierarchyLevel fixed to series).
In addition some additional metadata elements were defined that were notcovered in ISO19115. The names of some of these elements were takenfrom the ISO19115/Part 2 Draft version available at that time without
however adopting the full ISO19115-Part 2 information model.

6

Copyright © 2013 Open Geospatial Consortium

OGC 11-035r1

6

Metadata models

6.1

EO Product Collection minimal information model

6.1.1

EO Product Collection information model

The following simplified UML class diagram shows the metadata elements thatare minimally required for describing EO Product Collections. Other elements
as permitted by ISO19115 may be added to obtain a more complete description:

Figure 1 EO Product Collection metadata (Simplified UML class diagram – using ISO19115
elements only – not all dataTypes/codelists included)

The following tables constitute the data dictionary. It only lists the mandated
metadata elements with the changes and additional constraints with respect toISO19115 indicated in Bold.
The contents of the INSPIRE column indicates whether this is one of themetadata elements mandated by INSPIRE and gives the INSPIRE Metadata
Element name as well as the reference to the paragraph of the Implementing
Rule.
Name / Role
name

Definition

Copyright © 2013 Open Geospatial Consortium

Obligation/
Condition

Maximum
occurrence

DomainINSPIRE

7

OGC 11-035
MI_Metadata
fileIdentifier

root entity which defines
metadata about aresource or resources
unique identifier for thismetadata file

M

1

M

1

Followinglines inthis table
Free text

Clarification for EO ProductCollection metadata:
This fileiIdentifier is equal tothe identifier of the EO ProductCollection
language

language used for
documenting metadataM

1

ISO 639-2,
other parts
may be usedcharacterSet

full name of the character
coding standard used for the
metadata set

M

1

MD_Character
SetCode<<CodeList>>hierarchyLevel

scope to which the metadata
applies.

M

1

Fixed value“series”

hierarchyLevel
Namename of the hierarchy level forwhich the metadata isprovided.

M

1

Fixed value“EO ProductCollection”

contact

party responsible for the EO
Product Collection

M

1

CI_Responsibl
eParty<<DataType>>

dateStamp

date that the metadata wascreated

M

1

Date

Metadata
language
Part B
10.3

Part B1.3
Resourc e
Type

Metadata
point ofcontact
Part B
10.1
Metadata
date
Part
B10.2

metadataStand
ardNamename of the metadata
standard (including
profile name) used

M

1

Fixed value of
OGC 11-035

metadataStand
ardVersion

version of the metadata
standard(version of the profile) usedM

1

Free text

Role name:identificationInfobasic information about theresource(s) to which the metadata
appliesM

1

MD_DataIdent
ification

Role name:contentInfo

describes the coverage andimage data characteristics

O

1

MD_ContentIn
formation<<Abstract>>
MD_Coverage
Description

Role namedataQualityInfo

provides an overall assessment ofquality of a
resource (s)M1

DQ_DataQuality

RequiredforLineage - B
6.1

Table 1 Metadata entity set information (EO Product Collection Mandatory elements only)

8

Name / Role
name

Definition

Obligation/
Condition

Maximum
occurrence

CI_Responsible
Party

identification of, and means ofcommunication with,person(s) and organizations
associated with the dataset

M

1

DomainINSPIRE

Copyright © 2013 Open Geospatial Consortium

OGC 11-035r1
individualName

name of the responsible
person- surname,given name, title separated by adelimiter

M

1

Free text

organisationNa
mename of the responsibleorganization

M

1

Free text

positionNamerole or position of the
responsible person

M

1Free Text

contactInfo

contactInfo

M

1

CI_Contact<<DataType>>

Role

function performed by the
responsible party

M

1

CI_RoleCode<<CodeList>>
INSPIRE
schematron rules
mandatespointOfContact

Responsi
ble Party
RolePart B
9.2

Table 2 CI_ResponsibleParty (EO Product Collection Mandatory elements only)
Definition

Obligation/
Condition

Maximum
occurrence

Domaincitation data for theresource(s)M

1

CI_Citation<<D
ataType>>brief narrative
summary ofthe
content of theresource(s)language(s) used within
thedataset

M

1

Free text

Part B1.2
Resource
Abstract

MN

identification of, andmeansof communication
with, person(s)andorganization(s)associated with theresource(s)MN

ISO 6392,other parts
may be used
CI_Responsible
Party<<DataTy
pe>>Part B 1.7
Resource
Language
Responsib
le Party

Role name:graphicOverview

Reference to an image that
illustrates the EO ProductCollection.

M

N

MD_BrowseGr
aphic

Role name:provides information
aboutconstraints whichapply tothe resource(s)M1

MD_ConstraintsRequiredfor Part
B.8.2 and
B.8.1

provides category
keywords,theirtype, and reference
sourceM

N

MD_Keywords

Requiredfor Parts B
3.1 and
B.3.2

Name / Role
name
MD_Identification
citation
abstract

languagepointOfContact

resourceConstraints
Role name:descriptiveKeywor
ds1

INSPIREPart B.9.1
andResponsib
le Party
Role
Part B 9.2

1 compositeType is stored in ISO19115 using Keywords of Type Temporal that identifies a identifies a time
period related to the dataset

Copyright © 2013 Open Geospatial Consortium

9

OGC 11-035
full name of thecharactercoding
standard used for thedatasetmain theme(s) of thedatasetM

1

MD_CharacterS
etCode<<CodeList>>

M

N

Fixedvalue isimageryBase
MapsEarthCoVerspatialRepresenta
tionType

method used to spatiallyrepresent geographic
informationM

1

spatialResolution

factor which provides a
general understandingof the density of spatial data inthe dataset

M

1

MD_SpatialR
epresentationTypeCodeLi
stDefault value
is grid
MD_Resoluti
onextentextent information including
the bounding box,
bounding polygon, vertical,
and temporalextentM

1characterSet

topicCategory

EX_Extent

Part B2.1
Topic
category

SpatialResolution(Part B
6.2)
Requiredfor
GeographicBounding
Box Part
B4.1) And
Temporal
Extent(Part
B.5.1)
Minimally
1 temporal
propertyneeds tobeprovided.

Table 3 DataIdentification Information (EO Product Collection Mandatory elements only)
Name / Role
name

Definition

CI_Citation

standardized resource
referencereference date for the citedresource

date

Obligation/
Condition

Maximum
occurrence

DomainINSPIREM

N

CI_DateDate ofpublication (Part B
5.2)

Both creation and revisiondates should be included

Date oflast
revision(Part B
5.3)
Date ofcreation(Part B
5.4)

title

10

Name by which the citedresource is known

M

1

Free Text

Part B1.1
Resourc
e titleCopyright © 2013 Open Geospatial Consortium

OGC 11-035r1
identifier

value uniquely identifying an
object within anamespaceM

1

MD_Identifier

Part B1.5
UniqueResource
Identifier

DomainINSPIRE

Table 4 CI_Citation (EO Product Collection Mandatory elements only)
Name / Role
Name

Definition

Obligation/
Condition

Maximum
occurrence

CI_Datereference date and event used
to describe it

datereference date for the citedresourceUse
obligation/c
onditionfromreferencing
objectM

Usemaximum
occurrence
fromreferencing
object1

dateType

event used for reference date

M

1

CI_Citation<<DataType>>
CI_DateType
Code<<CodeList>>
Creation,
revision andpublication

Table 5 CI_Date (EO Product Collection Mandatory elements only)
Name / Role
Name

Definition

MD_Resolution

level of detail expressed as aground distanceground sample distancedistance

Obligation/
Condition

Maximum
occurrence

DomainM

1

Distance(ISO/TS
19103)INSPIRE

Table 6 MD_resolution (EO Product Collection Mandatory elements only)

Name / Role
Name

Definition

Obligation/
Condition

Maximum
occurrence

MD_Keywords2

keywords, their type andreference sourceUseobligationfromreferencing
objectkeyword3

commonly used word(s) orformalised word(s)or phrase(s) used to describe thesubject
For INSPIRE the use of one
keyword expressing the
INSPIRE Data theme isrequired. Relevant INSPIRE
data themes concerning EO
Product collections are “Landcover” and “Orthoimagery”

M

Use
maximum
occurrence
fromreferencing
objectN

DomainINSPIREFree Text

Part B
3.1

2 See INSPIRE metadata technical guidance for description on how to use the descriptive keywords to encode
the INSPIRE data theme.

Copyright © 2013 Open Geospatial Consortium

11

OGC 11-035
typesubject matter used to groupsimilar keywordsO1

thesaurusName

name of the formally registeredthesaurus or asimilar authoritative source of
keywords

O

1

MD_Keyword
TypeCode<<CodeList>>
CI_Citation<<DataType>>Part B
3.2

Table 7 MD_Keywords
Name / Role
Name

Definition

Obligation/
Condition

Maximum
occurrence

DQ_DataQualityquality information for the data
specified by adata quality scopeUseobligationfromreferencing
objectScope

the specific data to which thedata quality
information applies

M

Use
maximum
occurrence
fromreferencing
object1

DQ_Scope

Role name:
Reportquantitative quality information
for the data
specified by the scope
non-quantitative quality
information about thelineage of the data specified by the
scope

M

1

DQ_Element

M1

LI_Lineage

DomainINSPIRE

DQ_Result

Requiredfor Part
B7.1/B7.
2

DomainINSPIRE

Role name:lineage

DomainINSPIRE

Requiredfor Part B
7.1/B 7.2
Requiredfor Part B
6.1

Table 8 DQ_DataQuality
Name / Role
Name

Definition

Obligation/
Condition

Maximum
occurrence

DQ_Element

aspect of quantitative quality
informationUse
obligationfromreferencing
objectResultvalue (or set of values)
obtained from applying
a data quality measure or theoutcome ofevaluating the obtained value(or set ofvalues) against a specified
acceptableconformance quality levelM

Usemaximum
occurrence
fromreferencing
objectN

Table 9 DQ_Element
Name / Role
Name

Definition

Obligation/
Condition

Maximum
occurrence

DQ_Resultgeneralization of more specificresult classes

Use
obligationfromreferencing
objectUsemaximum
occurrence
fromreferencing
object3 See [RD19] for best practice proposal for using Semantic Annotation in ISO19115 Metadata

12

Copyright © 2013 Open Geospatial Consortium

OGC 11-035r1
DQ_Conforman
ceResult

Information about the outcomeof evaluating
the obtained value (or set ofvalues) against a
specified acceptableconformance quality
level

Use
obligationfromreferencing
objectUsemaximum
occurrence
fromreferencing
objectspecification

citation of product specificationor userrequirement against whichdata is being
evaluated
explanation of the meaning ofconformancefor this result
indication of the conformance
result where 0 =fail and 1 = pass

M

1

CI_Citation

M

1

Free Text

M

1

true/false (asper INSPIRE
ISO19139
instead ofISO19115 0,1)

Part B
7.2

DomainINSPIREPart B
6.1

explanation
Pass

Part B
7.1

Table 10 DQ_Result
Name / Role
Name

Definition

Obligation/
Condition

Maximum
occurrence

LI_Lineage

information about the events orsource data
used in constructing the data
specified by thescope or lack of knowledge
about lineage
general explanation of the data
producer’s
knowledge about the lineage of adatasetinformation about an event ortransformation in the life of adataset including the process used
to maintain the d atasetUseobligationfromreferencing
objectUsemaximum
occurrence
fromreferencing
objectM

1

Free Text

C asstatement isprovided

NFree Text

DomainINSPIREFree Text

Condition
applying
to accessand usePart B
8.1

statement

LI_ProcessStep.de
scription

Table 11 LI_Lineage
Name / Role
name

Definition

Obligation/
Condition

Maximum
occurrence

MD_Constraints

restrictions on the access anduse of a
resource or metadataUseobligationfromreferencing
objectUsemaximum
occurrence
fromreferencing
ObjectuseLimitation

limitation affecting the fitness
for use of theresource or metadata.
Example, “not to be
used for navigation”

M

1

MD_LegalConst
Raintsrestrictions and legal
prerequisites for accessing
and using the resource ormetadataUseobligationfromreferencing
objectN

Copyright © 2013 Open Geospatial Consortium

13

OGC 11-035
accessConstrai
ntsotherConstraintsaccess constraints applied toassure theprotection of privacy orintellectual property,
and any special restrictions orlimitations on
obtaining the resource ormetadata
other restrictions and legal
prerequisites for accessing
and using theresource or metadata

MD_SecurityCo
Nstraints

or metadata for national
security or similar
security concerns

Classification

name of the handling
restrictions on the
resource or metadata

M

1

MD_Restrictio
nCode<<CodeList>>

Limitatio
ns onpublicaccessPart B
8.2

C/
accessCon
straints
equal“otherRestri
ctions”?
Useobligationfromreferencing
objectN

Free Text

Limitatio
ns onpublicaccessPart B
8.2

M

1

MD_Classifica
tionCode<<CodeList>>

Limitatio
ns onpublicaccessPart B
8.2

Use
maximum
occurrence
fromreferencing
objectTable 12 MD_Constraints/LegalConstraints

6.1.2

Non ISO 19115 elements for eo product collection discovery

In addition to the ISO19115 subset described above, [RD08] also defined a set of
metadata elements for EO Product Collection Discovery that could not be directly
mapped on ISO19115. That information can be described in other metadata
documents, like a sensorML XML file. ISO19115:2003 does not have a generic
metadata element to provide additional documentation, but define a rather precise
structure of metadata elements with well-defined semantic.
To represent the platform and instrument identifiers and allow linking tosensorML description, it is required to use some extensions from ISO19115-2
metadata model. The sensorML document will be based on the Annex A of
[RD04] which describes the profile of sensorML for Earth Observation domain.

14

Copyright © 2013 Open Geospatial Consortium

OGC 11-035r1
class Fig A.8 - Acquisition Ov erv iew
Metadata Entity Set - Imagery::
MI_Metadata
Acquisition information - Imagery::MI_Platform++++

citation: CI_Citation [0..*]identifier: MD_Identifier
description: CharacterString
sponsor: CI_ResponsibleParty [0..*]+platform

0..*+acquisitionInformation0..*
Acquisition information - Imagery::
MI_AcquisitionInformation+instrument

0..*

Acquisition information - Imagery::
MI_Instrument++++

citation: CI_Citation [0..*]identifier: MD_Identifier
type: CharacterString
description: CharacterString [0..1]

Figure 2 EO Product Collection metadata (Simplified UML class diagram –using ISO19115 -2 extension for Platform & Instrument elements only)

PropertyName

Proposed
Cardinality

Description

Copyright © 2013 Open Geospatial Consortium

Potential mappingon ISO19115

Potential
mapping on ISO
19115-2

SensorML
extensions for EO
instruments
and platforms
Mapping

15

OGC 11-035
platformShortName

1

Platform shortname (ex. PHR)

MI_Metadata.acq
uisitionInformation>
MI_AcquisitionInf
ormation.platform> MI_Platform.identi
fier
MD_Identifier.cod e

platformSerialIdentifier

0..1

Platform serial
identifier (ex. for
PHR : 1A)

instrumentShortName4

1

Instrument /Sensor nameTo be combinedwith Shortname intheaforementioned
code element
MI_Metadata.acq
uisistionInformation>MI_AcquisitionInf
ormation.instrument >MI_Instrument.ide
ntifier >MD_Identifier.codeacquiredBy/Sensor/sensorType1Sensor type. This
field should
contain an
enumeration(“optical”, “radar”,“altimetric”,“atmospheric”)

MI_Metadata.acq
uisitionInformation>
MI_AcquisitionInf
ormation.instrume nt> MI_Instrument.typeunique identifierof the platform
which is specified
via the“gml:identifier”
propertyof the SensorML
System in theform of a URI.
TBD if theidentifier or thecorresponding
shortnameproperty is used
for making thelink.
To be combinedwith Shortname intheaforementioned
code element?
Gml :identifier
property of theSensorML
System which is
specified in theform of a URI.

OGCEO/0/SensorType

The most relevant observations are:
The distinction that is made between the platformShortName andplatformSerialIdentifier does not map well on ISO19115-2 and SensorML.
Both properties should be combined to obtain a unique identification of aplatform instanceFor cross-model linkage it is better to use identifiers than shortnames for
identifying platforms and instruments
In Earth Observation domain, an Instrument can be configured with specificparameters. It can be seen as a customization of a generic Instrument for a
specific usage. In SensorML, this is described as a specific System (called
Instrument Mode) referencing the generic Instrument ID.
<sml:SensorML

4 In ISO 19115-2, only Platform and Instrument properties exist to reference external document.

16

Copyright © 2013 Open Geospatial Consortium

OGC 11-035r1
xmlns:sml="http://www.opengis.net/sensorML/1.0.1"
xmlns:swe="http://www.opengis.net/swe/1.0.1"
xmlns:gml="http://www.opengis.net/gml"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xlink="http://www.w3.org/1999/xlink"
xsi:schemaLocation="http://www.opengis.net/sensorML/1.0.1../OGC/sensorML/sensorML.xsd" version="1.0.1"><!-- --><sml:member
xlink:role="urn:ogc:def:dictionary:CEOS:documentRoles:v01#instrument_configur
ation"><!-- --><sml:System gml:id="SPOT5_HRG_PA-XS"><!-- ================================================= --><!-System Description--><!-- ================================================= --><gml:description>
The PA+XS mode is used to acquire 5m resolution multispectral
images by pan sharpening
the 10m resolution multispectral data with the 5m resolution
panchromatic data.
</gml:description><!-- ================================================= --><!-System Identifiers--><!-- ================================================= --><sml:identification><sml:IdentifierList><sml:identifier name="Configuration UID"><sml:Termdefinition="urn:ogc:def:property:CEOS:eop:InstrumentMode"><sml:value>urn:ogc:id:CEOS:instrument:SPOT5:HRG:PA+XS:v01</sml:value></sml:Term></sml:identifier><sml:identifier name="Instrument UID"><sml:Termdefinition="urn:ogc:def:property:CEOS:eop:InstrumentID"><sml:value>urn:ogc:id:CEOS:instrument:SPOT5:HRG1:v01</sml:value></sml:Term></sml:identifier><sml:identifier name="Short Name"><sml:Term definition="urn:ogc:def:property:OGC:shortName"><sml:value>SPOT5 HRG Mode PA+XS</sml:value></sml:Term></sml:identifier></sml:IdentifierList></sml:identification>

The processing information could potentially be added in an unstructured
manner within a single descriptive field LI_ProcessStep.description of
ISO19115. The ISO19115-Part 2 provided LE_ProcessStep provides
additional fields to better structure the processing information
6.2

EO Services minimal information model

During the Heterogeneous Missions Accessibility Project series of ESA, the
HMA stakeholders also defined the minimal set of metadata elements that are
required to describe the different Web Service Instances that are being
deployed throughout the Ground Segments of the GMES Contributing
Missions.
These Web Services include Catalogue Services for discovery of EO Products, EO
Copyright © 2013 Open Geospatial Consortium

17

OGC 11-035

Product Collections and EO Services, Ordering Services, Feasibility Analysis,
Web Map Services and Web Coverage Services.
The information model employed was based on the ISO 19119 metadata model
which was adapted for use in the EO Context in the following manner:a number of optional elements are not included in this minimum element
set. These elements mainly relate to the chaining of operations and theparameters that are associated with the operations.
a number of optional elements have been declared mandatory.
It is to note that the original document defined a set of minimal elements
required for EO Service discovery hereby not excluding the use of additional
optional ISO19119 metadata elements for obtaining a more complete
description of EO Services.
The information model proposed in this section started from the information model
proposed in OGC07-025 but applies the following changes:
Using the latest corrigenda: ISO 19119:2005, Amendment 1 [RD13].
With the adoption of the INSPIRE Directive and the INSPIRE Metadata
Implementing Rules, it is desirable for EO Services metadata to contain all
the minimal information elements required by the INSPIRE Metadata
Implementing Rule and following the INSPIRE technical guidelines. The
Elements mandated by INSPIRE have been added to the minimal set ofISO19119 elements.
Minor corrections to elements occurring in the original table.
6.2.1

EO Services information model

The following simplified UML class diagram shows the minimal elementsthat are required for describing EO Product Collections. Other elements aspermitted by ISO19119 may be added to obtain a more complete description:

18

Copyright © 2013 Open Geospatial Consortium

OGC 11-035r1

Figure 2 EO Services Minimal Information Model

The following tables constitute the data dictionary. The tables are based on
the corresponding ISO19115/19119 tables with changes/additional constraints
with respect to ISO19119 are highlighted in Bold.
The contents of the INSPIRE column indicates whether this is one of themetadata elements mandated by INSPIRE and gives the INSPIRE Metadata
Element name as well as the reference to the paragraph of the Implementing
Rule.
Name / Role
Name

Definition

Obligation/
Condition

Maximum
occurrence

DomainMD_Metadata

root entity which defines
metadata about aresource or resources
unique identifier for thismetadata file

M

1

M

1

Followinglines in thistable
Free text

language

language used for
documenting metadataM

1

ISO 639-2,
other parts
may be used

Metadata
language
Part B
10.3

hierarchyLevel

scope to which the metadata
applies.

M

1

Fixed value“service”

Part B1.3

name of the hierarchy level forwhich the metadata is provided.

M

fileIdentifier

hierarchyLevel
Name

Copyright © 2013 Open Geospatial Consortium

1

INSPIRE

Resource TypeFixed value“EO Service”

19

OGC 11-035
contact

party responsible for the EO
ServiceM

1

CI_Responsibl
eParty<<DataType>>

dateStamp

date that the metadata wascreated

M

1

Date

Metadata
point ofcontact
Part B
10.1
Metadata
date
Part
B10.2

metadataStand1
ardNamename of the metadata
standard (including
profile name) used

M

1

Fixed value of
OGC 11-035

metadataStand
ardVersion

version of the metadata
standard(version of the profile) usedM

1

Free text

Role name:identificationInfobasic information about theresource(s) towhich the metadata applies

M

1

SV_ServiceId
entificationRole namedataQualityInfo

provides overall assessment ofquality of a resource(s)M

N

DQ_DataQuality

RequiredforLineage - B
6.1

Table 13 Metadata entity set information (EO Services Mandatory elements only)
Name / Role
Name

Definition

Obligation/
Condition

Maximum
occurrence

CI_Responsible
Party

identification of, and means ofcommunication with,person(s) andorganizations associatedwith the dataset
name of the responsible
person- surname,given name, title separated by adelimiter

M

1

M

1

Free text

organisationNa
mename of the responsibleorganization

M

1

Free text

positionNamerole or position of the
responsible person

M

1Free Text

contactInfo

contactInfo

M

1

CI_Contact<<DataType>>

Role

function performed by the
responsible party

M

1

CI_RoleCode<<CodeList>>

individualName

DomainINSPIRE

Responsi
ble Party
RolePart B
9.2

Table 14 CI_ResponsibleParty (EO Services Collection Mandatory elements only)
Name / RoleName
MD_Identification
Citation
abstract

20

Definition

Obligation/
Condition

Maximum
occurrence

Domaincitation data for the
resource(s)M1brief narrative summary of
the content of the resource(s)M

1

CI_Citation<<DataType>>
Free text

INSPIREPart B1.2
Resource
Abstract

Copyright © 2013 Open Geospatial Consortium

OGC 11-035r1
pointOfContact

identification of, and meansof communication
with, person(s) andorganization(s) associatedwith the resource(s)

M

M

N

resourceConstrain ts

provides information about
constraints which
apply to the resource(s)MD_Constrai
nts

Role name:descriptiveKeywor
dsprovides category keywords,
their type, andreference source

M

N

MD_Keywords

Extentthe geographic/temporal
region where the service isvalid. including the boundingbox, bounding polygon,
vertical, or temporal extent
of the service

C/ if
couplingT
ype equals“mixed” or"tight"1

EX_Extent

accessProperties

Information about theavailability of theservice, including,- Fees- Planned available date andtime- Ordering instructions- Turnaround
Legal and security
constraints on accessing theservice and distributing
data generated by
the service.
A service type name from a
registry ofservices. For example, thevalues of the
nameSpace and nameattributes ofGeneralName may be "OGC "and"catalogue."
Provides for searchingbased on the version ofserviceType. For
example, we may only
be interested in OGC
Catalogue V1.1
services. If version is
maintained as aseparate attribute, users caneasily search for
all services of a typeregardless of theversion.
further description of thedata coupling in the case oftightly coupled services

O

1

MD_StandardOrderProce
ss

O

1

MD_Constrai
nts

M

1

GenericName

O

NFree TextON

SV_CoupledResourceRole name:restrictions

serviceTypeserviceTypeVersioncoupledResource

Copyright © 2013 Open Geospatial Consortium

1

CI_Responsi
bleParty<<DataType>>

Responsib
le Party
Part B.9.1
andResponsib
le Party
Role
Part B 9.2
Requiredfor Part
B.8.2 and
B.8.1
Requiredfor Parts B
3.1 and
B.3.2
Requiredfor
GeographicBounding
Box Part
B4.1)
And
Temopral
Extent(Part
B.5.1)
Optional
for
Services

Spatialdata
service
typePart B 2.2

21

OGC 11-035
couplingType

type of coupling between
service and associated data
(if exists)M

1

SV_CouplingType

Role name:containsOperations

Provides information about
the operations
that comprise the service

M

N

SV_Operatio
nMetadata

Role name:operatesOn

Provides information on thedatasets that theservice operates on

O

N

MD_DataIde
ntification<<CodeList>>

CoupledResource
Part B 1.6
Implement
ed byReference

Table 15 ServiceIdentification Information
Name / Role
Name

Definition

Obligation/
Condition

Maximum
occurrence

DomainSV_CoupledReso
urcefurther description of the data
coupling in the case of tightly
coupled services

operationName

name of the service
operation

M

1

Free Text

identifier

name of the identifier of agiven tightly coupled dataset

M

1

Free Text

scopedName

e.g. the name of the layer in the
WMS or the featureTypeNameof the WFS

M

1

Free text

Obligation/
Condition

Maximum
occurrence

DomainINSPIRE

Table 16 SV_CoupledResource
Name / Role
Name

Definition

SV_OperationMet
adata

describes the signature of one
and only one method provided
by the service.

operationName

name of the service
operation

M

1

Free Text

DCP

Distributed Computing
Platforms on which

M

N

DCPListM

1

Free Text

M

N

CI_OnlineResourceObligation/
Condition

Maximum
occurrence

DomainoperationDescription

connectPoint

the operation has been
implemented
Free text description of theintent of theoperation and the results of
the operation.
Handle for accessing theservice interface

INSPIRE

Table 17 SV_OperationMetadata
Name / Role
Name

22

Definition

INSPIRE

Copyright © 2013 Open Geospatial Consortium

OGC 11-035r1
MDStandardORderProcess

describes the signature of
one and only one method
provided by the service.

Fees

fees and terms for retrieving
the resource.
Include monetary units

M

1

Free Text

orderingInstructions

general instructions, terms
and services

01Free Text

Obligation/
Condition

Maximum
occurrence

DomainO

1

CI_Citation

M

1

Free Text

Obligation/
Condition

Maximum
occurrence

DomainINSPIREM

N

CI_DateDate ofpublication (Part B
5.2)

provided by the distributor

Table 18 MD_StandardOrderProcess

Name / Role
Name

Definition

MDIdentifier

value uniquely identifying an
object within anamespaceperson or party responsible
for maintenanceof the namespaceauthority

Codealphanumeric value
identifying an instance inthe namespace

Name / Role
Name

Definition

CI_Citation

standardized resource
referencereference date for the citedresource

Date

Both creation and revisiondates should be included

INSPIRE

Date oflast
revision(Part B
5.3)
Date ofcreation(Part B
5.4)

title

Name by which the citedresource is known

M

1

Free Text

identifier

value uniquely identifying an
object within anamespaceM

1

MD_Identifier

Obligation/
Condition

Maximum
occurrence

DomainPart B1.1
Resourc
e titlePart B1.5
UniqueResource
Identifier

Table 19 CI_Citation
Name / Role
Name

Definition

Copyright © 2013 Open Geospatial Consortium

INSPIRE

23

OGC 11-035
CI_Datereference date and event used
to describe it

Datereference date for the citedresource

dateTypeUseobligation/c
onditionfromreferencing
objectM

Usemaximum
occurrence
fromreferencing
object1

event used for reference date

M

1

CI_DateType
Code<<CodeList>>
Creation,
revision andpublication

Name / Role
Name

Definition

Obligation/
Condition

Maximum
occurrence

DomainINSPIRE

MD_Keywords5

keywords, their type andreference sourceUseobligationfromreferencing
objectkeyword6

commonly used word(s) orformalised word(s)or phrase(s) used to describe thesubjectM

Usemaximum
occurrence
fromreferencing
objectN

Free Text

Part B
3.1

Type

subject matter used to groupsimilar keywordsO1

thesaurusName

name of the formally registeredthesaurus or asimilar authoritative source of
keywords

O

1

MD_Keyword
TypeCode<<CodeList>>
CI_Citation<<DataType>>

CI_Citation<<DataType>>

Table 20 CI_Date

Part B
3.2

Table 21 MD_Keywords

Name / Role
Name

Definition

Obligation/
Condition

Maximum
occurrence

MD_Constraints

restrictions on the access anduse of a
resource or metadataUseobligationfromreferencing
objectUsemaximum
occurrence
fromreferencing
ObjectuseLimitation

limitation affecting the fitness
for use of theresource or metadata.
Example, “not to be
used for navigation”

M

1

DomainINSPIREFree Text

Condition
applying
to accessand usePart B
8.1

5 One of the keywords used should indicate the spatial data service type
6 See [RD19] for best practice proposal for using Semantic Annotation in ISO19115 Metadata

24

Copyright © 2013 Open Geospatial Consortium

OGC 11-035r1
MD_LegalConst
Raintsrestrictions and legal
prerequisites for accessing
and using the resource ormetadataUseobligationfromreferencing
objectN

accessConstrai
nts

access constraints applied toassure theprotection of privacy orintellectual property,
and any special restrictions orlimitations on
obtaining the resource ormetadata
Other restrictions and legal
prerequisites for accessing
and using the resource ormetadata

M

1

MD_Restrictio
nCode<<CodeList>>

Limitatio
ns onpublicaccessPart B
8.2

C/
accessCon
straints equal“otherRestri
ctions”?

N

Free Text

MD_SecurityCo
nstraints

or metadata for national
security or similar
security concerns

Useobligationfromreferencing
objectUsemaximum
occurrence
fromreferencing
objectLimitatio
ns onpublicaccessPart B
8.2

classification

name of the handling
restrictions on the
resource or metadata

M

1

MD_Classifica
tionCode<<CodeList>>

Limitatio
ns onpublicaccessPart B
8.2

otherConstraints

Table 22 MD_Constraints/LegalConstraints

6.2.2

INSPIRE mapping notes

The table in section Error! Reference source not found. includes mapping
notes for EO Services.
6.3

SensorML minimal information model

6.3.1

SensorML Discovery Profile

The SensorML data model specifies a majority of its elements as optional. It allows
expressing the same information in several, differently structured ways. This open
and flexible structure was one of the main aims of the SensorML design in order tomake it possible to apply the data model to nearly any type of sensor. For ensuringthat SensorML documents which are intended for discovery purposes can bereliably handled by automatic harvesting mechanisms, it is necessary to create aprofile for SensorML that define the information which shall be contained in a
SensorML document as well as the structure in which the metadata shall be
encoded. This profile called Discovery Profile of SensorML is currently specified in
the OGC document 09-163r2, SensorML Extension Package for ebRIM.
To constrain the flexibility of the SensorML data model, a set of Schematron rules
have been defined. These rules check that the mandatory information are present in
an instance of SensorML (System or Component).
The list of properties of which the presence is verified is:

Copyright © 2013 Open Geospatial Consortium

25

OGC 11-035-

gml:description-

keywords-

Identificationo urn:ogc:def:identifier:OGC:1.0:uniqueIDo urn:ogc:def:identifier:OGC:1.0:longNameo urn:ogc:def:identifier:OGC:1.0:shortNameo parentSystemUniqueID-

Classificationo intendedApplication [urn:ogc:def:classifier:OGC:1.0:application]o sensorType [urn:ogc:def:classifier:OGC:1.0:sensorType]-validTime-

Capabilities
o observedBBOX-

contact-

position-

Inputs-

Outputs-

Components

The most important elements are the uniqueID and the shortName, as they are used
to make the link between the different entities involved (EO Series, sensors, EO
Product).
7

Discovery strategy in EO Community

7.1

EO Community Metadata model

As seen before, there are various data models that are used in order to describe
components of EO product acquisition systems. Figure 3 tries to illustrate in a
simplified sketch the major EO data models (left-hand side) and what they describe(right-hand side).

26

Copyright © 2013 Open Geospatial Consortium

OGC 11-035r1

Figure 3 : EO Data Models and what they describe

7.1.1

Link between EO product metadata and the acquiring sensor

Each EO Product described using the Earth Observation Metadata profile ofObservations & Measurements [RD20] contains an EarthObservationEquipment
section grouping information about the platform, instrument and sensor used to
produce this EO product. SensorML defines all the information about platform,
instrument and sensor. So there clearly is a conceptual relationship between EO
Product and Sensors. But with the current metadata model, there is currently no
definition on how to express this linkage between an EO Product (EO GML) and a
SensorML.
A snippet of the eop:EarthObservationEquipment of an EO Product taken by the
SPOT-4 platform using the instrument HRVIR-Nb2 is given here:<eop:EarthObservationEquipment><eop:platform><eop:Platform><eop:shortName>SPOT</eop:shortName><eop:serialIdentifier>4</eop:serialIdentifier><eop:orbitType>LEO</eop:orbitType></eop:Platform></eop:platform><eop:instrument><eop:Instrument><eop:shortName>HRVIR-Nb2</eop:shortName></eop:Instrument></eop:instrument><eop:sensor><eop:Sensor><eop:sensorType>OPTICAL</eop:sensorType>

Copyright © 2013 Open Geospatial Consortium

27

OGC 11-035</eop:Sensor></eop:sensor>…
<eop:EarthObservationEquipment>

A snippet of a SensorML describing the Spot 4 platform is given below. The unique
Identifier « urn:ogc:id:CEOS:platform:SPOT4:v01», the shortName« SPOT4 » and the sensor type « Satellite » in the platform codespace« urn:ogc:def:dictionary:CEOS:eop:PlatformTypes:v01» are present.
<sml:SensorML version="1.0.1"><sml:member><sml:System gml:id="SPOT4"><gml:description>…</gml:description><!-- ================================================= --><!-System Identifiers--><!-- ================================================= --><sml:identification><sml:IdentifierList><sml:identifier name="uniqueID"><sml:Term definition="urn:ogc:def:identifier:OGC:1.0:uniqueID"><sml:value>urn:ogc:id:CEOS:platform:SPOT4:v01</sml:value></sml:Term></sml:identifier><sml:identifier name="shortName"><sml:Term definition="urn:ogc:def:identifier:OGC:1.0:shortName"><sml:value>SPOT4</sml:value></sml:Term></sml:identifier>…
</sml:IdentifierList></sml:identification><!-- ================================================= --><!-System Classifiers--><!-- ================================================= --><sml:classification><sml:ClassifierList><sml:classifier name="sensorType"><sml:Term definition="urn:ogc:def:classifier:OGC:1.0:sensorType"><sml:codeSpace xlink:href="urn:ogc:def:dictionary:CEOS:eop:PlatformTypes:v01"/><sml:value>Satellite</sml:value></sml:Term></sml:classifier>…
</sml:ClassifierList></sml:classification>…
</sml:System></sml:member></sml:SensorML>

28

Copyright © 2013 Open Geospatial Consortium

OGC 11-035r1

A snippet of a SensorML instance describing the SPOT-4 HRVIR1 instrument isgiven below. The unique Identifier« urn:ogc:id:CEOS:instrument:SPOT4:HRVIR1:v01», the shortName « SPOT-4
HRVIR1» and the sensor type « Imaging Multispectral Radiometer» in the
instrument codespace « urn:ogc:def:dictionary:CEOS:eop:InstrumentTypes:v01»
are present.

<sml:SensorML version="1.0.1"><sml:member<sml:System gml:id="SPOT4_HRVIR"><!-- ================================================= --><!-System Description--><!-- ================================================= --><gml:description>…</gml:description><!-- ================================================= --><!-System Identifiers--><!-- ================================================= --><sml:identification><sml:IdentifierList><sml:identifier name="uniqueID"><sml:Term definition="urn:ogc:def:identifier:OGC:1.0:uniqueID"><sml:value>urn:ogc:id:CEOS:instrument:SPOT4:HRVIR1:v01</sml:value></sml:Term></sml:identifier><!-<sml:identifier name="Platform UID"><sml:Term definition="urn:ogc:def:property:CEOS:eop:PlatformID"><sml:value>urn:ogc:id:CEOS:platform:SPOT4:v01</sml:value></sml:Term></sml:identifier>--><sml:identifier name="shortName"><sml:Term definition="urn:ogc:def:identifier:OGC:1.0:shortName"><sml:value>SPOT-4 HRVIR1</sml:value></sml:Term></sml:identifier>…
<sml:identifier name="parentSystemUniqueID"><sml:Term definition="urn:ogc:def:identifier:OGC:1.0:parentSystemUniqueID"><sml:value>urn:ogc:id:CEOS:platform:SPOT4:v01</sml:value></sml:Term></sml:identifier></sml:IdentifierList></sml:identification><!-- ================================================= --><!-System Classifiers--><!-- ================================================= --><sml:classification><sml:ClassifierList><sml:classifier name="sensorType"><sml:Term definition="urn:ogc:def:classifier:OGC:1.0:sensorType"><sml:codeSpace xlink:href="urn:ogc:def:dictionary:CEOS:eop:InstrumentTypes:v01"/><sml:value>Imaging Multispectral Radiometer</sml:value></sml:Term></sml:classifier><sml:classifier name="intendedApplication"><sml:Term definition="urn:ogc:def:classifier:OGC:1.0:application"><sml:value>Land - Multi-purpose Imagery</sml:value>

Copyright © 2013 Open Geospatial Consortium

29

OGC 11-035</sml:Term></sml:classifier><sml:classifier name="Acquisition Method"><sml:Term definition="urn:ogc:def:property:OGC:sensorType"><sml:codeSpace
xlink:href="urn:ogc:def:dictionary:CEOS:eop:AcquisitionMethods:v01"/><sml:value>Pushbroom</sml:value></sml:Term></sml:classifier></sml:ClassifierList></sml:classification>

To express the linkage between EO Product metadata and the acquiring platform
and sensor, we need to add the unique identifier of the platform, the instrument andperhaps the detector to the EOProduct metadata. Unfortunately, in the current
version of OGC10-157 there are no elements to store these identifiers.
The long term solution is to add a new “identifier” element in the “eop:platform”,“eop:instrument” and “eop:sensor”. This solution would break backward
compatibility.
Another solution that can be realized with the current version of OGC10-157, is to
use the eop:platform:shortName and eop:instrument:shortName to make the linkage
and fill them with the appropriate SensorML shortName. Note that this means thatthe platform shortname should include the platform serial identifier.
Here is the previous EO Product snippet updated to use the same platform andinstrument short name.
<eop:EarthObservationEquipment><eop:platform><eop:Platform><eop:shortName>SPOT4</eop:shortName><eop:serialIdentifier>4</eop:serialIdentifier><eop:orbitType>LEO</eop:orbitType></eop:Platform></eop:platform><eop:instrument><eop:Instrument><eop:shortName>SPOT-4 HRVIR1</eop:shortName></eop:Instrument></eop:instrument><eop:sensor><eop:Sensor><eop:sensorType>OPTICAL</eop:sensorType></eop:Sensor></eop:sensor>…
<eop:EarthObservationEquipment>

30

Copyright © 2013 Open Geospatial Consortium

OGC 11-035r1
7.1.2

Link between EO product metadata and the metadata of the corresponding
EO Product Collection

The link between an EO Product and the corresponding dataset series is done using
the “parentIdentifier” element. The “parentIdentifier” contains the identifier(element fileIdentifier) of the dataset series.
Here is a snippet of the “parentIdentifier” of the EO Product.
<opt:EarthObservation version="1.2.1"><gml:metaDataProperty><eop:EarthObservationMetaData><eop:identifier>urn:spot:sn:19336775:sat:Shift0:eop</eop:identifier><eop:doi>urn:spot:sn:19336775:sat:Shift0:eop</eop:doi><eop:parentIdentifier> urn:ogc:def:EOP:ESA:EECF.ENVISAT_ASA_APx_xS</eop:parentIdentifier>…
</eop:EarthObservationMetaData></gml:metaDataProperty></opt:EarthObservation>

Here is a snippet of a dataset series with the same fileIdentifier:<gmd:MD_Metadata><gmd:fileIdentifier><gco:CharacterString> urn:ogc:def:EOP:ESA:EECF.ENVISAT_ASA_APx_xS</gco:CharacterString></gmd:fileIdentifier>…
</gmd:MD_Metadata>

7.1.3

Link between the EO Product Collection metadata and the sensors
information

The EO Product Collection metadata can contain a link to the sensors information.
The ISO 19115/2 defines the extension to store acquisition information.
Here is a snippet of a dataset series with the“urn:ogc:id:CEOS:platform:SPOT1:v01” platform identifier and the“urn:ogc:id:CEOS:instrument:SPOT1:HRV:v01” instrument identifier.
<gmi:MI_Metadata>…
<gmi:acquisitionInformation><gmi:MI_AcquisitionInformation><gmi:platform><gmi:MI_Platform><gmi:identifier><gmd:RS_Identifier><gmd:code><gco:CharacterString>urn:ogc:id:CEOS:platform:SPOT1:v01</gco:CharacterString></gmd:code>

Copyright © 2013 Open Geospatial Consortium

31

OGC 11-035<gmd:codeSpace><gco:CharacterString>http://spotimage.fr</gco:CharacterString></gmd:codeSpace></gmd:RS_Identifier></gmi:identifier><gmi:description><gco:CharacterString>Spot 1 platform</gco:CharacterString></gmi:description><gmi:instrument><gmi:MI_Instrument><gmi:citation><gmd:CI_Citation><gmd:title><gco:CharacterString>…</gco:CharacterString></gmd:title>…
<gmd:identifier><gmd:RS_Identifier><gmd:code><gco:CharacterString>urn:ogc:id:CEOS:instrument:SPOT1:HRV:v01</gco:CharacterString></gmd:code><gmd:codeSpace><gco:CharacterString>http://spotimage.fr</gco:CharacterString></gmd:codeSpace></gmd:RS_Identifier></gmd:identifier></gmd:CI_Citation></gmi:citation><gmi:type><gmi:MI_SensorTypeCode id="Imaging.Multispectral.Radiometer"/></gmi:type></gmi:MI_Instrument></gmi:instrument></gmi:MI_Platform></gmi:platform></gmi:MI_AcquisitionInformation></gmi:acquisitionInformation></gmi:MI_Metadata>

7.1.4

Identifier definition

The key point to be able to define a formal link between metadata of EO Products,
EO Product Collections and Sensors is to define stable, unique, coherent identifiersfor each metadata entity. These identifiers will be used to make the link between the
different metadata models. These identifier will also be used to identify and retrieve
the metadata in catalogue/registry.
7.2

Metadata cataloguing

To catalogue metadata corresponding to the three different metadata models, weneed to have a catalog solution capable of handling “any” metadata model.
The CSW ISO Application Profile (OGC 07-045) catalogue is only able to store
ISO 19115/ISO19119 Metadata i.e EO Product Collections.

32

Copyright © 2013 Open Geospatial Consortium

OGC 11-035r1

The CSW ebRIM Application Profile (OGC 07-110) catalogue is based on thegeneric ebXML model that can be profiled to store any model. These profiles arecalled extension packages. Currently there is one extension package defined foreach of the three metadata models:
OGC 06-131: EO Product Extension Package
OGC 10-189: EO Product Extension Package v2
OGC 07-038: ISO 19115/19119 Extension Package
OGC 09-163: SensorML Extension Package

-­‐
-­‐
-­‐
-­‐

Currently, there is no official document that defines the interlinkage between these
extension packages. The following section proposes some ideas to implement theselinks.
7.2.1

How to link different extension packages in a CSW ebRIM catalog

There are two ways to make a link between extension packages.
7.2.1.1

Link by association

The most obvious way to link objects (Registry Objects) in an ebRIM catalog is tocreate an Association between these objects. For instance, we can create an
SubsetOf association between an EO product and its collection.
To create this association when an EO Product is harvested the identifier of thecollection (the parentIdentifier element) needs to be extracted. Based on thecollection identifier, we query the catalog to retrieve the Registry Object
corresponding to this collection. If the Registry Object is found, the Association
between the EO Product and the Collection Registry Object can be created.
This procedure can only work if the parentIdentifier within the EO Productmetadata points to an existing collection. Hence the importance of a coherent
identifier scheme.
7.2.1.2

Link by equivalent slot

Another solution is to define equivalent slots between the different extension
packages. For instance, the EO Product Registry Object contains a slot called“parentIdentifier” which is equal to the slot “identifier” of the Collection registry
Object. A GetRecords request can search for all EO Product in the collections
matching one or several constraints (like a keyword equal to a particular value…).
An example CSW GetRecords Query searching for all EO Products within acollection where the topicCategory equals « imageryBaseMapsEarthCover » isgiven below:<?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"
version="2.0.2"
resultType="RESULTS"

Copyright © 2013 Open Geospatial Consortium

33

OGC 11-035

maxRecords="10"
outputSchema="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0"><csw:Query typeNames="RegistryPackage ExtrinsicObject__product ExtrinsicObject__collection"><csw:ElementName>/RegistryPackage</csw:ElementName><csw:Constraint version="1.0.0"><ogc:Filter><ogc:And><ogc:PropertyIsEqualTo><ogc:PropertyName>/RegistryPackage/RegistryObjectList/*/@id</ogc:PropertyName><ogc:PropertyName>/product/@id</ogc:PropertyName></ogc:PropertyIsEqualTo><ogc:PropertyIsEqualTo><ogc:PropertyName>/product/@objectType</ogc:PropertyName><ogc:Literal>urn:ogc:def:objectType:OGC-CSW-ebRIM-EO::EOProduct</ogc:Literal></ogc:PropertyIsEqualTo><ogc:PropertyIsEqualTo><ogc:PropertyName>/product/Slot[@name="urn:ogc:def:slot:OGC-CSW-ebRIMEO::parentIdentifier"]/ValueList/Value[1]</ogc:PropertyName><ogc:PropertyName>/collection/Slot[@name="urn:ogc:def:slot:OGC-CSW-ebRIMCIM::identifier"]/ValueList/Value[1]</ogc:PropertyName></ogc:PropertyIsEqualTo><ogc:PropertyIsEqualTo><ogc:PropertyName>/collection/@objectType</ogc:PropertyName><ogc:Literal>urn:ogc:def:objectType:OGC-CSW-ebRIM-CIM::DataMetadata</ogc:Literal></ogc:PropertyIsEqualTo><ogc:PropertyIsEqualTo><ogc:PropertyName>/collection/Slot[@name="urn:ogc:def:slot:OGC-CSW-ebRIMEO::topicCategory"]/ValueList/Value[1]</ogc:PropertyName><ogc:Literal>imageryBaseMapsEarthCover</ogc:Literal></ogc:PropertyIsEqualTo></ogc:And></ogc:Filter></csw:Constraint></csw:Query></csw:GetRecords>

To have a more coherent slot naming, OGC recommends using HTTP URIs
(http://www.opengis.net/def/property/OGC/). For instance the identifier of aplatform should be http://www.opengis.net/def/property/OGC-EO/0/Platform . This
slot name should be used in EO Product, Collection and Sensor RegistryObjects.
At OGC, the slot names are URI and are registered into the OGC registry of
Naming Authority. Another way of making a semantic relation between two slots is
to create a relation like a skos:exactMatch or a rdf:sameAs between two URIs.
7.2.2

Link between EO Product and EO Product Collection metadata

The link can be done by using the “parentIdentifier” slot from the EOProduct
ExtrinsicObject (EO extension Package) and the “identifier” slot of theMetadataInformation ExtrinsicObject (CIM Extension Package)
7.2.3

Link between EO Product and Sensor metata

For the platform, the link can be established using the “name” of the
EOAcquisitionPlatform ExtrinsicObject and the “shortName” slot from the System

34

Copyright © 2013 Open Geospatial Consortium

OGC 11-035r1

ExtrinsicObject describing the platform. The “name” must be identical in the 2
metadata records .
For the instrument, the link can be done between the “instrumentShortName » slot of
the EOAcquisitionPlatform ExtrinsicObject and the “shortName” slot from the
System ExtrinsicObject describing the Instrument. The “name” must be identical in
the 2 metadata records .
What concerns the detector, there is no reference to the detector in the EO Productmetadata model.
7.2.4

Link between Collection and Sensor

Currently, the ISO Extension package (CIM) does not support the ISO 19115/2
extensions. So we cannot establish the linkage with the current draft specification.
To solve this issue, the proposal is to extend the current discovery model to take
into account some part of ISO 19115/2.
For the platform, a suggestion is to extract the« gmi:MI_AcquisitionInformation/gmi:platform/gmi:MI_Platform/gmi:identifier/gm
d:RS_Identifier/gmd:code/gco:CharacterString » property in the« platformIdentifier » slot of the MetadataInformation ExtrinsicObject. Then thelink can be done with the “shortName” slot from the System ExtrinsicObject
describing the platform.
For the instrument, a suggestion is to extract the« gmi:MI_AcquisitionInformation/gmi:instrument/gmi:MI_Instrument/gmi:citation/
gmd:CI_Citation/gmd:identifier/gmd:RS_Identifier/gmd:code/gco:CharacterString» property in the « instrumentIdentifier » slot of the MetadataInformation
ExtrinsicObject. Then the link can be done with the “shortName” slot from the
System ExtrinsicObject describing the instrument.

Copyright © 2013 Open Geospatial Consortium

35

OGC 11-035

36

Copyright © 2013 Open Geospatial Consortium

OGC 11-035r1

Annex A
Informative
Example of EO Product Collection metadata<?xml version="1.0" encoding="UTF-8"?><MI_Metadata xmlns="http://www.isotc211.org/2005/gmi"
xmlns:gco="http://www.isotc211.org/2005/gco" xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:gmd="http://www.isotc211.org/2005/gmd"
xsi:schemaLocation="http://www.isotc211.org/2005/gmd
http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/metadata
Application.xsd http://www.isotc211.org/2005/gmi
http://www.isotc211.org/2005/gmi/gmi.xsd" ><gmd:fileIdentifier><gco:CharacterString>urn:HMA:GS:F81D4FAE-7DEC-11D0-A76500A0C91E6BF6</gco:CharacterString></gmd:fileIdentifier><gmd:language><gmd:LanguageCode codeList="http://www.loc.gov/standards/iso639-2/"
codeListValue="eng">eng</gmd:LanguageCode></gmd:language><gmd:characterSet><gmd:MD_CharacterSetCode
codeList="http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#MD_Charact
erSetCode" codeListValue="utf8"/></gmd:characterSet><gmd:hierarchyLevel><gmd:MD_ScopeCode
codeList="http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#MD_ScopeCode" codeListValue="series"/></gmd:hierarchyLevel><gmd:hierarchyLevelName><gco:CharacterString>EO Product Collection</gco:CharacterString></gmd:hierarchyLevelName><gmd:contact><gmd:CI_ResponsibleParty><gmd:individualName><gco:CharacterString>eoHelp</gco:CharacterString></gmd:individualName><gmd:organisationName><gco:CharacterString>ESA</gco:CharacterString></gmd:organisationName><gmd:positionName><gco:CharacterString>Order Desk</gco:CharacterString></gmd:positionName><gmd:contactInfo><gmd:CI_Contact><gmd:address><gmd:CI_Address><gmd:electronicMailAddress><gco:CharacterString>eohelp@esa.int</gco:CharacterString></gmd:electronicMailAddress></gmd:CI_Address></gmd:address></gmd:CI_Contact>

Copyright © 2013 Open Geospatial Consortium

37

OGC 11-035</gmd:contactInfo><gmd:role><gmd:CI_RoleCode
codeList="http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#CI_RoleCode" codeListValue="pointOfContact"/></gmd:role></gmd:CI_ResponsibleParty></gmd:contact><gmd:dateStamp><gco:Date>2006-05-04</gco:Date></gmd:dateStamp><gmd:metadataStandardName><gco:CharacterString>OGC 11-035</gco:CharacterString></gmd:metadataStandardName><gmd:metadataStandardVersion><gco:CharacterString>1.0</gco:CharacterString></gmd:metadataStandardVersion><gmd:identificationInfo><gmd:MD_DataIdentification><gmd:citation><gmd:CI_Citation><gmd:title><gco:CharacterString>ASAR Image Mode
Acquisitions</gco:CharacterString></gmd:title><gmd:date><gmd:CI_Date><gmd:date><gco:Date>2006-05-04</gco:Date></gmd:date><gmd:dateType><gmd:CI_DateTypeCode
codeList="http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#CI_DateTypeCode" codeListValue="creation"/></gmd:dateType></gmd:CI_Date></gmd:date><gmd:identifier><gmd:MD_Identifier><gmd:code><gco:CharacterString>urn:HMA:GS:F81D4FAE-7DEC11D0-A765-00A0C91E6BF6</gco:CharacterString></gmd:code></gmd:MD_Identifier></gmd:identifier></gmd:CI_Citation></gmd:citation><gmd:abstract><gco:CharacterString><![CDATA[The <ahref=http://envisat.esa.int/instruments/asar/>Advanced Synthetic Aperture Radar(ASAR)</a> (more info <ahref=http://envisat.esa.int/dataproducts/asar/CNTR3.htm>here</a>) is one of the
instruments aboard the Environmental Satellite <a href=http://envisat.esa.int/ms/>ENVISAT</a> ... br><br>From this collection you may order <ahref=http://envisat.esa.int/instruments/asar/data-app/dataprod.html>products</a> of thefollowing types:<br>- <a href=http://envisat.esa.int/instruments/asar/dataapp/prodspread.html#pgfId=ASA_IM__0P>Image Mode Level 0 (ASA_IM__0P)</a><br><a href=http://envisat.esa.int/instruments/asar/dataapp/prodspread.html#pgfId=ASA_IMP_1P>Image Mode Precision Image

38

Copyright © 2013 Open Geospatial Consortium

OGC 11-035r1(ASA_IMP_1P)</a><br>- <a href=http://envisat.esa.int/instruments/asar/dataapp/prodspread.html#pgfId=ASA_IMS_1P>Image Mode Single Look Complex(ASA_IMS_1P)</a><br>- <a href=http://envisat.esa.int/instruments/asar/dataapp/prodspread.html#pgfId=ASA_IMG_1P>Image Mode Ellipsoid Geocoded Image(ASA_IMG_1P)</a><br>- <a href=http://envisat.esa.int/instruments/asar/dataapp/prodspread.html#pgfId=ASA_IMM_1P>Image Mode Medium Resolution(ASA_IMM_1P)</a>]]></gco:CharacterString></gmd:abstract><gmd:pointOfContact><gmd:CI_ResponsibleParty><gmd:individualName><gco:CharacterString>eoHelp</gco:CharacterString></gmd:individualName><gmd:organisationName><gco:CharacterString>ESA</gco:CharacterString></gmd:organisationName><gmd:positionName><gco:CharacterString>Order Desk</gco:CharacterString></gmd:positionName><gmd:contactInfo><gmd:CI_Contact><gmd:address><gmd:CI_Address><gmd:electronicMailAddress><gco:CharacterString>eohelp@esa.int</gco:CharacterString></gmd:electronicMailAddress></gmd:CI_Address></gmd:address></gmd:CI_Contact></gmd:contactInfo><gmd:role><gmd:CI_RoleCode
codeList="http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#CI_RoleCode" codeListValue="originator"/></gmd:role></gmd:CI_ResponsibleParty></gmd:pointOfContact><gmd:descriptiveKeywords xmlns:gmd="http://www.isotc211.org/2005/gmd"><gmd:MD_Keywords><gmd:keyword><gco:CharacterString>Orthoimagery</gco:CharacterString></gmd:keyword><gmd:type><gmd:MD_KeywordTypeCode
codeList="http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#MD_Keywor
dTypeCode" codeListValue="theme"/></gmd:type><gmd:thesaurusName><gmd:CI_Citation><gmd:title><gco:CharacterString>GEMET - INSPIRE themes,version 1.0</gco:CharacterString></gmd:title><gmd:date><gmd:CI_Date><gmd:date><gco:Date>2008-06-01</gco:Date></gmd:date>

Copyright © 2013 Open Geospatial Consortium

39

OGC 11-035<gmd:dateType><gmd:CI_DateTypeCode
codeList="hhttp://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#CI_DateTy
peCode" codeListValue="publication"/></gmd:dateType></gmd:CI_Date></gmd:date></gmd:CI_Citation></gmd:thesaurusName></gmd:MD_Keywords></gmd:descriptiveKeywords><gmd:resourceConstraints><gmd:MD_Constraints><gmd:useLimitation><gco:CharacterString>See </gco:CharacterString></gmd:useLimitation></gmd:MD_Constraints></gmd:resourceConstraints><gmd:resourceConstraints><gmd:MD_LegalConstraints><gmd:accessConstraints><gmd:MD_RestrictionCode codeListValue="copyright"
codeList="http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#MD_Restricti
onCode">copyright</gmd:MD_RestrictionCode></gmd:accessConstraints></gmd:MD_LegalConstraints></gmd:resourceConstraints><gmd:spatialRepresentationType><gmd:MD_SpatialRepresentationTypeCode
codeList="http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#MD_Spatial
RepresentationTypeCode" codeListValue="grid"/></gmd:spatialRepresentationType><gmd:spatialResolution><gmd:MD_Resolution><gmd:distance><gco:Distance uom="m">30</gco:Distance></gmd:distance></gmd:MD_Resolution></gmd:spatialResolution><gmd:language><gco:CharacterString>eng</gco:CharacterString></gmd:language><gmd:characterSet><gmd:MD_CharacterSetCode
codeList="http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#MD_Charact
erSetCode" codeListValue="utf8"/></gmd:characterSet><gmd:topicCategory><gmd:MD_TopicCategoryCode>imageryBaseMapsEarthCover</gmd:MD_TopicCateg
oryCode></gmd:topicCategory><gmd:extent><gmd:EX_Extent><gmd:geographicElement><gmd:EX_GeographicBoundingBox><gmd:westBoundLongitude><gco:Decimal>-11.0</gco:Decimal></gmd:westBoundLongitude>

40

Copyright © 2013 Open Geospatial Consortium

OGC 11-035r1<gmd:eastBoundLongitude><gco:Decimal>120.0</gco:Decimal></gmd:eastBoundLongitude><gmd:southBoundLatitude><gco:Decimal>17.5</gco:Decimal></gmd:southBoundLatitude><gmd:northBoundLatitude><gco:Decimal>68.0</gco:Decimal></gmd:northBoundLatitude></gmd:EX_GeographicBoundingBox></gmd:geographicElement></gmd:EX_Extent></gmd:extent></gmd:MD_DataIdentification></gmd:identificationInfo><gmd:dataQualityInfo><gmd:DQ_DataQuality><gmd:scope><gmd:DQ_Scope><gmd:level><gmd:MD_ScopeCode codeListValue="series"
codeList="">series</gmd:MD_ScopeCode></gmd:level></gmd:DQ_Scope></gmd:scope><gmd:report><gmd:DQ_DomainConsistency><gmd:result><gmd:DQ_ConformanceResult><gmd:specification><gmd:CI_Citation><gmd:title><gco:CharacterString>INSPIRE data
specification concerning orthoimagery - exact reference TBC</gco:CharacterString></gmd:title><gmd:date><gmd:CI_Date><gmd:date><gco:Date>2001-01-01</gco:Date></gmd:date><gmd:dateType/></gmd:CI_Date></gmd:date></gmd:CI_Citation></gmd:specification><gmd:explanation><gco:CharacterString>INSPIRE Data specification fororthoimagery is not yet officially published so conformity has not yet been
evaluated.</gco:CharacterString></gmd:explanation><gmd:pass/></gmd:DQ_ConformanceResult></gmd:result></gmd:DQ_DomainConsistency></gmd:report></gmd:DQ_DataQuality></gmd:dataQualityInfo><acquisitionInformation><MI_AcquisitionInformation><platform><MI_Platform>

Copyright © 2013 Open Geospatial Consortium

41

OGC 11-035<identifier><gmd:RS_Identifier><gmd:code><gco:CharacterString>urn:ogc:id:CEOS:platform:ENVISAT:v01</gco:Char
acterString></gmd:code><gmd:codeSpace><gco:CharacterString>http://www.esa.int</gco:CharacterString></gmd:codeSpace></gmd:RS_Identifier></identifier><description><gco:CharacterString>Envisat</gco:CharacterString></description><instrument><MI_Instrument><identifier><gmd:RS_Identifier><gmd:code><gco:CharacterString>urn:ogc:id:CEOS:instrument:ENVISAT:ASAR:v01</
gco:CharacterString></gmd:code><gmd:codeSpace><gco:CharacterString>http://www.esa.int</gco:CharacterString></gmd:codeSpace></gmd:RS_Identifier></identifier><type><MI_SensorTypeCode codeListValue=""
codeList="">Imaging.microwave.radars</MI_SensorTypeCode></type></MI_Instrument></instrument></MI_Platform></platform></MI_AcquisitionInformation></acquisitionInformation></MI_Metadata>

42

Copyright © 2013 Open Geospatial Consortium

OGC 11-035r1

Annex B:
(Informative)
Example of EO Service Metadata<?xml version="1.0" encoding="UTF-8"?><MD_Metadata xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns:gts="http://www.isotc211.org/2005/gts"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:srv="http://www.isotc211.org/2005/srv" xmlns:gml="http://www.opengis.net/gml"
xmlns:wms="http://www.opengis.net/wms" xmlns:gco="http://www.isotc211.org/2005/gco"
xmlns="http://www.isotc211.org/2005/gmd"
xsi:schemaLocation="http://www.isotc211.org/2005/gmd
http://schemas.opengis.net/iso/19139/20060504/gmd/gmd.xsd
http://www.isotc211.org/2005/srv
http://schemas.opengis.net/iso/19139/20060504/srv/srv.xsd"><fileIdentifier><gco:CharacterString>F81D4FAE-7DEC-11D0-A76500A0C91E6BF6</gco:CharacterString></fileIdentifier><language><LanguageCode codeList="http://www.loc.gov/standards/iso639-2/"
codeListValue="eng">eng</LanguageCode></language><hierarchyLevel><MD_ScopeCode
codeList="http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#MD_ScopeCode" codeListValue="service">service</MD_ScopeCode></hierarchyLevel><hierarchyLevelName><gco:CharacterString>EO Service</gco:CharacterString></hierarchyLevelName><contact><CI_ResponsibleParty><individualName><gco:CharacterString>B. B.</gco:CharacterString></individualName><organisationName><gco:CharacterString>DLR/DFD</gco:CharacterString></organisationName><positionName><gco:CharacterString>DLR HMA System
Engineer</gco:CharacterString></positionName><contactInfo><CI_Contact><phone><CI_Telephone><voice><gco:CharacterString>+49 ...</gco:CharacterString></voice><facsimile><gco:CharacterString>+49 ...</gco:CharacterString></facsimile></CI_Telephone></phone><address>

Copyright © 2013 Open Geospatial Consortium

43

OGC 11-035

20</gco:CharacterString><CI_Address><deliveryPoint><gco:CharacterString>Muenchner Str.
</deliveryPoint><city><gco:CharacterString>Oberpfaffenhofen</gco:CharacterString></city><postalCode><gco:CharacterString>82234</gco:CharacterString></postalCode><country><gco:CharacterString>DE</gco:CharacterString></country><electronicMailAddress><gco:CharacterString>b.b@...</gco:CharacterString></electronicMailAddress></CI_Address></address></CI_Contact></contactInfo><role><CI_RoleCode codeList=""codeListValue="pointOfContact">pointOfContact</CI_RoleCode></role></CI_ResponsibleParty></contact><dateStamp><gco:Date>2006-06-06</gco:Date></dateStamp><metadataStandardName><gco:CharacterString>OGC 11-035</gco:CharacterString></metadataStandardName><metadataStandardVersion><gco:CharacterString>1.0.0</gco:CharacterString></metadataStandardVersion><identificationInfo><srv:SV_ServiceIdentification><citation><CI_Citation><title><gco:CharacterString>My Example
Service</gco:CharacterString></title><date><CI_Date><date><gco:Date>2006-06-06</gco:Date></date><dateType><CI_DateTypeCode codeList=""codeListValue="creation">creation</CI_DateTypeCode></dateType></CI_Date></date><edition><gco:CharacterString>1.0.0</gco:CharacterString></edition>

44

Copyright © 2013 Open Geospatial Consortium

OGC 11-035r1<identifier><MD_Identifier><code><gco:CharacterString>DLR:DFD:MyExampleService</gco:CharacterString></code></MD_Identifier></identifier></CI_Citation></citation><abstract><gco:CharacterString> This service provides an example for a service
metadata record</gco:CharacterString></abstract><pointOfContact><CI_ResponsibleParty><individualName><gco:CharacterString>B.B.</gco:CharacterString></individualName><organisationName><gco:CharacterString>DLR/DFD</gco:CharacterString></organisationName><positionName><gco:CharacterString>DLR HMA System
Engineer</gco:CharacterString></positionName><contactInfo><CI_Contact><phone><CI_Telephone><voice><gco:CharacterString>+49...</gco:CharacterString></voice><facsimile><gco:CharacterString>+49...</gco:CharacterString></facsimile></CI_Telephone></phone><address><CI_Address><deliveryPoint><gco:CharacterString>Muenchner Str.
20</gco:CharacterString></deliveryPoint><city><gco:CharacterString>Oberpfaffenhofen</gco:CharacterString></city><postalCode><gco:CharacterString>82234</gco:CharacterString></postalCode><country><gco:CharacterString>DE</gco:CharacterString></country><electronicMailAddress>

Copyright © 2013 Open Geospatial Consortium

45

OGC 11-035<gco:CharacterString>b.b@...</gco:CharacterString></electronicMailAddress></CI_Address></address></CI_Contact></contactInfo><role><CI_RoleCode codeList=""codeListValue="pointOfContact">pointOfContact</CI_RoleCode></role></CI_ResponsibleParty></pointOfContact><descriptiveKeywords><MD_Keywords><keyword><gco:CharacterString>infoMapAccessService</gco:CharacterString></keyword><thesaurusName><CI_Citation><title><gco:CharacterString> D.4 of the Commission
Regulation (EG) NR. 1205/2008</gco:CharacterString></title><date><CI_Date><date><gco:Date>2008-12-03</gco:Date></date><dateType><CI_DateTypeCode
codeListValue="publication"
codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/res
ources/Codelist/ML_gmxCodelists.xml#CI_DateTypeCode">publication</CI_DateTypeCode></dateType></CI_Date></date></CI_Citation></thesaurusName></MD_Keywords></descriptiveKeywords><resourceConstraints><MD_Constraints><useLimitation><gco:CharacterString>No limitation</gco:CharacterString></useLimitation></MD_Constraints></resourceConstraints><srv:serviceType><gco:ScopedName codeSpace="anyURI">view</gco:ScopedName></srv:serviceType><srv:serviceTypeVersion><gco:CharacterString>1.0.0</gco:CharacterString></srv:serviceTypeVersion><srv:extent><EX_Extent><geographicElement>

46

Copyright © 2013 Open Geospatial Consortium

OGC 11-035r1<EX_GeographicBoundingBox><westBoundLongitude><gco:Decimal>-11.0</gco:Decimal></westBoundLongitude><eastBoundLongitude><gco:Decimal>120.0</gco:Decimal></eastBoundLongitude><southBoundLatitude><gco:Decimal>17.5</gco:Decimal></southBoundLatitude><northBoundLatitude><gco:Decimal>68.0</gco:Decimal></northBoundLatitude></EX_GeographicBoundingBox></geographicElement></EX_Extent></srv:extent><srv:coupledResource><srv:SV_CoupledResource><srv:operationName><gco:CharacterString>GetMap</gco:CharacterString></srv:operationName><srv:identifier><gco:CharacterString>41C627E2-2EA5-4D4F-9381B5BAC0C49A90</gco:CharacterString></srv:identifier><gco:ScopedName>TerraSAR-X_EEC</gco:ScopedName></srv:SV_CoupledResource></srv:coupledResource><srv:couplingType><srv:SV_CouplingType codeList=""codeListValue="loose">loose</srv:SV_CouplingType></srv:couplingType><srv:containsOperations><srv:SV_OperationMetadata><srv:operationName><gco:CharacterString>GetCapabilities</gco:CharacterString></srv:operationName><srv:DCP><srv:DCPList codeList="" codeListValue="HTTPGet"/></srv:DCP><srv:operationDescription><gco:CharacterString>Retrieve Service
Details</gco:CharacterString></srv:operationDescription><srv:connectPoint><CI_OnlineResource><linkage><URL>http://xyz/GetCapabilities</URL></linkage><protocol><gco:CharacterString>HTTP</gco:CharacterString></protocol></CI_OnlineResource></srv:connectPoint></srv:SV_OperationMetadata></srv:containsOperations><srv:operatesOn><MD_DataIdentification>

Copyright © 2013 Open Geospatial Consortium

47

OGC 11-035<citation><CI_Citation><title><gco:CharacterString>TerraSAR-X
EEC</gco:CharacterString></title><date><CI_Date><date><gco:Date>2006-06-06</gco:Date></date><dateType><CI_DateTypeCode codeList=""codeListValue="publication">publication</CI_DateTypeCode></dateType></CI_Date></date><identifier><MD_Identifier><code><gco:CharacterString>DLR:DFD:TerraSARX:EEC</gco:CharacterString></code></MD_Identifier></identifier></CI_Citation></citation><abstract><gco:CharacterString>Abstract for TerraSAR-X EEC products...</gco:CharacterString></abstract><language><gco:CharacterString>EN</gco:CharacterString></language></MD_DataIdentification></srv:operatesOn></srv:SV_ServiceIdentification></identificationInfo></MD_Metadata>48

Copyright © 2013 Open Geospatial Consortium