INSPIRE - Europa · Web view2015/09/10 · 2015-09-10 Subject INSPIRE Implementing Rules for...

INSPIREInfrastructure for Spatial Information in Europe

INSPIRE Metadata Implementing Rules: Technical Guidelines based on EN ISO 19115 and EN ISO 19119

Title INSPIRE Metadata Implementing Rules: Technical Guidelines based on EN ISO 19115 and EN ISO 19119

Creator Drafting Team Metadata and European Commission Joint Research Centre. Updated by MIG-MIWP8

Creation date 2007-10-26

Date of last revision 20153-09710-102016200529

Subject INSPIRE Implementing Rules for Metadata

Status V. 1.4 draft 0.5432x Draft document for editing in subgroups for MIWP8

Publisher European Commission Joint Research Centre

Type Text

Description Guidelines based on EN ISO 19115 and EN ISO 19119 for Commission Regulation (EC) No 1205/2008 of 3 December 2008 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards metadata

Contributor See Acknowledgements

Format doc

Source European Commission Joint Research Centre

Rights Public

Identifier document.docdocument.doc

Language EN

Relation Not applicable

CoverageComments

Not applicable

Current draft is updated at the following chapters2.2.5 Unique resource identifier2.3.6 Coupled resource

2.6.2, 2.6.3, 2.6.4 Date of publication, last revision, creation2.9 Contraints related to Access and use2.11.3 Metadata Language2.12 Metadata for interoperability (new chapter)2.13 Theme specific metadata (new chapter)

12345678

9

10

1112

13

1

Yet to be added/updated are the section below 2.14 Metadata for Spatial data services (new chapter)

2

1

1

Table of Contents

Acknowledgements ................................................................................................................... 5Introduction ............................................................................................................................... 6Changes from Version 1.2 of 2010-06-06 .................................................................................8Normative references ................................................................................................................9Verbal forms for expression of provisions .................................................................................91 INSPIRE profile of ISO 19115 and ISO 19119 .................................................................11

1.1 ISO Core Metadata Elements .................................................................................111.1.1 Spatial dataset and spatial dataset series ...........................................................111.1.2 Services ..............................................................................................................131.1.3 Conclusion ...........................................................................................................14

1.2 INSPIRE specific constraints (SC) ..........................................................................141.3 Extensions ...............................................................................................................15

1.3.1 Spatial data service type .....................................................................................151.3.2 Classification of spatial data services ..................................................................161.3.3 Resource locator function code ...........................................................................16

2 Basic mapping .................................................................................................................162.1 Introduction .............................................................................................................16

2.1.1 Xpath expression .................................................................................................172.1.2 ISO Schemas Location ........................................................................................17

2.2 Identification ............................................................................................................182.2.1 Resource title ......................................................................................................182.2.2 Resource abstract ...............................................................................................192.2.3 Resource Type ....................................................................................................212.2.4 Resource locator .................................................................................................222.2.5 Unique resource identifier ...................................................................................252.2.6 Coupled resource ................................................................................................272.2.7 Resource language .............................................................................................29

2.3 Classification of spatial data and services ...............................................................312.3.1 Topic category .....................................................................................................312.3.2 Spatial data service type .....................................................................................33

2.4 Keyword ..................................................................................................................342.4.1 Keyword value .....................................................................................................352.4.2 Originating controlled vocabulary ........................................................................37

2.5 Geographic location ................................................................................................392.5.1 Geographic bounding box ...................................................................................39

2.6 Temporal reference .................................................................................................412.6.1 Temporal extent ..................................................................................................412.6.2 Date of publication ...............................................................................................422.6.3 Date of last revision .............................................................................................442.6.4 Date of creation ...................................................................................................45

2.7 Quality and validity ..................................................................................................462.7.1 Lineage ...............................................................................................................462.7.2 Spatial resolution .................................................................................................48

2.8 Conformity ...............................................................................................................512.8.1 Degree ................................................................................................................522.8.2 Specification ........................................................................................................53

2.9 Constraints related to access and use ....................................................................552.9.1 Limitations on public access ................................................................................552.9.2 Conditions applying to access and use ...............................................................582.9.3 Limitations on public access – Alternative solution ..............................................602.9.4 Conditions applying to access and use - alternative implementation ..................63

2.10 Responsible organisation ........................................................................................682.10.1 Responsible party ............................................................................................682.10.2 Responsible party role .....................................................................................70

2.11 Metadata on metadata ............................................................................................712.11.1 Metadata point of contact ................................................................................712.11.2 Metadata date .................................................................................................732.11.3 Metadata language ..........................................................................................73

2.12 Metadata elements for interoperability ....................................................................752.12.1 Coordinate reference system ..........................................................................75

3

123456789

1011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162

1

2.12.2 Temporal Reference System ...........................................................................772.12.3 Encoding .........................................................................................................782.12.4 Character Encoding .........................................................................................792.12.5 Spatial representation type ..............................................................................802.12.6 Topological Consistency ..................................................................................81

2.13 Theme-specific metadata elements from Data specifications .................................862.13.1 Maintenance information .................................................................................862.13.2 Spatial representation information ...................................................................872.13.3 Supplemental information ................................................................................882.13.4 Process step ....................................................................................................892.13.5 Data source .....................................................................................................912.13.6 Browse graphic information .............................................................................932.13.7 Image description ............................................................................................942.13.8 Content information .........................................................................................952.13.9 Digital transfer options information ..................................................................962.13.10 Identification - Extent .......................................................................................982.13.11 Data Quality – several issues ..........................................................................99

2.14 Metadata for Spatial data services ........................................................................1042.14.1 Introduction ....................................................................................................1042.14.2 Metadata for interoperable Spatial data services ..........................................104

2.14.3 Quality of Service ..............................................................................................1112.14.4 Invocation metadata ..........................................................................................115

3 Detailed mapping ...........................................................................................................1183.1 Introduction ...........................................................................................................1183.2 Resource MetadataSet ..........................................................................................1183.3 Identification Section .............................................................................................119

3.3.1 Sub-elements for spatial dataset and spatial dataset series .............................1193.3.2 Sub-elements for service resources ..................................................................120

3.4 Data Quality Section ..............................................................................................1213.4.1 Lineage .............................................................................................................1213.4.2 Conformity .........................................................................................................121

3.5 Responsible Organisation .....................................................................................1223.5.1 Resource responsible organisation ...................................................................1223.5.2 Metadata point of contact ..................................................................................122

3.6 Constraint section ..................................................................................................1223.7 Abbreviations ........................................................................................................123

Annex A – ISO/TS 19139 encoding of the INSPIRE metadata elements ..............................1243.8 A.1 Introduction .....................................................................................................1243.9 A.2 From the conceptual schema to XML File instances .......................................1243.10 A.3 Polymorphism .................................................................................................1243.11 A.4 Management of polymorphism ........................................................................124

3.11.1 A.4.1 Management of community extensions ................................................1243.11.2 A.4.2 Parsing of metadata files ......................................................................124

3.12 A.5 Management of containment by reference ......................................................1253.13 A.6 ISO 19139 and multilingual metadata .............................................................125

3.13.1 A.6.1 The default language ...........................................................................1263.13.2 A.6.2 Alternate languages .............................................................................1273.13.3 A.6.3 Embedded translations ........................................................................1273.13.4 A.6.4 Use of translation files ..........................................................................128

3.14 A.7 Contexts of use ...............................................................................................1293.14.1 A.7.1 Use of ISO 19139 in the context of a Catalogue Service .....................1293.14.2 A.7.2 Use of ISO 19139 in the context of the standard interchange by transfer 129

3.15 A.8 Character encoding .........................................................................................1293.16 A.9 Temporal extent encoding ..............................................................................1293.17 A.10 Spatial resolution encoding ...........................................................................1313.18 A.11 Codelists .......................................................................................................1323.19 A.12 Example of ISO 19139 XML Metadata Sets ..................................................133

3.19.1 A.12.1 Dataset ...............................................................................................1333.19.2 A.12.2 Dataset series ....................................................................................1423.19.3 A.12.3 Service ...............................................................................................142

Annex B (informative) Metadata elements for interoperability ..............................................151

4

123456789

1011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162

1

3.20 B.1. Metadata elements required by the INSPIRE Implementing Rules on the Interoperability of Spatial Datasets and Services ..............................................................1513.21 B.2. Metadata elements recommended in the INSPIRE Data Specifications Technical Guidelines .........................................................................................................152

Acknowledgements ................................................................................................................... 4Introduction ............................................................................................................................... 5Changes from Version 1.2 of 2010-06-06 .................................................................................7Normative references ................................................................................................................8Verbal forms for expression of provisions .................................................................................81 INSPIRE profile of ISO 19115 and ISO 19119 ..................................................................10

1.1 ISO Core Metadata Elements ....................................................................................101.1.1 Spatial dataset and spatial dataset series ...........................................................101.1.2 Services ...............................................................................................................121.1.3 Conclusion ...........................................................................................................13

1.2 INSPIRE specific constraints (SC) .............................................................................131.3 Extensions ..................................................................................................................14

1.3.1 Spatial data service type ......................................................................................141.3.2 Classification of spatial data services ..................................................................15

2 Basic mapping .................................................................................................................. 152.1 Introduction ................................................................................................................15

2.1.1 Xpath expression .................................................................................................162.1.2 ISO Schemas Location ........................................................................................16

2.2 Identification ...............................................................................................................172.2.1 Resource title .......................................................................................................172.2.2 Resource abstract ...............................................................................................182.2.3 Resource Type ....................................................................................................202.2.4 Resource locator .................................................................................................212.2.4.1 Resource Locator for data sets and dataset series ..........................................212.2.4.2 Resource Locator for Services .........................................................................232.2.5 Unique resource identifier ....................................................................................242.2.6 Coupled resource ................................................................................................252.2.7 Resource language ......................................................................................2727262.3 Classification of spatial data and services ...................................................2929272.3.1 Topic category .............................................................................................2929272.3.2 Spatial data service type ..............................................................................3131292.4 Keyword .......................................................................................................3232302.4.1 Keyword value .............................................................................................3333312.4.2 Originating controlled vocabulary .................................................................3535332.5 Geographic location .....................................................................................3737352.5.1 Geographic bounding box ............................................................................3737352.6 Temporal reference .....................................................................................3939372.6.1 Temporal extent ...........................................................................................3939372.6.2 Date of publication .......................................................................................4040382.6.3 Date of last revision .....................................................................................4242402.6.4 Date of creation ...........................................................................................4343412.7 Quality and validity .......................................................................................4444422.7.1 Lineage ........................................................................................................4444422.7.2 Spatial resolution .........................................................................................4646442.8 Conformity ...................................................................................................4949472.8.1 Degree .........................................................................................................5050482.8.2 Specification ................................................................................................5151492.9 Constraints related to access and use .........................................................5353512.9.1 Limitations on public access ........................................................................5353512.9.2 Conditions applying to access and use ........................................................5656532.10 Responsible organisation ............................................................................6666552.10.1 Responsible party ........................................................................................6666552.10.2 Responsible party role .................................................................................6868572.11 Metadata on metadata .................................................................................6969582.11.1 Metadata point of contact ............................................................................6969582.11.2 Metadata date ..............................................................................................7171602.11.3 Metadata language ......................................................................................7171603 Detailed mapping .........................................................................................9999623.1 Introduction ..................................................................................................999962

5

123456789

101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263

1

3.2 Resource MetadataSet ................................................................................9999623.3 Identification Section ................................................................................100100633.3.1 Sub-elements for spatial dataset and spatial dataset series ....................100100633.3.2 Sub-elements for service resources ........................................................101101643.4 Data Quality Section ................................................................................102102653.4.1 Lineage ....................................................................................................102102653.4.2 Conformity ...............................................................................................102102653.5 Responsible Organisation ........................................................................103103663.5.1 Resource responsible organisation ..........................................................103103663.5.2 Metadata point of contact ........................................................................103103663.6 Constraint section ....................................................................................103103663.7 Abbreviations ...........................................................................................10410467Annex A – ISO/TS 19139 encoding of the INSPIRE metadata elements .............10510568A.1 Introduction ..............................................................................................10510568A.2 From the conceptual schema to XML File instances ...............................10510568A.3 Polymorphism ..........................................................................................10510568A.4 Management of polymorphism ................................................................10510568A.4.1 Management of community extensions ...................................................10510568A.4.2 Parsing of metadata files .........................................................................10510568A.5 Management of containment by reference ..............................................10610669A.6 ISO 19139 and multilingual metadata ......................................................10610669A.6.1 The default language ...............................................................................10710770A.6.2 Alternate languages .................................................................................10810871A.6.3 Embedded translations ............................................................................10810871A.6.4 Use of translation files .............................................................................10910972A.7 Contexts of use ........................................................................................11011073A.7.1 Use of ISO 19139 in the context of a Catalogue Service .........................11011073A.7.2 Use of ISO 19139 in the context of the standard interchange by transfer11011073A.8 Character encoding .................................................................................11011073A.9 Temporal extent encoding .......................................................................11011073A.10 Spatial resolution encoding ......................................................................11211275A.11 Codelists ..................................................................................................11311376A.12 Example of ISO 19139 XML Metadata Sets ............................................11411477A.12.1 Dataset ....................................................................................................11411477A.12.2 Dataset series ..........................................................................................12312386A.12.3 Service .....................................................................................................12312386Annex B (informative) Metadata elements for interoperability .............................13213295B.1. Metadata elements required by the INSPIRE Implementing Rules on the Interoperability of Spatial Datasets and Services .................................................13213295B.2. Metadata elements recommended in the INSPIRE Data Specifications Technical Guidelines ............................................................................................................13313396

6

123456789

10111213141516171819202122232425262728293031323334353637383940414243

1

AcknowledgementsMany individuals and organisations have contributed to the development of these Guidelines.

The original Drafting Team on Metadata (2006-08) included: Marcel Reuvers (Netherlands), Nicolas Lesage (France), Kristian Senkler (Germany), Michael Gould (Spain), Gil Ross (UK), Stefano Nativi (Italy), Jan Hjelmager (Denmark), Franz Daffner (European Environment Agency), Per Ryghaud (Norway), Thomas Vögele and Fred Kruse (Germany), David Danko (USA).

We are grateful for the comments received during the consultation (28 th May-15th June 2010) with the Member States via their Points of Contact.

We also wish to acknowledge the contribution of Jesus Barrera and his team at GeoSpatiumLab who have provided editorial assistance in preparing this new version of the guidelines, as well as the precious contribution of Angelo Quaglia at JRC in checking the final draft.

This version 1.3 of the Technical Guidelines clarifies some aspects of the implementation of the discovery metadata elements based on the experience built during the period of implementation 2010-13. It also includes an overview of the Metadata elements for Evaluation and Use defined in the INSPIRE Implementing Rules for the Interoperability of Spatial Datasets and Services

This update has been funded by the EU Interoperability Solutions for European Public Adminstrations (ISA) Programme through ISA Action 1.17: A Reusable INSPIRE Reference Platform (ARE3NA), which is supporting the development of open source solutions and the technical guidelines that aid cross-sector and cross-border interoperability and the implementation of the INSPIRE Directive.

Contact information

Massimo Craglia (Editor)European Commission Joint Research CentreInstitute for Environment and SustainabilityDigital Earth and Reference Data UnitTP262, Via Fermi 2749I-21027 Ispra (VA)ITALYE-mail: [email protected] Tel.: +39-0332-786269Fax: +39-0332-786325

http://ies.jrc.ec.europa.eu/ http://www.jrc.ec.europa.eu/

7

123456789

101112131415161718192021222324252627282930313233343536373839404142434445464748

1

http://www.jrc.ec.europa.eu/

http://ies.jrc.ec.europa.eu/

mailto:[email protected]

IntroductionAccording to Article 5(1) of Directive 2007/2/EC, Member States shall ensure that metadata are created for the spatial data sets and services corresponding to the themes listed in Annexes I, II and III, and that those metadata are kept up to date. According to Article 5(4) of Directive 2007/2/EC, Implementing Rules shall be adopted taking account of relevant, existing international standards and user requirements. In the context of metadata for spatial data and spatial data services, the standards EN ISO 19115, EN ISO 19119, and ISO 15836 (Dublin Core) have been identified as important standards.

Commission Regulation (EC) No. 1205/2008 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards metadata was adopted on of 3rd

December 2008, and published on the Official Journal of the European Union on 4 th

December (OJ L 326, 4.12.2008, p. 12–30). Any reference in this document to “Implementing Rules for Metadata” refers to the above-mentioned Regulation.

The Regulation sets out the requirements for the creation and maintenance of metadata for spatial data sets, spatial data set series and spatial data services corresponding to the themes listed in Annexes I, II and III to Directive 2007/2/EC. It defines a number of metadata elements, their multiplicities and the value domains to be used in the metadata.

NOTE1 The metadata elements defined in the Implementing Rules for Metadata are usually called discovery metadata.

In addition to these requirements, Commission Regulation (EU) No 1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services (OJ L 323, 08/12/2010, p. 11–102) and its sub-sequent amendments1,2 define six additional metadata elements for interoperability as well as some theme-specific requirements for the discovery metadata elements. Any reference in this document to “Implementing Rules for interoperability of spatial data sets and services” refers to the above-mentioned Regulation.

NOTE 2 The metadata elements defined in the Implementing Rules for interoperability of spatial data sets and services are also sometimes referred to as evaluation and use metadata.

The aim of this document is to define how the requirements of the Implementing Rules for Metadata can be implemented using EN ISO 19115 and EN ISO 19119. The following subsections describe for each element of the Implementing Rules its relation with the mentioned European standards. Furthermore, Annex B provides an overview of the additional metadata elements and requirements defined in the Implementing Rules for interoperability of spatial data sets and services as well as pointers to the INSPIRE Data Specifications, which provide guidance and recommendations for their implementation.

The timelines relevant for the provision of discovery metadata are different from those for metadata for interoperability. The former need to be provided according to the deadlines specified in the INSPIRE Directive for the Implementing Rules for Metadata (2 years after adoption for Annex I and II and 5 years after adoption for Annex III), while the latter need to be provided according to the deadlines specified in the INSPIRE Directive for the Implementing Rules for interoperability of spatial data sets and services (2 years after adoption for newly created or extensively restructured data sets, and 7 years for all other data sets). Figure 1 gives an overview of the dates at which the requirements included in the two Implementing Rules for data sets related to Annex I, II or III have to be met.

1 Commission Regulation (EU) No 102/2011 of 4 February 2011 amending Regulation (EU) No 1089/2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services (OJ L 31, 05/02/2011, p. 13–34)

2 Commission Regulation (EU) No …/.. of XXX amending Regulation (EU) No 1089/2010 implementing Directive 2007/2/EC as regards interoperability of spatial data sets and services (Annex II+III amendment).

8

123456789

101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354

12345

6

Annex I

Annex II

Annex III

03/1

2/20

10

03/1

2/20

13

23/1

1/20

12

23/1

1/20

17

Autu

mn

2015

Autu

mn

2020

Discovery metadata shall be available for spatial data sets and services

Metadata for interoperability shall be available for newly collected and extensively restructured spatial data sets

Metadata for interoperability shall be available for all spatial data sets

Figure 1. Illustration of Implementation Roadmap for discovery metadata and metadata for interoperability3

Note on Corrigenda to the Implementing Rules for Metadata

Regulation 1205/2008 has been amended with the corrigenda published in the OJ L 328/83 of 15.12.2009 as follows:

On page 12 delete the subtitle “Text with EEA relevance” (European Economic Area) On page 20, Annex D, point 1.3 replace “Spatial data services (services)” with

“Spatial data services (service)”.

PLEASE NOTE that in the course of this revision, another typing error has come to light in the Regulation 1205/2008 which will need a further amendment. In Part D 4, the language neutral name for element 501: Geoparameter calculation service should be (thematicGeoparameterCalculationService) and not (thematicGoparameterCalculationService) (part in bold is added to put in evidence the typing error). Still in Part D 4, a number of typos have been detected in the language-independent values when comparing the English version with those in other languages. These will be corrected in an amendment of the Regulation.

Legal Notice

This document will be publicly available as a ‘non-paper’, as it does not represent an official position of the Commission, and as such can not be invoked in the context of legal procedures.

Neither the European Commission nor any person acting on behalf of the Commission is responsible for the use that might be made of this publication.

3 Dates in this figure are accurate at the time of publication and are based on the assumption that the Annex II+III amendment of the Implementing Rules for interoperability of spatial data sets and services will be adopted in autumn 2013. For definitive dates refer to the roadmap published on the INSPIRE website (http://inspire.jrc.ec.europa.eu/index.cfm/pageid/44).

9

123

456789

10111213141516171819202122232425262728293031

1234

5

Changes from Version 1.2 of 2010-06-06This document is Version 1.3. The changes introduced since Version 1.2 includes:

Rewording to make the text clearer, Introduction of boxes specifying what is a Requirement, from what is a

Reccomendation. Inclusion of examples of good practice, Recommendations on Conformity to include also conformity to INSPIRE Network

Service, Overview table of the elements of metadata for evaluation and use defined in the

INSPIRE Implementing Rules for the Interoperability of Spatial Datasets and Services.

Throughout the document we have also corrected a typo from the previous version that referred to:

http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/gmxCodelists.xml Whereas the live path is: http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/ c odelist/gmxCodelists.xml

Most significant changes in V. 1.3 are:

Page no. Issue17 Change in Note to update links from Osor to Join-up21 Section 2.2.4: separation between Resource locator for datasets and dataset

series (2.2.4.1) and services (2.2.4.2)24 Section 2.2.5: suggest use of code and codespace and provided working

example25 Section 2.2.6: Clarified definition and provided working example26 Section 2.2.7: added Croatian to the domain29 Section 2.3.2: clarified that if a spatial data service is also an INSPIRE Network

service, then it is necessary to include in the Metadata element 2.8.2 Specifications, reference to the relevant INSPIRE Network Service Implementing Rule or amendment (see also 2.8.2)

48 Section 2.8: Recommended to avoid using “Not Evaluated” for the element Conformity now that all Technical Specifications for Datasets and Services are available. Therefore, it is recommended to evaluate and declare the conformity of all data sets (i.e. as “conformant” or “not conformant”).

49 Section 2.8.2: If a spatial data service is an INSPIRE Network service, use this element to report the relevant INSPIRE Network Implementing Rule to which it conforms.

Example of how to cite correctly an INSPIRE Specification is provided60-61 Section 2.11.3: added Croatian to the domain79- Section A.12: Changed examples throughout95 Section B: new section summarising the additional metadata elements required

by the Implementing Rules for the Interoperability of Spatial Datasets and Services.

10

123456789

10111213141516171819202122232425

26

1

http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/gmxCodelists.xml

http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/gmxCodelists.xml

http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/

http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/

Normative referencesThe following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.

[ISO 19108] EN ISO 19108:2005, Geographic Information – Temporal Schema

[ISO 19108-c] ISO 19108:2002/Cor 1:2006, Geographic Information – Temporal Schema, Technical Corrigendum 1

[ISO 19115] EN ISO 19115:2005, Geographic information – Metadata (ISO 19115:2003) 4

[ISO 19119] EN ISO 19119:2005, Geographic information – Services (ISO 19119:2005)

[ISO 639-2] EN ISO 639-2:1998, Codes for the representation of names of languages – Part 2: Alpha-3 code

[ISO 8601] EN ISO 8601:2004, Data elements and interchange formats – Information interchange – Representation of dates and times

[ISO 19139] ISO/TS 19139:2007, Geographic information – Metadata – XML schema implementation

[CSW2 AP ISO] OpenGIS Catalogue Services Specification 2.0.2 - ISO Metadata Application Profile, Version 1.0.0, OGC 07-045, 2007

[ISO 10646-1] ISO/IEC 10646-1:2000, Information technology ― Universal Multiple-Octet Coded Character Set (UCS) ― Part 1: Architecture and Basic Multilingual Plane

[IR MDTG] INSPIRE Metadata Implementing Rules. Guidelines based on EN ISO 19115 and EN ISO 19119 for Commission Regulation (EC) No 1205/2008 of 3 December 2008 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards metadata

[INSPIRE Directive] INSPIRE, Implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial datasets and services

[Regulation 1205/2008/EC] Regulation 1205/2008/EC implementing Directive 2007/2/EC of the European Parliament and of the Council as regards metadata

Verbal forms for expression of provisionsIn accordance with the ISO rules for drafting, the following verbal forms shall be interpreted in the given way:

“shall” / “shall not”: a requirement, mandatory to comply with the technical guidance “should” / “should not”: a recommendation, but an alternative approach may be

chosen for a specific case if there are reasons to do so “may” / “need not”: a permission

Technical Guideline Requirements and Recommendations notation

4 EN ISO 19115:2005 is the adoption by CEN of ISO 19115:2003

11

123456789

10111213141516171819202122232425262728293031323334353637383940414243

44454647

484950515253545556

1

2

http://portal.opengeospatial.org/files/?artifact_id=21460

http://portal.opengeospatial.org/files/?artifact_id=21460

Requirements and the recommendations for INSPIRE Metadata Implementing Rules within this technical guideline are highlighted and numbered as shown below:

TG Requirement #requirements are shown using this style

TG Recommendation #recommendations are shown using this style.

It is important to note that, implementation requirements and implementation recommendations may refer to either data or services.

Note: It is worth noting that requirements as specified in the INSPIRE Regulations and Implementing Rules are legally binding, and that requirements and recommendations as specified in INSPIRE Technical Guideline are not legally binding. Therefore, within this technical guideline we have used the terms ‘TG requirement’ and ‘TG recommendation’ to indicate what is technically required or recommended to conform to the Technical Guidance.

XML Example notationXML Examples are shown using Courier New on a grey background with yellow for emphasis as below:

<inspire:example><inspire:highlight>

Highlighted Text for emphasis</inspire:highlight>

</inspire:example>

Note: XML Examples are informative and are provided for information only and are expressly not normative.

12

1234

5

6

7

89

10111213141516171819202122232425262728

29303132

1

1 INSPIRE profile of ISO 19115 and ISO 19119

1.1 ISO Core Metadata Elements

1.1.1 Spatial dataset and spatial dataset series

The table below compares the core requirements of ISO 19115 (see Table 3 in 6.5 of ISO 19115:2003) to the requirements of INSPIRE for spatial dataset and spatial dataset series as defined in the Implementing Rules for metadata.

ISO 19115 Core INSPIRE Implementing Rules for Metadata

Comments

Dataset title (M) Part B 1.1 Resource Title -

Dataset reference date (M)

Part B 5 Temporal Reference

ISO 19115 is more demanding. The metadata shall contain a date of publication, revision or creation of the resource, while in INSPIRE the Temporal Reference can also be expressed through Temporal Extent.

Dataset responsible party (O)

Part B 9 Responsible organisation

INSPIRE is more demanding by mandating both the name of the organisation, and a contact e-mail address

Geographic location of the dataset (C)

Part B 4.1 Geographic Bounding Box

INSPIRE is more restrictive. A Geographic bounding box is mandated

Dataset language (M) Part B 1.7 Resource Language

ISO 19115 is more demanding. It mandates the dataset language, even if the resource does not include any textual information. The ISO 19115 Dataset language is defaulted to the Metadata language.

Dataset character set (C) - ISO 19115 is more demanding. The dataset character set has to be documented in ISO 19115 when ISO 10646-1 is not used.

The ISO 19115 element maps to the conditional “Character Encoding” metadata element defined in Art. 13(5) of the Implementing Rules on interoperability of spatial data sets and services. This element is mandatory only if an encoding is used that is not based on UTF-8 (the dominant encoding of ISO 10646-1).

Dataset topic category (M) Part B 2.1 Topic Category -

Spatial resolution of the dataset (O)

Part B 6.2 Spatial Resolution

-

Abstract describing the dataset (M)

Part B 1.2 Resource abstract

-

Distribution format (O) - The ISO 19115 element maps to the mandatory “Encoding” metadata element defined in Art. 13(3) of the Implementing Rules on interoperability of spatial data sets and services.

Additional extent information for the dataset (vertical and temporal) (O)

Part B 5.1 Temporal extent INSPIRE is more demanding. A temporal reference is mandated, and can be expressed as a temporal extent.

13

1

2

345678

1

ISO 19115 Core INSPIRE Implementing Rules for Metadata

Comments

Spatial representation type (O)

- The ISO 19115 element maps to the mandatory “Spatial Representation Type” metadata element defined in Art. 13(6) of the Implementing Rules on interoperability of spatial data sets and services5.

Reference system (O) - The ISO 19115 element maps to the mandatory “Coordinate Reference System” and the conditional “Temporal Reference System” metadata elements defined in Art. 13(1) and (2) of the Implementing Rules on interoperability of spatial data sets and services set.

Lineage (O) Part B 6.1 Lineage INSPIRE is more demanding. A general lineage statement is mandated.

On-line resource (O) Part B 1.4 Resource Locator

-

Metadata file identifier (O) - -

Metadata standard name (O)

- -

Metadata standard version (O)

- -

Metadata language (C) Part B 10.3 Metadata Language

INSPIRE is more demanding. The metadata language is mandated even if it is defined by the encoding.

Metadata character set (C)

- ISO 19115 is more demanding. The metadata character set has to be documented in ISO 19115 when ISO 10646-1 is not used.

Metadata point of contact (M)

Part B 10.1 Metadata point of contact

INSPIRE is more demanding by mandating both the name of the organisation, and a contact e-mail address.

Metadata date stamp (M) Part B 10.2 Metadata Date ISO is more restrictive because this element shall contain the “date that the metadata was created” and INSPIRE may contain the “date when the metadata record was created or updated

- Part B 1.3 Resource Type INSPIRE is more demanding

Part B 1.5 Unique Resource Identifier

INSPIRE is more demanding

Part B 3 Keyword INSPIRE is more demanding

- Part B 7 Conformity INSPIRE is more demanding

- Part B 8.1 Conditions for access and use


- Part B 8.2 Limitations on public access


5 This element will be introduced in the Annex II+III amendment to the Implementing Rules on interoperability of spatial data sets and services.

14

12

3

1.1.2 Services

The table below compares the core requirements of ISO 19115 (see Table 3 in 6.5 of ISO 19115:2003) to the requirements of INSPIRE for services as defined in the Implementing Rules for metadata. The greyed lines correspond to core metadata elements not applicable to services.

ISO 19115 Core INSPIRE Comments

Dataset title (M) Part B 1.1 Resource Title -

Dataset reference date (M)

Part B 5 Temporal Reference

ISO 19115 is more demanding. Despite its name, this ISO 19115 Core metadata element applies to services. A reference date of the service (date of publication, revision or creation …) is mandated.

Dataset responsible party (O)

Part B 9 Responsible organisation

-

Geographic location of the dataset (C)

- See INSPIRE Geographic Bounding Box

- Part B 4.1 Geographic Bounding Box

The Geographic Bounding Box is handled in ISO 19119 with a different metadata element from the one corresponding to “Geographic location of the dataset”

Dataset language (M) - Not applicable to services

Dataset character set (C) - Not applicable to services

Dataset topic category (M) - Not applicable to services

Spatial resolution of the dataset (O)

Part B 6.2 Spatial Resolution

In the current version of ISO 19119, it is not possible to express the restriction of a service concerning the spatial resolution

Abstract describing the dataset (M)

Part B 1.2 Resource abstract

-

Distribution format (O) - -

Additional extent information for the dataset (O)

- -

Spatial representation type (O)

- -

Reference system (O) - -

Lineage (O) - -

On-line resource (O) Part B 1.4 Resource Locator

-

Metadata file identifier (O) - -

Metadata standard name (O)

- -

Metadata standard version (O)

- -

Metadata language (C) Part B 10.3 Metadata Language

INSPIRE is more demanding. The metadata language is mandated.

15

1234567

1

ISO 19115 Core INSPIRE Comments

Metadata character set (C)

- ISO 19115 is more demanding. The metadata character set has to be documented in ISO 19115 when ISO 10646-1 is not used.

Metadata point of contact (M)

Part B 10.1 Metadata point of contact

-

Metadata date stamp (M) Part B 10.2 Metadata Date ISO is more restrictive because this element shall contain the “date that the metadata was created” and INSPIRE may contain the “date when the metadata record was created or updated

- Part B 1.3 Resource Type INSPIRE is more demanding

- Part B 1.6 Coupled Resource

Optional in INSPIRE

- Part B 2.2 Spatial Data Service Type


Part B 3 Keyword INSPIRE is more demanding

- Part B 7 Conformity INSPIRE is more demanding

- Part B 8.1 Conditions for access and use


- Part B 8.2 Limitations on public access


1.1.3 Conclusion

The conformance of an ISO 19115 metadata set to the ISO 19115 Core does not guarantee the conformance to INSPIRE;

The use of these guideline to create INSPIRE metadata ensures that the metadata is not in conflict with ISO 19115. However, full conformance to ISO 19115 implies the provision of additional metadata elements which are not required by the INSPIRE Implementing Rule on Metadata. Additional metadata elements are required by the INSPIRE Implementing Rules for the Interoperability of Spatial Datasets and Services. An overview list of these additional elements is provided in Annex B.

Over the structural requirements formalised through the mappings, the conformance to INSPIRE is also a matter of semantic of the information provided. If it is acceptable that the ISO 19115/ISO 19119 contain information which are not strictly bounded to the definition of the corresponding INSPIRE metadata elements, the minimum requirements expressed in the implementing rules have also to be met semantically, i.e. with metadata contents strictly satisfying the INSPIRE requirements.

1.2 INSPIRE specific constraints (SC)

Here is an initial list of INSPIRE Regulation 1205/2008/EC constraints applicable to an ISO 19115/ISO 19119 metadata set (i.e. an instance of MD_Metadata) describing a resource:SC1. MD_Metadata.language is mandatory;SC2. MD_Metadata.hierarchyLevel is mandatory;SC3. INSPIRE only considers the first instance of MD_Metadata.hierarchyLevel (i.e.

MD_Metadata.hierarchyLevel[1]) when there are many;SC4. If the value of MD_Metadata.hierarchyLevel[1] is not service, dataset or series, the

metadata set is out of scope of the directive;

16

1

23456789

101112131415161718

19202122232425262728

1

SC5. When there are many instances of MD_Metadata.identificationInfo, only the first one (i.e. MD_Metadata.identificationInfo[1]) concerns the current INSPIRE Resource;

SC6. INSPIRE only considers the instance of MD_Metadata.dataQualityInfo applicable to the whole resource;

SC7. There shall not be more than one instance of MD_Metadata.identificationInfo[1].MD_Identification.citation.CI_Citation.date declared as a creation date (i.e. CI_Date.dateType having the creation value);

SC8. MD_Metadata.identificationInfo[1].MD_DataIdentification.citation.CI_Citation.identifier is mandatory for metadata sets related to spatial dataset and spatial dataset series;

SC9. The data type of MD_Metadata.identificationInfo.MD_DataIdentification.language is the codelist LanguageCode from ISO/TS 19139;

SC10.There is at least one instance of MD_Metadata.identificationInfo[1].MD_DataIdentification.extent defining the geographic location of the resource as a geographic bounding box (i.e. an instance of EX_GeographicBoundingBox or one of its subclasses).

SC11.MD_Metadata.identificationInfo[1].SV_ServiceIdentification.operatesOn shall be instantiated by reference

SC12.There shall be at least one instance of MD_Metadata.identificationInfo[1].MD_Identification.resourceConstraints

SC13.The coordinates of the bounding boxes (instance of EX_GeographicBoundingBox) shall be expressed in any geodetic coordinate reference system with the Greenwich Prime Meridian

SC14.For datasets and series: MD_Metadata.identificationInfo[1].MD_DataIdentification.pointOfContact[1].CI_ResponsibleParty.organisationName and MD_Metadata.identificationInfo[1].MD_DataIdentification.pointOfContact[1].CI_ResponsibleParty.contactInfo.CI_Contact.address.CI_Address.electronicMailAddress are mandatory.For services these elements are also mandatory but they are referred as follows: MD_Metadata.identificationInfo[1].SV_ServiceIdentification.pointOfContact[1].CI_ResponsibleParty.organisationName and MD_Metadata.identificationInfo[1].SV_ServiceIdentification.pointOfContact[1].CI_ResponsibleParty.contactInfo.CI_Contact.address.CI_Address.electronicMailAddress.

SC15.MD_Metadata.contact[1].CI_ResponsibleParty.organisationName and MD_Metadata.contact[1].CI_ResponsibleParty.contactInfo.CI_Contact.address.CI_Address.electronicMailAddress are mandatory.

SC16.The value of MD_Metadata.contact[1].CI_ResponsibleParty.role.CI_RoleCode shall be pointOfContact.

SC17.For datasets and series at least one keyword of GEMET thesaurus shall be documented using MD_Metadata.identificationInfo[1].MD_DataIdentification.descriptiveKeywords.

SC18.For services at least one keyword of Part D.4 of Commission Regulation (EC) No. 1205/2008 shall be documented using MD_Metadata.identificationInfo[1].SV_ServiceIdentification.descriptiveKeywords

TBD Add Constraints for the elements for Metadata for Interoperability.

1.3 Extensions

1.3.1 Spatial data service type

For spatial data service types, the INSPIRE Metadata Regulation 1205/2008/EC mandate the use of the value domain of Part D 3. This information is handled using the serviceType attribute (See 2.3.2) of the class SV_ServiceIdentification (See ISO 19119).

The Table below defines the values of the serviceType property. In brackets are the language neutral names to be used.

17

123456789

10111213141516171819202122232425262728293031323334353637383940414243444546

47

484950515253545556

1

SPATIAL DATA SERVICE TYPE

Discovery Service (discovery)View Service (view)Download Service (download)Transformation Service (transformation)Invoke Spatial Data Service (invoke)Other Services (other)

1.3.2 Classification of spatial data services

For classification of spatial data services, the Implementing Rules mandate the use of the value domain of Part D 4 of Regulation 1205/2008/EC. In order to ensure a language independent expression of the classification of spatial data services, the language neutral name is to be used as the value of the ISO 19115 keywords (See 2.4).

1.3.3 Resource locator function

The Resource Locator metadata element set out in Regulation (EC) No 1205/2008 shall also contain all access points from the spatial data service provider and these access points shall be unambiguously identified as such. This information will be handled in the description element (See 2.2.4.3)2.3.2) The table below defines the values of the description element.

Value Description

accessPoint Containing a detailed description of a spatial data service, including a list of end points to allow its execution,

accessPoint-selfDescribing Used to describe an access point of the service that describe itself in a machine readable format (e.g. WSDL)

providesServiceMetadata Used to specify an address to a document that describe the service metadata (such as GetCapabilities or a WSDL containing a reference to the getCapabilities operation)

endPoint Used to directly call an operation provided by a spatial data service

1.3.4

a

2 Basic mapping

2.1 Introduction

18

1

2345678

9101112131415161718

19

202122

23

24

2526

1

Ine de Visser, 05/20/15,

Add in TG MD as 1.3.3

The following tables describe the mapping between the metadata elements of INSPIRE, as defined in the INSPIRE implementing rules for metadata, and ISO 19115/ISO 19119. For each of the INSPIRE Metadata element, the mapping is composed of the main characteristics of the metadata element as they are defined6 in the INSPIRE implementing rules (IR) for metadata and the main characteristics of the corresponding metadata element of ISO 19115 or ISO 19119:

The metadata element name as used in the INSPIRE implementing rules; The reference to the paragraph of the INSPIRE implementing rules describing the

metadata element; The definition, which gives the current ISO 19115 or ISO 19119 terms for describing

the metadata element (Annex B of ISO 19115 standard: Data Dictionary for geographic metadata or Annex C of ISO 19119: Data dictionary for geographic service metadata);

The number and the name that identifies the metadata element inside tables in ISO 19115 (or ISO 19119) published standard;

An XPath expression indicating the metadata element within the ISO 19115 / ISO 19119 UML model (see 2.1.1);

The INSPIRE obligation/condition applicable to the metadata element; The INSPIRE multiplicity of the metadata element; The Data Type and the Domain required by the metadata element; An example that illustrates the description of the metadata element by providing a

concrete case Some comments, which give more information about the metadata element

Apart from the tables collecting the main significant aspects, additional information is provided regarding: the description of the metadata element, advices on its fulfilment and important requirements and recommendations, as well as an example of XML encoding, i.e. a fragment of the XML of a metadata record created and validated with the INSPIRE Metadata Editor available from the EU Geoportal (http://inspire-geoportal.ec.europa.eu).

The overall structure of an ISO 19115/ISO 19119 metadata set supporting the requirements expressed in the INSPIRE Implementing rules for metadata is defined in Section 3 of this document.

2.1.1 Xpath expression

This compact notation allows many defaults and abbreviations for common cases. The simplest XPath takes a form such as /A/B/C which selects C elements that are children of B elements that are children of the A element that forms the outermost element of the model. More complex expressions can be constructed by specifying an axis other than the default 'child' axis, a node test other than a simple name, or predicates, which can be written in square brackets after any step. The main rules are the following ones:

* selects all element children of the context node; text() selects all text node children of the context node; @name selects the name attribute of the context node; @* selects all the attributes of the context node; . selects the context node; .//para selects the para element descendants at any level of the context node; .. selects the parent of the context node.

Hereafter, the root element of the XPath expression is an instance of MD_Metadata or one of its subclasses. The possible subelements of a class are its properties. The possible subelement of a property is its data type or a subtype of its data type. In order to manage the polymorphism, the XPath expression deals with the data type in a generic way (e.g., property_element_name/*/datatype_property_name).

2.1.2 ISO Schemas Location

6 In case of discrepancy, the INSPIRE Implementing rules take precedence

19

123456789

101112131415161718192021222324252627282930313233

343536373839404142434445464748495051525354

5556

1

2

Official ISO schemas (ISO AP or ISO 19139) are currently found in two separate locations:

1) ISO repository for public available standards. The ISO 19139 schemas can be found here: http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/Date of schemas: 2007-08-11.

2.) OGC Schema repository. The ISO 19139 schemas are located here: http://schemas.opengis.net/iso/19139/20070417/Date of schemas: 2007-04-17.and here: http://schemas.opengis.net/iso/19139/20060504/Date of schemas: 2006-06-04.

ISO AP schemas are located here: http://schemas.opengis.net/csw/2.0.2/profiles/apiso/Date of schemas: 2007-07-19.

The ISO AP schemas are bound to http://schemas.opengis.net/iso/19139/20060504/

The difference in the schemas located in the OGC repository is the GML version. The version dated "2007-04-17" uses GML 3.2.1, the version dated "2006-06-04" use GML 3.2.0. The version "2006-06-04" provides gml in a separate directory (/gml) whereas the version "2007-04-17" directly refers to http://schemas.opengis.net/gml/3.2.1/. The major difference is that GML 3.2.0 schemas are defined in the namespace http://www.opengis.net/gml whereas GML 3.2.1 schemas are defined in the namespace http://www.opengis.net/gml/3.2.

The schemas located in the ISO repository for public available standards are comparable to OGC schemas located here: http://schemas.opengis.net/iso/19139/20070417/.

In conclusion:To Validate XML against ISO AP 1.0:http://schemas.opengis.net/csw/2.0.2/profiles/apiso/1.0.0/apiso.xsd

To Validate XML against ISO 19139 with GML 3.2.0:http://schemas.opengis.net/iso/19139/20060504/gmd/gmd.xsd

To Validate XML against ISO 19139 with GML 3.2.1:http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/gmd.xsd or http://schemas.opengis.net/iso/19139/20070417/gmd/gmd.xsd

INSPIRE Validator Service: A RESTful Web service that can be invoked by http request to validate INSPIRE Metadata. The purpose of the INSPIRE Metadata Validator is to test compliance of INSPIRE metadata with the INSPIRE Metadata Regulation. The validator accepts metadata that follow the Metadata Technical Guidance encoded in EN ISO 19139 schema. The INSPIRE Metadata Validator is implemented by ISO Schematron (2006).

The web application and service are provided for testing. Please report any issues you find so that they can be improved at [email protected]

End point: http://inspire-geoportal.ec.europa.eu/validator2/ Supported method: POSTSupported response formats: XML, HTML (The response format is returned according to the Accept value of the http request header)Request parameter: dataFile (This is the name of the parameter associated with the metadata record xml file that should be added to the request)

PLEASE NOTE: The validator is a proof of concept that has been developed to test these guidelines. It is not intended to be an operational tool, and at the present time works in English only. All the files of the Validator including documentation are available under EU Public License from the JoinUp Platform (https://joinup.ec.europa.eu/software/validator/home). Interested stakeholders are welcome to adapt the current Validator to their own language, and contribute it back through JoinUp to enrich the collective portfolio of tools supporting the implementation of INSPIRE, currently being explored by the ISA Action A Reusable INSPIRE Reference Platform (ARE3NA:

20

123456789

101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263

1

https://joinup.ec.europa.eu/software/validator/home

http://inspire-geoportal.ec.europa.eu/validator2/


http://schemas.opengis.net/iso/19139/20070417/gmd/gmd.xsd

http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/gmd.xsd


http://schemas.opengis.net/csw/2.0.2/profiles/apiso/1.0.0/apiso.xsd

http://schemas.opengis.net/iso/19139/20070417/

http://www.opengis.net/gml/3.2

http://www.opengis.net/gml

http://schemas.opengis.net/gml/3.2.1/


http://schemas.opengis.net/csw/2.0.2/profiles/apiso/



http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/

https://joinup.ec.europa.eu/community/are3na/description). A new validator is being developed and will also be added to JoinUp.

2.2 Identification

2.2.1 Resource title

This is a characteristic, and often unique, name by which the resource is known. The title is the most informative element of a metadata record and usually the highest priority as search engines go to this element.

TG Recommendation 1 The Resource Title has to be concise and to the point. It should not contain unexplained acronyms or abbreviations. It is recommended a maximum length of 250 characters and keeping the similarity with the original title of the resource, in the sense of the ‘official naming’.

TG Recommendation 2 If the data or service is part of a larger project, it is recommended to indicate the Project at the end of the title, in brackets. In case of Project names, abbreviations are allowed, as long as the rest of the title follows the guidelines above and the abbreviation is spelled out immediately in the abstract.

Metadata element name Resource title

Reference Part B 1.1

Definition Name by which the cited resource is known

ISO 19115 number and name 360. title

ISO/TS 19139 path identificationInfo[1]/*/citation/*/title

INSPIRE obligation / condition Mandatory

INSPIRE multiplicity [1]

Data type (and ISO 19115 no.) CharacterString

Domain Free text

Example SPI: Standardized Precipitation Index

Comments

Example of XML encoding:

<gmd:MD_Metadata …...

<gmd:identificationInfo><gmd:MD_DataIdentification>

<gmd:citation><gmd:CI_Citation>

<gmd:title><gco:CharacterString>SPI: Standardized

Precipitation Index</gco:CharacterString></gmd:title>

</gmd:CI_Citation></gmd:citation>

</gmd:MD_DataIdentification>

21

123

4

56789

10

11121314

15

1617181920

21

22232425262728293031323334353637383940

1

https://joinup.ec.europa.eu/community/are3na/description

</gmd:identificationInfo>...</gmd:MD_Metadata>

2.2.2 Resource abstract

This is a brief narrative summary of the content of the resource. The abstract provides a clear and concise statement that enables the reader to understand the content of the data or service

Metadata element name Resource abstract


Definition Brief narrative summary of the content of the resource(s)

ISO 19115 number and name 25. abstract

ISO/TS 19139 path identificationInfo[1]/*/abstract




Domain Free text

Example The Standardized Precipitation Index (SPI-n) is a statistical indicator comparing the total precipitation received at a particular location during a period of n months with the long-term rainfall distribution for the same period of time at that location. SPI is calculated on a monthly basis for a moving window of n months, where n indicates the rainfall accumulation period, which is typically 1, 3, 6, 9, 12, 24 or 48 months. The corresponding SPIs are denoted as SPI-1, SPI-3, SPI-6, etc. In order to allow for the statistical comparison of wetter and drier climates, SPI is based on a transformation of the accumulated precipitation into a standard normal variable with zero mean and variance equal to one. SPI results are given in units of standard deviation from the long-term mean of the standardized distribution. In 2010 WMO selected the SPI as a key meteorological drought indicator to be produced operationally by meteorological services

Comments

TG Recommendation 3 The resource abstract is a succinct description that can include:

- A brief summary with the most important details that summarise the data or service

- Coverage: linguistic transcriptions of the extent or location inaddition to the bounding box

- Main attributes

- Data sources

- Legal references

- Importance of the work

TG Recommendation 4 Do not use unexplained acronyms.

22

1234

56789

10

1112

13

1415

1617

18

19

20

21

22

23

1

TG Recommendation 5 Summarise the most important details in the first sentence or first 100 characters.




...<gmd:abstract>

<gco:CharacterString>The Standardized Precipitation Index (SPI-n) is a statistical indicator comparing the total precipitation received at a particular location during a period of n months with the long-term rainfall distribution for the same period of time at that location. SPI is calculated on a monthly basis for a moving window of n months, where n indicates the rainfall accumulation period, which is typically 1, 3, 6, 9, 12, 24 or 48 months. The corresponding SPIs are denoted as SPI-1, SPI-3, SPI-6, etc.In order to allow for the statistical comparison of wetter and drier climates, SPI is based on a transformation of the accumulated precipitation into a standard normal variable with zero mean and variance equal to one. SPI results are given in units of standard deviation from the long-term mean of the standardized distribution. In 2010 WMO selected the SPI as a key meteorological drought indicator to be produced operationally by meteorological services.

</gco:CharacterString></gmd:abstract>

...</gmd:MD_DataIdentification>


2.2.3 Resource Type

This is the type of resource being described by the metadata and it is filled in with a value from a classification of the resource based on its scope. The choice of Resource Type will be probably the first decision made by the user and it will define the metadata elements that should be filled.

Metadata element name Resource type


Definition Scope to which metadata applies

ISO 19115 number and name 6. hierarchyLevel

ISO/TS 19139 path hierarchyLevel



Data type (and ISO 19115 no.) MD_ScopeCode

Domain CodeList (see annex B.5.25 of ISO 19115)

Example dataset

Comments

23

1

23

456789

1011121314151617181920212223242526272829303132333435

36373839404142

43

1

TG Requirement 1 The hierarchyLevel property is not mandated by ISO 19115 but is mandated for conformance to the INSPIRE Metadata Regulation 1205/2008/EC (See SC2 in 1.2).

TG Requirement 2 The values of MD_ScopeCode in the scope of the INSPIRE Directive (See SC4 in 1.2) are:

- dataset for spatial datasets;

- series for spatial dataset series;

- service for spatial data services

TG Recommendation 6 The choice between the values should follow these recommendations

- dataset: is an identifiable data that can be accessed separately. A dataset can be a part of a whole (series) or a segregate resource

- series: is a collection of resources or related datasets that share the same product specification

- service: technologies providing availability and access to spatialinformation, for example, web map services, web feature services,web coverage services, web processing services, catalogue webservices, etc



<gmd:hierarchyLevel><gmd:MD_ScopeCode

codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/gmxCodelists.xml#MD_ScopeCode" codeListValue="dataset">dataset</gmd:MD_ScopeCode>

</gmd:hierarchyLevel>...</gmd:MD_Metadata>

2.2.4 Resource locator

2.2.4.1 Resource Locator for data sets and dataset series

The Resource Locator is the ‘navigation section’ of a metadata record which point users to the location (URL) where the data can be downloaded, or to where additional information about the resource may be provided. Setting up the correct resource locators is important for the connection between the data and the services that provide access to them or for providing additional information concerning the resource.

24

1

234

5

67

8

9

10

11

1213

1415

1617

18192021

22232425262728293031323334353637383940

41

424344454647484950

1

Metadata element name Resource locator


Definition Location (address) for on-line access using a Uniform Resource Locator address or similar addressing scheme

ISO 19115 number and name 397. linkage

ISO/TS 19139 path distributionInfo/*/transferOptions/*/onLine/*/linkage

INSPIRE obligation / condition Conditional for spatial dataset and spatial dataset series: Mandatory if a URL is available to obtain more information on the resources and/or access related services.

INSPIRE multiplicity [0..*]

Data type (and ISO 19115 no.) URL

Domain URL (IETF RFC1738 and IETF RFC 2056)

Example http://edo.jrc.ec.europa.eu/chm/ows.php?VERSION=1.3.0&SERVICE=WMS&REQUEST=GetCapabilities

Comments A Resource Locator could be described, moreover, by other additional elements as a Title, a Description and a Function. In that case, the Title and the Description shall be free text and the Function shall be filled by the CI_OnLineFunctionCode (ISO 19115 codelist). Example of Resource Locator with these additional elements: Linkage: http://edo.jrc.ec.europa.eu/chm/ows.php?

VERSION=1.3.0&SERVICE=WMS&REQUEST=GetCapabilities

Title: JRC EDO (European Drought Observatory) - Drought Indexes WMS

Description: WMS delivering maps of drought indexes provided by the European Drought Observatory (EDO).

Function: information

TG Requirement 3 If a linkage for data is available, the Resource Locator shall be a valid URL providing one of the following:

- a link to a web page with further instructions

- a link to a service capabilities document

- a link to the service WSDL document (SOAP Binding)

- a link to a client application that directly accesses the service data

TG Recommendation 7 If no direct link to a resource is available, provide link to a contact point where more information about the resource is available.


<gmd:MD_Metadata ……

<gmd:distributionInfo><gmd:MD_Distribution>

…

25

12

34

5

6

7

8

910

1112

13141516171819202122

1

<gmd:transferOptions><gmd:MD_DigitalTransferOptions>

<gmd:onLine><gmd:CI_OnlineResource>

<gmd:linkage><gmd:URL>http://edo.jrc.ec.europa.eu/chm/ows.php?

VERSION=1.3.0&SERVICE=WMS&REQUEST=GetCapabilities</gmd:URL></gmd:linkage>

<!—Name and description are optional elements not required by INSPIRE -->

<gmd:name><gco:CharacterString>JRC EDO (European Drought

Observatory) - Drought Indexes WMS</gco:CharacterString></gmd:name><gmd:description>

<gco:CharacterString>WMS delivering maps of drought indexes provided by the European Drought Observatory (EDO)</gco:CharacterString>

</gmd:description><gmd:function>

<gmd:CI_OnLineFunctionCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#CI_OnLineFunctionCode" codeListValue="information">information</gmd:CI_OnLineFunctionCode>

</gmd:function></gmd:CI_OnlineResource>

</gmd:onLine></gmd:MD_DigitalTransferOptions>

</gmd:transferOptions></gmd:MD_Distribution>

</gmd:distributionInfo>…</gmd:MD_Metadata>

2.2.4.2 Resource Locator for Services

The Resource Locator for Services, if available, provides the access point of the service, that is an Internet address containing a detailed description of a spatial data service, including a list of endpoints to allow an automatic execution.






INSPIRE obligation / condition Conditional for services: Mandatory if linkage to the service is available




Example http://www.dinoservices.nl/geo3dmodelwebservices-1/Geo3DModelService

26

123456789

1011121314151617181920212223242526272829303132333435

36373839404142

1

http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#CI_OnLineFunctionCode



Comments

TG Requirement 4 If a linkage for a service is available, the Resource Locator shall be a valid URL providing one of the following:

- a link to a web with further instructions

- a link to a service capabilities document

- a link to the service WSDL document (SOAP Binding)

- a link to a client application that directly accesses the service

TG Recommendation 8 If no direct link to a resource is available, provide link to a contact point where more information about the resource is available.



<gmd:distributionInfo><gmd:MD_Distribution>

…<gmd:transferOptions>

<gmd:MD_DigitalTransferOptions><gmd:onLine>

<gmd:CI_OnlineResource><gmd:linkage>

<gmd:URL> http://www.dinoservices.nl/geo3dmodelwebservices-1/Geo3DModelService /</gmd:URL>

</gmd:linkage></gmd:CI_OnlineResource>

</gmd:onLine></gmd:MD_DigitalTransferOptions>

</gmd:transferOptions></gmd:MD_Distribution>

</gmd:distributionInfo>…</gmd:MD_Metadata>

2.2.4.3 Resource Locator for invocable Spatial Data services

The Resource Locator metadata element set out in “Implementing Rules for Metadata” shall also contain all access points from the spatial data service provider and these access points shall be unambiguously identified as such, using the resource locator function code

The access point of the service, is an Internet address containing a detailed description of a spatial data service, including a list of endpoints to allow an automatic execution.

TG Requirement 5 An invocable spatial data service shall have at least one resource locator that is an access point.

27

12

34

5

6

7

8

910

1112

1314151617181920212223242526272829303132333435363738

394041424344454647

4849

50

1

TG Requirement 6 The Resource Locator metadata element set out in Regulation (EC) No 1205/2008 shall also contain all access points from the spatial data service provider and these access points shall be unambiguously identified as such.


Reference COMMISSION REGULATION (EU) No 1089/2010, Annex V, Part D 1




INSPIRE obligation / condition Mandatory for invocable spatial data services




Example http://www.dinoservices.nl/geo3dmodelwebservices-1/Geo3DModelService

Comments

Metadata element name Function

Reference COMMISSION REGULATION (EU) No 1089/2010, Annex V, Part D 1

Definition Detailed text description of what the online resource is/does

ISO 19115 number and name 401. description

ISO/TS 19139 path distributionInfo/*/transferOptions/*/onLine/*/description



Data type (and ISO 19115 no.) Free text

Domain Codelist, see section 1.3.3

Example accessPoint

Comments


<gmd:MD_Metadata …… <gmd:distributionInfo> <gmd:MD_Distribution>… <gmd:transferOptions> <gmd:MD_DigitalTransferOptions> <gmd:onLine> <gmd:CI_OnlineResource> <gmd:linkage>

28

1234

56

789

1011121314151617181920212223

1


I will add that to the wiki, it was the suggestion of Eliane to change this so this is in line with ISO, in stead of replacing the codelist and have an non iso XML

Michael Östling, 07/15/15,

This was previously handled as OnLineFunction codeWhar arguments have we used to move it to description field (pro/con)

<gmd:URL> http://www.dinoservices.nl/geo3dmodelwebservices-1/Geo3DModelService </gmd:URL> </gmd:linkage> <gmd:description> <gco:CharacterString>accessPoint</gco:CharacterString> </gmd:description> </gmd:CI_OnlineResource> </gmd:onLine> </gmd:MD_DigitalTransferOptions> </gmd:transferOptions> </gmd:MD_Distribution> </gmd:distributionInfo>…</gmd:MD_Metadata>

2.2.5 Unique resource identifier

This element is a value uniquely identifying the resource. Within the INSPIRE infrastructure this is used as a reference to realize the data-service-coupling (2.2.6).

Metadata element name Unique resource identifier


Definition Value uniquely identifying an object within a namespace

ISO 19115 number and name 365. identifier

ISO/TS 19139 path identificationInfo[1]/*/citation/*/identifier

INSPIRE obligation / condition Mandatory for dataset and dataset series

INSPIRE multiplicity [1..*] for dataset and series

Data type (and ISO 19115 no.) 205. MD_Identifier

Domain URI (IETF RFC 3986)See B.2.7.3 of ISO 19115

Example namespace: https://example.org/ identifier: ab749859

code: https://example.org/ab749859(unique identifier with code + codeSpace) code: lakes codeSpace: urn:eu:europa:ec:jrc:rdsi:id:dataset:ccm2.1

Comments The unique resource identifier is needed to provide a queryable information when following data-service-coupling (see also 2.2.6). Therefore it is necessary to have the identifier itself together with the namespace in element code. The use of RS_Identifier (with a separate element codeSpace) is not suitable here

TG Requirement 7 The code property is required (see B.2.7.3 of ISO 19115). The code property is required. It is a URI that consists of a namespace and an identifier that is unique within the context of the namespace

29

123456789

101112131415161718

192021222324

2526

272829

1

TG Requirement 8 If a value for codeSpace is provided, then the data type for the identifier shall be RS_Identifier, which is substitutable for the usual MD_Identifier.

TG Recommendation 9 Never delete an existing identifier for a resource. If a change in resource identification is needed, add a new identifier but also keep the old one.

30

1

2

345

6

789

10

1



<gmd:identificationInfo><gmd:MD_DataIdentification id="lakes" >


…<gmd:identifier>

<gmd:RS_Identifier> <gmd:code> <gco:CharacterString>lakes</gco:CharacterString> </gmd:code> <gmd:codeSpace> <gco:CharacterString> urn:eu:europa:ec:jrc:rdsi:id:dataset:ccm2.1</gco:CharacterString> </gmd:codeSpace> </gmd:RS_Identifier>

<gmd:MD_Identifier> <gmd:code>

<gco:CharacterString>https://example.org/ab749859

</gco:CharacterString> </gmd:code> </gmd:MD_Identifier>

</gmd:identifier></gmd:CI_Citation>

</gmd:citation>…

</gmd:MD_DataIdentification></gmd:identificationInfo>

…</gmd:MD_Metadata>

2.2.6 Coupled resource

If the resource is a spatial data service, this metadata element refers to, where relevant, the target spatial data set(s) of the service. It is implemented by reference, , i.e. by providing the URI (see 2.2.5) giving the resource identifier for the datasets on which the service operates on. Recommended is also to give a URL that points to the metadata record of the data on which the service operates. It helps therefore linking services to the relevant datasets.

To reference the dataset(s) that the service operates on either of the XML the attribute @xlink:href or @uuidref shallcan be used.

TG Requirement 9 The property shall be implemented by reference using the XML attribute xlink:href or uuidref to reference the resource identifier of dataset (see SC11 in 1.2 and 2.2.5).

TG Recommendation 10 (9a) If the URI is a dereferenceable URL, pointing to the metadata record of the resource, t shall at least be provided through the xlink:href attribute.

TG Recommendation 11 (9b) If the URI is not a dereferenceable URL is shall be provided through the uuidref attribute.

31

123456789

1011121314151617181920212223242526272829303132333435

3637383940414243444546

474849

5051

525354

55

5657

1

Seiler, Martin, 05/12/15,

I suggest not to mention this here, as it’s a bit confusing and acutally the construction of URIs is up to that other group.

If the URI is not a dereferenceable URL, pointing to the metadata record of the resource, a URL to the resources’ record can be provided in the xlink attribute additionally to facilitate the direct linking of resources. This could e.g. be a direct link to an XML file, a GetRecordById request or a GetRecords request.

Note: The usage of @uuidref to provide the URI (2.2.5) here is not compliant to ISO 19118. However, to ensure backwards compatibility to broadly implemented solutions, it is considered acceptable.

Since only giving a uuidref will not be enough to find the resource in case the identifier is not a URL it is recommended to in addition to having a uuidref to also add a xlink:href with the URL to the metadata record for the dataset.This can either be done using a GetRecords request using the OperatesOn queryable with the resource identifier(example ..)

If a GetRecords request is not possible, (eg in the case the CSW-catalogue does not support the GET request for OperatesOn) then a URL to the metadata record could be given (eg a GetrecordsByID could be given with the datasets fileIdentifier as argument).(example ..)TG Reccomendation xx(9b ?) Add a url to the metadata record that describes the dataset the service operates on. If possible use a GetRecords query against a CSW using the OperatesOn queryable.If that is not possible use a GetrecordsById request using the metadata fileIdentifier as argument or reference directly a physical xml-file.

i.e. through a URL that points to the metadata record of the data on which the service operates. It helps therefore linking services to the relevant datasets.

Metadata element name Coupled resource


Definition Provides information about the datasets that the service operates on.

ISO 19119 number and name 9 of table C.1. operatesOn

ISO/TS 19139 path identificationInfo[1]/*/operatesOn

INSPIRE obligation / condition Not applicable to dataset and dataset series Conditional to services: Mandatory if linkage to datasets on

which the service operates are available.INSPIRE multiplicity [0] for datasets and series

[0..*] for services

Data type (and ISO 19115 no.) 36. MD_DataIdentification

Domain A unique resource identifier or locator (URL) of the MD_DataIdentification object

Example http://vap-xgeodev.jrc.ec.europa.eu/geonetwork/srv/eng/csw?SERVICE=CSW&VERSION=2.0.2&REQUEST=GetRecordById&ID=f9ee6623-cf4c-11e1-9105-0017085a97ab&OUTPUTSCHEMA=http://www.isotc211.org/2005/gmd&ELEMENTSETNAME=full#lakes

Comments

TG Requirement 10 The property shall be implemented by reference (see SC11 in 1.2).


32

123456789

101112131415

17181920212223242526272829

30

31

323334

1

Seiler, Martin, 05/12/15,

Specific CSW constraints are out of scope here.

http://vap-xgeodev.jrc.ec.europa.eu/geonetwork/srv/eng/csw?SERVICE=CSW&VERSION=2.0.2&REQUEST=GetRecordById&ID=f9ee6623-cf4c-11e1-9105-0017085a97ab&OUTPUTSCHEMA=http://www.isotc211.org/2005/gmd&ELEMENTSETNAME=full#lakes



<gmd:MD_Metadata …… <gmd:identificationInfo> <srv:SV_ServiceIdentification>… <srv:operatesOn xlink:href="http://vap-xgeodev.jrc.ec.europa.eu/geonetwork/srv/eng/csw?SERVICE=CSW&VERSION=2.0.2&REQUEST=GetRecordById&ID=f9ee6623-cf4c-11e1-9105-0017085a97ab&OUTPUTSCHEMA=http://www.isotc211.org/2005/gmd&ELEMENTSETNAME=full#lakes"/>… </srv:SV_ServiceIdentification>… </gmd:identificationInfo>…</gmd:MD_Metadata>Metadata element name Coupled resource


Definition Provides information about the datasets that the service operates on.

ISO 19119 number and name 9 of table C.1. operatesOn

ISO/TS 19139 path identificationInfo[1]/*/operatesOn

INSPIRE obligation / condition Not applicable to dataset and dataset series Conditional to services: Mandatory if linkage to datasets on

which the service operates are available.INSPIRE multiplicity [0] for datasets and series

[0..*] for services

Data type (and ISO 19115 no.) 36. MD_DataIdentification.citation.CI_Citation.identifier.MD_Identifier.code

Domain A unique resource identifier (2.2.5)and optionally a locator (URL) to the metadata record for the dataset (from where the MD_DataIdentification object can retrieved)

Example The mandatory uuidref xlink <srv:operatesOn xlink:href="https://example.org/ab749859" />

xlink and uuidref<srv:operatesOn xlink:href=https://example.org/ab749859 uuidref="https://example.org/ab749859" />

uuidref<srv:operatesOn uuidref="https://example.org/ab749859" />

<srv:operatesOn uuidref=" https://example.org/ab749859" />

GetRecords request using OperatesOn attributehttps://www.geodata.se/geonetwork/srv/swe/csw?request=GetRecords&service=CSW&version=2.0.2&resultType=results&typeNames=gmd:MD_Metadata&outputSchema=http://www.isotc211.org/2005/gmd&elementSetName=full&constraintLanguage=CQL_TEXT&constraint_language_version=1.1.0&constraint=ResourceIdentifier like ‘https://example.org/ab749859'

GetrecordById request

33

123456789

101112131415

1

https://example.org/ab749859




https://www.geodata.se/geonetwork/srv/en/csw?request=GetRecordById&service=CSW&version=2.0.2&elementSetName=full&id=a20dee7a-ca67-4dc0-8426-11dbfa16c94e&outputSchema=csw:IsoRecord

Comments

Example of XML encoding:In the example a service operates on a dataset with resource identifier = https://example.org/ab749859 and where metadata for the resource have the fileidentifier=a20dee7a-ca67-4dc0-8426-11dbfa16c94e

First example is with only an xlink uuidref to resource identifier<gmd:MD_Metadata …… <gmd:identificationInfo> <srv:SV_ServiceIdentification>… <srv:operatesOn uuidref=xlink:href=" https://example.org/ab749859"/>… </srv:SV_ServiceIdentification>… </gmd:identificationInfo>…</gmd:MD_Metadata>

Second example is with both the mandatory uuidrefURI (here encoded as uuidref) and the an additional recommended xlink:href to a GetRecords request using the oOperatesOn argument pointing to the same resource identifier.<gmd:MD_Metadata …… <gmd:identificationInfo> <srv:SV_ServiceIdentification>… <srv:operatesOn uuidref=" https://example.org/ab749859 f9ee6623-cf4c-11e1-9105-0017085a97ab" xlink:href="https://www.geodata.se/geonetwork/srv/swe/csw?request=GetRecords&service=CSW&version=2.0.2&resultType=results&typeNames=csw:Record&outputSchema=csw:IsoRecord&elementSetName=full&constraintLanguage=CQL_TEXT&constraint_language_version=1.1.0&constraint=ResourceIdentifier like ‘https://example.org/ab749859'"/>… </srv:SV_ServiceIdentification>… </gmd:identificationInfo>…</gmd:MD_Metadata>

Third example is with both the mandatory URI and an uuidref and the recommendedadditional xlink :href to the metadata record, here by linking to GetRecordById request to a CSW-catalogue.<gmd:MD_Metadata …… <gmd:identificationInfo> <srv:SV_ServiceIdentification>… <srv:operatesOn uuidref=" https://example.org/ab749859" xlink:href="https://www.geodata.se/geonetwork/srv/en/csw?request=GetRecordById&service=CSW&version=2.0.2&elementSetName=full&id= a20dee7a-ca67-4dc0-8426-11dbfa16c94e &outputSchema=csw:IsoRecord

34

123456789

1011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556

1




/>… </srv:SV_ServiceIdentification>… </gmd:identificationInfo>…</gmd:MD_Metadata>

2.2.7 Resource language

It refers to the language(s) used within the resource (dataset, series, or service if relevant).

Metadata element name Resource language


Definition Language(s) used within the datasets

ISO 19115 number and name 39. language

ISO/TS 19139 path identificationInfo[1]/*/language

INSPIRE obligation / condition Conditional for spatial dataset and spatial dataset series: Mandatory if the resource includes textual information.

Not applicable to services

INSPIRE multiplicity [0..*] for datasets and series[0] for services

Data type (and ISO 19115 no.) LanguageCode (ISO/TS 19139)

Domain Codelist (See ISO/TS 19139) based on alpha-3 codes of ISO 639-2. Use only three-letter codes from in ISO 639-2/B (bibliographic codes),

The list of codes for the 24 official EU languages is:Bulgarian – bul Irish – gleCroatian – hrv Italian – itaCzech – cze Latvian – lavDanish – dan Lithuanian – litDutch – dut Maltese – mltEnglish – eng Polish – polEstonian – est Portuguese – porFinnish – fin Romanian – rumFrench – fre Slovak – sloGerman – ger Slovenian – slvGreek – gre Spanish – spaHungarian – hun Swedish – swe

The list of all the codes is defined at http://www.loc.gov/standards/iso639-2/ Regional languages also are included in this list.

Example eng

Comments There are two ways of inserting the languagevalues in code-lists see section A.11 (see example XML encoding): most compliant: the element value is the name of the

codeListValue expressed in the default language of the metadata (ej: if the metadata is filled in English, the values should be English, Spanish, French…)

35

123456789

10

11121314

1

http://www.loc.gov/standards/iso639-2/

most interoperable: the element value repeats the codeListValue (ej: eng for English, spa for Spanish, fre for French…)

TG Requirement 11 The resource language is mandated by ISO 19115.

TG Requirement 12 The resource language has to be filled with a value from the codelist ISO/TS 19139 based on alpha-3 codes of ISO 639-2.

TG Recommendation 12 If the resource does not contain any textual information (e.g. only codes and digits), the language should be defaulted to the value of the metadata language.

Examples of XML encoding:

1) Most interoperable: the element value repeats the codeListValue

<gmd:language><gmd:LanguageCode codeList="http://www.loc.gov/standards/iso639-

2/" codeListValue="eng">eng</gmd:LanguageCode></gmd:language>

2) Most compliant: the element value is the name of the codeListValue expressed in the default language of the Metadata

<gmd:language><gmd:LanguageCode codeList="http://www.loc.gov/standards/iso639-

2/ " codeListValue="eng">English</gmd:LanguageCode></gmd:language>

2.3 Classification of spatial data and services

2.3.1 Topic category

The topic category is a high-level classification scheme to assist in the grouping and topic-based search of available spatial data resources.A correct categorization is very important to help users to search and find the resources they are looking for.

Metadata element name Topic category


Definition Main theme(s) of the dataset

ISO 19115 number and name 41. topicCategory

ISO/TS 19139 path identificationInfo[1]/*/topicCategory

INSPIRE obligation / condition Mandatory for datasets and dataset series Not applicable to services

INSPIRE multiplicity [1..*] for datasets and dataset series[0] for services

36

1

2

34

56

7

89

10

111213141516171819202122232425262728

29

303132333435363738

1

Data type (and ISO 19115 no.) MD_TopicCategory

Domain Enumeration (See B.5.27 of ISO 19115 or Part D 2 of the INSPIRE Metadata Regulation 1205/2008/EC)

Example climatologyMeteorologyAtmosphere

Comments The topic categories defined in Part D 2 of the INSPIRE Metadata Regulation 1205/2008/EC are derived directly from the topic categories defined in MD_TopicCategoryCode (B.5.27 of ISO 19115)

TG Requirement 13 The topic category has to be filled with a value from the enumeration MD_TopicCategoryCode (ISO 19115).

TG Requirement 14 The value saved in the XML metadata element shall be a language neutral name (see the value appearing in the “name” column of the table in B.5.27 of ISO 19115).




…<gmd:topicCategory>

<gmd:MD_TopicCategoryCode>climatologyMeteorologyAtmosphere</gmd:MD_TopicCategoryCode>

</gmd:topicCategory>…



37

12

34

5

678

91011121314151617181920212223242526272829

1

2.3.2 Spatial data service type

This is a classification to assist in the search of available spatial data services. The list of language-neutral values as in Part D3 of the INSPIRE Metadata Regulation 1205/2008/EC includes: discovery, view, download, transformation, invoke and other.

If the service is also an INSPIRE Network Services, then it is necessary to include in the Metadata element 2.8.2 Specifications, reference to the relevant INSPIRE Network Service Implementing Rule or amendment (see also 2.8.2)

Metadata element name Spatial data service type


Definition A service type name from a registry of services

ISO 19119 number and name 1 of table C.1. serviceType

ISO/TS 19139 path identificationInfo[1]/*/serviceType

INSPIRE obligation / condition Not applicable to datasets and dataset series Mandatory for services

INSPIRE multiplicity [1] for services[0] for datasets and dataset series

Data type (and ISO 19115 no.) GenericName

Domain List of values. See section 1.3.1 in this document

Example view

Comments

TG Requirement 15 Use language neutral name from table in 1.3.1.



<gmd:identificationInfo><srv:SV_ServiceIdentification>

…<srv:serviceType>

<gco:LocalName>view</gco:LocalName></srv:serviceType>

…</srv:SV_ServiceIdentification>

</gmd:identificationInfo></gmd:MD_Metadata>

38

123456789

1011

12

13

14151617181920212223242526272829

1

2.4 Keyword

An INSPIRE Keyword is defined by: a keyword value (see 2.4.1), which in ISO standard is referred to as “Keyword”; an optional originating controlled vocabulary (see 2.4.2), which in ISO standard is

referred to as “Thesaurus”. It is possible to add as many keywords as relevant to the resource.

TG Requirement 16 The INSPIRE Metadata Regulation 1205/2008/EC mandate the presence of at least one keyword.

TG Requirement 17 If only one keyword is used, then for spatial dataset or spatial dataset series, the keyword:

- shall describe the relevant INSPIRE Spatial Data Theme (as defined in Annex I, II and III of the INSPIRE Directive)

- shall be expressed in the language of the metadata for the 34

INSPIRE Spatial Data Themes (please use the terms in each of the

official languages in which the INSPIRE Directive has been translated) or a neutral language values such as a URI.

The titles and definitions of all 34 INSPIRE Spatial Data Themes have been integrated into a dedicated branch of the General Environmental Multilingual Thesaurus (GEMET) in the 24 official Community languages (see http://www.eionet.europa.eu/gemet/inspire_themes). This special branch is known as “GEMET - INSPIRE themes”.

TG Requirement 18 For spatial services, the keyword:

- shall at least define the category or subcategory of the service using its language neutral name as defined in Part D 4 of the INSPIRE Metadata Regulation 1205/2008/EC

- shall be expressed as neutral language values such as the neutral

language values defined in Part D.4 of the INSPIRE Metadata Regulation 1205/2008/EC for spatial data services)

In addition to the mentioned thesaurus also other keywords might be added. These may be described as a free text or may originate from any Controlled Vocabulary.

TG Requirement 19 If other keywords are added and they originate from a Controlled Vocabulary (thesaurus or ontology), for example GEMET - Concepts, EUROVOC or AGROVOC, then the citation of the originating Controlled Vocabulary shall be provided.

For example, a keyword that comes from GEMET - Concepts shall be cited as follows: keyword: freshwater thesaurus title: GEMET - Concepts, version 2.4 thesaurus date: 2010-01-13

39

12345678

910

11

1213

1415

161718192021

22232425262728

29

303132

33343536

373839

40

41424344

4546474849

1

http://www.eionet.europa.eu/gemet/inspire_themes

thesaurus date type: publication

Or a keyword that comes from AGROVOC shall be cited as follows: keyword: water springs thesaurus title: AGROVOC thesaurus date: 2008-04-14 thesaurus date type: publication

2.4.1 Keyword value

The keyword value is a commonly used word, formalised word or phrase used to describe the subject. While the topic category is too coarse for detailed queries, keywords help narrowing a full text search and they allow for structured keyword search

Metadata element name Keyword value


Definition Commonly used word(s) or formalised word(s) or phrase(s) used to describe the subject

ISO 19115 number and name 53. keyword

ISO/TS 19139 path identificationInfo[1]/*/descriptiveKeywords/*/keyword




Domain Free text

Example Atmospheric conditions (INSPIRE Spatial Data Theme)humanCatalogueViewer (spatial data service subcategory)water springs (AGROVOC)rain water (GEMET Concepts)

Comments Each instance of ISO 19115 keyword may originate from a controlled vocabulary described through the thesaurusName property of the instance of descriptiveKeywords to which the keyword pertains

TG Recommendation 13 It is better to select keyword values from a collection of terms linked and predefined (controlled vocabularies).

TG Recommendation 14 It is suggested to choose a minimum of two keywords in addition to the required keyword from the GEMET - INSPIRE themes (for dataset and dataset series) or the categories from part D 4 of the INSPIRE Metadata Regulation 1205/2008/EC (for services).

TG Recommendation 15 Ideally, both a code (neutral language value) and a human-readable label (in any language) should be included in the metadata.

Here is an example of XML encoding of the keyword value for a spatial data services category or subcategory as defined in Part D.4 of the INSPIRE Metadata Regulation 1205/2008/EC.

40

12345678

9101112131415

16

1718

19

20212223

24

2526

27282930

1


<gmd:identificationInfo><srv:SV_ServiceIdentification >

…<gmd:descriptiveKeywords>

<gmd:MD_Keywords><gmd:keyword>

<gco:CharacterString> humanCatalogueViewer</gco:CharacterString></gmd:keyword><gmd:thesaurusName> …(see 2.4.2)</gmd:thesaurusName>

</gmd:MD_Keywords></gmd:descriptiveKeywords>

</srv:SV_ServiceIdentification ></gmd:identificationInfo>


An INSPIRE aware tool is expected to manage the neutral language values (e.g. humanCatalogueViewer), of the service category or subcategory and eventually display the corresponding value in a language chosen by the user (e.g. Visualiseur de catalogue in French).

Here is an example of XML encoding for a keyword referring to a spatial data set. Whether the keyword refers to an INSPIRE spatial data theme or not, is defined by the originating controlled vocabulary (see 2.4.2)





<gco:CharacterString>Atmospheric conditions </gco:CharacterString>

</gmd:keyword><gmd:thesaurusName>…(see 2.4.2)</gmd:thesaurusName>

</gmd:MD_Keywords></gmd:descriptiveKeywords>



41

123456789

1011121314151617181920212223242526272829303132333435363738394041424344454647484950515253

1

2.4.2 Originating controlled vocabulary

TG Requirement 20 If the keyword value originates from a controlled vocabulary (thesaurus, ontology), for example GEMET - Concepts, the citation of the originating controlled vocabulary shall be provided.

TG Requirement 21 The thesaurusName identification shall include at least the title and a reference date (date of publication, date of last revision or of creation) of the originating controlled vocabulary.

Metadata element name Originating controlled vocabulary


Definition Name of the formally registered thesaurus or a similar authoritative source of keywords

ISO 19115 number and name 55. thesaurusName

ISO/TS 19139 path identificationInfo[1]/*/descriptiveKeywords/*/thesaurusName

INSPIRE obligation / condition Conditional: Mandatory if the keyword value originates from a controlled vocabulary

INSPIRE multiplicity [0..1] relative to a single Keyword, but there may be many keywords originating from different controlled vocabularies

Data type (and ISO 19115 no.) CI_Citation

Domain The following properties are expected: Title (characterString and free text) Reference date (CI_Date):

o dateType: creation, publication or revisiono date: an effective date

Example Identification for a keyword originating from GEMET- INSPIRE themes: title: GEMET - INSPIRE themes, version 1.0 date:

o dateType: publicationo date: 2008-06-01

Identification for a keyword originating from GEMET - Concepts: title: GEMET - Concepts, version 2.4 date:


Identification for a keyword originating from AGROVOC: title: AGROVOC date:


Comments

42

12

345

6

789

10

11

1

TG Requirement 22 In order to be consistent with ISO 19115, all the keyword values originating from a single version of a single controlled vocabulary shall be grouped in a single instance of the ISO 19115 descriptiveKeywords property. See also SC17 for datasets and series, and SC18 for Services.

TG Recommendation 16 It is important to specify which version of the thesaurus was used to take the keyword value from.

Example of XML encoding for keyword referring to an INSPIRE Spatial Data Theme





…(see 2.4.1)</gmd:keyword><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><gmd:dateType>

<gmd:CI_DateTypeCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#CI_DateTypeCode" codeListValue="publication">publication</gmd:CI_DateTypeCode>

</gmd:dateType></gmd:CI_Date>

</gmd:date></gmd:CI_Citation>

</gmd:thesaurusName></gmd:MD_Keywords>

</gmd:descriptiveKeywords></gmd:MD_DataIdentification>

</gmd:identificationInfo>…</gmd:MD_Metadata>

43

1

23456

7

89

101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354

1

2.5 Geographic location

2.5.1 Geographic bounding box

This is the extent of the resource in the geographic space, given as a bounding box. Defining the coordinates of a rectangle representing the resource area on a map allows the discovery by geographical area

Metadata element name Geographic bounding box


Definition Western-most coordinate of the limit of the dataset extent, expressed in longitude in decimal degrees (positive east).Eastern-most coordinate of the limit of the dataset extent, expressed in longitude in decimal degrees (positive east)Northern-most coordinate of the limit of the dataset extent, expressed in latitude in decimal degrees (positive north)Southern-most coordinate of the limit of the dataset extent, expressed in latitude in decimal degrees (positive north).

ISO 19115 number and name 344. westBoundLongitude345. eastBoundLongitude346. southBoundLatitude347. northBoundLatitude

ISO/TS 19139 path identificationInfo[1]/*/extent/*/geographicElement/*/westBoundLongitudeidentificationInfo[1]/*/extent/*/geographicElement/*/eastBoundLongitudeidentificationInfo[1]/*/extent/*/geographicElement/*/southBoundLatitudeidentificationInfo[1]/*/extent/*/geographicElement/*/northBoundLatitude

INSPIRE obligation / condition Mandatory for datasets and spatial dataset series Conditional for spatial services: mandatory for services with an

explicit geographic extent

INSPIRE multiplicity [1..*] for spatial data sets and spatial dataset series[0..*] for spatial data services

Data type (and ISO 19115 no.) Decimal

Domain -180.00 ≤ westBoundLongitude ≤ 180.00-180.00 ≤ eastBoundLongitude ≤ 180.00-90.00 ≤ southBoundingLatitude ≤ 90.00-90.00 ≤ northBoundingLatitude ≤ 90.00

Example -15.00 (westBoundLongitude )45.00 (eastBoundLongitude )35.00 (southBoundLatitude)72.00 (northBoundLatitude)

Comments There may be as many bounding boxes defining the geographic location of the resource as instances of identificationInfo[1]/*/extent/*/geographicElement having the westBoundLongitude, eastBoundLongitude, southBoundLatitude and northBoundLatitude properties. The four coordinates of the bounding box originate from the same

44

1

234567

1

instance. If the bounding box crosses the 180 meridian, then the value

of the westBoundLongitude will be greater than the eastBoundLongitude value.

The coordinates of the bounding box are expressed in any geodetic coordinate reference system with a Greenwich Prime Meridian (See SC13 in 1.2).

TG Requirement 23 The bounding box shall be as small as possible.

TG Requirement 24 The bounding box shall be expressed in decimal degree with a precision of at least 2 decimals.




…<gmd:extent>

<gmd:EX_Extent><gmd:geographicElement>

<gmd:EX_GeographicBoundingBox><gmd:westBoundLongitude>

<gco:Decimal>-15.00</gco:Decimal></gmd:westBoundLongitude><gmd:eastBoundLongitude>

<gco:Decimal>45.00</gco:Decimal></gmd:eastBoundLongitude><gmd:southBoundLatitude>

<gco:Decimal>35.00</gco:Decimal></gmd:southBoundLatitude><gmd:northBoundLatitude>

<gco:Decimal>72.00</gco:Decimal></gmd:northBoundLatitude>

</gmd:EX_GeographicBoundingBox></gmd:geographicElement>

</gmd:EX_Extent></gmd:extent>

…</gmd:MD_DataIdentification>


45

1

2

3

45

6789

10111213141516171819202122232425262728293031323334353637383940

1

2.6 Temporal reference

TG Requirement 25 The INSPIRE Metadata Regulation 1205/2008/EC requires at least one temporal reference chosen from one of these four categories:

- temporal extent

- date of publication

- date of last revision

- date of creation

ISO 19115 is more demanding than INSPIRE. Therefore, whilst providing a temporal extent would suffice to satisfy the INSPIRE Metadata Regulation 1205/2008/EC it is not enough to be compliant with ISO 19115.

TG Requirement 26 To be compliant with ISO 19115 it is necessary to use at least one among date of publication, date of last revision, or the date of creation.

TG Recommendation 17 In case of spatial data set, report at least the date of the last revision of the spatial data set

TG Requirement 27 The default reference system shall be the Gregorian calendar, with dates expressed in accordance with ISO 8601 (yyyy-mm-dd where yyyy is the year, mm is the month and dd is the day).

2.6.1 Temporal extent

The temporal extent defines the time period covered by the content of the resource. This time period may be expressed as:

an individual date an interval of dates (starting date and ending date) a mix of individual dates and intervals of dates

Metadata element name Temporal extent


Definition Time period covered by the content of the dataset

ISO 19115 number and name 351. extent

ISO/TS 19139 path identificationInfo[1]/*/extent/*/temporalElement/*/extent

INSPIRE obligation / condition Conditional: At least one temporal reference is required

INSPIRE multiplicity [0..*] for temporal extent but at least one temporal reference is required

Data type (and ISO 19115 no.) TM_Primitive7

7 ISO19108 describes other domains which might support the INSPIRE requirements for temporal metadata. There are no implementations currently known. ISO19108 allows ordinal temporal extents (TM_Position values of TM_OrdinalEras defined within a TM_OrdinalReferenceSystem) and an indeterminate value of “now” is valid under

46

12

345

6

7

8

9

10111213

141516

17

1819

20

21222324

25

2627282930313233

123

4

Domain As described in ISO 19108

Example From 2008-01-01T11:45:30 to 2008-12-31T09:10:00

Comments The overall time period covered by the content of the resource may be composed of one or many instances




…<gmd:extent>

<gmd:EX_Extent><gmd:temporalElement>

<gmd:EX_TemporalExtent><gmd:extent>

<gml:TimePeriod gml:id="IDd2febbb4-e66f-4ac8-ba76- 8fd9bc7c8be6">

<gml:beginPosition>2008-01-01T11:45:30</gml:beginPosition><gml:endPosition>2008-12-31T09:10:00 </gml:endPosition></gml:TimePeriod>

</gmd:extent></gmd:EX_TemporalExtent>

</gmd:temporalElement></gmd:EX_Extent>

</gmd:extent>…

</gmd:MD_DataIdentification>…


2.6.2 Date of publication

This is the date of publication of the resource when available, or the date of entry into force. There may be more than one date of publication. Date of publication differs from the temporal extent. For example, a dataset might have been published in March 2009 (2009-03-15) but the covered information was collected over the year 2008 (temporal extent from 2008-01-01 to 2008-12-31)

Metadata element name Date of publication


Definition Reference date for the cited resource - publication

ISO 19115 number and name 3692. date

ISO/TS 19139 path identificationInfo[1]/*/citation/*/date[./*/dateType/*/text()='publication']/*/date

INSPIRE obligation / condition Conditional: at least one date of publication / date of creation /

TM_Position. ISO 19108 TM_PeriodDuration also defines the distance in the temporal dimension

47

123456789

10111213141516171819202122232425262728293031323334

3536373839404142

1

2

date of revision is required

INSPIRE multiplicity [0..*] but at least one date of publication / date of creation / date of revision or one temporal extent is required

Data type (and ISO 19115 no.) 393. CI_Date

Domain Described in ISO 19108 and ISO 8601

Example 2009-03-152009-03-15T11:15:00

Comments





…<gmd:date>



<gmd:CI_DateTypeCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#CI_DateTypeCode" codeListValue="publication">publication</gmd:CI_DateTypeCode>


</gmd:date>…



…</gmd:identificationInfo>

...</gmd:MD_Metadata>

48

123456789

1011121314151617181920212223242526272829303132333435363738

1

2.6.3 Date of last revision

This date describes when the resource was last revised, if the resource has been revised. Date of revision differs from the temporal extent. For example, a dataset might have been revised in April 2009 (2009-04-15) but the covered information was collected over the year 2008 (temporal extent from 2008-01-01 to 2008-12-31)

Metadata element name Date of last revision


Definition Reference date for the cited resource - revision



INSPIRE obligation / condition Conditional: at least one date of publication / date of creation / date of revision is required

INSPIRE multiplicity [0..1] but at least one date of publication / date of creation / date of revision or one temporal extent is required



Example 2009-04-152009-04-15T11:15:00

Comments There may be more than one revision date provided in an ISO 19115 metadata, but INSPIRE will consider as date of last revision the more recent one





…<gmd:date>


<gco:DateTime>2009-04-15T11:15:00</gco:DateTime></gmd:date><gmd:dateType>

<gmd:CI_DateTypeCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#CI_DateTypeCode" codeListValue="revision">revision</gmd:CI_DateTypeCode>


</gmd:date>…



</gmd:identificationInfo>...

49

1234567

89

1011121314151617181920212223242526272829303132333435363738

1

</gmd:MD_Metadata>

2.6.4 Date of creation

This date describes when the resource was created. Date of creation differs from the temporal extent. For example, a dataset might have been created in February 2009 (2009-02-15) but the covered information was collected over the year 2008 (temporal extent from 2008-01-01 to 2008-12-31)

Metadata element name Date of creation


Definition Reference date for the cited resource - creation



INSPIRE obligation / condition Conditional: at least one date of publication / date of creation / date of revision is required

INSPIRE multiplicity [0..1] but at least one date of publication / date of creation / date of revision or one temporal extent is required



Example 2009-02-152009-02-15T11:15:00

Comments

TG Requirement 28 There shall be a single creation date for the resource (See SC7 in 1.2).

50

12

3456789

10

11

1213

14

1





…<gmd:date>



<gmd:CI_DateTypeCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#CI_DateTypeCode" codeListValue="creation">creation</gmd:CI_DateTypeCode>


</gmd:date>…



…</gmd:identificationInfo>


2.7 Quality and validity

2.7.1 Lineage

According to the Implementing Rules for Metadata, Lineage is “a statement on process history and/or overall quality of the spatial data set. Where appropriate it may include a statement whether the data set has been validated or quality assured, whether it is the official version (if multiple versions exist), and whether it has legal validity. The value domain of this element is free text.”

The process history may be described by information on the source data used and the main transformation steps that took place in creating the current data set (series).

Metadata element name Lineage


Definition General explanation of the data producer’s knowledge about the lineage of a dataset

ISO 19115 number and name 83. statement

ISO/TS 19139 path dataQualityInfo/*/lineage/*/statement

INSPIRE obligation / condition Mandatory for spatial dataset and spatial dataset series. Not applicable to services.

INSPIRE multiplicity [1] for datasets and data set series[0] for spatial data services

51

123456789

101112131415161718192021222324252627282930313233

34

353637383940414243444546

1


Domain Free text

Example Computation of the SPI involves fitting a probability density function to a given frequency distribution of precipitation totals for a station or grid point and for an accumulation period. We use the gamma probability density function. The statistics for the frequency distribution are calculated on the basis of a reference period of at least 30 years. The parameters of the probability density function are then used to find the cumulative probability of the observed precipitation for the required month and temporal scale. This cumulative probability is then transformed to the standardised normal distribution with mean zero and variance one, which results in the value of the SPI. The SPI values are computed using the so-called MARS weather stations as rainfall input data. Refer the MARS weather catalogue for characteristics of the quality and quantity of these data. We only rely on the rainfall data input

Comments

A single ISO 19115 metadata set may comprise more than one set of quality information (dataQualityInfo elements), each of them having one or zero lineage elements.

TG Requirement 29 There shall be one and only one set of quality information scoped to the full resource and having a lineage statement (dataQualityInfo element). This element shall be scoped to the full data set (series) and have one lineage element (See SC6 in 1.2). The statement sub-element of the lineage element shall be used to implement the Lineage element defined in the Implementing Rules for Metadata.

TG Recommendation 18 If a data provider has a procedure for the quality management of their spatial data set (series) then the appropriate ISO data quality elements and measures should be used to evaluate and report (in the metadata) the results. If not, the Lineage metadata element (defined in the Implementing Rules for Metadata) should be used to describe the overall quality of a spatial data set (series).

TG Recommendation 19 The use of acronyms should be avoided. If used, their meaning should be explained.

NOTE: The INSPIRE data specifications contain further recommendations for documenting the sources and process steps used for the creation of the data set (series), including its transformation to make it compliant with the Implementing Rules on interoperability of spatial data sets and services (see Annex B).

52

1234

56789

1011

12

131415161718

1920

2122

232425262728

1



<gmd:identificationInfo>...

</gmd:identificationInfo><gmd:dataQualityInfo>

<gmd:DQ_DataQuality><gmd:scope>

…</gmd:scope><gmd:report>

…</gmd:report><gmd:lineage>

<gmd:LI_Lineage><gmd:statement>

<gco:CharacterString>Computation of the SPI involves fitting a probability density function to a given frequency distribution of precipitation totals for a station or grid point and for an accumulation period. We use the gamma probability density function. The statistics for the frequency distribution are calculated on the basis of a reference period of at least 30 years. The parameters of the probability density function are then used to find the cumulative probability of the observed precipitation for the required month and temporal scale. This cumulative probability is then transformed to the standardised normal distribution with mean zero and variance one, which results in the value of the SPI. The SPI values are computed using the so-called MARS weather stations as rainfall input data. Refer the MARS weather catalogue for characteristics of the quality and quantity of these data. We only rely on the rainfall data input</gco:CharacterString>

</gmd:statement></gmd:LI_Lineage>

</gmd:lineage></gmd:DQ_DataQuality>

</gmd:dataQualityInfo></gmd:MD_Metadata>

2.7.2 Spatial resolution

Spatial resolution refers to the level of detail of the data set. It shall be expressed as a set of zero to many resolution distances (typically for gridded data and imagery-derived products) or equivalent scales (typically for maps or map-derived products). An equivalent scale is generally expressed as an integer value expressing the scale denominador. A resolution distance shall be expressed as a numerical value associated with a unit of length

Metadata element name Spatial resolution


Definition Equivalent scale: level of detail expressed as the scale denominator of a comparable hardcopy map or chart

Distance: ground sample distanceISO 19115 number and name 60. equivalentScale

61. distanceISO/TS 19139 path identificationInfo[1]/*/spatialResolution/*/equivalentScale/*/

denominator (equivalent scale)

53

123456789

101112131415161718192021222324252627282930313233343536373839404142

434445464748495051

1

identificationInfo[1]/*/spatialResolution/*/distance (distance)INSPIRE obligation / condition Conditional: Mandatory if an equivalent scale or a resolution

distance can be specified. Conditional: Mandatory when there is a restriction on the

spatial resolution for service.INSPIRE multiplicity [0..*]

Data type (and ISO 19115 no.) Integer (equivalent scale) Distance (distance)

Domain positive integer (equivalent scale) number expressing the distance value and a unit of measure

of the distance value (distance)Example 50000 (e.g. 1:50000 scale map)

0.25 (degrees)

Comments For services, it is not possible to express the restriction of a service concerning the spatial resolution in the current version of ISO 19119. While the problem is addressed by the standardization community, spatial resolution restrictions for services shall be expressed in the Abstract

TG Requirement 30 Each spatial resolution is either an equivalent scale OR a ground sample distance. Each spatialResolution element must contain either an equivalent scale or a distance but not both

TG Recommendation 20 When two equivalent scales or two ground sample distances are expressed, the spatial resolution is an interval bounded by these two values

54

1

234

5

678

9

1

Example of XML encoding (equivalentScale):


<gmd:identificationInfo>…

<gmd:MD_DataIdentification>…

<gmd:spatialResolution><gmd:MD_Resolution>

<gmd:distance>…(see next example)

</gmd:distance></gmd:MD_Resolution>

</gmd:spatialResolution><gmd:spatialResolution>

<gmd:MD_Resolution><gmd:equivalentScale>

<gmd:MD_RepresentativeFraction><gmd:denominator>

<gco:Integer>50000</gco:Integer></gmd:denominator>

</gmd:MD_RepresentativeFraction></gmd:equivalentScale>

</gmd:MD_Resolution></gmd:spatialResolution>



Example of XML encoding (distance):


<gmd:identificationInfo>…

<gmd:MD_DataIdentification>…

<gmd:spatialResolution><gmd:MD_Resolution>

<gmd:distance><gco:Distance uom="dd">0.25</gco:Distance>

</gmd:distance></gmd:MD_Resolution>

</gmd:spatialResolution><gmd:spatialResolution>

<gmd:MD_Resolution><gmd:equivalentScale>

…(see previous example)</gmd:equivalentScale>

</gmd:MD_Resolution></gmd:spatialResolution>



55

123456789

10111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364

1

2.8 ConformityTG Requirement 31 In conformance to INSPIRE Directive 2007/2/EC, the

metadata shall include information on the degree of conformity with the implementing rules on interoperability of spatial data sets and services8.

NOTE 1 All Data Specifications Technical Guidelines include an Abstract Test Suite (ATS) in Annex A describing through a number of tests how to evaluate conformity with the Implementing Rules on interoperability of spatial data sets and services.

NOTE 2 The ATS consists of several conformance classes that can be tested independently. This enables data providers to also report conformity to different aspects of the Implementing Rules in detail (see section 8 of the Data Specifications Technical Guidelines9).

TG Recommendation 21 If a spatial data service is also an INSPIRE Network Service, it is recommended to include in its metadata information on the degree of conformity with the implementing rules provided in Art 11 (Network Services).

ISO 19115 provides an element (DQ_ConformanceResult) for reporting about the evaluation of the conformity of the resource against a given specification. This element is used to handle the requirements to report on the conformity with the Implementing Rules on interoperability of spatial data sets and services or other specifications and standards.

TG Requirement 32 The INSPIRE Metadata Regulation 1205/2008/EC defines in Part D 5 When the conformity to any specification has been evaluated, it shall be reported as a domain consistency element (i.e. an instance of DQ_DomainConsistency) in ISO 19115 metadata

NOTE: The TG Requirement above applies to any specification against which the data has been tested, not just those established by INSPIRE. In other words, if a dataset is produced or transformed according to an external specification that includes specific quality assurance procedures, the conformity with this specification should be documented using the Conformity metadata element.

The Conformity element defined in section 7 of Part B of the INSPIRE Implementing Rules for metadata includes two sub-elements: the Specification (a citation of the specification against which conformity was tested), and the Degree of conformity. The Degree of conformity can take either of the following three values (see Part D.5 of the Implementing Rules):

i. conformant (if the dataset is fully conformant with the cited specification), ii. not conformant (if the dataset does not conform to the cited specification)iii. not evaluated (if the conformance has not been evaluated)

The case “not evaluated” was introduced as a transition measure because at the time of adoption of the Metadata Implementing Rules (2008) there were no INSPIRE specifications (Implementing rules on the interoperability of spatial datasets and services) against which conformance could be tested.

8 Commission Regulation (EU) No 1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services, OJ L 323, 08/12/2010, p. 11–102.

9 See http://inspire.jrc.ec.europa.eu/index.cfm/pageid/2

56

1

2345

6789

101112131415

16171819

202122232425

26272829

30313233343536373839404142434445464748

1234

5

TG Recommendation 22 Now that the Implementing Rules on the interoperability of spatial datasets and services are in place, it is recommended to evaluate and declare the conformity of all data sets (i.e. as “conformant” or “not conformant”).

NOTE: It is still possible to declare in the metadata that the conformity with the Implementing Rules on interoperability of spatial data sets and services was “not evaluated”. This however is difficult to implement using ISO 19115 which has only two degrees of conformity: conformant (true) or not conformant (false). The previous version of these guidelines have recommended to represent the value “not evaluated” by leaving the Conformity element empty. This makes the metadata record compliant with ISO but not with INSPIRE as the multiplicity of the Conformity element in the Metadata Implementing Rules is (1..*).

ISO 19139 provides a mechanism to provide a null value with an explanation (using the nilReason attribute).

TG Recommendation 23 To declare that the conformity with the Implementing Rules on the interoperability of spatial datasets and services has not yet been evaluated, a null value should be provided with a nilReason of “unknown”.

NOTE: A metadata record containing a null value for the Boolean-typed Pass element is not compliant with ISO 19115. However, it is compliant with ISO 19139 and widely implemented. In order to be sure to comply both with INSPIRE and ISO 19115, you are advised to follow TG Recommendation 22 above.

The conformance report metadata elements are also used for the citation of the status of the spatial data service versus invocability. In those elements the conformance levels for SDS category, invocable, interoperable or harmonised shall be reported, according to the different conformance levels of the data specifications.

TG Requirement 33 An invocable spatial data services shall be conform to one of the conformance levels; invocable, interoperable or harmonised

The Specification metadata element set out in Regulation (EC) No 1205/2008 shall also refer to or contain technical specifications (such as INSPIRE technical guidance but not only), to which the invocable spatial data service fully conforms, providing all the necessary technical elements (human, and wherever relevant, machine readable) to allow its invocation.’The specification metadata element needs to provide sufficient information to actually invoke the service and enable its usage.

TG Requirement 34 Invocable spatial data services contains the specification metadata element set out in Regulation (EC) No 1205/2008 that shall also refer to or contain technical specifications (such as INSPIRE technical guidance but not only), to which the invocable spatial data service fully conforms, providing all the necessary technical elements (human, and wherever relevant, machine readable) to allow its invocation.’

TG Requirement 35 Invocable spatial data services are in conformity with a documented and publicly available set of technical specifications providing the information necessary for its execution,

57

1234

56789

10111213141516

17181920

2122232425262728293031

3233

34353637383940

414243444546

47

484950

515253

1

2.8.1 Degree

This is the degree of conformity of the resource to the implementing rules adopted under Article 7(1) of INSPIRE Directive 2007/2/EC or other specification.

Metadata element name Degree


Definition Indication of the conformance result

ISO 19115 number and name 132. pass

ISO/TS 19139 path dataQualityInfo/*/report/*/result/*/pass


INSPIRE multiplicity [1] understood in the context of a conformity statement when reported in the metadata – there may be more than one conformity statement

Data type (and ISO 19115 no.) Boolean10

Domain true if conformant false if not conformant null (with nilReason = “unknown”) if not evaluated11

Example true

CommentsExample of XML encoding

…<gmd:result>

<gmd:DQ_ConformanceResult><gmd:specification>

… </gmd:specification>



<gmd:explanation><gco:CharacterString>See the referenced

specification</gco:CharacterString></gmd:explanation>

<gmd:pass><gco:Boolean>true<gco:Boolean>

</gmd:pass></gmd:DQ_ConformanceResult>

</gmd:result>

2.8.2 Specification

This is a citation of the implementing rules adopted under Article 7(1) of INSPIRE Directive 2007/2/EC or other specificationto which a particular resource conforms.

If a spatial data service is an INSPIRE Network service, use this element to report the relevant INSPIRE Network Implementing Rule to which it confirms.

10

11 ISO/TS 19103 defines Boolean as a value defining TRUE or FALSE (EXAMPLE: true or false), while ISO 19115:2003 clearly states that the domain of value of the Boolean properties is 0="no", 1="yes". In the meantime, ISO/TS 19139 implements the Boolean class using the XML build-in type xs:boolean (values are true or false), but allows the provision of null values (together with a nilReason explaining why the actual value cannot be provided) also for Boolean-type properties (see sections 8.4.1 and 9.7.3.4 in ISO 19139).

58

12345

6789

10111213141516171819202122232425

2627282930313233

1234567

8

A resource may conform to more than one implementing rules adopted under Article 7(1) of INSPIRE Directive 2007/2/EC or other specification.

Metadata element name Specification


Definition Citation of the product specification or user requirement against which data is being evaluated

ISO 19115 number and name 130. specification

ISO/TS 19139 path dataQualityInfo/*/report/*/result/*/specification



Data type (and ISO 19115 no.) 359. CI_Citation

Domain The following properties are expected: Title (characterString and free text) Reference date (CI_Date):

o dateType: creation, publication or revisiondate: an effective date

Example title: COMMISSION REGULATION (EU) No 1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services

date:o dateType: publicationo date: 2010-12-08

Comments



<gmd:dataQualityInfo><gmd:DQ_DataQuality>

<gmd:scope><gmd:DQ_Scope>

<gmd:level><gmd:MD_ScopeCode codeListValue="dataset"

codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/gmxCodelists.xml#MD_ScopeCode">dataset</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>COMMISSION REGULATION (EU) No

1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services</gco:CharacterString>

</gmd:title><gmd:date>

59

123

456789

101112131415161718192021222324252627282930313233

1

<gmd:CI_Date><gmd:date><gco:Date>2010-12-08</gco:Date>

</gmd:date><gmd:dateType><gmd:CI_DateTypeCode

codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#CI_DateTypeCode" codeListValue="publication">publication</gmd:CI_DateTypeCode>


</gmd:date></gmd:CI_Citation>

</gmd:specification><gmd:explanation>

<gco:CharacterString>See the referenced specification</gco:CharacterString>

</gmd:explanation><gmd:pass>

<gco:Boolean>true</gco:Boolean></gmd:pass>

</gmd:DQ_ConformanceResult></gmd:result>

</gmd:DQ_DomainConsistency></gmd:report><gmd:lineage>

…</gmd:lineage>

</gmd:DQ_DataQuality></gmd:dataQualityInfo>

</gmd:MD_Metadata>

2.8.3 Specification for invocable Spatial Data Services

If a service is an invocable spatial data service, this element is used to report the degree of invocability to which it confirms.

The metadata element specification contains also the citation of technical specification (such as INSPIRE technical guidance but not only), to which the invocable spatial data service fully conforms.

Metadata element name Category

Reference COMMISSION REGULATION (EU) No 1089/2010, Annex V, Part B 1 and Annex V, Part D 2

Definition Citation of the product specification or user requirement against which data is being evaluated

ISO 19115 number and name 130. specification

ISO/TS 19139 path dataQualityInfo/*/report/*/result/*/specification



Data type (and ISO 19115 no.) 359. CI_Citation

60

123456789

1011121314151617181920212223242526272829303132333435

36373839404142434445

1

Domain http://inspire.ec.europa.eu/conformanceClass/MD/1.4/SDS_Invocable

http://inspire.ec.europa.eu/conformanceClass/MD/1.4/SDS_Interoperable

http://inspire.ec.europa.eu/conformanceClass/MD/1.4/SDS_Harmonised

Example xlink:href="http://inspire.ec.europa.eu/conformanceClass/MD/1.4/SDS_Invocable"

Comments The conformance class shall be referenced with a xlink.


<gmd:MD_Metadata …<gmd:dataQualityInfo> <gmd:DQ_DataQuality> <gmd:scope> <gmd:DQ_Scope> <gmd:level> <gmd:MD_ScopeCode codeListValue="service" codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/gmxCodelists.xml#MD_ScopeCode">service</gmd:MD_ScopeCode> </gmd:level> </gmd:DQ_Scope> </gmd:scope>… <gmd:report> <gmd:DQ_DomainConsistency> <gmd:result> <gmd:DQ_ConformanceResult> <gmd:specification xlink:href="http://inspire.ec.europa.eu/conformanceClass/MD/1.4/SDS_Invocable"> </gmd:specification> <gmd:explanation> <gco:CharacterString>Conform category invocable</gco:CharacterString> </gmd:explanation> <gmd:pass> <gco:Boolean>true</gco:Boolean> </gmd:pass> </gmd:DQ_ConformanceResult> </gmd:result> </gmd:DQ_DomainConsistency> </gmd:report> … </gmd:DQ_DataQuality> </gmd:dataQualityInfo></gmd:MD_Metadata>

In order to make a reference to or machine-readable, the documentation of the service interface (e.g. WSDL) the element gmx:Anchor could be used instead of gco:CharacterString. The backward compatibility is still valid because the human readable text is kept.


<gmd:specification> <gmd:CI_Citation> <gmd:title>

61

123456789

1011121314151617181920212223242526272829303132333435363738394041424344454647484950515253

1

<gmx:Anchor xlink:href=" http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=32546"> EN ISO 19128:2005(E) : Geographic information — Web map server interface </gmx:Anchor> </gmd:title>

62

123456

1

63

12

1

2.9 Constraints related to access and use

ISO 19115 provides a general mechanism for documenting different categories of constraints applicable to the resource (or its metadata). This mechanism is supported by the class MD_Constraints and its subclasses:

MD_LegalConstraints for legal constraints; MD_SecurityConstraints for security constraints.

There are two major requirements expressed in INSPIRE Metadata Regulation 1205/2008/EC INSPIRE Directive 20007/2/EC in terms of documentation of the constraints as part of the metadata:

Part B 8.1 - The conditions applying to access and use of the resource, and where applicable, the corresponding fees as required by Articles 5-2(b) and 11-2(f).

Part B 8.2 T- The limitations on public access: the Member States may limit public access to spatial datasets and spatial data services.

in a set of cases defined in Article 13. These cases include public security or national defence, i.e. more generally the existence of a security constraint.

The current implementation guidelines (version 1.3) in chapter 2.9.1 and chapter 2.9.2 is not fully inline with the intentions of ISO 19115 since the use of useLlmitation is used here also for legal constraints. To give an option for thoose wanting an implementation closer to ISO 19115 we here describe an alternative solution. To fulfil the requirements of these technical guidelines an implementation can select to either use 2.9.1 and 2.9.2 or to select the implementation defined in 2.9.3 and 2.9.4.

A metadata record that is using the implementation based on 2.9.3 and 2.9.4 is identified by it’s reference in otherRestrictions to the the codelist in Inspire Registry athttp://inspire.ec.europa.eu/registry/metadata-codelist/LimitationsOnPublicAccess/

(Comment, we have to fully investigate consequences for discovery services queryables by this alternative solution)

Each instance of MD_Constraints expresses: Zero or One condition applying to access and use (see 2.9.2 or 2.9.4); Zero or More limitations on public access (see 2.9.1 or 2.9.2); Or, both one or more limitations on public access and a condition applying to access

and use.

TG Requirement 36 There shall be at least one ISO 19115 metadata element representing a limitation on public access (see 2.9.1 or 2.9.3) and one ISO 19115 metadata element representing a condition applying to access and use (see 2.9.2 or 2.9.4) as part of the different instances of MD_Constraints and its subclasses.

TG Requirement 37 There shall be at least one instance of MD_Constraints or one of its subclasses (See SC12 in Section 1.2) even if there is no limitation on public access or no specific condition applies to access and use of the resource.

2.9.1 Limitations on public access

This metadata element shall provide information on the limitations and the reasons for them. If there are no limitations on public access, use the free text available in MD_LegalConstraints. otherConstraints to enter “No Limitations” in the language used for the metadata.

64

1

23456789

1011121314151617181920212223242526272829303132333435363738

3940414243

44

45464748

49

505152535455

1

http://inspire.ec.europa.eu/registry/metadata-codelist/LimitationsOnPublicAccess

TG Requirement 38 Limitations on public access shall be represented by at least one of these metadata elements:

- MD_LegalConstraints. accessConstraints

- MD_LegalConstraints. otherConstraints

- MD_SecurityConstraints. classification

Metadata element name Limitations on public access (access constraints)


Definition access constraints applied to assure the protection of privacy or intellectual property, and any special restrictions or limitations on obtaining the resource

ISO 19115 number and name 70. accessConstraints

ISO/TS 19139 path identificationInfo[1]/*/resourceConstraints/*/accessConstraints

INSPIRE obligation / condition Conditional: referring to limitations on public access. Mandatory if otherConstraints or classification are not documented

INSPIRE multiplicity [0..*] for accessConstraints per instance of MD_LegalConstraints

Data type (and ISO 19115 no.) MD_RestrictionCode

Domain Codelist (strictly limited ti the value defined in B.5.24 of ISO 19115)

Example otherRestrictions (limitation not listed).

Comments

Metadata element name Limitations on public access (other constraints)


Definition Other restrictions and legal prerequisites for accessing and using the resource or metadata

ISO 19115 number and name 72. otherConstraints

ISO/TS 19139 path identificationInfo[1]/*/resourceConstraints/*/otherConstraints

INSPIRE obligation / condition Conditional: referring to limitations on public access. Mandatory if accessConstraints or classification are not documented

INSPIRE multiplicity [0..*] for otherConstraints per instance of MD_LegalConstraints


Domain Free text

Example No limitations

Comments

Metadata element name Limitations on public access (classification)


Definition Name of the handling restrictions on the resource

ISO 19115 number and name 74. classification

65

1

23

4

5

6

78

910

1112

1

ISO/TS 19139 path identificationInfo[1]/*/resourceConstraints/*/classification

INSPIRE obligation / condition Conditional: referring to limitations on public access. Mandatory if accessConstraints or otherConstraints are not documented

INSPIRE multiplicity [1] for classification per instance of MD_SecurityConstraints

Data type (and ISO 19115 no.) MD_ClassificationCode

Domain Codelist (see B.5.11 of ISO 19115)

Example unclassified

Comments

In relation to MD_Constraints class, there may be three scenarios according to the tables above: There may be no limitation on public access; There may be only a classification property when expressing a security constraint (i.e.,

this is an instance of MD_SecurityConstraints or one of its subclasses); There may be one or more instances of the accessConstraints property, possibly

associated with one or more instances of otherRestrictions property (i.e, this is an instance of MD_LegalConstraints);




…<gmd:resourceConstraints>

...(see next example)… </gmd:resourceConstraints>

<gmd:resourceConstraints><gmd:MD_LegalConstraints>

<gmd:accessConstraints><gmd:MD_RestrictionCodecodeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/gmxCodelists.xml#MD_RestrictionCode"codeListValue="otherRestrictions">otherRestrictions</gmd:MD_RestrictionCode>

</gmd:accessConstraints><gmd:otherConstraints>

<gco:CharacterString>no limitations</gco:CharacterString>

</gmd:otherConstraints></gmd:MD_LegalConstraints>

</gmd:resourceConstraints><gmd:resourceConstraints>

<gmd:MD_SecurityConstraints><gmd:classification>

<gmd:MD_ClassificationCode codeList="./resources/codeList.xml#MD_ClassificationCode" codeListValue="unclassified">unclassified</gmd:MD_ClassificationCode>

</gmd:classification></gmd:MD_SecurityConstraints>

</gmd:resourceConstraints>…



66

123456789

101112131415161718192021222324252627282930313233343536373839404142434445464748495051

1

2.9.2 Conditions applying to access and use

Conditions for access and use of spatial data sets and services, and where applicable, corresponding fees as required by Article 5(2)(b) and Article 11(2)(f) of INSPIRE Directive 2007/2/EC

Metadata element name Conditions applying to access and use


Definition Restrictions on the access and use of a resource or metadata

ISO 19115 number and name 68. useLimitation

ISO/TS 19139 path identificationInfo[1]/*/resourceConstraints/*/useLimitation




Domain Free text

Example Example if no conditions apply:no conditions applyExample if there is information about restrictions:Reproduction for non-commercial purposes is authorised, provided the source is acknowledged. Commercial use is not permitted without prior written consent of the JRC. Reports, articles, papers, scientific and non-scientific works of any form, including tables, maps, or any other kind of output, in printed or electronic form, based in whole or in part on the data supplied, must contain an acknowledgement of the form: Data re-used from the European Drought Observatory (EDO) http://edo.jrc.ec.europa.eu The SPI data were created as part of JRC's research activities. Although every care has been taken in preparing and testing the data, JRC cannot guarantee that the data are correct; neither does JRC accept any liability whatsoever for any error, missing data or omission in the data, or for any loss or damage arising from its use. The JRC will not be responsible for any direct or indirect use which might be made of the data. The JRC does not provide any assistance or support in using the data

Comments

TG Requirement 39 If no conditions apply to the access and use of the resource, ‘no conditions apply’ shall be used. If conditions are unknown, ‘conditions unknown’ shall be used.

TG Requirement 40 Descriptions of terms and conditions, including where applicable, the corresponding fees shall be provided through this element or a link (URL) where these terms and conditions are described.

67

1234

56789

10

11

121314

15

161718

19

1

TG Recommendation 24 For detailed information it is recommended to provide a link to a license type (e.g. http://creativecommons.org/licenses/by/3.0), a website or to a document containing the necessary information.

68

123

45

1




…<gmd:resourceConstraints>

<gmd:MD_Constraints><gmd:useLimitation>

<gco:CharacterString>Reproduction for non-commercial purposes is authorised, provided the source is acknowledged. Commercial use is not permitted without prior written consent of the JRC. Reports, articles, papers, scientific and non-scientific works of any form, including tables, maps, or any other kind of output, in printed or electronic form, based in whole or in part on the data supplied, must contain an acknowledgement of the form: Data re-used from the European Drought Observatory (EDO) http://edo.jrc.ec.europa.eu The SPI data were created as part of JRC's research activities. Although every care has been taken in preparing and testing the data, JRC cannot guarantee that the data are correct; neither does JRC accept any liability whatsoever for any error, missing data or omission in the data, or for any loss or damage arising from its use. The JRC will not be responsible for any direct or indirect use which might be made of the data. The JRC does not provide any assistance or support in using the data</gco:CharacterString>

</gmd:useLimitation></gmd:MD_Constraints>

</gmd:resourceConstraints><gmd:resourceConstraints>

...(see previous example)… </gmd:resourceConstraints>…



2.9.3 Limitations on public access – Alternative solution

In Article 13 in INSPIRE Directive 20007/2/EC there is a list of cases where limitations to public acess can be set.

These are:(a) the confidentiality of the proceedings of public auth

where such confidentiality is provided for by law ;(b) international relations, public security or national defence; (c) the course of justice, the ability of any person to receive a

fair trial or the ability of a public authority to conduct anenquiry of a criminal or disciplinary nature;

(d) the confidentiality of commercial or industr ial infor mation,where such conf identiality is provided for by national orCommunity law to protect a legitimate economic interest,including the public interest in maintaining statisticalconfidentiality and tax secrecy ;

(e) intellectual property rights;(f) the confidentiality of personal data and/or files relating to a

natural person where that person has not consented to thedisclosure of the information to the public, where such

69

123456789

1011121314151617181920212223242526272829303132333435363738394041

424344454647484950515253545556575859606162

1

confidentiality is provided for by national or Communitylaw ;

(g) the interests or protection of any person who supplied theinfor mation requested on a voluntary basis without beingunder, or capable of being put under, a legal obligation todo so, unless that person has consented to the release of theinformation concerned;

(h) the protection of the environment to which such information relates, such as the location of rare species.

TG Requirement 41 Limitations on public access shall be represented by one instance of

MD_LegalConstraints.accessConstraints and at least one instance of MD_LegalConstraints. otherConstraints containing a link to the code list for Limitations on Public Access in Inspire registry describing the limitation. ( http://inspire.ec.europa.eu/registry/metadata-codelist /LimitationsOnPublicAccess/)

To separate the Limitations on public access from other access restrictions the description of the access restriction in element otherRestrictions shall be implemented using an Anchor element linking to the Inspire registry referencing the specific restriction.The url to this code list is

http://inspire.ec.europa.eu/registry/metadata-codelist /LimitationsOnPublicAccess /

To reference a specific Public Limitations eg “( e ) intellectual property rights”; the following codevalue should be used http://inspire.ec.europa.eu/registry/metadata-codelist / LimitationsOnPublicAccess/INSPIRE_Directive_Article13_e

If no limitation on public access exists then the value no limitations shall be used http://inspire.ec.europa.eu/registry/metadata-codelist / LimitationsOnPublicAccess/noLimitations

<gmd:MD_Metadata …… <gmd:identificationInfo> <gmd:MD_DataIdentification>… <gmd:resourceConstraints>...(see next example)… </gmd:resourceConstraints> <gmd:resourceConstraints> <gmd:MD_LegalConstraints> <gmd:accessConstraints> <gmd:MD_RestrictionCode

codeList="http://standards.iso.org/ittf/ PubliclyAvailableStandards/ISO_19139_Schemas/ resources/codelist/gmxCodelists.xml#MD_RestrictionCode" codeListValue="otherRestrictions">otherRestrictions </gmd:MD_RestrictionCode> </gmd:accessConstraints> <gmd:otherConstraints> <gmx:Anchor link:href=" http://inspire.ec.europa.eu/registry/metadata-codelist /LimitationsOnPublicAccess/INSPIRE_Directive_Article13_e">

70

123456789

101112

13

14151617181920

21

2223242526272829303132333435363738394041424344454647484950515253545556575859

1

http://inspire-regadmin.jrc.ec.europa.eu/service-sandbox/metadata-codelist/LimitationsOnPublicAccess

intellectual property rights;</gmx:Anchor> </gmd:otherConstraints> </gmd:MD_LegalConstraints> </gmd:resourceConstraints> … </gmd:MD_DataIdentification> </gmd:identificationInfo>…</gmd:MD_Metadata>

Metadata element name Limitations on public access (access constraints)


Definition access constraints applied to assure the protection of privacy or intellectual property, and any special restrictions or limitations on obtaining the resource



INSPIRE obligation / condition Conditional: referring to limitations on public access. Mandatory if otherConstraints or classification are not documented





Comments

Metadata element name Limitations on public access (other constraints)







Data type (and ISO 19115 no.) Gmx:anchor

Domain A codelist value from the codelist at http://inspire.ec.europa.eu/registry/metadata-codelist /LimitationsOnPublicAccess/

Example <gmx:Anchor link:href=" http://inspire.ec.europa.eu/registry/metadata-codelist /LimitationsOnPublicAccess//NoLimitations"> no limitations</gmx:Anchor>

Comments

71

123456789

10111213

1415

1617

1



2.9.4 Conditions applying to access and use - alternative implementation

Conditions for access and use of spatial data sets and services, and where applicable, corresponding fees as required by Article 5(2)(b) and Article 11(2)(f) of INSPIRE Directive 2007/2/EC

TG Requirement 42 Contitions applying to access and use shall be represented by one instance of

MD_LegalConstraints.otherConstraints

This shall NOT contain a link to the code list for Limitations on Public Access in Inspire registry since that is reserved for documenting Limitations on public access ( see 2.9.3)

Conditions applying to access

Metadata element name Conditions applying to access


Definition Restrictions on the access and use of a resource or metadata



INSPIRE obligation / condition





Comments

Metadata element name Conditions applying to access (other constraints)








Domain Free textor if the values “no conditions apply” or “conditions unknown” is used then a an Anchor to the codelist in the Inspire Registry should be used.

72

12345678

910

11

12131415

16171819

2021

1

Examplehttp://inspire.ec.europa.eu/registry /metadata-codelist/ ConditionsApplyingToAccessAndUse/ NoConditionsApply

CommentsThe domain of the metadata element otherConstraints is Free text. This makes it hard to unambiguous define some common values in all official languages in the Communiy.Therefore it is recommended to refer to codelists in the Inspire registry for some specific values like “no conditions apply” and “conditions unknown”.

Conditions applying to use

Metadata element name Conditions applying to use


Definition Restrictions on the use of a resource or metadata

ISO 19115 number and name 71. useConstraints

ISO/TS 19139 path identificationInfo[1]/*/resourceConstraints/*/useConstraints

INSPIRE obligation / condition

INSPIRE multiplicity [0..*] for useConstraints per instance of MD_LegalConstraints


Domain Codelist (strictly limited to the value defined in B.5.24 of ISO 19115)


Comments

Metadata element name Conditions applying to use (other constraints)








Domain Free textor if the values “no conditions apply” or “conditions unknown” is used then a an Anchor to the codelist in the Inspire Registry should be used.

Example http://inspire.ec.europa.eu/registry/metadata-codelist/ConditionsApplyingToAccessAndUse/NoConditionsApply

Comments The domain of the metadata element otherConstraints is Free text. This makes it hard to unambiguous define some common values in all official languages in the Communiy.

73

1234

56

1

http://inspire.ec.europa.eu/registry/metadata-codelist/%0BConditionsApplyingToAccessAndUse/NoConditionsApply




Therefore it is recommended to refer to codelists in the Inspire registry for some specific values like “no conditions apply” and “conditions unknown”.

Examples

No conditions apply (note we could have also added both leaints with codelistvalue OtherConstraints. l.)<gmd:MD_Metadata …… <gmd:identificationInfo> <gmd:MD_DataIdentification>… <gmd:resourceConstraints>...(see next example)… </gmd:resourceConstraints> <gmd:resourceConstraints> <gmd:MD_LegalConstraints> <gmd:accessConstraints> <gmd:MD_RestrictionCode

codeList="http://standards.iso.org/ittf/ PubliclyAvailableStandards/ISO_19139_Schemas/ resources/codelist/gmxCodelists.xml#MD_RestrictionCode" codeListValue="otherRestrictions">otherRestrictions </gmd:MD_RestrictionCode> </gmd:accessConstraints>

<gmd:otherConstraints> <gco:CharacterString> no conditions apply </gco:CharacterString> </gmd:otherConstraints> </gmd:MD_LegalConstraints> </gmd:resourceConstraints> … </gmd:MD_DataIdentification> </gmd:identificationInfo>…</gmd:MD_Metadata>

No conditions apply using a language neutral identifier in English



74

123456789

1011121314151617181920212223242526272829303132333435363738394041

434445464748495051525354555657585960

1

<gmd:otherConstraints> <gmx:Anchor xlink:href="http://inspire.ec.europa.eu/registry/metadata-codelist/ConditionsApplyingToAccessAndUse/NoConditionsApply">no conditions apply </gmx:Anchor> </gmd:otherConstraints> </gmd:MD_LegalConstraints> </gmd:resourceConstraints> … </gmd:MD_DataIdentification> </gmd:identificationInfo>…</gmd:MD_Metadata>

No conditions apply using a language neutral identifier in Swedish


codeList="http://standards.iso.org/ittf/ PubliclyAvailableStandards/ISO_19139_Schemas/ resources/codelist/gmxCodelists.xml#MD_RestrictionCode" codeListValue="otherRestrictions">otherRestrictions </gmd:MD_RestrictionCode> </gmd:accessConstraints><gmd:otherConstraints> <gmx:Anchor xlink:href="http://inspire.ec.europa.eu/registry/metadata-codelist/ConditionsApplyingToAccessAndUse/NoConditionsApply">inga tillämpliga villkor </gmx:Anchor> </gmd:otherConstraints> </gmd:MD_LegalConstraints> </gmd:resourceConstraints> … </gmd:MD_DataIdentification> </gmd:identificationInfo>…</gmd:MD_Metadata>

An access restriction apply

<gmd:MD_Metadata …… <gmd:identificationInfo> <gmd:MD_DataIdentification>… <gmd:resourceConstraints>...(see next example)… </gmd:resourceConstraints>

75

123456789

101112131415161718

202122232425262728293031323334353637383940414243444546474849505152535455

5758596061626364

1

<gmd:resourceConstraints> <gmd:MD_LegalConstraints> <gmd:accessConstraints> <gmd:MD_RestrictionCode


<gmd:otherConstraints> <gco:CharacterString>Reproduction for non-commercial purposes is authorised, provided the source is acknowledged. Commercial use is not permitted without prior written consent of the JRC. Reports, articles, papers, scientific and non-scientific works of any form, including tables, maps, or any other kind of output, in printed or electronic form, based in whole or in part on the data supplied, must contain an acknowledgement of the form: Data re-used from the European Drought Observatory (EDO) http://edo.jrc.ec.europa.eu The SPI data were created as part of JRC's research activities. Although every care has been taken in preparing and testing the data, JRC cannot guarantee that the data are correct; neither does JRC accept any liability whatsoever for any error, missing data or omission in the data, or for any loss or damage arising from its use. The JRC will not be responsible for any direct or indirect use which might be made of the data. The JRC does not provide any assistance or support in using the data</gco:CharacterString> </gmd:otherConstraints> </gmd:MD_LegalConstraints> </gmd:resourceConstraints> … </gmd:MD_DataIdentification> </gmd:identificationInfo>…</gmd:MD_Metadata>

An access and use restriction apply

<gmd:MD_Metadata …… <gmd:identificationInfo> <gmd:MD_DataIdentification>… <!-- The ACCESS restriction -- > <gmd:resourceConstraints> <gmd:MD_LegalConstraints> <gmd:accessConstraints> <gmd:MD_RestrictionCode


<gmd:otherConstraints>

76

123456789

101112131415161718192021222324252627282930

313334353637383940414243

45464748495051525354555657585960616263

1

<gco:CharacterString>description of the access restriction …</gco:CharacterString> </gmd:otherConstraints> </gmd:MD_LegalConstraints> </gmd:resourceConstraints> <!-- The USE restriction -- > <gmd:resourceConstraints> <gmd:MD_LegalConstraints> <gmd:useConstraints> <gmd:MD_RestrictionCode

codeList="http://standards.iso.org/ittf/ PubliclyAvailableStandards/ISO_19139_Schemas/ resources/codelist/gmxCodelists.xml#MD_RestrictionCode" codeListValue="otherRestrictions">otherRestrictions </gmd:MD_RestrictionCode> </gmd:useConstraints>

<gmd:otherConstraints> <gco:CharacterString> description of the use restriction … </gco:CharacterString> </gmd:otherConstraints> </gmd:MD_LegalConstraints> </gmd:resourceConstraints> … </gmd:MD_DataIdentification> </gmd:identificationInfo>…</gmd:MD_Metadata>

2.10 Responsible organisation

Organisation responsible for the establishment, management, maintenance and distribution of spatial data sets and services. A responsible organisation is defined by:

a responsible party (see 2.10.1); and a responsible party role (see 2.10.2).

There may be one to many responsible organisations for a single resource, but the multiplicity of the responsible and its role are expressed relative to a single responsible organisation.

Interoperable spatial data services have additional requirements on metadata. The responsible party set out in Regulation (EC) No 1205/2008 shall at least describe the custodian responsible organisation, corresponding to the Custodian responsible party role set out in Regulation (EC) No 1205/2008.

TG Requirement 43 The responsible party set out in Regulation (EC) No 1205/2008 shall at least describe the custodian responsible organisation, corresponding to the Custodian responsible party role set out in Regulation (EC) No 1205/2008.

2.10.1 Responsible party

77

123

46789

1011121314151617181920212223242526272829303132333435

3637383940414243444546474849

50515253

5455

5657

1


Is the sentence above this requirement


Should be clarified this is only for SDS

This is the description of the organisation responsible for the establishment, management, maintenance or distribution of the resource

TG Requirement 44 This description shall include: name of the organisation and contact email address.

Metadata element name Responsible party

Reference Part B 9.1 and COMMISSION REGULATION (EU) No 1089/2010, Annex VI Part A 2Part B 9.1

Definition Identification of, and means of communication with, person(s) and organization(s) associated with the resource(s)

ISO 19115 number and name 29. pointOfContact

ISO/TS 19139 path identificationInfo[1]/*/pointOfContact

INSPIRE obligation / condition Mandatory for datasets and servicesMandatory for interoperable spatial data services Mandatory

INSPIRE multiplicity [1] Relative to a responsible organisation, but there may be many responsible organisations for a single resource

Data type (and ISO 19115 no.) 374. CI_ResponsibleParty

Domain The following properties are expected: organisationName (characterString and free text) contactInfo (CI_Contact):

o address: electronicMailAddress [1..*] (characterString)

Example organisationName: European Commission, Joint Research Centre

contactInfo:o address:

electronicMailAddress: [email protected]

Comments

TG Requirement 45 See SC14 for more information about elements required for data and services.

TG Recommendation 25 The name of the organization should be given in full, without abbreviations. It is recommended to use institutional email instead of personal emails.

78

123

45

6

78

910

11

121314

15

1


<gmd:MD_Metadata>...<gmd:identificationInfo>

<gmd:MD_DataIdentification>...<gmd:pointOfContact>

<gmd:CI_ResponsibleParty><gmd:organisationName>

<gco:CharacterString>European Commission, Joint Research Centre</gco:CharacterString>

</gmd:organisationName><gmd:contactInfo>

<gmd:CI_Contact><gmd:address>

<gmd:CI_Address><gmd:electronicMailAddress>

<gco:CharacterString>[email protected] </gco:CharacterString>

</gmd:electronicMailAddress></gmd:CI_Address>

</gmd:address></gmd:CI_Contact>

</gmd:contactInfo><gmd:role>

...(see next example)</gmd:role>

</gmd:CI_ResponsibleParty></gmd:pointOfContact>...


</gmd:MD_Metadata>

2.10.2 Responsible party role

This is the role of the responsible organisation

Metadata element name Responsible party role

Reference Part B 9.2 and COMMISSION REGULATION (EU) No 1089/2010, Annex VI Part A 2Part B 9.2

Definition Function performed by the responsible party

ISO 19115 number and name 379. role

ISO/TS 19139 path identificationInfo[1]/*/pointOfContact/*/role

INSPIRE obligation / condition Mandatory for datasets and servicesMandatory for interoperable spatial data servicesMandatory

INSPIRE multiplicity [1] relative to a responsible organisation, but there may be many responsible organisations for a single resource

Data type (and ISO 19115 no.) CI_RoleCode

Domain Codelist (see B.5.5 of ISO 19115)

Example custodian

Comments There is a direct mapping between the responsible party roles defined in Part D 6 of the INSPIRE Metadata Regulation

79

123456789

101112131415161718192021222324252627282930313233343536

37383940

1

1205/2008/EC and the values of the CI_RoleCode codelist of ISO 19115

TG Recommendation 26 Select all roles that best represent the function performed by the responsible party.


<gmd:MD_Metadata>...<gmd:identificationInfo>

<gmd:MD_DataIdentification>...<gmd:pointOfContact>




…(see previous example)</gmd:contactInfo><gmd:role>

<gmd:CI_RoleCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/gmxCodelists.xml#CI_RoleCode" codeListValue="custodian">custodian</gmd:CI_RoleCode>

</gmd:role></gmd:CI_ResponsibleParty>

</gmd:pointOfContact>...


</gmd:MD_Metadata>

2.11Metadata on metadata

2.11.1 Metadata point of contact

This is the description of the organisation responsible for the creation and maintenance of the metadata. This refers to the metadata record and not to the resource responsible party; they will not necessarily be the same.

TG Requirement 46 This description shall include: name of the organization and contact email address.

Metadata element name Metadata point of contact


Definition Party responsible for the metadata information

ISO 19115 number and name 8. contact

ISO/TS 19139 path contact


80

1

23

456789

10111213141516171819202122232425262728293031323334

35

363738394041

4243

44

1


Data type (and ISO 19115 no.) 374. CI_ResponsibleParty

Domain The following properties are expected: organisationName (characterString and free text) contactInfo (CI_Contact):

o address: electronicMailAddress [1..*] (characterString)

Example organisationName: European Commission, Joint Research Centre

contactInfo:o address:

electronicMailAddress: [email protected]

Comments

TG Requirement 47 The role of the responsible party serving as a metadata point of contact is out of scope of the INSPIRE Metadata Regulation 1205/2008/EC, but this property is mandated by ISO 19115. The default value is pointOfContact. See SC15 and SC16

TG Recommendation 27 The name of the organization should be given in full, without abbreviations. It is recommended to use institutional email instead of personal emails.


<gmd:MD_Metadata>...<gmd:contact>




<gmd:CI_Contact><gmd:address>

<gmd:CI_Address><gmd:electronicMailAddress>

<gco:CharacterString>[email protected] </gco:CharacterString>

</gmd:electronicMailAddress></gmd:CI_Address>

</gmd:address></gmd:CI_Contact>

</gmd:contactInfo><gmd:role>

<gmd:CI_RoleCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/gmxCodelists.xml#CI_RoleCode" codeListValue="pointOfContact">pointOfContact</gmd:CI_RoleCode>

</gmd:role></gmd:CI_ResponsibleParty>

</gmd:contact>...

81

1

2345

6

789

10111213141516171819202122232425262728293031323334353637383940

1

</gmd:MD_Metadata>

2.11.2 Metadata date

The date which specifies when the metadata record was created or updated

Metadata element name Metadata date


Definition Date that the metadata was created

ISO 19115 number and name 9. dateStamp

ISO/TS 19139 path dateStamp



Data type (and ISO 19115 no.) Date

Domain ISO 8601

Example 2012-02-20

Comments


<gmd:MD_Metadata>...<gmd:dateStamp>

<gco:Date>2012-02-20</gco:Date></gmd:dateStamp>...

</gmd:MD_Metadata>

2.11.3 Metadata language

This is the language in which the metadata elements are expressed

Metadata element name Metadata language


Definition Language used for documenting metadata

ISO 19115 number and name 3. language

ISO/TS 19139 path language



Data type (and ISO 19115 no.) LanguageCode (ISO/TS 19139)

Domain Codelist (See ISO/TS 19139) based on alpha-3 codes of ISO 639-2. Use only three-letter codes from in ISO 639-2/B (bibliographic codes),

The value domain for this element is limited to the official languages of the commuityEU member states.The list of valid codes for the 24 official EU languages is:Bulgarian – bul Irish – gle

82

12

3456

789

1011121314151617

18192021

1

Croatian – hrv Italian – itaCzech – cze Latvian – lavDanish – dan Lithuanian – litDutch – dut Maltese – mltEnglish – eng Polish – polEstonian – est Portuguese – porFinnish – fin Romanian – rumFrench – fre Slovak – sloGerman – ger Slovenian – slvGreek – gre Spanish – spaHungarian – hun Swedish – swe

These values are part of the list of all the codes is defined at http://www.loc.gov/standards/iso639-2/ Regional languages also are included in this list.

Example Eng

Comments There are two ways of inserting values in code-lists see section A.11

TG Requirement 48 The language property is not mandated by ISO 19115, but is mandated for conformance to the INSPIRE Metadata Regulation 1205/2008/EC (See SC1 in 1.2).

TG Requirement 49 The value domain of this metadata element is limited to the official languages of the Community expressed in conformity with ISO 639-2 (See INSPIRE Metadata Regulation 1205/2008/EC, Part B, 10.3)

Examples of XML encoding:

Please refer to the examples for Resource Language (section 2.2.7)

83

1

234

5

678

9101112131415

1


2.12 Metadata elements for interoperability

2.12.1

TG Requirement 50 eference system shall be expressed using an identifier.

Description of the coordinate reference system(s) used in the data set.

, article 13, pointclause 1 and COMMISS No 1089/2010, AnnePart B

andatory for dataset and dataset series;not applicable to servicesMor interoperable spatiata s

for dataset and dataset series

MD_e

(RS_Identifier) shall be provided.

RS_Identifier itself is a complex type (lines 206-207 and 208.1-208.2 from ISO 19115). At least the following element that is mandatory for ISO should be used (the multiplicity according to ISO 19115 is shown in parentheses): 207. code [1] / domain value: free text

TG Requirement 2 in INSPIRE Data specifications states that a URI identifier listed in a table provided there shall be used for referring to the Coordinate reference system. The table is listed below. If the code is given as an URI as shown above, the element codespace is not needed.

code: http://www.opengis.net/def/crs/EPSG/0/4258)ETRS_89codeSpace: INSPIRE RS registry

ISO 19115 lists several elements which build MD_ReferenceSystem. For the purpose of theme-specific metadata according to the INSPIRE Data specifications the element listed above is sufficient.

TG Requirement 51 Coordinate Refenc (see Article 13, clause 1). At least one Coordinate Reference System must be specified.

TG Requirement 52

TG Requirement 53 Coordinate reference system parameters and identifiers shall be managed in one or several common registers for coordinate reference systems. Only identifiers contained in a common register shall be used for referring to the coordinate reference systems listed in this Section (see INSPIRE Regulation 1089/2010/EC, II, 1.5). The identifiers listed in the table below shall be used for referring to the coordinate reference systems used in a data set.

Coordinate reference system

Short name http URI identifier

84

1

23

4

56

7

89

10

11121314151617

18

1

http://www.opengis.net/def/crs/EPSG/0/4258

3D Cartesian in ETRS89 ETRS89-XYZ http://www.opengis.net/def/crs/EPSG/0/4936

3D geodetic in ETRS89 on GRS80

ETRS89-GRS80h http://www.opengis.net/def/crs/EPSG/0/4937


ETRS89-GRS80 http://www.opengis.net/def/crs/EPSG/0/4258

2D LAEA projection in ETRS89 on GRS80

ETRS89-LAEA http://www.opengis.net/def/crs/EPSG/0/3035

2D LCC projection in ETRS89 on GRS80

ETRS89-LCC http://www.opengis.net/def/crs/EPSG/0/3034

2D TM projection in ETRS89 on GRS80, zone 26N (30°W to 24°W)

ETRS89-TM26N http://www.opengis.net/def/crs/EPSG/0/3038







2D TM projection in ETRS89 on GRS80, zone 30N (6°W to 0°)


2D TM projection in ETRS89 on GRS80, zone 31N (0° to 6°E)


2D TM projection in ETRS89 on GRS80, zone 32N (6°E to 12°E)
















Height in EVRS EVRS http://www.opengis.net/def/crs/EPSG/0/5730

3D compound: 2D geodetic in ETRS89 on GRS80, and EVRS height

ETRS89-GRS80-EVRS http://www.opengis.net/def/crs/EPSG/0/7409

<gmd:MD_Metadata> ...<m <gmd:MD_ReferenceSystem> entifier> <gmd:RS_Identifier> <gco:CharacterString>3004http://www.opengis.net/def/crs/EPSG/0/4258</gco:CharacterString> <gmd:codeSpace>org/</gco:Chara </gmd:codeSpace> </gmd:referenceSystemIdentifier> </gmd:MD_ReferenceSystem> </gmd:referenceSystemInfo> ...</gmd:MD_Metadata>

85

123456

789

1112131415161718

1

2.12.2

T, article 13, pointclause 2

e

for dataset and dataset series:ired if a n;not applicable to services


systems. Thus, the generic MD_ReferenceSystem element and its e vided.

RS_Identifier itself is a complex type (lines 206-207 and 208.1-208.2 from ISO 19115). At least the following element that is mandatory for ISO should be used (the multiplicity according to ISO 19115 is shown in parentheses):

- 207. code [1] / domain value: free text

JulianGregorianCalendar

The primary temporal reference system for use with geographic information is the Gregorian Calendar and 24 hour local or Coordinated Universal Time (UTC), but special applications may entail the use of alternative reference systems. So ti ontains temporal information that does not refer to hISO 19115 lists several elements which build MD_ReferenceSystem. For the purpose of theme-specific metadata according to the INSPIRE Data specifications the element listed above is sufficient.FuFurther elements like authority, codeSpace and The reference system namespace Authority and Version are optional but a

TG Requirement 54 Temporal Referee sause 52).

<gmd:MD_Metadata> ... <gmd:referenceSystemInfo> <gmd:MD_ReferenceSystem> <gmd:referenceSystemIdentifier> <gmd:RS_Identifier> <gmd:code> <gco:CharacterString>JulianCalendar</gco:CharacterString> </gmd:code> </gmd:RS_Identifier> </gmd:referenceSystemIdentifier> </gmd:MD_ReferenceSystem> </gmd:referenceSystemInfo> ...</gmd:MD_Metadata><gmd:referenceSystemInfo>

86

12

3

4

56789

101112

1315161718192021222324

1

roat, 01/20/15,

I think that the more suitable class to document the temporal Reference System is RS_ReferenceSystem in the Reference System Information package (its definition by ISO 19115 is "description of the spatial and temporal reference systems used in the dataset" - see http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/referenceSystem.xsd). That class could be conformant also to the Standard 19108 (Geographic information - Temporal schema), which, at Annex C (normative) defines the metadata elements for describing temporal reference systems. Unfortunately the above mentioned class is defined by ISO 19115 as abstract and without any relations with other classes. So, I haven't found the way to use it. Any idea?

2.12.3

, article 13, point 1, article 13, poinclause

for dataset and dataset series;not applicable to services

[1..*] for dataset and dataset series

This is a complex type (lines 285-290 from ISO 19115). At least the following elements that are mandatory for ISO should be used (the multiplicity according to ISO 19115 is shown in parentheses): 285. name [1] / domain value: free text286. version [1] / domain value: free text

Content for name could also be taken from

applicunknownspecifica2.8.II.

ISO 19115 lists several elements which build MD_Format. For the purpose of theme-specific metadata according to the INSPIRE Data specifications the elements listed above are sufficient.Instead of using element specification here the documentation of the supported data scheme inside the distributed dataset (as mentioned in INSPIRE Data specification) can be given either in conformity statement (see 2.8) or the maybe existing metadata element applicationSchemaInfo (see ISO 19115, B.2.1, No. 21).

TG Requirement 55 Encoding property (in the meaning of the supported file format when providing data) is not mandated by ISO 19115 but is mandated for conformance to the INSPIRE Regulation 1089/2010/EC (see Article 13, clause 3).

<gmd:MD_Metadata> ... <gmd:distributionInfo> <gmd:MD_Distribution> ... <gmd:distributionFormat> <gmd:MD_Format> <gmd:name> <gco:CharacterString>application/x-shapefile</gco:CharacterString> </gmd:name> <gmd:version> <gco:CharacterString>unknown</gco:CharacterString> </gmd:version>

</gmd:specification> </gmd:MD_Format> <gmd:distributionFormat> ... </gmd:MD_Distribution> </gmd:distributionInfo>

87

123

4

56789

10111213141516

171920212223242526272829

1


2.12.4

C, article 13, point 1, article 13, poinclause5

;nNot applicable to services

N

TG Requirement 56 The Character Eods, clause 5).

TG Recommendation 28

<gmd:MD_Metadata> ... <gmd:identificationInfo> <gmd:MD_DataIdentification> ... <gmd:characterSet> <gmd:MD_CharacterSetCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/gmxCodelists.xml#MD_CharacterSetCode" codeListValue="usAscii">usAscii</gmd:MD_CharacterSetCode> </gmd:characterSet> ... </gmd:MD_DataIdentification> </gmd:identificationInfo> ...</gmd:MD_Metadata>

The method used to spatially represent geographic information.

, article 13, pointclause 6 (element added by amendment 1253/2013ed on)

identificationInfo[1]/*/spatialRepresentationType

ondition for dataset and dataset series;not applicable to services

88

1234

56

7

8

9

10111213141516171819202122232425262728293031

1


TG Requirement 57 The Spatial repsethe INSPIRE Regulation 1089/2010/EC (see Article 13, clause 6)Art. 13(6) of the Implementing Rules on inte Spatial representation type shall be recorded and domain vle

TG Requirement 58 <gmd:MD_Metadata> ... <gmd:identificationInfo> <gmd:MD_DataIdentification> ... <gmd:spatialRepresentationType> <gmd:gmd:MD_SpatialRepresentationTypeCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/gmxCodelists.xml#MD_SpatialRepresentationTypeCode" codeListValue="vector">vector</gmd:MD_SpatialRepresentationTypeCode> </gmd:spatialRepresentationType> ... </gmd:MD_DataIdentification> </gmd:identificationInfo> ...</gmd:MD_Metadata>

2.12.5 2.12.6 Topological Consistency

While giving this metadata element as one of the “Metadata elements for interoperability” in chapters 8.2 of INSPIRE Data specifications the description of “Topological consistency” refers to chapters 8.3.2 (“Metadata elements for reporting data Quality”). All the elements mentioned there are based on ISO 19157, which provides different ways to report data quality information. INSPIRE Data specifications make use of two ways: reporting quantitative results and reporting descriptive results. ISO 19157 itself works along with metadata structures according to ISO 19115-1.As long as being based on ISO 19115 only a mapping of the metadata elements designated in ISO 19157 to metadata elements existing in ISO 19115 is necessary:For quantitative results there is a equivalent structure in ISO 19115, so the mapping is obvious.For descriptive results there is no matching element that seems likely. The attempt here is to store the data quality statements in the existing Lineage statement and flag them as a turnout from data quality.

2.12.5.1 Topological Consistency – Quantitative results

– Quantitative resultsCOMMISSION REGULATION (EU) No 1089/2010, article 13, clause 4

80. report

89

1

234

56789

10111213141516171819202122

23242526272829303132333435363738394041

4243

1

dataQualityInfo/DQ_DataQuality/report/

for dataset and dataset series: mandatory if the data set includes types from the Generic Network Model and does not assure centreline topology (connectivity of centrelines) for the network;not applicable to services


115. DQ_TopologicalConsistency

DQ_TopologicalConsistency is forming of the abstract complex type DQ_Element. See B.2.4.3 in ISO 19115:2003 for further information.

The following ISO 19115 elements are the corresponding ones to express quantitative results of the data quality evaluation as given in INSPIRE Data specifications chapters 8.3.2 which in fact focus on ISO 19157:

- 100. nameOfMeasure [0..*]: name of the test applied to the data / domain value: free text

- 103. evaluationMethodType [0..1]: type of method used to evaluate quality of the dataset/ domain value: DQ_EvaluationMethod TypeCode

- 104. evaluationMethodDescription [0..1]: description of the evaluation method / domain value: free text

- 106. dateTime [0..*]: date or range of dates on which a data quality measure was applied / domain value: DateTime (ISO 19103)

- 107. result [1..2]: value (or set of values) obtained from applying a data quality measure or the outcome of evaluating the obtained value (or set of values) against a specified acceptable conformance quality level / domain value: DQ_Result (abstract)

- 133. DQ_QuantitativeResult, consisting of- 137. value [1..*]: quantitative value or values, content

determined by the evaluation procedure used / domain value: Record (ISO 19103)

- Due to making use of DQ_QuantitativeResult subset there is a mandatory element in ISO 19115 to be considerer too:

- 135. valueUnit [1]

- - see XML example -

ISO 19115 lists several elements which build DQ_Element. For the purpose of theme-specific metadata according to the INSPIRE Data specifications the elements won by mapping from ISO 19157 are sufficient.

TG Requirement 48

TG Recommendation 29 As long as being based on ISO 19115 only the metadata elements reporting quantitative results on Topological consistency should be expressed by corresponding ISO 19115 elements as shown in the table above considering a mandatory element given by ISO 19115 in addition.

<gmd:MD_Metadata> ... <gmd:dataQualityInfo> <gmd:DQ_DataQuality> ... <gmd:report> <gmd:DQ_TopologicalConsistency> <gmd:nameOfMeasure>

90

1

23456

789

10111213141516

1

<gco:CharacterString>---appropriate text---</gco:CharacterString> </gmd:nameOfMeasure> ... <gmd:evaluationMethodType> <DQ_EvaluationMethodTypeCode xmlns="http://www.isotc211.org/2005/gmd" codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml# DQ_EvaluationMethodTypeCode" codeListValue="indirect"/> </gmd:evaluationMethodType> <gmd:evaluationMethodDescription> <gco:CharacterString>---appropriate text---</gco:CharacterString> </gmd:evaluationMethodDescription> ... <gmd:dateTime> <gco:DateTime>2015-04-01T16:20:00</gco:DateTime> </gmd:dateTime> <gmd:result> <gmd:DQ_QuantitativeResult> ... <gmd:valueUnit>---appropriate content--- </gmd:valueUnit> ... <gmd:value>---appropriate content--- </gmd:value> </gmd:DQ_QuantitativeResult> </gmd:result> </gmd:DQ_TopologicalConsistency> </gmd:report> ... </gmd: DQ_DataQuality> </gmd:dataQualityInfo> ...</gmd:MD_Metadata>if topological consistency has to be expressed by a value then:<gmd:MD_Metadata> <gmd:dataQualityInfo> …eport> <DQ_TopologicalConsistency> …gmd </gmd:dataQualityInfo></gmd:MD_Metadata>if topological consistency has to be expressed through the conformance to a specification (I referred to INSPIRE Generic Network Model) then:<gmd:MD_Metadata> <gmd:dataQualityInfo> …eport> <DQ_TopologicalConsistency><DQ_ConformanceResult><title></dateType></specification> …gmd </gmd:dataQualityInfo></gmd:MD_Metadata>

2.12.5.2 Topological Consistency – Descriptive results

91

123456789

1011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859

6061

1

Kochmann, Peter, 05/20/15,

Conformance Result is not in focus of Topological consistency as given in Data specifications concerning Metadata elements for interoperability! There are given descriptive and quantitative results only!

Metadata element name Topological Consistency – Descriptive resultsReference COMMISSION REGULATION (EU) No 1089/2010, article 13, clause 4

Definition Correctness of the explicitly encoded topological characteristics of the data set as described by the scope.

ISO 19115 number and name 81. lineage

ISO/TS 19139 path dataQualityInfo/DQ_DataQuality/lineage/

INSPIRE obligation / condition Conditional for dataset and dataset series: mandatory if the data set includes types from the Generic Network Model and does not assure centreline topology (connectivity of centrelines) for the network;not applicable to services

INSPIRE multiplicity [0..*] for dataset and dataset series

Data type (and ISO 19115 no.) 82. LI_Lineage

Domain This is a complex type (lines 85-85 from ISO 19115). To provide the descriptive results of Topological consistency evaluation the following element should be used (the multiplicity according to ISO 19115 is shown in parentheses): 83. statement [C..1]: general explanation of the data producer’s knowledge about the lineage of a dataset / domain value: free text

Example - see XML example -

Comments ISO 19115 lists several elements which build LI_Lineage. For the purpose of Topological consistency according to the INSPIRE Data specifications the element listed above is sufficient.Note that the path for dataQualityInfo/DQ_DataQuality/lineage/ will already exist in metadata because of being used for carrying information about lineage itself (see 2.7.1). Therefore an addition of these information into the same entity of LI_Lineage may be useful but has to be flagged by using the name of the corresponding DQ_ TopologicalConsistency subelement as a prefix or topic in the lineage element.

TG Recommendation 30 As long as being based on ISO 19115 only the metadata elements reporting descriptive results on Topological consistency should be expressed by using the lineage statement. This element is already used for documenting the lineage of the resource (see 2.7.1), so a prefix or topic (e.g. “TopologicalConsistency: …”) may be helpful when using the same entity of LI_Lineage.



<gmd:MD_Metadata> ... <gmd:dataQualityInfo> <gmd:DQ_DataQuality> ... <gmd:lineage> <gmd:LI_Lineage> <gmd:statement> <gco:CharacterString>...Topological Consistency:---appropriate text---</gco:CharacterString> </gmd:statement> ... </gmd:LI_Lineage> </gmd:lineage> ...

92

12

345678

9

1011121314151617181920212223242526

1

</gmd: DQ_DataQuality> </gmd:dataQualityInfo> ...</gmd:MD_Metadata>

2.12.6 Coordinate reference system

Description of the coordinate reference system(s) used in the data set or supported in the service.

Interoperable spatial data services have the additional requirement;

TG Requirement 59 Where appropriate, Each supported coordinate reference system shall be expressed using an identifier.

Metadata element name Coordinate Reference SystemReference COMMISSION REGULATION (EU) No 1089/2010, article 13, clause 1

and COMMISSION REGULATION (EU) No 1089/2010, Annex VI, Part B 3

Definition Description of the coordinate reference system(s) used in the data set.

ISO 19115 number and name 13. referenceSystem

ISO/TS 19139 path referenceSystemInfo

INSPIRE obligation / condition Mandatory for dataset and dataset series;not applicable to Network services;

Conditional Mandatory if relevant for interoperableOther spatial data services: mandatory if category of other SDS is at least “harmonised”

INSPIRE multiplicity [1..*] for dataset and dataset series;[0..*] for Other spatial data services

Data type (and ISO 19115 no.) 186. MD_ReferenceSystem

Domain To identify the reference system, the referenceSystemIdentifier (RS_Identifier) shall be provided.


- 207. code [1] / domain value: free text

TG Requirement 2 in INSPIRE Data specifications states that a URI identifier listed in a table provided there shall be used for referring to the Coordinate reference system. The table is listed below. If the code is given as an URI as shown above, the element codespace is not needed. The identifiers can be accessed via gmx:Anchor (see XML example).For regions outside of continental Europe, Member States may define suitable coordinate reference systems

Example code: http://www.opengis.net/def/crs/EPSG/0/4258)

Comments ISO 19115 lists several elements which build MD_ReferenceSystem. For the purpose of theme-specific metadata according to the INSPIRE Data specifications the element listed above is sufficient.

93

123456

789

101112

1314

1516

1


It was not my idee to add metadata on this. But its in the IR, so we need to fulfill that


How is this planned to work in practice. A WMS already have this in it’s capabilities-. Should this be repeated here ?


TG Requirement 60 Coordinate Reference System property is not mandated by ISO 19115 but is mandated for conformance to the INSPIRE Regulation 1089/2010/EC (see Article 13, clause 1). At least one Coordinate Reference System must be specified.

TG Requirement 61 The code property is required (see B.2.7.3 of ISO 19115).

TG Requirement 62 Coordinate reference system parameters and identifiers shall be managed in one or several common registers for coordinate reference systems. Only identifiers contained in a common register shall be used for referring to the coordinate reference systems listed in this Section (see INSPIRE Regulation 1089/2010/EC, II, 1.5). The identifiers listed in the table below shall be used for referring to the coordinate reference systems used in a data set.


Short name http URI identifier

3D Cartesian in ETRS89 ETRS89-XYZ http://www.opengis.net/def/crs/EPSG/0/4936


ETRS89-GRS80h http://www.opengis.net/def/crs/EPSG/0/4937


ETRS89-GRS80 http://www.opengis.net/def/crs/EPSG/0/4258

2D LAEA projection in ETRS89 on GRS80

ETRS89-LAEA http://www.opengis.net/def/crs/EPSG/0/3035

2D LCC projection in ETRS89 on GRS80

ETRS89-LCC http://www.opengis.net/def/crs/EPSG/0/3034









2D TM projection in ETRS89 on GRS80, zone 30N (6°W to 0°)


2D TM projection in ETRS89 on GRS80, zone 31N (0° to 6°E)


















94

1

2345

6

7

8

9101112131415

16

1

Height in EVRS EVRS http://www.opengis.net/def/crs/EPSG/0/5730

3D compound: 2D geodetic in ETRS89 on GRS80, and EVRS height

ETRS89-GRS80-EVRS http://www.opengis.net/def/crs/EPSG/0/7409

Example of XML encoding (using free text):

<gmd:MD_Metadata> ... <gmd:referenceSystemInfo> <gmd:MD_ReferenceSystem> <gmd:referenceSystemIdentifier> <gmd:RS_Identifier> <gmd:code> <gco:CharacterString>http://www.opengis.net/def/crs/EPSG/0/4258</gco:CharacterString> </gmd:code> </gmd:RS_Identifier> </gmd:referenceSystemIdentifier> </gmd:MD_ReferenceSystem> </gmd:referenceSystemInfo> ...</gmd:MD_Metadata>

Example of XML encoding (using gmx:Anchor):

<gmd:MD_Metadata> ... <gmd:referenceSystemInfo> <gmd:MD_ReferenceSystem> <gmd:referenceSystemIdentifier> <gmd:RS_Identifier> <gmd:code><gmx:Anchor xlink:href="http://www.opengis.net/def/crs/EPSG/0/4258" xlink:title="ETRS89-GRS80">4258</gmx:Anchor> </gmd:code> </gmd:RS_Identifier> </gmd:referenceSystemIdentifier> </gmd:MD_ReferenceSystem> </gmd:referenceSystemInfo> ...</gmd:MD_Metadata>

2.12.7 Temporal Reference System

Description of the temporal reference system(s) used in the data set.

Metadata element name Temporal Reference SystemReference COMMISSION REGULATION (EU) No 1089/2010, article 13, clause 2

Definition Description of the temporal reference system(s) used in the data set.

ISO 19115 number and name 13. referenceSystemInfo

ISO/TS 19139 path referenceSystemInfo

INSPIRE obligation / condition Conditional for dataset and dataset series: Only required if a non-default temporal reference system (i.e. Gregorian Calendar or the Coordinated Universal Time) is used;

95

123456789

101112131415161718192021222324252627282930313233343536373839404142

43444546

1



roat, 08/20/15,

I think that the more suitable class to document the temporal Reference System is RS_ReferenceSystem in the Reference System Information package (its definition by ISO 19115 is "description of the spatial and temporal reference systems used in the dataset" - see http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/referenceSystem.xsd). That class could be conformant also to the Standard 19108 (Geographic information - Temporal schema), which, at Annex C (normative) defines the metadata elements for describing temporal reference systems. Unfortunately the above mentioned class is defined by ISO 19115 as abstract and without any relations with other classes. So, I haven't found the way to use it. Any idea?

http://www.opengis.net/def/crs/EPSG/0/4258%22

not applicable to services.


Data type (and ISO 19115 no.) 186. MD_ReferenceSystem

Domain No specific type is defined in ISO 19115 for temporal reference systems. Thus, the generic MD_ReferenceSystem element and its referenceSystemIdentifier (RS_Identifier) property shall be provided.


- 207. code [1] / domain value: free text-

Example code: JulianCalendar

Comments The primary temporal reference system for use with geographic information is the Gregorian Calendar and 24 hour local or Coordinated Universal Time (UTC), but special applications may entail the use of alternative reference systems. So this element is mandatory only if the spatial data set contains temporal information that does not refer to the default temporal reference system.ISO 19115 lists several elements which build MD_ReferenceSystem. For the purpose of theme-specific metadata according to the INSPIRE Data specifications the element listed above is sufficient.

Further elements like authority, codeSpace and version are optional but may be included for completeness if required..

TG Requirement 63 Temporal Reference System property is not mandated by ISO 19115 but is mandated for conformance to the INSPIRE Regulation 1089/2010/EC only if the Temporal Reference System is other than Gregorian Calendar or the Coordinated Universal Time (see Article 13, clause 2).


<gmd:MD_Metadata> ... <gmd:referenceSystemInfo> <gmd:MD_ReferenceSystem> <gmd:referenceSystemIdentifier> <gmd:RS_Identifier> <gmd:code> <gco:CharacterString>JulianCalendar</gco:CharacterString> </gmd:code> </gmd:RS_Identifier> </gmd:referenceSystemIdentifier> </gmd:MD_ReferenceSystem> </gmd:referenceSystemInfo> ...</gmd:MD_Metadata>

96

1

23456

789

101112131415161718192021222324252627

1

2.12.8 Encoding

Description of the computer language construct(s) specifying the representation of data objects in a record, file, message, storage device or transmission channel.

Metadata element name EncodingReference COMMISSION REGULATION (EU) No 1089/2010, article 13, clause 3

Definition Description of the computer language construct(s) specifying the representation of data objects in a record, file, message, storage device or transmission channel.

ISO 19115 number and name 271.distributionFormat

ISO/TS 19139 path distributionInfo/MD_Distribution/distributionFormat

INSPIRE obligation / condition Mandatory for dataset and dataset series;not applicable to services


Data type (and ISO 19115 no.) 284. MD_Format

Domain This is a complex type (lines 285-290 from ISO 19115). At least the following elements that are mandatory for ISO should be used (the multiplicity according to ISO 19115 is shown in parentheses):

- 285. name [1] / domain value: free text- 286. version [1] / domain value: free text

Content for name could also be taken from INSIPRE Registry using the codelist available here: http://inspire.ec.europa.eu/media-types/ and can be accessed via gmx:Anchor (see XML example).

Example name: GMLversion: 3.2.1

Comments ISO 19115 lists several elements which build MD_Format. For the purpose of theme-specific metadata according to the INSPIRE Data specifications the elements listed above are sufficient.Instead of using element specification here the documentation of the supported data scheme inside the distributed dataset (as mentioned in INSPIRE Data specification) can be given either in conformity statement (see 2.8) or the maybe existing metadata element applicationSchemaInfo (see ISO 19115, B.2.1, No. 21).

TG Requirement 64 Encoding property (in the meaning of the supported file format when providing data) is not mandated by ISO 19115 but is mandated for conformance to the INSPIRE Regulation 1089/2010/EC (see Article 13, clause 3).

TG Recommendation 32 T he documentation of the supported data scheme inside the distributed dataset (as mentioned in INSPIRE Data specification) can be given either in conformity statement (see 2.8) or the maybe existing metadata element applicationSchemaInfo (see ISO 19115, B.2.1, No. 21).

Example of XML encoding (using free text):

<gmd:MD_Metadata> ... <gmd:distributionInfo> <gmd:MD_Distribution>

97

12345

6

789

10

11

1213141516

17181920212223

1

http://inspire.ec.europa.eu/media-types/

... <gmd:distributionFormat> <gmd:MD_Format> <gmd:name> <gco:CharacterString>GML</gco:CharacterString> </gmd:name> <gmd:version> <gco:CharacterString>3.2.1</gco:CharacterString> </gmd:version> </gmd:MD_Format> <gmd:distributionFormat> ... </gmd:MD_Distribution> </gmd:distributionInfo> ...</gmd:MD_Metadata>

Example of XML encoding (using gmx:Anchor):

<gmd:MD_Metadata> ... <gmd:distributionInfo> <gmd:MD_Distribution> ... <gmd:distributionFormat> <gmd:MD_Format> <gmd:name> <gmx:Anchor xlink:href="http://inspire.ec.europa.eu/media-types/">application/gml+xml</gmx:Anchor> </gmd:name> <gmd:version> <gco:CharacterString>unknown</gco:CharacterString> </gmd:version> </gmd:MD_Format> <gmd:distributionFormat> ... </gmd:MD_Distribution> </gmd:distributionInfo> ...</gmd:MD_Metadata>

2.12.9 Character Encoding

Full name of the character encoding used for the data set. You must supply this character set if you are not using UTF-8.

Metadata element name Character EncodingReference COMMISSION REGULATION (EU) No 1089/2010, article 13, clause 5

Definition Full name of the character coding standard used for the dataset

ISO 19115 number and name 40. characterSet

ISO/TS 19139 path identificationInfo[1]/*/characterSet

INSPIRE obligation / condition Conditional for dataset and dataset series: mandatory if NOT using standard UTF-8 encoding;not applicable to services


98

123456789

1011121314151617181920212223242526272829303132333435363738394041424344

4546474849

1

http://inspire.ec.europa.eu/media-types/%22%3Eapplication/gml+xml%3C/gmx:Anchor

http://inspire.ec.europa.eu/media-types/%22%3Eapplication/gml+xml%3C/gmx:Anchor

Data type (and ISO 19115 no.) MD_CharacterSetCode

Domain CodeList (see B.5.10 of ISO 19115)

Example usAsciiComments

TG Requirement 65 The Character Encoding property is not mandated by ISO 19115 but is mandated for conformance to the INSPIRE Regulation 1089/2010/EC only if not using UTF-8 (see Article 13, clause 5).

TG Recommendation 33 Use of character encoding other that UTF-8 is discouraged unless there are compelling and overriding reasons to use it.


<gmd:MD_Metadata> ... <gmd:identificationInfo> <gmd:MD_DataIdentification> ... <gmd:characterSet> <gmd:MD_CharacterSetCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/gmxCodelists.xml#MD_CharacterSetCode" codeListValue="usAscii">usAscii</gmd:MD_CharacterSetCode> </gmd:characterSet> ... </gmd:MD_DataIdentification> </gmd:identificationInfo> ...</gmd:MD_Metadata>

2.12.10 Spatial representation type


Metadata element name Spatial representation typeReference COMMISSION REGULATION (EU) No 1089/2010, article 13, clause 6

(element added by amendment 1253/2013)

Definition The method used to spatially represent geographic information

ISO 19115 number and name 37. SpatialRepresentationType

ISO/TS 19139 path identificationInfo[1]/*/spatialRepresentationType

INSPIRE obligation / condition Mandatory for dataset and dataset series;not applicable to services


Data type (and ISO 19115 no.) MD_SpatialRepresentation TypeCode

Domain Codelist (see B.5.26 of ISO 19115), following INSPIRE Data specifications only vector, grid and tin should be used.

Example "vector"

99

1

234

5

67

89

1011121314151617181920212223242526272829

30313233

1

Comments This element is used to broadly categorise a spatial data resource being described.

TG Requirement 66 The Spatial representation type property is not mandated by ISO 19115 but is mandated for conformance to the INSPIRE Regulation 1089/2010/EC (see Article 13, clause 6). At least one Spatial representation type shall be recorded and domain values shall be taken from the Codelist B.5.26 from ISO 19115.

TG Requirement 67 The value of MD_SpatialRepresentationTypeCode in the scope of Directive INSPIRE are: vector, grid or tin.


<gmd:MD_Metadata> ... <gmd:identificationInfo> <gmd:MD_DataIdentification> ... <gmd:spatialRepresentationType> <gmd:gmd:MD_SpatialRepresentationTypeCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/gmxCodelists.xml#MD_SpatialRepresentationTypeCode" codeListValue="vector">vector</gmd:MD_SpatialRepresentationTypeCode> </gmd:spatialRepresentationType> ... </gmd:MD_DataIdentification> </gmd:identificationInfo> ...</gmd:MD_Metadata>

2.12.11 Topological Consistency

Correctness of the explicitly encoded topological characteristics of the data set as described by the scope.

While giving this metadata element as one of the “Metadata elements for interoperability” in chapters 8.2 of INSPIRE Data specifications the description of “Topological consistency” refers to chapters 8.3.2 (“Metadata elements for reporting data Quality”). All the elements mentioned there are based on ISO 19157, which provides different ways to report data quality information. INSPIRE Data specifications make use of two ways: reporting quantitative results and reporting descriptive results. ISO 19157 itself works along with metadata structures according to ISO 19115-1.As long as being based on ISO 19115 only, a mapping of the metadata elements designated in ISO 19157 to metadata elements existing in ISO 19115 is necessary:

- For quantitative results there is an equivalent structure in ISO 19115, so the mapping is obvious.

- For descriptive results there is no matching element matching directlythat seems likely. The attempt here is to store the information in an instance of DQ_ConformanceResult instead. The descriptive result itself can be stored in element explanation which is free text; the elements specification and pass will be filled with citing the Generic Network Model and the value FALSE. This is exactly the condition when to have this metadata issue Topologogical consistency at all when following Implementing Rule 1089/2010 (article 13).

100

1

23456

7

89

10111213141516171819202122232425262728293031

3233343536373839404142434445464748495051525354

1

2.12.11.1 Topological Consistency – Quantitative results

Metadata element name Topological Consistency – Quantitative resultsReference COMMISSION REGULATION (EU) No 1089/2010, article 13, clause 4


ISO 19115 number and name 80. report

ISO/TS 19139 path dataQualityInfo/DQ_DataQuality/report/



Data type (and ISO 19115 no.) 115. DQ_TopologicalConsistency

Domain DQ_TopologicalConsistency is a forming of the abstract complex type DQ_Element. See B.2.4.3 in ISO 19115:2003 for further information.









Due to making use of DQ_QuantitativeResult subset there is a mandatory element in ISO 19115 to be considerer too:



Comments ISO 19115 lists several elements which build DQ_Element. For the purpose of theme-specific metadata according to the INSPIRE Data specifications the elements won by mapping from ISO 19157 are sufficient.This element is mandatory only if the data set includes types from the Generic Network Model and does not assure centreline topology (connectivity of centrelines) for the network.

101

1

23

4

1

TG Recommendation 34 As long as being based on ISO 19115 only, the metadata elements reporting quantitative results on Topological consistency should be expressed by corresponding ISO 19115 elements of DQ_QuantitativeResult as shown in the table above. Due to ISO 19115 one mandatory element (valueUnit) is added there though not derived from matching with the foreseen ISO 19157 elements.


<gmd:MD_Metadata> ... <gmd:dataQualityInfo> <gmd:DQ_DataQuality> ... <gmd:report> <gmd:DQ_TopologicalConsistency> <gmd:nameOfMeasure> <gco:CharacterString>number of faulty point-curve connections</gco:CharacterString> </gmd:nameOfMeasure> ... <gmd:evaluationMethodType> <DQ_EvaluationMethodTypeCode xmlns="http://www.isotc211.org/2005/gmd" codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml# DQ_EvaluationMethodTypeCode" codeListValue="indirect"/> </gmd:evaluationMethodType> <gmd:evaluationMethodDescription> <gco:CharacterString>A point-curve connection exists where different curves touch. These curves have an intrinsic topological relationship that shall reflect the true constellation. If the point-curve connection contradicts the universe of discourse, the point-curve connection is faulty with respect to this data quality measure. The data quality measure counts the number of errors of this kind.</gco:CharacterString> </gmd:evaluationMethodDescription> ... <gmd:dateTime> <gco:DateTime>2015-04-01T16:20:00</gco:DateTime> </gmd:dateTime> <gmd:result> <gmd:DQ_QuantitativeResult> ... <gmd:valueUnit xlink:href="http://www.opengis.net/def/uom/OGC/1.0/unity"/> ... <gmd:value> <gco:Record xsi:type="xs:integer">12</gco:Record> </gmd:value> </gmd:DQ_QuantitativeResult> </gmd:result> </gmd:DQ_TopologicalConsistency> </gmd:report> ... </gmd: DQ_DataQuality> </gmd:dataQualityInfo> ...</gmd:MD_Metadata>

102

123456

789

10111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061

1

Kochmann, Peter, 08/20/15,

@Eliane: Is this code suitable with your example?

2.12.11.2 Topological Consistency – Descriptive results

Metadata element name Topological Consistency – Descriptive resultsReference COMMISSION REGULATION (EU) No 1089/2010, article 13, clause 4






Data type (and ISO 19115 no.) 115. DQ_TopologicalConsistency

Domain DQ_TopologicalConsistency is a forming of the abstract complex type DQ_Element. See B.2.4.3 in ISO 19115:2003 for further information.

To provide the descriptive results of Topological consistency evaluation DQ_ConformanceResult containing the following elements should be used (the multiplicity according to ISO 19115 is shown in parentheses):

- 130. specification [1..1]: citation of product specification or user requirement against which data is being evaluated / domain value: CI_Citation

- 131. explanation [1..1]: explanation of the meaning of conformance for this result / domain value: free text

- 132. pass [1..1]: indication of the conformance result / domain value: Boolean

Example specification: INSPIRE Data Specifications - Base Models - Generic Network Model- see XML example -–pass: false

Comments To provide the descriptive results of Topological consistency evaluation DQ_ConformanceResult should be used because there is no well matching element for descriptive results at all. The specification to be cited in this case will be the Generic Network Model and pass will be FALSE. This is exactly the condition when to have this statement at all (see reference above).

TG Recommendation 35 As long as being based on ISO 19115 only, the metadata elements reporting descriptive results on Topological consistency should be expressed by using DQ_ConformanceResult (with specification = Generic Network Model and pass = FALSE).


<gmd:MD_Metadata> ... <gmd:dataQualityInfo> <gmd:DQ_DataQuality> ... <gmd:report> <gmd:DQ_TopologicalConsistency> ... <gmd:dateTime> <gco:DateTime>2015-04-01T16:20:00</gco:DateTime> </gmd:dateTime> <gmd:result>

103

12

3

4567

89

10111213141516171819202122

1

<gmd:DQ_ConformanceResult> <gmd:specification> <CI_Citation> <title> <gco:CharacterString>INSPIRE Data Specifications - Base Models - Generic Network Model</gco:CharacterString> </title> <date> <CI_Date> <date> <gco:Date>2013-04-05</gco:Date> </date> <dateType> <gmd:CI_DateTypeCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/gmxCodelists.xml#CI_DateTypeCode" codeListValue="publication">publication</gmd:CI_DateTypeCode> </dateType> </CI_Date> </date> </CI_Citation> </gmd:specification> <gmd:explanation> <gco:CharacterString>---place descriptive results here---</gco:CharacterString> </gmd:explanation> <gmd:pass> <gco:Boolean>false</gco:Boolean> </gmd:pass> </gmd:DQ_ConformanceResult> </gmd:result> </gmd:DQ_TopologicalConsistency> </gmd:report> ... </gmd: DQ_DataQuality> </gmd:dataQualityInfo> ...</gmd:MD_Metadata>

104

123456789

10111213141516171819202122232425262728293031323334353637383940414243

1

2.13 Theme-specific metadata elements from Data specifications

“Population distribution”). Everyone is free to have these elements with other than the mentioned INSPIRE annex themes as well. TG Recommendation XX The metadata describing a spatial dataset or spatial dataset series should comprise the theme-specific metadata elements specified in the following paragraphs if the particular INSPIRE annex theme is listed there.

2.13.1 Maintenance information

nformation about the fre scope of those updates.

MD_Ma

TG Recommendation 36 TG Recommendation XX The metadata elements concerning maintenance information should be included to metadata describing a spatial dataset or spatial dataset series related to each of the INSPIRE annex themes with the exception of “Population distribution” because of missing chapter 8 in the data specification.

<gmd:MD_Metadata> <gmd:identificationInfo> ...eMan <gmd:MD_MaintenanceInformation> <gm <MD_MaintenanceFrequencyCode xmlns="http://www.isotc211.org/2005/gmd" codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#MD_MaintenanceFrequencyCode" codeListValue="annually"/>enance <gmd:updateScope>Code ="htttc211.org/2 </gmd:updateScope> <gco:CharacterString>updatet completely every year</gco:CharacterString> </gmd:MD_MaintenanceInformation>sou .../gmD_D </gmd:identificationInfo></gmd:MD_Metadata>

2.13.2

105

1234567

89

10

111213141516

1718192021222324252627282930313233343536

3738

1

information

spat

MD_Sp

is an abstract complex ty_GridSpatialRepresentation, MD_G

TG Recommendation 37 The metadata elements concerning spatial representation information should be included to metadata describing a spatial dataset or spatial dataset series related to the following INSPIRE annex themes:

Elevation

Example of XML encoding:<gmd:MD_Metadata> <gmd:spatialRepresentationInfo> </gmd:spatialRepresentationInfo></gmd:MD_Metadata>

2.13.3

information

Vector t. Grid or Tin - Interpolation method recommended by the data provider in order to calculate the elevation values at any direct position within the DEM extent (either a grid coverage or TIN surface. The calculation involves the interpolation of the elevation values known for the grid coverage range set points or TIN control points, respectively). The values defined for the CV_InterpolationType code list defined in ISO 19123:2005 should be re-used where possible.

106

1

2345

6

789

101112

1314

1

TG Recommendation 38 TG Recommendation XX The metadata elements concerning supplemental information should be included to metadata describing a spatial dataset or spatial dataset series related to the following INSPIRE annex themes:

... <gmd:MD_DataIdentification> <gmd:supplementalInformation>:Cha </gmd:supplementalInformation>/gmd:MD_DataIdentification> ...

2.13.4 Process step

n

Definition

LI_ProcessStep. For the purpose of theme-specaccording to tNote that the path for dataQualityInfo/DQ_DataQuality/lineage/ will already exist in metadata because of being used for carrying information about lineage itself (see 2.7.1). Therefore an addition of these information into the same entity of LI_Lineage may be useful.This metadata element aims to supplement the Lineage metadata element defined in Regulation 1205/2008/EC with a precise description of a process or operation that has been applied to the elevation or In the case of the data acquisition process it is important to highlight any known limitations which may lead to quality problems, for example the description of the geographical areas where the reliability of geographic information is reduced or limited due to limitations of the data capture technology used. Information relative to the geometry of low reliability areas (e.g. links to elsewhere such geometries may be obtained) can be particularly helpful to assess the accuracy and the reliability of the elevation data set.

TG Recommendation 39 TG Recommendation XX The metadata elements concerning process step should be included to metadata describing a spatial dataset or spatial dataset series related to the following INSPIRE annex themes:

TG Recommendation 40 TG Recommendation XX This element is already used for documenting the lineage of the resource (see 2.7.1). Therefore an addition of these information into the same entity of LI_Lineage may be useful.

107

1234

5

6789

10111213

141516

17181920

21

22232425

1

<gmd:MD_Metadata> <gmd:dataQualityInfo> ...> <gmd:LI_Lineage> ... <gmd:processStep><gco:CharacterString>---appropriate text---</gco:CharacterString>...neag </gmd:lineage>... </gmd: DQ_DataQuality>liIn ...

2.13.5 Data source

Definition

Either the description (93., free text) or the sourceExtent (97., EX_Extent) elements shall be provided.

LI_Source. For the purpose of theme-specific accordingNote that the path for dataQualityInfo/DQ_DataQuality/lineage/ will already exist in metadata because of being used for carrying information about lineage itself (see 2.7.1). Therefore an addition of these information into the same entity of LI_Lineage may be useful.This metadata element aims to supplement the Lineage metadata element defined in Regulation 1205/2008/EC with a precise description of data sources that have been used as input to generate the elevation or orthoimagery dataset. e described and referenced here: conditions of data acquisition (e.g. sensors characteristics, data properties like image overlaps, known lacks of source data, solar elevation, etc).

TG Recommendation 41 TG Recommendation XX The metadata elements concerning data source should be included to metadata describing a spatial dataset or spatial dataset series related to the following INSPIRE annex themes:

TG Recommendation 42 TG Recommendation XX This element is already used for documenting the lineage of the resource (see 2.7.1). Therefore an addition of these information into the same entity of LI_Lineage may be useful.

<gmd:MD_Metadata> <gmd:dataQualityInfo> ...

108

123456789

101112

131415

16171819

20

21222324

25262728

1

> <gmd:LI_Lineage> ... <gmd:source><gco:CharacterString>---appropriate text---</gco:CharacterString>...neag </gmd:lineage>... </gmd: DQ_DataQuality>liIn ...

2.13.6 Browse graphic information

Definition )

The following element is mandatory (the multiplicity according to ISO 19115 is shown in brackets):

-

ML ex

which build MD_BrowseGraphic. Forpurpoecifications the element listed above is sufficient.

TG Recommendation 43 TG Recommendation XX The metadata elements concerning browse graphic information should be included to metadata describing a spatial dataset or spatial dataset series related to the following INSPIRE annex themes:

Example of XML encoding:<gmd:MD_Metadata> <gmd:identificationInfo> ......DaId </gmd:identificationInfo>.</gmd:MD_Metadata>

2.13.7

109

12345678

91011

12131415

16

1718192021222324

2526

1

At least the following element should be used: - attributeDescription [1]- 241.

- ML ex

MD_ImageDescription. For the purpose of them according to the I listed above are sufficient.

TG Recommendation 44 TG Recommendation XX The metadata elements concerning image description should be included to metadata describing a spatial dataset or spatial dataset series related to the following INSPIRE annex themes:

... <gmd:MD_ImageDescription> <---appropriate content---tion> <gmd:contentType>/gmd:contentType>cloudCoverPercentage> <gcoecimal>cloudCoverPercentage> ...</gmd:contentInfo> ...

2.13.8 Content information

MD_Fe

Data specification on Buildings does not give a minimum element. FeatureCatalogueDescription:includedWithDataset [1]

- 238.

ML ex

MD_ FeatureCatalogueDescription. For the pure ocording to the INSPIRE Data e are sufficient.supplied in annex E of Data Specification on Buildings for additional information once they have been filled by the data producer, just by ticking the populated features and properties.

TG Recommendation 45 TG Recommendation XX The metadata elements concerning content information should be included to metadata describing a spatial dataset or spatial dataset series related to the following INSPIRE annex themes:

...

110

1234

5

6789

10111213141516

171819

20212223

24

2526

1

<gmd:MD_FeatureCatalogueDescription> ....</gmd:MD_Metadata>

2.13.9

Definition

-278 from ISO 19115). At least the following elements should be used (the multiplicity according to ISO 19115 is shown in parentheses):

- 275. unitsOfDistribution [0..1]: tiles, layers, geographic areas, etc., in which data is available / domain value: free text

- ]: inforaFor Hydrography:- ted size of a unit in the specified transfer format, expressed in

megabytes. The transfer size is > 0.0/ domain value: Real

may already exist in metadata if being used for carrying information about online access (277. online, see 2.2.4). Therefore an addition of these information into the same entity of MD_DigitalTransferOptions may be useful.

TG Recommendation 46 TG Recommendation XX The metadata elements concerning digital transfer options information should be included to metadata describing a spatial dataset or spatial dataset series related to the following INSPIRE annex themes:

TG Recommendation 47 also carry informatl (see 2.2.4). Therefore the path for distributionInfo/MD_Distribution/transferOptions/ can already exist in metadata esent Digital transfer option into thesmTransferOptions may beful.

...... <gmd:unitsOfDistribution> <gco:CharacterString>tiles of 4 square metres</gco:CharacterString></gmd:transferSize> <MD_MediumNameCode xmlns="http://www.isotc211.org/2005/gmd" codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#MediumNameCode" codeListValue="dvdRom"/> </gmd:name></gmd:transferOptions> <...

111

1234

56

789

10

11

12

13141516

171819202122232425262728293031

1

</gmd:MD_Metadata>

2.13.10

335-338 from ISO 19115). In addition to the Geographic bounding box (see 2.5.1) the following element should be used to provide a common "name" for the extent (the multiplicity according to ISO 19115 is shown in parentheses):

- xtent for the referring object/ domain value: fe

Use the terms provided here: <http://dataservice.eea.europa.eu/dataservice/metadetails.asp?id=1041>

EX_Extent. For the purpose of theme-specific accordin

TG Recommendation 48 TG Recommendation XX The metadata elements concerning extent information should be included to metadata describing a spatial dataset or spatial dataset series related to the following INSPIRE annex themes:

TG Recommendation 49 2.5.1

... <gmd:MD_DataIdentification> <gmd:extent>...DaId </gmd:identificationInfo>.</gmd:MD_Metadata>

2.13.11

to report data quality information. INSPIRE Data specifications make use of two ways: reporting quantitative results and reporting descriptive results. ISO 19157 itseements designated in ISO 19157 to metadata elements existing in ISO 19115 is necessary:

- For quantitative results there is a equivalent structure in ISO 19115descriptive results there is no matching element that seems likely. The attempt here is to store the data quality statements in the existing Lineage statement and flag them as a turnout from data quality.

2.13.11.1 Data Quality – Quantitative results

Quantitative re

112

12

34

5678

9

10

1112131415161718

19202122232425262728

2930

1

has to be expressed by a corresponding DQ_xning the particular nameOfMeasure [0..*]: name of the test applied to the data / domain value: free text



- 107. ..2]: valet of va of evaluating the obtained value (or set of values) against a spentitativeResult, consisting of

- 137. f DQ_QuantitativeResult subset there is a mandatory element in ISO 19115 to be considerer too:

-

which build DQ_Element. For the pe of pecificaccording

TG Recommendation 50 TG Recommendation XX As long as being based on ISO 19115 only the metadata elements reporting quantitative results as given in INSPIRE Data specifications’ chapters 8.3.2 should be expressed by corresponding ISO 19115 elements as shown in the table above considering a mandatory element given by ISO 19115 in addition.

Example of XML encoding:<gmd:MD_Metadata> <gmd:dataQualityInfo> ...<gco:CharacterString>---appropriate text---</gco:CharacterString>

<gm <DQ_EvaluationMethodTypeCode xmlns="http://www.isotc211.org/2005/gmd" codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml# DQ_EvaluationMethodTypeCode" codeListValue="indirect"/>/gmd:ea <gmd:evaluationMethodDescription>/gmd:evaluationMethodDescription> <gmd:dateTime>

<gmd:valueUnit> </gmd:valueUnit> <gmd:value> </gmd:value>/gmd:DQ... </gmd: DQ_DataQuality> ...

113

123456

789

101112131415161718192021222324252627282930

1

2.13.11.2 Data Quality – Descriptive results

Descriptive res

LI_L

85-85 from ISO 19115). To provide the descriptive results of data quality evaluation the following element should be used (the multiplicity according to ISO 19115 is shown in parentheses):

- statement [C..1]: general explanation of the data producer’s knowledge about the lineage of a dataset / domain value: free text

INSPIRE Data specifications the element listed above is sufficient. the path for dataQualityInfo/DQ_DataQuality/lineage/ will already exist in metadata because of being used for carrying information about lineage itself (see 2.7.1). Therefore an addition of these information into the same entity of LI_Lineage may be useful but has to be flagged by using the name of the corresponding DQ_xxx subelement concerning the particular data quality issue (e.g. ConceptualConsistency) as a prefix or topic in the lineage element.

2.14The following metadata elements are named in chapters 8.3 of INSPIRE Data specifications (“Recommended theme-specific metadata elements”). All of them are optional but recommended for certain INSPIRE annex themes. Each of the following metadata elements therefore carries a list of involved INSPIRE annex themes in the “TG Recommendation box” (exception is the first one “Maintenance information”; it apllies to all INSPIRE annex themes but “Population distribution”). Everyone is free to have these elements with other than the mentionedforeseen INSPIRE annex themes as well. A list of the particular INSPIRE Annex themes in combination with the metadata elements described here along with further information and examples can be found in document to be done.

TG Recommendation 51 The metadata describing a spatial dataset or spatial dataset series should comprise the theme-specific metadata elements specified in the following paragraphs if the particular INSPIRE annex theme is listed there.

2.14.1 Maintenance information

This element provides information about the frequency of resource updates and the scope of those updates.

Metadata element name Maintenance informationReference INSPIRE Data specifications, chapters 8.3.x1

Definition Information about the scope and frequency of updating

ISO 19115 number and name 30. resourceMaintenance

114

12

3456789

10111213

14151617

18

1920212223

1

ISO/TS 19139 path identificationInfo[1]/MD_DataIdentification/resourceMaintenance/

INSPIRE obligation / condition optional for dataset and dataset series;not applicable to services

INSPIRE multiplicity [0..1] for dataset and dataset series

Data type (and ISO 19115 no.) 142. MD_MaintenanceInformation

Domain This is a complex type (lines 143-148 from ISO 19115). At least the following element should be used (the multiplicity according to ISO 19115 is shown in parentheses):

- 143. maintenanceAndUpdateFrequency [1]: frequency with which changes and additions are made to the resource after the initial resource is completed / domain value: MD_MaintenanceFrequencyCode

In addition the following elements are recommended, but in contrast to ISO each of them should not appear multiple but single only:

- 146. updateScope [0..*]: scope of data to which maintenance is applied / domain value: MD_ScopeCode

- 148. maintenanceNote [0..*]: information regarding specific requirements for maintaining the resource / domain value: free text

Example maintenanceAndUpdateFrequency: annuallyupdateScope: dataset- see XML example -

Comments ISO 19115 lists several elements which build MD_MaintenanceInformation. For the purpose of theme-specific metadata according to the INSPIRE Data specifications the three elements listed above are sufficient.

TG Recommendation 52 The metadata elements concerning maintenance information should be included to metadata describing a spatial dataset or spatial dataset series related to each of the INSPIRE annex themes with the exception of “Population distribution” because of missing chapter 8 in the data specification.


<gmd:MD_Metadata> ... <gmd:identificationInfo> <gmd:MD_DataIdentification> ... <gmd:resourceMaintenance> <gmd:MD_MaintenanceInformation> <gmd:maintenanceAndUpdateFrequency> <MD_MaintenanceFrequencyCode xmlns="http://www.isotc211.org/2005/gmd" codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#MD_MaintenanceFrequencyCode" codeListValue="annually"/> </gmd:maintenanceAndUpdateFrequency> <gmd:updateScope> <MD_ScopeCode xmlns="http://www.isotc211.org/2005/gmd" codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#MD_ScopeCode" codeListValue="dataset"/> </gmd:updateScope> <gmd:maintenanceNote> <gco:CharacterString>updatedt completely every year</gco:CharacterString>

115

1

23456

789

101112131415161718192021222324252627282930313233

1

</gmd:maintenanceNote> </gmd:MD_MaintenanceInformation> </gmd:resourceMaintenance> ... </gmd:MD_DataIdentification> </gmd:identificationInfo> ...</gmd:MD_Metadata>

2.14.2 Spatial representation information

Digital representation of spatial information in the dataset.

Metadata element name Spatial representation informationReference INSPIRE Data specifications, chapters 8.3.xINSPIRE Data specification

on Elevation, chapter 8.3.3 (D2.8.II.1)

Definition Digital representation of spatial information in the dataset

ISO 19115 number and name 12. spatialRepresentationInfo

ISO/TS 19139 path spatialRepresentationInfo/

INSPIRE obligation / condition optional for dataset and dataset series concerning INSPIRE annex theme Elevation;not applicable to services


Data type (and ISO 19115 no.) 156. MD_SpatialRepresentation

Domain MD_SpatialRepresentation is an abstract complex type and has to be expressed as MD_GridSpatialRepresentation, MD_Georectified, MD_Georeferenceable or MD_VectorSpatialRepresentation.See B.2.6 in ISO 19115:2003 for further information.


Comments For further information on theme-specific presettings see document to be done

TG Recommendation 53 The metadata elements concerning spatial representation information should be included to metadata describing a spatial dataset or spatial dataset series related to the following INSPIRE annex themes:

Elevation


<gmd:MD_Metadata> ... <gmd:spatialRepresentationInfo>--- theme-specific content, see separate documentto be done --- </gmd:spatialRepresentationInfo> ...</gmd:MD_Metadata>

2.14.3 Supplemental information

116

123456789

10

11121314

15

16171819

20

212223242526272829303132

3334

1

Any other descriptive information about the dataset.

Metadata element name Supplemental informationReference INSPIRE Data specifications, chapters 8.3.xINSPIRE Data specification

on Elevation, chapter 8.3.4 (D2.8.II.1)

Definition Any other descriptive information about the dataset

ISO 19115 number and name 46. supplementalInformation

ISO/TS 19139 path identificationInfo[1]/MD_DataIdentification/supplementalInformation

INSPIRE obligation / condition optional for dataset and dataset series concerning INSPIRE annex theme Elevation;not applicable to services



Domain Free text


Comments For further information on theme-specific presettings see document to be doneThis metadata element is recommended to concisely describe general properties of the spatial data set which should be traced here. As illustration, depending on the spatial representation types of the data set: Vector - Contour line vertical intervals (i.e. equidistance parameters), indicating in which geographic areas and/or conditions they are used (if any) within the data set.

Grid or Tin - Interpolation method recommended by the data provider in order to calculate the elevation values at any direct position within the DEM extent (either a grid coverage or TIN surface. The calculation involves the interpolation of the elevation values known for the grid coverage range set points or TIN control points, respectively). The values defined for the CV_InterpolationType code list defined in ISO 19123:2005 should be re-used where possible. - Description of the geographic features that are included (measured) within the DEM surface. Organizations very often have discrepancies to what it is considered as a pure DTM or DSM. Data providers should explain here any existing deviations from the concepts of pure DTM / DSM. As illustration, declaration of any known dynamic features included within the DEM surface, limitations due to the data capture process (e.g. trees or bridges not included within a DSM), if water body surfaces have been flattened or not, etc.

TG Recommendation 54 The metadata elements concerning supplemental information should be included to metadata describing a spatial dataset or spatial dataset series related to the following INSPIRE annex themes:

Elevation


<gmd:MD_Metadata> ...

117

12

3

456

7

89

101112

1

<gmd:identificationInfo> <gmd:MD_DataIdentification> ... <gmd:supplementalInformation> <gco:CharacterString>---appropriate text------ theme-specific content, see separate document --- </gco:CharacterString> </gmd:supplementalInformation> ... </gmd:MD_DataIdentification> </gmd:identificationInfo> ...</gmd:MD_Metadata>

2.14.4 Process step

Information about events in the life of a dataset specified by the scope.

Metadata element name Process stepReference INSPIRE Data specifications, chapters 8.3.xINSPIRE Data specification

on Elevation, chapter 8.3.5 (D2.8.II.1),INSPIRE Data specification on Orthoimagery, chapter 8.3.5 (D2.8.II.3)

Definition Information about an event or transformation in the life of a dataset including the process used to maintain the dataset

ISO 19115 number and name 84. processStep

ISO/TS 19139 path dataQualityInfo/DQ_DataQuality/lineage/LI_Lineage/processStep/

INSPIRE obligation / condition optional for dataset and dataset series concerning INSPIRE annex themes Elevation and Orthoimagery;not applicable to services


Data type (and ISO 19115 no.) 86. LI_ProcessStep

Domain This is a complex type (lines 87-91 from ISO 19115).The description (87., free text) property shall be provided.


Comments ISO 19115 lists several elements which build LI_ProcessStep. For the purpose of theme-specific metadata according to the INSPIRE Data specifications the element listed above is sufficient.Note that the path for dataQualityInfo/DQ_DataQuality/lineage/ will already exist in metadata because of being used for carrying information about lineage itself (see 2.7.1). Therefore an addition of these information into the same entity of LI_Lineage may be useful.

For further information on theme-specific presettings see document to be doneThis metadata element aims to supplement the Lineage metadata element defined in Regulation 1205/2008/EC with a precise description of a process or operation that has been applied to the elevation or orthoimagery dataset. For example, the following processing steps may be traced here: - data acquisition - data editing - aero/spatio-triangulation - stereo-plotting- grid calculation / sampling

118

123456789

101112131415

16171819

1

- orthorectification - mosaicking - radiometric correction

Note that such information may convey, most often implicitly, supplementary indications of the expected quality of a dataset, which often depends on the nature of the production process. In the case of the data acquisition process it is important to highlight any known limitations which may lead to quality problems, for example the description of the geographical areas where the reliability of geographic information is reduced or limited due to limitations of the data capture technology used. Information relative to the geometry of low reliability areas (e.g. links to elsewhere such geometries may be obtained) can be particularly helpful to assess the accuracy and the reliability of the elevation data set.

TG Recommendation 55 The metadata elements concerning process step should be included to metadata describing a spatial dataset or spatial dataset series related to the following INSPIRE annex themes:

ElevationOrthoimagery

TG Recommendation 56 This element is already used for documenting the lineage of the resource (see 2.7.1). Therefore an addition of these information into the same entity of LI_Lineage may be useful.


<gmd:MD_Metadata> ... <gmd:dataQualityInfo> <gmd:DQ_DataQuality> ... <gmd:lineage> <gmd:LI_Lineage> ... <gmd:processStep> <gmd:LI_ProcessStep> <gmd:description> <gco:CharacterString>---appropriate text------ theme-specific content, see separate document --- </gco:CharacterString> </gmd:description> ... </gmd:LI_ProcessStep> </gmd:processStep> ... </gmd:LI_Lineage> </gmd:lineage> ... </gmd: DQ_DataQuality> </gmd:dataQualityInfo> ...</gmd:MD_Metadata>

119

1

234

5

6

7

89

10

11121314151617181920212223242526272829303132333435363738394041

1

2.14.5 Data source

Information about the source data used in creating the data specified by the scope.

Metadata element name Data sourceReference INSPIRE Data specifications, chapters 8.3.xINSPIRE Data specification


Definition Information about the source data used in creating the data specified by the scope

ISO 19115 number and name 85. source

ISO/TS 19139 path dataQualityInfo/DQ_DataQuality/lineage/LI_Lineage/source/



Data type (and ISO 19115 no.) 92. LI_Source

Domain This is a complex type (lines 93-98 from ISO 19115).Either the description (93., free text) or the sourceExtent (97., EX_Extent) elements shall be provided.


Comments ISO 19115 lists several elements which build LI_Source. For the purpose of theme-specific metadata according to the INSPIRE Data specifications the elements listed above are sufficient.Note that the path for dataQualityInfo/DQ_DataQuality/lineage/ will already exist in metadata because of being used for carrying information about lineage itself (see 2.7.1). Therefore an addition of these information into the same entity of LI_Lineage may be useful.

For further information on theme-specific presettings see document to be doneThis metadata element aims to supplement the Lineage metadata element defined in Regulation 1205/2008/EC with a precise description of data sources that have been used as input to generate the elevation or orthoimagery dataset. For example, the following data sources may be described and referenced here: - image sources and orientations - calibration data - control data (e.g. aero-triangulation control points) - data sources used to infer break lines - image positions and orientations - elevation data - seamlines used to build the mosaic elements

Metadata may as well include any specifications available and the conditions of data acquisition (e.g. sensors characteristics, data properties like image overlaps, known lacks of source data, solar elevation, etc). Concerning elevation data, it is recommended to provide information about the following basic characteristics of the Digital Elevation Models (DEM) used to rectify images: - structure (grid or TIN data) - for grid data: surface type (Digital Terrain Model or Digital Surface Model) - for grid data: DTM/DSM spacing (distance)

120

1234

1

- for grid data: water bodies flattened (yes/no) - for DSM: modelling of buildings (yes/no) - for DSM: modelling of trees (yes/no) - additional breaklines (yes/no) - vertical datum information - vertical accuracy (rmse) - positional accuracy (rmse) Information relative to the seamlines carrying the geometry of the mosaic elements can be particularly helpful to assess the accuracy and the reliability of the acquisition times provided through these mosaic elements. Seamlines may have been slightly generalized, so that the exact race between adjoining pixels from neighbouring images is lost. Or feathering may have been applied to mosaick images, so that some range values in the mosaic can be defined as a combination of values stemming from several input images with different capture time.

TG Recommendation 57 The metadata elements concerning data source should be included to metadata describing a spatial dataset or spatial dataset series related to the following INSPIRE annex themes:


TG Recommendation 58 This element is already used for documenting the lineage of the resource (see 2.7.1). Therefore an addition of these information into the same entity of LI_Lineage may be useful.


<gmd:MD_Metadata> ... <gmd:dataQualityInfo> <gmd:DQ_DataQuality> ... <gmd:lineage> <gmd:LI_Lineage> ... <gmd:source> <gmd:LI_Source> <gmd:description> <gco:CharacterString>---appropriate text------ theme-specific content, see separate document --- </gco:CharacterString> </gmd:description> ... </gmd:LI_Source> </gmd:source> ... </gmd:LI_Lineage> </gmd:lineage> ... </gmd: DQ_DataQuality> </gmd:dataQualityInfo> ...</gmd:MD_Metadata>

121

1

234

5

6

7

89

10

11121314151617181920212223242526272829303132333435363738394041

1

2.14.6 Browse graphic information

Graphic that provides an illustration of the dataset (should include a legend for the graphic).

Metadata element name Browse graphic informationReference INSPIRE Data specifications, chapters 8.3.xINSPIRE Data specification


Definition Graphic that provides an illustration of the dataset (should include a legend for the graphic)

ISO 19115 number and name 31. graphicOverview

ISO/TS 19139 path identificationInfo[1]/MD_DataIdentification/graphicOverview/



Data type (and ISO 19115 no.) 48. MD_BrowseGraphic

Domain This is a complex type (lines 49-51 from ISO 19115). The following element is mandatory (the multiplicity according to ISO 19115 is shown in brackets):

- 49. filename [1]: name of the file that contains a graphic that provides an illustration of the dataset / domain value: free text


Comments ISO 19115 lists several elements which build MD_BrowseGraphic. For the purpose of theme-specific metadata according to the INSPIRE Data specifications the element listed above is sufficient.

For further information on theme-specific presettings see document to be done

TG Recommendation 59 The metadata elements concerning browse graphic information should be included to metadata describing a spatial dataset or spatial dataset series related to the following INSPIRE annex themes:



<gmd:MD_Metadata> ... <gmd:identificationInfo> <gmd:MD_DataIdentification> ... <gmd:graphicOverview> <gmd:MD_BrowseGraphic> <gmd:fileName> <gco:CharacterString>https://www.geoportal.nrw.de/grafik/dtk100.PNG</gco:CharacterString> </gmd:fileName> ... </gmd:MD_BrowseGraphic> </gmd:graphicOverview> ... </gmd:MD_DataIdentification> </gmd:identificationInfo>

122

1234

5

678

9

10

1112131415161718192021222324252627282930

1


2.14.7 Image description

Describes the coverage and image data characteristics Information about an image‘s suitability for use.

Metadata element name Image descriptionReference INSPIRE Data specifications, chapters 8.3.xINSPIRE Data specification

on Orthoimagery, chapter 8.3.7 (D2.8.II.3)

Definition Information about an image‘s suitability for use

ISO 19115 number and name 16. contentInfo

ISO/TS 19139 path contentInfo/

INSPIRE obligation / condition optional for dataset and dataset series concerning INSPIRE annex theme Orthoimagery;not applicable to services


Data type (and ISO 19115 no.) 243. MD_ImageDescription

Domain This is a complex type (lines 244-255 and 249-242 from ISO 19115). At least the following element should be used:

- 248. cloudCoverPercentage [1]: area of the dataset obscured by clouds, expressed as a percentage of the spatial extent/ domain value: Real

ISO 19115 itself demands two mandatory elements in MD_ImageDescription:

- 240. attributeDescription [1]- 241. contentType [1]


Comments ISO 19115 lists several elements that build MD_ImageDescription. For the purpose of theme-specific metadata according to the INSPIRE Data specifications the elements listed above are sufficient.


TG Recommendation 60 The metadata elements concerning image description should be included to metadata describing a spatial dataset or spatial dataset series related to the following INSPIRE annex themes:

Orthoimagery


<gmd:MD_Metadata> ... <gmd:contentInfo> <gmd:MD_ImageDescription> <gmd:attributeDescription>--- theme-specific content, see separate document ------appropriate content--- </gmd:attributeDescription> <gmd:contentType>

123

1234

56789

10

111213

14

151617181920212223242526

1

<MD_CoverageContentTypeCode xmlns="http://www.isotc211.org/2005/gmd" codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#MD_CoverageContentTypeCode" codeListValue="image"/> </gmd:contentType> ... <gmd:cloudCoverPercentage> <gco:Decimal>15.0</gco:Decimal> </gmd:cloudCoverPercentage> ... </gmd:MD_ImageDescription> </gmd:contentInfo> ...</gmd:MD_Metadata>

2.14.8 Content information

Description of the content of a dataset.

Metadata element name Content informationReference INSPIRE Data specifications, chapters 8.3.xINSPIRE Data specification

on Buildings, chapter 8.3.3 (D2.8.III.2)

Definition Description of the content of a dataset

ISO 19115 number and name 16. contentInfo

ISO/TS 19139 path contentInfo/

INSPIRE obligation / condition optional for dataset and dataset series concerning INSPIRE annex theme Buildings;not applicable to services


Data type (and ISO 19115 no.) 233. MD_FeatureCatalogueDescription

Domain This is a complex type (lines 234-238 from ISO 19115). Data specification on Buildings does not give a minimum element.ISO 19115 itself demands two mandatory elements in MD_ FeatureCatalogueDescription:

- 236. includedWithDataset [1]- 238. featureCatalogueCitation [1]


Comments ISO 19115 lists several elements that build MD_ FeatureCatalogueDescription. For the purpose of theme-specific metadata according to the INSPIRE Data specifications the elements listed above are sufficient.

For further information on theme-specific presettings see document to be doneThe purpose of this metadata element is to inform the user about the feature types and properties that are populated in the data set. This has to be done by a reference to a feature catalogue including only the populated feature types and properties. It may be done by referencing the tables supplied in annex E of Data Specification on Buildings for additional information once they have been filled by the data producer, just by ticking the populated features and properties.

124

123456789

101112131415161718

19202122

23

1

TG Recommendation 61 The metadata elements concerning content information should be included to metadata describing a spatial dataset or spatial dataset series related to the following INSPIRE annex themes:

Buildings


<gmd:MD_Metadata> ... <gmd:contentInfo> <gmd:MD_FeatureCatalogueDescription> ... <gmd:includedWithDataset> <gco:Boolean>false</gco:Boolean> </gmd:includedWithDataset> ... <gmd:featureCatalogueCitation> <gmd:CI_Citation> <gmd:title> <gco:CharacterString>GeoInfoDok</gco:CharacterString> </gmd:title> ... <gmd:date> ... </gmd:date> ... </gmd:CI_Citation> </gmd:featureCatalogueCitation> </gmd:MD_FeatureCatalogueDescription> </gmd:contentInfo> ...</gmd:MD_Metadata>

2.14.9 Digital transfer options information

Technical means and media by which a resource is obtained from the distributor.

Metadata element name Digital transfer options informationReference INSPIRE Data specifications, chapters 8.3.xINSPIRE Data specification

on Hydrography, chapter 8.3.4 (D2.8.I.8),INSPIRE Data specification on Elevation, chapter 8.3.8 (D2.8.II.1),INSPIRE Data specification on Orthoimagery, chapter 8.3.8 (D2.8.II.3)

Definition Technical means and media by which a resource is obtained from the distributor

ISO 19115 number and name 273. transferOptions

ISO/TS 19139 path distributionInfo/MD_Distribution/transferOptions/

INSPIRE obligation / condition optional for dataset and dataset series concerning INSPIRE annex themes Hydrography, Elevation and Orthoimagery;not applicable to services


Data type (and ISO 19115 no.) 274. MD_DigitalTransferOptions

Domain This is a complex type (lines 275-278 from ISO 19115). At least the following elements should be used (the multiplicity according to ISO 19115 is shown in parentheses):

125

123

4

56789

10111213141516171819202122232425262728293031323334

35363738

1

For Elevation and Orthoimagery:- 275. unitsOfDistribution [0..1]: tiles, layers, geographic areas,

etc., in which data is available / domain value: free text - 278. offLine [0..1]: information about offline media on which the

resource can be obtained / domain value: MD_Medium For Hydrography:

- 276. transferSize [0..1]: estimated size of a unit in the specified transfer format, expressed in megabytes. The transfer size is > 0.0/ domain value: Real


Comments ISO 19115 lists several elements that build MD_DigitalTransferOptions. For the purpose of theme-specific metadata according to the INSPIRE Data specifications the elements listed above are sufficient.Note that the path for distributionInfo/MD_Distribution/transferOptions/ may already exist in metadata if being used for carrying information about online access (277. online, see 2.2.4). Therefore an addition of these information into the same entity of MD_DigitalTransferOptions may be useful.


TG Recommendation 62 The metadata elements concerning digital transfer options information should be included to metadata describing a spatial dataset or spatial dataset series related to the following INSPIRE annex themes:

HydrographyElevation

Orthoimagery

TG Recommendation 63 If metadata also carry information about online access to a resource, this information usually will be placed in MD_DigitalTransferOptions as well (see 2.2.4). Therefore the path for distributionInfo/MD_Distribution/transferOptions/ can already exist in metadata and an addition of the present Digital transfer options information into the same entity of MD_DigitalTransferOptions may be useful.


<gmd:MD_Metadata> ... <gmd:distributionInfo> <gmd:MD_Distribution> ... <gmd:transferOptions> <gmd:MD_DigitalTransferOptions> <gmd:unitsOfDistribution> <gco:CharacterString>tiles of 4 square metres</gco:CharacterString> </gmd:unitsOfDistribution> <gmd:transferSize> <gco:Decimal>5.0</gco:Decimal> </gmd:transferSize> ... <gmd:offLine> <gmd:MD_Medium>

126

1

2345

6

7

8

9

10111213141516

1718192021222324252627282930313233343536

1

<gmd:name> <MD_MediumNameCode xmlns="http://www.isotc211.org/2005/gmd" codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#MediumNameCode" codeListValue="dvdRom"/> </gmd:name> ... </gmd:MD_Medium> </gmd:offLine> </gmd:MD_DigitalTransferOptions> </gmd:transferOptions> </gmd:MD_Distribution> </gmd:distributionInfo> ...</gmd:MD_Metadata>

2.14.10 Identification - Extent

Extent information including the bounding box, bounding polygon, vertical, and temporal extent of the dataset.

Metadata element name Identification - ExtentReference INSPIRE Data specifications, chapters 8.3.xINSPIRE Data specification

on Hydrography, chapter 8.3.3 (D2.8.I.8)

Definition Extent information including the bounding box, bounding polygon, vertical, and temporal extent of the dataset

ISO 19115 number and name 45. extent

ISO/TS 19139 path identificationInfo[1]/MD_DataIdentification/extent

INSPIRE obligation / condition optional for dataset and dataset series concerning INSPIRE annex theme Hydrography;not applicable to services


Data type (and ISO 19115 no.) 334. EX_Extent

Domain This is a complex type (lines 335-338 from ISO 19115). In addition to the Geographic bounding box (see 2.5.1) the following element should be used to provide a common "name" for the extent (the multiplicity according to ISO 19115 is shown in parentheses):

- 335. description [0..1]: spatial and temporal extent for the referring object/ domain value: free text

Example Use e.g. NAME_ENGL and EUCD_RBD values like description: "East Estonia, A6018" or description: "Rhine, A5001" Use e.g. WISE River basin districts (RBDs) Use the terms provided here: <http://dataservice.eea.europa.eu/dataservice/metadetails.asp?id=1041> - see also XML example -

Comments ISO 19115 lists several elements that build EX_Extent. For the purpose of theme-specific metadata according to the INSPIRE Data specifications the element listed above is sufficient in addition to the geographic extent.In future the use of a common register (gazetteer) of e.g. river names is expected to be useful.

127

123456789

101112131415161718

1920212223

1


TG Recommendation 64 The metadata elements concerning extent information should be included to metadata describing a spatial dataset or spatial dataset series related to the following INSPIRE annex themes:

Hydrography

TG Recommendation 65 Metadata also carry information about the geographic extent itself (see 2.5.1). This information will be placed in EX_Extent as well. Therefore it may be useful to store the present information (description) into the same entity of EX_Extent.


<gmd:MD_Metadata> ... <gmd:identificationInfo> <gmd:MD_DataIdentification> ... <gmd:extent> <gmd:EX_Extent> <gmd:description> <gco:CharacterString>Rhine, A5001</gco:CharacterString> </gmd:description> <gmd:geographicElement> <gmd:EX_GeographicBoundingBox> ... </gmd:EX_GeographicBoundingBox> </gmd:geographicElement> ... </gmd:EX_Extent> </gmd:extent> ... </gmd:MD_DataIdentification> </gmd:identificationInfo> ...</gmd:MD_Metadata>

2.14.11 Data Quality – several issues

There are different issues of data quality named in chapters 8.3.2 of INSPIRE Data specifications. All of them are mapped to ISO 19115 metadata elements the same way. Therefore the following data quality element is described abstractly. There is a mapping table after that showing the concerned data quality issues for each INSPIRE annex theme.

The description of “Metadata elements for reporting data Quality” in chapters 8.3.2 of INSPIRE Data specifications is based on ISO 19157, which provides different ways to report data quality information. INSPIRE Data specifications make use of two ways: reporting quantitative results and reporting descriptive results. ISO 19157 itself works along with metadata structures according to ISO 19115-1.As long as being based on ISO 19115 only, a mapping of the metadata elements designated in ISO 19157 to metadata elements existing in ISO 19115 is necessary:

- For quantitative results there is an equivalent structure in ISO 19115, so the mapping is obvious.

128

1

234

5

6

789

10

11121314151617181920212223242526272829303132333435363738

39404142434445464748495051525354

1

- For descriptive results there is no matching element that seems likely. Thus there is no recommendation for a particular element today. Support of new ISO 19115-1 and ISO 19157 has to be awaited for documenting these issues in a unique manner. The attempt here is to store the data quality statements in the existing Lineage statement and flag them as a turnout from data quality.

2.14.11.1 Data Quality – Quantitative results

Metadata element name Data Quality – Quantitative resultsReference INSPIRE Data specifications, chapters 8.3.2

Definition Several, theme specific aspects of Data Quality - See corresponding Data Specfication for further information





Data type (and ISO 19115 no.) 99. DQ_Element

Domain DQ_Element is an abstract complex type and has to be expressed by a corresponding DQ_xxx subelement concerning the particular data quality issue e.g. DQ_ConceptualConsistency.See B.2.4.3 in ISO 19115:2003 for further information.









Due to making use of DQ_QuantitativeResult subset there is a mandatory element in ISO 19115 to be considerer too:



Comments ISO 19115 lists several elements which build DQ_Element. For the purpose of theme-specific metadata according to the INSPIRE Data specifications the elements won by mapping from ISO 19157 are sufficient.

129

123456

78

1


TG Recommendation 66 As long as being based on ISO 19115 only the metadata elements reporting quantitative results as given in INSPIRE Data specifications’ chapters 8.3.2 should be expressed by corresponding ISO 19115 elements as shown in the table above. Due to ISO 19115 one mandatory element (valueUnit) is added there though not derived from matching with the foreseen ISO 19157 elements.


<gmd:MD_Metadata> ... <gmd:dataQualityInfo> <gmd:DQ_DataQuality> ... <gmd:report> <gmd:DQ_ConceptualConsistency> <gmd:nameOfMeasure> <gco:CharacterString>---appropriate text------ theme-specific content, see separate document --- </gco:CharacterString> </gmd:nameOfMeasure> ... <gmd:evaluationMethodType> <DQ_EvaluationMethodTypeCode xmlns="http://www.isotc211.org/2005/gmd" codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml# DQ_EvaluationMethodTypeCode" codeListValue="indirect"/> </gmd:evaluationMethodType> <gmd:evaluationMethodDescription> <gco:CharacterString>---appropriate text------ theme-specific content, see separate document --- </gco:CharacterString> </gmd:evaluationMethodDescription> ... <gmd:dateTime> <gco:DateTime>2015-04-01T16:20:00</gco:DateTime> </gmd:dateTime> <gmd:result> <gmd:DQ_QuantitativeResult> ... <gmd:valueUnit>--- theme-specific content, see separate document ------appropriate content--- </gmd:valueUnit> ... <gmd:value>--- theme-specific content, see separate document ------appropriate content--- </gmd:value> </gmd:DQ_QuantitativeResult> </gmd:result> </gmd:DQ_ConceptualConsistency> </gmd:report> ... </gmd: DQ_DataQuality> </gmd:dataQualityInfo> ...</gmd:MD_Metadata>

130

1

234567

89

101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960

1

2.14.11.2 Data Quality – Descriptive results

Metadata element name Data Quality – Descriptive resultsReference INSPIRE Data specifications, chapters 8.3.2

Definition Several, theme specific aspects of Data Quality - See corresponding Data Specfication for further information

ISO 19115 number and name 81. lineage

ISO/TS 19139 path dataQualityInfo/DQ_DataQuality/lineage/



Data type (and ISO 19115 no.) 82. LI_Lineage

Domain This is a complex type (lines 85-85 from ISO 19115). To provide the descriptive results of data quality evaluation the following element should be used (the multiplicity according to ISO 19115 is shown in parentheses):

- 83. statement [C..1]: general explanation of the data producer’s knowledge about the lineage of a dataset / domain value: free text

- Example - - see XML example -

- Comments - ISO 19115 lists several elements which build LI_Lineage. For the purpose of theme-specific metadata according to the INSPIRE Data specifications the element listed above is sufficient.

- Note that the path for dataQualityInfo/DQ_DataQuality/lineage/ will already exist in metadata because of being used for carrying information about lineage itself (see 2.7.1). Therefore an addition of these information into the same entity of LI_Lineage may be useful but has to be flagged by using the name of the corresponding DQ_xxx subelement concerning the particular data quality issue (e.g. ConceptualConsistency) as a prefix or topic in the lineage element.

TG Recommendation 67 As long as being based on ISO 19115 only the metadata elements reporting descriptive results as given in INSPIRE Data specifications’ chapters 8.3.2 should be expressed by using the lineage statement. This element is already used for documenting the lineage of the resource (see 2.7.1), so a prefix or topic (e.g. “ConceptualConsistency: …”) may be helpful when using the same entity of LI_Lineage.



<gmd:MD_Metadata> ... <gmd:dataQualityInfo> <gmd:DQ_DataQuality> ... <gmd:lineage> <gmd:LI_Lineage> <gmd:statement>

131

12

34

5

6789

101112

13

14151617181920212223

1

<gco:CharacterString>...Conceptual Consistency:---appropriate text---</gco:CharacterString> </gmd:statement> ... </gmd:LI_Lineage> </gmd:lineage> ... </gmd: DQ_DataQuality> </gmd:dataQualityInfo> ...</gmd:MD_Metadata>

TG Recommendation 69 The metadata elements concerning the listed issues of data quality information should be included to metadata describing a spatial dataset or spatial dataset series related to each of the INSPIRE annex themes with the exception of “Population distribution” (because of missing chapter 8 in the data specification) if the particular issue of data quality is listed in combination with the particular INSPIRE annex theme.

132

123456789

10111213

14151617181920

2122

2324

1

TG Recommendation 70 TG Recommendation XX As long as being based on ISO 19115 only the metadata elements reporting descriptive results as given in INSPIRE Data specifications’ chapters 8.3.2 should be expressed by using the lineage statement. This element is already used for documenting the lineage of the resource (see), so a prefix or topic (e.g. “ConceptualConsistency: …” may be helpful when using the same entity of LI_Lineage.



<gmd:MD_Metadata> ... <gmd:dataQualityInfo> <gmd:DQ_DataQuality> ... <gmd:lineage> <gmd:LI_Lineage> <gmd:statement> <gco:CharacterString>---appropriate text---</gco:CharacterString> </gmd:statement> ... </gmd:LI_Lineage> </gmd:lineage> ... </gmd: DQ_DataQuality> </gmd:dataQualityInfo> ...</gmd:MD_Metadata>

TG Recommendation 72 TG Recommendation XX The metadata elements concerning the listed issues of data quality information should be included to metadata describing a spatial dataset or spatial dataset series related to each of the INSPIRE annex themes with the exception of “Population distribution” (because of missing chapter 8 in the data specification) if the particular issue of data quality is listed in combination with the particular INSPIRE annex theme.


133

1234567

8

910111213141516171819202122232425262728293031

3233343536373839

40

1

134

1

1

135

12

1

2.15 Metadata for Spatial data services

2.15.1 IntroductionThe following paragraphs describe the additional metadata elements of interoperable INSPIRE spatial data services (SDS), as defined in the INSPIRE Spatial data services Regulation (EU) No 1312/2014. They are additional to the metadata elements for services as described here before in chapter 2. Quality of Service

This is the minimum quality of service estimated by the spatial data service responsible party and expected to be valid over a period of time. There shall be three quality of service criteria reported to which the measurements refer; availability, performance and capacity. Availability describes the percentage of time the service is available. Performance describes how fast a request to the spatial data service can be completed. Capacity describes the maximum number of simultaneous requests that can be completed with the declared performance.

TG Requirement 68 This is the minimum quality of service estimated by the spatial data service responsible party and expected to be valid over a period of time.

Metadata element name Criteria

Reference COMMISSION REGULATION (EU) No 1089/2010, Annex VI Part B 4.1

Definition Name of the test applied to the data

ISO 19115 number and name 100. nameOfMeasure

ISO/TS 19139 path dataQualityInfo/*/report/DQ_ConceptualConsistency/nameOfMeasure

INSPIRE obligation / condition Mandatory for interoperable spatial data services



Domain Availability Performance Capacity

Example availability

Comments DQ_DataQuality/scope/DQ_Scope/level/MD_ScopeCode with the value “service” should be used

Metadata element name Description

Reference COMMISSION REGULATION (EU) No 1089/2010, Annex VI Part B 4.2.1

Definition Description of the measure

ISO 19115 number and name 102. measureDescription

ISO/TS 19139 path dataQualityInfo/*/report/DQ_ConceptualConsistency/measureDescription

136

12

3456789

101112131415

161718

1920

2122232425

1




Domain

Example Average response time, expressed as seconds


Metadata element name Value


Definition Quantitative value or values, content determined by the evaluation procedure used

ISO 19115 number and name 137. value

ISO/TS 19139 path dataQualityInfo/*/report/DQ_ConceptualConsistency/result/DQ_QuantitativeResult/value



Data type (and ISO 19115 no.) Record

Domain Described in ISO 19103

Example 1


Metadata element name Unit


Definition Value unit for reporting a data quality result.

ISO 19115 number and name 135. valueUnit

ISO/TS 19139 path dataQualityInfo/*/report/DQ_ConceptualConsistency/result/DQ_QuantitativeResult/valueUnit



Data type (and ISO 19115 no.) UnitOfMeasure

Domain Described in ISO 19103

Example <gmd:valueUnit xlink:href=" http://www.opengis.net/def/uom/SI/second"/>



<gmd:MD_Metadata>…<gmd:dataQualityInfo> <gmd:DQ_DataQuality>

137

12

34

56789

1011

1


Yes, Elaine had some suggestion about pre defined , I not totally understand. I think we can make it more userfrendly somehow


Could we add theallowed values to be defined in the domain so that the exact definitions are clear. Would there be an advantage to handle these also in multilingual codelist in registry.

http://www.opengis.net/def/uom/SI/second

<gmd:scope> <gmd:DQ_Scope> <gmd:level> <gmd:MD_ScopeCode codeList="http://www.isotc211.org/2005/resources/codeList.xml#MD_ScopeCode" codeListValue="service"/> </gmd:level> </gmd:DQ_Scope> </gmd:scope> <gmd:report> <gmd:DQ_ConceptualConsistency> <gmd:nameOfMeasure> <gco:CharacterString>Performance</gco:CharacterString> </gmd:nameOfMeasure> <gmd:measureDescription> <gco:CharacterString>Average response time, expressed as seconds</gco:CharacterString> </gmd:measureDescription> <gmd:result> <gmd:DQ_QuantitativeResult> <gmd:valueUnit xlink:href=" http://www.opengis.net/def/uom/SI/second"/> <gmd:value> <gco:Record>0.5</gco:Record> </gmd:value> </gmd:DQ_QuantitativeResult> </gmd:result> </gmd:DQ_ConceptualConsistency> </gmd:report> <gmd:report> <gmd:DQ_ConceptualConsistency> <gmd:nameOfMeasure> <gco:CharacterString>Availability</gco:CharacterString> </gmd:nameOfMeasure> <gmd:measureDescription> <gco:CharacterString>Availability on yearly basis, expressed as percentage of time</gco:CharacterString> </gmd:measureDescription> <gmd:result> <gmd:DQ_QuantitativeResult> <gmd:valueUnit gco:nilReason="inapplicable"/> <gmd:value> <gco:Record>83</gco:Record> </gmd:value> </gmd:DQ_QuantitativeResult> </gmd:result> </gmd:DQ_ConceptualConsistency> </gmd:report> <gmd:report> <gmd:DQ_ConceptualConsistency> <gmd:nameOfMeasure> <gco:CharacterString>Capacity</gco:CharacterString> </gmd:nameOfMeasure> <gmd:measureDescription> <gco:CharacterString>Maximum number of simultaneous requests per second meeting the performance criteria, expressed as number of requests per second</gco:CharacterString> </gmd:measureDescription> <gmd:result> <gmd:DQ_QuantitativeResult> <gmd:valueUnit gco:nilReason="inapplicable"/>

138

123456789

10111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364

1


<gmd:value> <gco:Record>5</gco:Record> </gmd:value> </gmd:DQ_QuantitativeResult> </gmd:result> </gmd:DQ_ConceptualConsistency> </gmd:report>…</gmd:MD_Metadata

2.15.2 Invocation metadata

A harmonised spatial data service shall have well documented interfaces and list the end points for each operation to enable machine to machine communication.

TG Requirement 69 The invocation metadata element documents the interfaces of the harmonised spatial data service and lists the end points to enable machine-to machine communication.

To describe the invocation metadata the ISO 19119 operation metadata elements are used. At least the mandatory ISO elements shall be provided as in the mappings and example here. The XML example also provided additional information in optional metadata elements. SV_OperationMetadata describes the signature of one method provided by the service. There can be for each method an instances of SV_OperationMetadata.

Metadata element name operationName

Reference COMMISSION REGULATION (EU) No 1089/2010, Annex VII Part B 3

Definition A unique identifier for this interface

ISO 19119 number and name Table C2 1. operationName

CSW ISO Metadata AP path identificationInfo[1]/*/containsOperations/*/operationName

INSPIRE obligation / condition Mandatory for harmonised spatial data services



Domain

Example GetSampleColumn

Comments

Metadata element name DCP


Definition Distributed computing platforms on which the operation has been implemented.

ISO 19119 number and name Table C2 2. DCP

CSW ISO Metadata AP path identificationInfo[1]/*/containsOperations/*/DCP



139

123456789

1011121314

151617

1819202122232425

26

1

Data type (and ISO 19115 no.) DCPlist

Domain XML, CORBA, JAVA, COM, SQL, WebServices

Example WebServices

Comments

Metadata element name connectPoint


Definition Handle for accessing the service interface.

ISO 19119 number and name Table C2 6. connectPoint

CSW ISO Metadata AP path identificationInfo[1]/*/containsOperations/*/connectPoint/*/linkage



Data type (and ISO 19115 no.)

Domain

Example http://www.dinoservices.nl:80/geo3dmodelwebservices-1/Geo3DModelService

Comments


<gmd:MD_Metadata … … <gmd:identificationInfo> <srv:SV_ServiceIdentification> … <srv:containsOperations> <srv:SV_OperationMetadata> <srv:operationName> <gco:CharacterString>GetSampleColumn</gco:CharacterString> </srv:operationName> <srv:DCP> <srv:DCPList codeList="http://someurl#DCPList" codeListValue="HTTPGet"/> </srv:DCP> <srv:parameters> <srv:SV_Parameter> <srv:name> <gco:aName> <gco:CharacterString>model</gco:CharacterString> </gco:aName> <gco:attributeType> <gco:TypeName> <gco:aName> <gco:CharacterString>CharacterString</gco:CharacterString> </gco:aName> </gco:TypeName> </gco:attributeType> </srv:name> <srv:direction> <srv:SV_ParameterDirection>in</srv:SV_ParameterDirection> </srv:direction> <srv:optionality>

140

1

23456789

101112131415161718192021222324252627282930313233343536

1

<gco:CharacterString>required</gco:CharacterString> </srv:optionality> <srv:repeatability> <gco:Boolean>false</gco:Boolean> </srv:repeatability> <srv:valueType>string</srv:valueType> </srv:SV_Parameter> </srv:parameters> <srv:parameters> <srv:SV_Parameter> <srv:name> <gco:aName> <gco:CharacterString>xCoordinate</gco:CharacterString> </gco:aName> <gco:attributeType> <gco:TypeName> <gco:aName> <gco:CharacterString>CharacterString</gco:CharacterString> </gco:aName> </gco:TypeName> </gco:attributeType> </srv:name> <srv:direction> <srv:SV_ParameterDirection>in</srv:SV_ParameterDirection> </srv:direction> <srv:optionality> <gco:CharacterString>required</gco:CharacterString> </srv:optionality> <srv:repeatability> <gco:Boolean>false</gco:Boolean> </srv:repeatability> <srv:valueType>double</srv:valueType> </srv:SV_Parameter> </srv:parameters> … <srv:connectPoint> <gmd:CI_OnlineResource> <gmd:linkage> <gmd:URL>http://www.dinoservices.nl:80/geo3dmodelwebservices-1/Geo3DModelService</gmd:URL> </gmd:linkage> </gmd:CI_OnlineResource> </srv:connectPoint> </srv:SV_OperationMetadata> </srv:containsOperations> … </srv:SV_ServiceIdentification> </gmd:identificationInfo> … </gmd:MD_Metadata>

141

123456789

10111213141516171819202122232425262728293031323334353637383940414243444546474849505152

1

2.15.3 nion

2.15.4

2.15.4.1

2.15.4.2 CategoryThis is a citation of the status of the spatial data service versus invocability. exn those elements the conformance levels for SDS category, invoca the data specifications.

TG Requirement 70 An invocable spatial data services shall be conform to one of the conformance levels; invocable, interoperable or harmonised

, Annex V, Part B 1

for invoaspat

Example

The metadata element degree contains the degree of conformity of the spatial data service to the conformance class.

, Annex V, Part B 1

for invocaspat

12

if

Example of XML encoding:<gmd:MD_Metadata

12

142

1

2

3

456

78

910

111213

141516

1

2

2.15.4.3 Resource locatorThe Resource Locator metadata element set out in Regulation (EC) No 1205/2008 shall also contain all access points from the spatial data service provider and these access points shall be unambiguously identified as such, using the resource locator function code The access point of the service, is an Internet address containing a detailed description of a spatial data service, including a list of endpoints to allow an automatic execution.

, Annex V, Part D 1

invocable spat

..

TG Requirement 71 spatial datl have at leassource lt is an ac

TG Requirement 72

, Annex V, Part D 1

function

invocable spat

..

1.3.2

Example of XML encoding:<gmd:MD_Metadata … <gmd:linkage><gmd:URL </gmd:URL>/gmd:lin <gmd:function> eFuncti="http://inspir </gmd:CI_OnLineFunctionCode> /gmd:fun </gmd:CI_OnlineResource>

2.15.4.4 SpecificationThe Specification metadata element set out in Regulation (EC) No 1205/2008 shall also refer to or contain technical specifications (such as INSPIRE technical guidance but not only), to

143

1234567

89

10

11

12

1314151617181920

212223

1

which the invocable spatial data service fully conforms, providing all the necessary technical elements (human, and wherever relevant, machine readable) to allow its invocation.’

TG Requirement 73 Invocable spatial data services contains the specification metadata element set out in Regulation (EC) No 1205/2008 that shall also refer to or contain technical specifications (such as INSPIRE technical guidance but not only), to which the invocable spatial data service fully conforms, providing all the necessary technical elements (human, and wherever relevant, machine readable) to allow its invocation.’

TG Requirement 74

, Annex V, Part D 2

for invoaspat

EN ISO date:o ype: -12-01

CommenIn order to make a reference to or machine-readable, the documentation of the service interface (e.g. WSDL) the element gmx:Anchor could be used instead of gco:CharacterString. The backward compatibility is still valid because the human readable text is kept.The metadata element degree contains the degree of conformity of the resource to the specification.

, Annex V, Part D 2

for invocaspat

13

if

…13

144

123

456789

10

11

1213

141516171819

202122

1

2

<gmd:specification> <gmd:title>hor xlink:href=" htpiso/iso_catalogc information — Web map server interface </gmd:title> <gmd:date>05-12-01</gco:Date> </gmd:date> <gmd:explanation> <gco:CharacterString>See the referenced specification</gco:CharacterString> <gmd:pass> </gmd:DQ_ConformanceResult>

2.15.4.5

TG Requirement 75

Description of the coordinate reference system(s) supported in the service.

, Annex VI, Part B 3

for interoperable spatiata

4258EPSG

Comments

TG Recommendation 74 It is recommended to use the http URIs provided by the Open Geospatial Consortium in combination with the coordinate reference system identifiers (see in Table 5). These are based on and redirect to the definition in the EPSG Geodetic Parameter Registry (http://www.epsg-registry.org/). It is therefore recommended the use of “EPSG” as code in the “codeSpace” medatada element.

Example of XML encoding:… <gmd:MD_ReferenceSystem ntifier> <gmd:RS_fier>r xlink:href=" http://www.opengis/crs/EPS e="ETRS89">4258</gmx <ace> <gco:CharacteS </gmd:codeSpace> </gmd:RS_Identifr> </gmd:MD_ReferenceSystem></gmd:remInfo> …

2.15.5 Quality of ServiceThis is the minimum quality of service estimated by the spatial data service responsible party and expected to be valid over a period of time. There shall be three quality of service criteria

145

123456789

10111213

14

15

1617

18

192021222324

2526272829303132333435

363738

1

http://www.opengis.net/def/crs/EPSG/0/4258%22


reported to which the measurements refer; availability, performance and capacity. Availability describes the percentage of time the service is available. Performance describes how fast a request to the spatial data service can be completed. Capacity describes the maximum number of simultaneous requests that can be completed with the declared performance.

TG Requirement 76 This is the minimum quality of service estimated by the spatial data service responsible party and expected to be valid over a period of time.

, Annex VI Part B 4.1a

nameO

DQ_ConceptualConsistency/

, Annex VI Part B 4.2.1

e

meas


, Annex VI Part B 4.2.2u value or ermined by the eval

value


146

1234

567

8

9

10

1

, Annex VI Part B 4.2.3.

value


for inteo

http://www.opengis.net/defu

Example of XML encoding:<gmd:MD_Metadata><gmd:dataQualityInfo> <gmd:DQ_DataQuality> <gmd:scope> <gmd:DQ_Scope> <gmd:level> <gmd:MD_ScopeCode codeList="http://www.isotc211.org/2005/resources/codeList.xml#MD_ScopeCode" codeListValue="service"/> </gmd:level> </gmd:DQ_Scope> </gmd:scope> <gmd:report> <gmd:DQ_ConceptualConsistency> <gmd:nameOfMeasure> <gco:CharacterString>Performance</gco:CharacterString> </gmd:nameOfMeasure> <gmd:measureDescription> <gco:CharacterString>Average response time, expressed as seconds</gco:CharacterString> </gmd:measureDescription> <gmd:result> <gmd:DQ_QuantitativeResult> <gmd:valueUnit xlink:href=" http://www.opengis.net/def/uom/SI/second"/> <gmd:value> <gco:Record>0.5</gco:Record> </gmd:value> </gmd:DQ_QuantitativeResult> </gmd:result> </gmd:DQ_ConceptualConsistency> </gmd:report> <gmd:report> <gmd:DQ_ConceptualConsistency> <gmd:nameOfMeasure> <gco:CharacterString>Availability</gco:CharacterString> </gmd:nameOfMeasure> <gmd:measureDescription> <gco:CharacterString>Availability on yearly basis, expressed as percentage of time</gco:CharacterString>

147

1

23456789

101112131415161718192021222324252627282930313233343536373839404142434445

1



</gmd:measureDescription> <gmd:result> <gmd:DQ_QuantitativeResult> <gmd:valueUnit gco:nilReason="inapplicable"/> <gmd:value> <gco:Record>83</gco:Record> </gmd:value> </gmd:DQ_QuantitativeResult> </gmd:result> </gmd:DQ_ConceptualConsistency> </gmd:report> <gmd:report> <gmd:DQ_ConceptualConsistency> <gmd:nameOfMeasure> <gco:CharacterString>Capacity</gco:CharacterString> </gmd:nameOfMeasure> <gmd:measureDescription> <gco:CharacterString>Maximum number of simultaneous requests per second meeting the performance criteria, expressed as number of requests per second</gco:CharacterString> </gmd:measureDescription> <gmd:result> <gmd:DQ_QuantitativeResult> <gmd:valueUnit gco:nilReason="inapplicable"/> <gmd:value> <gco:Record>5</gco:Record> </gmd:value> </gmd:DQ_QuantitativeResult> </gmd:result> </gmd:DQ_ConceptualConsistency> </gmd:report></gmd:MD_Metadata

2.15.6 Conditions applying to access and use dditional requirements on metadata. The technical restrictions applying to the access and use of the spatial data service shall also be documented in the metadata element “CONSTRAINT RELATED TO ACCESS AND USE”

TG Requirement 77 The technical restrictions applying to the access and use of the spatial data service shall be documented in the metadata element “CONSTRAINT RELATED TO ACCESS AND USE” set out in Regulation (EC) No 1205/2008.

See for the mapping table and the and XML example paragraph 2.9.2

2.15.7 Responsible partyrequirements on metadata. The responsible party set out in Regulation (EC) No 1205/2008 shall at least describe the custodian responsible organisation, corresponding to the Custodian responsible party role set out in Regulation (EC) No 1205/2008. See for the mapping table and the and XML example paragraph 2.10

2.15.8 A harmonised spatial data service shall have well documented interfaces and list the end points for each operation to enable machine to machine communication.

TG Requirement 78

148

123456789

1011121314151617181920212223242526272829303132

33343536

37383940

41

4243444546

474849

50

51

1

, Annex VII Part B 3

9 numbernd . operatioam path [1]/*/containsOperons

for harmn spaservices

, Annex VII Part B 3i

9 numbernd . DCP path [1]/*/containsOperons


..

, Annex VII Part B 3

a9 numbernd . connectPit path ations/*/connectPoint/*/linkage


..

<gmd:MD_Metadata … srv:SV_ServiceIdentification> …GetSampleColumn</gco:CharacterString> </srv:operationName>

149

1

2

3

4567

1

<srv:DCP> </srv:SV_Parameter> </srv:parameters> <gmd:linkage> <gmd:URL>http://www.dinoservices.nl:80/geo3dmodelwebservices-1/Geo3DModelService</gmd:URL>

150

12345678

1

3 Detailed mapping

3.1 Introduction

This structure is presented as a set of template instances of ISO 19115 and ISO 19119 classes. The template instance of a class is defined by a set of property instances. The description of each property instance is composed of: A + sign starting the description of the property instance; The property label as appearing in ISO 19115 and ISO 19119 UML Models; A presence requirement expressed with a cardinality statement between square brackets.

This cardinality statement expresses the INSPIRE requirements which implies possible differences with the ISO 19115 cardinality;

A colon; The property type name. The property type is implemented as a sub element of the

property. This sub element can be an instance of the property type or an instance of one of its derived types. In the latter case, the derived type is either an ISO type or an extension type defined in a profile.

A property instance statement which describes how the property type is implemented.

Additional information is provided in a Note section, at the bottom of each table.

This hierarchical set of labels acts as an instance Template. This template only shows the properties in the scope of the INSPIRE metadata elements, which encompass the mandatory properties of ISO 19115 and ISO 19119. The other optional properties of ISO 19115 are not described, but can be present in a real instance.Additional properties defined in a profile of ISO 19115 or ISO 19119 compliant with the INSPIRE metadata elements can be expressed but are not documented here.

3.2 Resource MetadataSet

An INSPIRE Metadata Set is an instance of: the class MD_Metadata (from ISO 19115), the class MI_Metadata (from ISO 19115-2), or, an instance of any community specialisation of one of these two classes.

This instance is composed at least of the following property instances:

+ language [1] : LanguageCode....................................................Metadata Language (See 2.11.3)+ hierarchyLevel [1] : MD_ScopeCode.........................................Resource Type (See 2.2.3 and note 2)+ contact [1..*] : CI_ResponsibleParty..........................................Metadata point of contact (See 2.11.1 and 3.5.2)+ dateStamp [1] : Date..................................................................Metadata date (See 2.11.2)+ identificationInfo [1] : MD_Identification.....................................See 3.3 and note 3+ distributionInfo [0..*] : MD_Distribution

+ transferOptions [0..*] : MD_Digital TransferOptions+ online [0..*] : CI_OnlineResource

+ linkage [1]: URL ............................................................... (See 2.2.4 and Note 1)+ dataQualityInfo [0..*] : DQ_DataQuality.....................................See 3.4 and Note 4

Notes :1. The linkage property is not multiple, but there may be many instances of distributionInfo, and for each many instances of

transferOptions and for each many instances of online, implying multiple INSPIRE Resource Locator. 2. There may be many instances of hierarchyLevel, but the value of the INSPIRE Resource Type corresponds to the first

instance (See SC3 in 1.2). 3. There may be many instances of identificationInfo, but only the first one will be considered (See SC5 in 1.2).4. In case of datasets and dataset series at least an instance of dataQualityInfo is mandatory.

151

1

23456789

1011121314151617181920212223242526

272829303132333435

36

1

3.3 Identification Section

3.3.1 Sub-elements for spatial dataset and spatial dataset series

If the Resource Type (i.e., the value of metadata set hierarchyLevel) is dataset or series, the data type of identificationInfo instance will be MD_DataIdentification or a subclass of MD_DataIdentification. Its property instances are described hereafter.

+ citation [1] : CI_Citation+ title [1] : CharacterString...........................................................Resource title (See 2.2.1)+ date [0..*] : CI_Date..................................................................See note 1

+ date [1] : Date........................................................................Date of publication (See 2.6.2) + dateType [1] : CI_DateTypeCode..........................................publication

+ date [0..1] : CI_Date..................................................................See notes 1 and 2+ date [1] : Date........................................................................Date of last revision (See 2.6.3)+ dateType [1] : CI_DateTypeCode..........................................revision

+ date [0..1] : CI_Date..................................................................See Note 1 and 3+ date [1] : Date........................................................................Date of creation (See 2.6.4) + dateType [1] : CI_DateTypeCode..........................................creation

+ identifier [1..*] : MD_Identifier....................................................Unique resource identifier (See and SC8)+ code [1] : CharacterString......................................................This is the mandatory code of the identifier+ codeSpace [0..1] : CharacterString.......................................This is the optional namespace of the identifier

+ abstract [1] : CharacterString....................................................... Resource abstract (See 2.2.2)+ pointOfContact [1..*] : CI_ResponsibleParty ...............................Responsible Organization (See 2.10)+ descriptiveKeywords [1..*] : MD_Keywords

+ keyword [1..*] : CharacterString................................................Keyword value (See 2.4.1) + thesaurusName [0..1] : CI_Citation...........................................Originating controlled vocabulary (See 2.4.2)

+ resourceConstraints [1..*] : MD_Constraints................................Constraints related to access and use (See 2.9 and 3.6).+ spatialResolution [0..*] : MD_Resolution...................................... Spatial resolution (2.7.2) – See Note 4

+ distance [0..1] : Distance...........................................................This is the ground distance+ equivalentScale [0..1] : MD_RepresentativeFraction

+ denominator [1] : Integer.......................................................This is equivalent scale denominator+ language [1..*] : LanguageCode................................................... Resource language (See 2.2.7, SC9 in 1.2 and Note 5)+ extent [1] : EX_Extent...................................................................See Note 6

+ geographicElement [1..*] : EX_GeographicBoundingBox.........Geographic bounding box (See 2.5.1) + westBoundLongitude [1] : Decimal+ eastBoundLongitude [1] : Decimal+ southBoundLatitude [1] : Decimal+ northBoundLatitude [1] : Decimal

+ temporalElement [0..*] : EX_TemporalExtent...........................See Note 7+ extent [1] : TM_Primitive........................................................Temporal extent (See 2.6.1)

+ topicCategory [1..*] : MD_TopicCategory.....................................Topic category (2.3.1)

Notes:1. There may be many instances of the date property with different date types including publication, revision or creation.

The order of these instances is free. If no instance of this property has the publication, revision or creation date type, then the metadata set has to include the description of a temporal extent. For compliance with ISO 19115, there is necessarily one instance of the date property, whatever its date type, even if a temporal extent is provided in the metadata.

2. The only instance of date having the revision date type matching the INSPIRE last revision date is the one having the more recent date.

3. Even if ISO 19115 allows the presence of many dates having a creation date type, it is considered inconsistent to have more than one creation date (See SC7 in 1.2).

4. MD_Resolution is a union data type. Its content is either a distance property or an equivalent scale property. In case of an equivalent scale, the denominator of the equivalent scale is provided.

5. An instance of the language property is mandated by ISO 19115 ; it can be defaulted to the value of the Metadata Language when the dataset or the dataset series does not contain textual information.

6. There may be other instances, but at least one defining the bounding box is required (See SC10 in 1.2). This instance is not necessarily the first instance.

7. There may be different instances of temporalElement defining the temporal extent of the resource. These instances may be in different instances of extent, one of them possibly handling the geographic bounding box.

152

1

234567

8

1

3.3.2 Sub-elements for service resources

If the Resource Type (i.e., the value of metadata set hierarchyLevel) is service, the data type of identificationInfo instance will be SV_ServiceIdentification or a subclass of SV_ServiceIdentification. Its property instances are described hereafter.

+ citation [1] : CI_Citation+ title [1] : CharacterString...........................................................Resource title (See 2.2.1)+ date [0..*] : CI_Date..................................................................See note 1

+ date [1] : Date........................................................................Date of publication (See 2.6.2) + dateType [1] : CI_DateTypeCode..........................................publication

+ date [0..1] : CI_Date..................................................................See notes 1 and 2+ date [1] : Date........................................................................Date of last revision (See 2.6.3)+ dateType [1] : CI_DateTypeCode..........................................revision

+ date [0..1] : CI_Date..................................................................See Note 1 and 3+ date [1] : Date........................................................................Date of creation (See 2.6.4) + dateType [1] : CI_DateTypeCode..........................................creation

+ abstract [1] : CharacterString.......................................................Resource abstract (See 2.2.2)+ pointOfContact [1..*] : CI_ResponsibleParty ...............................Responsible party (See 2.10.1) + descriptiveKeywords [1..*] : MD_Keywords

+ keyword [1..*] : CharacterString................................................Keyword value (See 2.4.1) + thesaurusName [0..1] : CI_Citation...........................................Originating Controlled Vocabulary (See 2.4.2)

+ resourceConstraints [1..*] : MD_Constraints................................See 3.6+ serviceType [1] : GenericName....................................................(See 2.3.2)+ couplingType [1] : SV_CouplingType...........................................Mandated by ISO 19119. See Note 8 + containsOperations [1..*] : SV_OperationMetadata....................Mandated by ISO 19119

+ operationName [1] : CharacterString........................................Mandated by ISO 19119. Default value is unknown+ DCP [1..*] : DCPList..................................................................Mandated by ISO 19119. Default value is WebServices+ connectPoint [1..*] : CI_OnlineResource..................................Mandated by ISO 19119.

+ linkage [1] : URL....................................................................Mandated by ISO 19119. See Note 5+ extent [0..*] : EX_Extent...............................................................See Note 4

+ geographicElement [1..*] : EX_GeographicBoundingBox.........Geographic bounding box (See 2.5.1) + westBoundLongitude [1] : Decimal+ eastBoundLongitude [1] : Decimal+ southBoundLatitude [1] : Decimal+ northBoundLatitude [1] : Decimal

+ temporalElement [0..*] : EX_TemporalExtent...........................See Note 6+ extent [1] : TM_Primitive........................................................Temporal extent (See 2.6.1)

+ operatesOn [0..*] : MD_DataIdentification....................................Coupled resource (See 2.2.6 and Note 7)

Notes:1. There may be many instances of the date property with different date types including publication, revision or creation.

The order of these instances is free. If no instance of this property has the publication, revision or creation date type, then the metadata set has to include the description of a temporal extent. For compliance with ISO 19115, there is necessarily one instance of the date property, whatever its date type, even if a temporal extent is provided in the metadata.

2. The only instance of date having the revision date type matching the INSPIRE last revision date is the one having the more recent date.

3. Even if ISO 19115 allows the presence of many dates having a creation date type, it is considered inconsistent to have more than one creation date (See SC7 in 1.2).

4. There may be other instances, but at least one defining the bounding box is required (See SC10 in 1.2). This instance is not necessarily the first instance.

5. One of the value of the INSPIRE Metadata Element “Resource Locator” (See 2.2.4) can be used as a default value6. There may be different instances of temporalElement defining the temporal extent of the resource. These instances may

be in different instances of extent, one of them possibly handling the geographic bounding box.7. This property has to be implemented by reference (See 2.2.6 and SC11 in 1.2)8. The value is:

a. loose if there is no coupled Resource (the operatesOn property of SV_ServiceIdentification is not instantiated);b. tight if the service only operates on the Coupled Resources c. mixed if the service operates on the Coupled Resources and external dataset and dataset series.

3.4 Data Quality Section

3.4.1 Lineage

This part is applicable only to spatial dataset and spatial dataset series. As defined in 3.2, a metadata set may contain different sets of quality information (i.e. instances of

153

123456

7

8

9101112

1

DQ_DataQuality or a subclass of DQ_DataQuality). The reason for this multiplicity is that each set is scoped to the whole or a part of the resource. Each of these sets of quality information may contain a lineage statement. INSPIRE only considers one lineage statement concerning the whole resource, i.e. scoped to the dataset or series without any restrictions on the resource extent.

There shall be a single instance of DQ_DataQuality (or one of its subtypes) scoped to the whole spatial dataset or spatial dataset series. This instance may be one also handling conformity statements (as defined in 2.8), but this is not illustrated in its property instances described below.

+ scope [1] : DQ_Scope+ level [1] : MD_ScopeCode........................................series for a spatial dataset series or dataset for a spatial dataset+ extentl [0] : EX_Extent..............................................There shall not be any restriction on the resource extent

+ lineage [1] : LI_Lineage+ statement [1] : CharacterString.................................Lineage (See 2.7.1)

3.4.2 Conformity

The general mechanism to handle the INSPIRE requirements relative to conformity is described in 2.8.

As defined in 3.2 a metadata set may contain different sets of quality information (i.e. instances of DQ_DataQuality or a subclass of DQ_DataQuality). Each set may contain conformity statements relative to one of the INSPIRE conformance specifications. The following property instances of the sets of quality information are involved, possibly with the property instance expressing a lineage statement as defined in 3.4.1.

+ report [0..*] : DQ_Element............................................See note 1 and 2+ measureIdentification[1] : MD_Identifier...................See note 3+ result[1] : DQ_ConformanceResult

+ specification [1] : CI_Citation.................................Specification (See 2.8.2)+ explanation [1] : CharacterString...........................See Note 4+ pass [1] : Boolean..................................................Degree (See 2.8.1)

Notes:1. ISO 19115 only reports the result of the conformance evaluation. There may be no information about the conformity

to the INSPIRE Conformance specifications, if the conformance has not been evaluated.2. DQ_Element is an abstract class. It has to be instantiated through one of its concrete subclasses. The appropriate

subclass depends on the quality criteria concerned by the quality measure. DQ_DomainConsistency will be used when the conformance does not involve a more precise quality criterion.

3. This metadata element of ISO 19115 will contain the identifier of the conformity statement. This identifier will be used by the application to differentiate the conformance statement related to INSPIRE from others.

4. ISO 19115 mandates an explanation of the meaning of the conformance for this result. A default explanation such as “See the referenced specification” can be used.

154

123456789

1011

1213141516171819202122

23

1

3.5 Responsible Organisation

3.5.1 Resource responsible organisation

Each instance of CI_ResponsibleParty or one of its subclasses (see 3.3.2 for services and 3.3.1 for spatial datasets and spatial dataset series) describes a responsible organisation, i.e.:

The name of the responsible party; A contact e-mail address of the responsible party; The responsible party role.

Here are the minimum property instances of CI_ResponsibleParty or one of its subclasses expected by INSPIRE:

+ organisationName[1] : CharacterString........................The name of the Responsible party (See 2.10.1)+ contactInfo[1] : CI_Contact

+ address[1..*] : CI_Address........................................There may be more than one address, so more than one e-mail+ electronicEmailAddress [1..*] : CharacterString....At least one e-mail addressof the Responsible party (See 2.10.1)

+ role[1] : CI_RoleCode...................................................Responsible party role (See 2.10.2)

3.5.2 Metadata point of contact

The metadata points of contact are also described by instances of MD_ResponsibleParty:

+ organisationName[1] : CharacterString....................The name of the Metadata point of contact (See 2.11.1)+ contactInfo[1] : CI_Contact

+ address[1..*] : CI_Address...................................There may be more than one address, so more than one e-mail+ electronicEmailAddress [1..*] : CharacterStringAt least one e-mail address of the Metadata point of contact (See 2.11.1)

+ role[1] : CI_RoleCode..............................................See Note 1

Notes:1. ISO 19115 mandates the definition of the role of the responsible party. The default role is pointOfContact.

3.6 Constraint section

Depending on the effective instance of MD_Constraints14, the following properties may have to be considered:

+useLimitation [0..*] : CharacterString............................................Conditions applying to access and use (See 2.9.2)+accessConstraints [0..*] : MD_RestrictionCode...........................Limitations on public access (See 2.9.1) –See Note 1 +otherConstraints [0..*] : CharacterString......................................Limitations on public access (See 2.9.1) –See Note 1+classification [0..1] : MD_ClassificationCode................................Limitations on public access (See 2.9.1) –See Note 2

Notes:1. If the value of accessConstraints is otherRestrictions, then the instances of otherConstraints may be used to describe

Limitations on public access (See 2.9.1).2. If the value of classification is not unclassified, the classification has to be reported as a Limitation on Public Access.

14 accessConstraints and otherConstraints are specific to instances of MD_LegalConstraints or one of its subclasses. classification is specific to instances of MD_SecurityConstraints and one of its subclasses.

155

1

23456789

101112

13

14151617

18

1920212223

24

12

3

3.7 Abbreviations

CEN Comité Européen de NormalisationCSW OGC Catalog Service WebEN European Norm by CENEU European UnionGML Geography Markup LanguageID IDentifierIRs Implementing RulesISO International Organisation for StandardizationISO/TS ISO Technical SpecificationOGC Open Geospatial ConsortiumUML Unified Modelling LanguageURL Uniform Resource LocatorUUID Universally Unique IDentifierXML eXtensible Markup Language

156

1

23456789

10111213141516171819

1

Annex A – ISO/TS 19139 encoding of the INSPIRE metadata elements

3.8 A.1 Introduction

This annex defines the XML ISO/TS 19139 encoding of the INSPIRE metadata elements. This XML encoding is based on XML Schemas derived from the UML models of ISO 19115 and ISO 19119 using the encoding rules defined in ISO/TS 19139 and:

the XML Schema Implementation of ISO 19115 and the related standards defined in ISO/TS 19139;

the XML Schema implementation of ISO 19119 defined in CSW2 AP ISO.

The XML encoding of the INSPIRE metadata elements shall follow the instance template defined in Section 3 and the instructions of Section 2 of this document with respect to the following instructions.

3.9 A.2 From the conceptual schema to XML File instances

The way in which the geographic metadata XML Schema is expected to be used makes it necessary to keep the organisation of the data, its associated metadata and the related information in very flexible files. Since the MD_Metadata XML element will rarely be the root element of an XML File, depending on the context, it may appear one or many times in a single XML File describing one or many different types of resources.

3.10A.3 Polymorphism

It is possible to have an XML file containing a metadata set without containing a single MD_Metadata XML element. This is a consequence of polymorphism, which may imply that an XML element representing a subclass of MD_Metadata, potentially defined in a user community profile, occurs instead of the MD_Metadata XML element. This is true for MD_Metadata as well as for any of the concepts defined in the ISO 19100 series of International Standards.

3.11A.4 Management of polymorphism

3.11.1 A.4.1 Management of community extensions

A.3 of ISO 19139 has a specific requirement to aid the understanding of user profiled metadata sets. The XML element of any new metadata element has to support a mandatory XML attribute called isoType that is expected to contain the name of the ISO class it derives from directly or indirectly.

<MY_Metadata gco:isoType=”MD_Metadata”>  <myProperty> <gco:CharacterString>Whatever text</gco:CharacterString> </myProperty></MY_Metadata>

3.11.2 A.4.2 Parsing of metadata files

To accommodate polymorphism of the data types, parsing of metadata files has to be driven by the XML elements corresponding to the properties of the UML models (look rather for the metadata elements named identificationInfo, than the metadata elements named

157

12

3456789

1011121314

1516171819202122

2324252627282930

31

32333435363738394041424344

4546474849

1

MD_DataIdentification or SV_ServiceIdentification). The elements corresponding to the data type can generally be skipped.

When it is necessary to evaluate the XML element representing data types (e.g., because the application needs to consider the data identification info, but not the service identification info), it is important to look for the XML element corresponding to the expected ISO data type (e.g., gmd:MD_DataIdentification) or the XML element for which the value of gco:isotype is the expected data type (e.g. MD_DataIdentification). There is no namespace indication in the value of the isoType attribute.

3.12A.5 Management of containment by reference

Any instance of a UML property can be implemented: by value, i.e. the instance of its datatype is a subelement of the property instance;

<gmx:MX_Aggregate> <gmd:composedOf> <gmx:MX_Dataset> … </gmx:MX_Dataset></gmd:composedOf>

<gmd:seriesMetadata> … </gmd:seriesMetadata></gmx:MX_Aggregate>

by reference, i.e. the property instance handles a xlink:href attribute which value is a reference (typically URL) to the instance of its datatype. In this case, the instance of the datatype handles an id XML attribute serving as an identifier.

<gmx: MX_Aggregate> <gmd:composedOf xlink:href=”product1.xml”> <gmd:seriesMetadata> … </gmd:seriesMetadata></gmx:MX_Aggregate>

The use of containment by reference is of course a very good way to ensure the consistency of the XML data and to reduce the maintenance cost. However it complicates the parsing of the XML file. It is recommended that the parser use a generic mechanism to manage the containment by-reference.

3.13A.6 ISO 19139 and multilingual metadata

An optional but repeatable attribute “locale” has been added to the class MD_Metadata. Two cases are to be considered:- When this attribute is not implemented, the metadata set is expected to be monolingual:

the language of the metadata is defined by the language attribute of MD_Metadata.- When this attribute is implemented, each instance represents a locale (language, country

and character encoding) in which the metadata elements may be translated. The language attribute still defines the default language of the metadata, i.e. the language in which all the metadata elements are expressed. Then each metadata element can be translated in some of the locales define for the metadata set.

158

123456789

10

111213141516171819202122232425262728293031323334353637

383940414243444546474849

1

MD_Metadata

+ fileIdentifier [0..1] : CharacterString+ language [0..1] : CharacterString+ characterSet [0..1] : MD_CharacterSetCode = "utf8"+ parentIdentifier [0..1] : CharacterString+ hierarchyLevel [0..*] : MD_ScopeCode = "dataset"+ hierarchyLevelName [0..*] : CharacterString+ contact [1..*] : CI_ResponsibleParty+ dateStamp : Date+ metadataStandardName [0..1] : CharacterString+ metadataStandardVersion [0..1] : CharacterString+ datasetURI [0..1] : CharacterString

MD_Metadata

+ fileIdentifier [0..1] : CharacterString+ language [0..1] : CharacterString+ characterSet [0..1] : MD_CharacterSetCode = "utf8"+ parentIdentifier [0..1] : CharacterString+ hierarchyLevel [0..*] : MD_ScopeCode = "dataset"+ hierarchyLevelName [0..*] : CharacterString+ contact [1..*] : CI_ResponsibleParty+ dateStamp : Date+ metadataStandardName [0..1] : CharacterString+ metadataStandardVersion [0..1] : CharacterString+ datasetURI [0..1] : CharacterString

MD_Metadata

+ fileIdentifier [0..1] : CharacterString+ language [0..1] : CharacterString+ characterSet [0..1] : MD_CharacterSetCode = "utf8"+ parentIdentifier [0..1] : CharacterString+ hierarchyLevel [0..*] : MD_ScopeCode = "dataset"+ hierarchyLevelName [0..*] : CharacterString+ contact [1..*] : CI_ResponsibleParty+ dateStamp : Date+ metadataStandardName [0..1] : CharacterString+ metadataStandardVersion [0..1] : CharacterString+ datasetURI [0..1] : CharacterString+ locale [0..*] : PT_Locale

MD_Metadata

+ fileIdentifier [0..1] : CharacterString+ language [0..1] : CharacterString+ characterSet [0..1] : MD_CharacterSetCode = "utf8"+ parentIdentifier [0..1] : CharacterString+ hierarchyLevel [0..*] : MD_ScopeCode = "dataset"+ hierarchyLevelName [0..*] : CharacterString+ contact [1..*] : CI_ResponsibleParty+ dateStamp : Date+ metadataStandardName [0..1] : CharacterString+ metadataStandardVersion [0..1] : CharacterString+ datasetURI [0..1] : CharacterString+ locale [0..*] : PT_Locale

PT_Locale+ language : LanguageCode+ country [0..1] : CountryCode+ characterEncoding : MD_CharacterSetCode



LanguageCode(from ISO 00639 Human Language)

<<CodeList>>

MD_CharacterSetCode(from ISO 19115 Identification information)

<<CodeList>>

CountryCode(from ISO 03166 Country Codes)

<<CodeList>>

LanguageCode(from ISO 00639 Human Language)

<<CodeList>>LanguageCode

(from ISO 00639 Human Language)

<<CodeList>>

MD_CharacterSetCode(from ISO 19115 Identification information)

<<CodeList>>MD_CharacterSetCode

(from ISO 19115 Identification information)

<<CodeList>>

CountryCode(from ISO 03166 Country Codes)

<<CodeList>>CountryCode

(from ISO 03166 Country Codes)

<<CodeList>>

The metadata elements which may require translations are those of type CharacterString having a free text domain.

Support of free text is enabled via a subtype of CharacterString called PT_FreeText which aggregates a set of localised character strings through its textGroup property. Each localised character string provides a translation of the character string in the related locale.

1..* +locale

LocalisedCharacterString

1 1


+textGroup1..* +locale

LocalisedCharacterString

1 1


+textGroup

PT_FreeText

CharacterString(from Text)

<<Type>>

PT_FreeTextPT_FreeText

CharacterString(from Text)

<<Type>>CharacterString

(from Text)

<<Type>>

The following clauses define the way multilingual metadata are implemented.

3.13.1 A.6.1 The default language

The default language of a metadata set is defined by the language property of MD_Metadata while the characterSet property defines the corresponding character encoding. Here is a sample instance of the class MD_Metadata illustrating the use of both properties.

<MD_Metadata>  <language>

159

12345

6789

1011

12131415

161718192021222324

1

<LanguageCode codeList="http://www.loc.gov/standards/iso639-2/" codeListValue="eng"> English </LanguageCode> </language> <characterSet> <MD_CharacterSetCode codeList="resources/codelist/gmxcodelists.xml#MD_CharacterSetCode" codeListValue="utf8"> UTF-8 </MD_CharacterSetCode> </characterSet> </MD_Metadata>

3.13.2 A.6.2 Alternate languages

Each metadata alternate language of the metadata is defined through the locale property of MD_Metadata. In the following example, some of these metadata are translated into French15:

<MD_Metadata>  <locale> <PT_Locale id="locale-fr"> <languageCode> <LanguageCode codeList="http://www.loc.gov/standards/iso639-2/" codeListValue="fre"> French </LanguageCode> </languageCode> <characterEncoding> <MD_CharacterSetCode codeList="resources/codelist/gmxcodelists.xml#MD_CharacterSetCode" codeListValue="utf8">UTF 8</MD_CharacterSetCode> </characterEncoding> </PT_Locale> </locale> </MD_Metadata>

3.13.3 A.6.3 Embedded translations

Any metadata element having a free text domain (e.g. the abstract property of MD_DataIdentification) can then be instantiated like this:

<abstract xsi:type="PT_FreeText_PropertyType"> <gco:CharacterString>Brief narrative summary of the content of the resource</gco:CharacterString>  <PT_FreeText> <textGroup> <LocalisedCharacterString locale="#locale-fr">Résumé succinct du contenu de la ressource</LocalisedCharacterString> </textGroup> </PT_FreeText></abstract>

15 Please note that both “fre” and “fra” are compatible with ISO 639-2 which distinguishes the bibliography codes (e.g. fre) from the terminology codes (e.g. fra). This issue concerns also any language having different codes for bibliography and terminology. The Drafting team has chosen the bibliography codes.

160

123456789

10111213

1415161718192021222324252627282930313233343536373839

40414243444546474849505152535455

1234

5

The xsi:type attribute indicates that this instance of the abstract property is not instantiated through a simple CharacterString, but rather as a free text. As a consequence, the element contains a complementary PT_FreeText subelement containing one or more textGroup elements (one per translation).

3.13.4 A.6.4 Use of translation files

In the preceding example, the definition of the locale property is provided by value which implies that the translations are embedded with default language metadata. It is also possible to store the translations corresponding to a given language into a translation file using the PT_LocaleContainer class. In such case, it is easier to define the locale within the translation file (e.g. fr-fr.xml) and to express the instance of the MD_Metadata locale property by reference. <gmd:locale xlink:href="./fr-fr.xml#locale-fr"/>

The content of the fr-fr.xml file would look like this:

<PT_LocaleContainer>  <locale> <PT_Locale id="locale-fr"> <languageCode> <LanguageCode codeList=”resources/codelist/gmxcodelists.xml#LanguageCode” codeListValue="fre"> French </LanguageCode> </languageCode> <characterEncoding> <MD_CharacterSetCode codeList="../codelist/ML_gmxCodelists.xml#MD_CharacterSetCode" codeListValue="utf8">UTF 8</MD_CharacterSetCode> </characterEncoding> </PT_Locale> </locale>  <localisedString> <LocalisedCharacterString locale="#locale-fr" id="#abstract-fr"> Résumé succinct du contenu de la ressource</LocalisedCharacterString> </localisedString> </PT_LocaleContainer>

The multilingual instance of the abstract property now implements the translation by reference to the translation file:

<abstract xsi:type="PT_FreeText_PropertyType"> <gco:CharacterString>Brief narrative summary of the content of the resource</gco:CharacterString>  <PT_FreeText> <textGroup xlink:href="fr-fr.xml#abstract-fr"/> </PT_FreeText></abstract>

161

123456

789

10111213141516

171819202122232425262728293031323334353637383940414243444546474849505152535455565758

1

3.14A.7 Contexts of use

3.14.1 A.7.1 Use of ISO 19139 in the context of a Catalogue Service

When the data being passed through a cataloguing service is XML encoded, the catalogue service interface defines the different XML Schemas to be used as a response to the user queries. When the geographic metadata XML Schema is used, there should be one or many MD_Metadata instances in the returned XML File.

3.14.2 A.7.2 Use of ISO 19139 in the context of the standard interchange by transfer

The transfer aggregate and transfer dataset concepts are the two major components of an interchange by transfer. There may be one or many XML Files composing the interchange, but the root element of at least one of the files is an XML instance of MX_Dataset, MX_Aggregate or one of their extensions. From such an element, the parsing of the interchange is model driven and it follows the principles described in 7.4 of ISO 19139. See ISO 19139 for details about MX_Dataset and MX_Aggregate.

3.15A.8 Character encoding

Character encoding is defined in MD_Metadata.characterEncoding and MD_Metadata.locale. Preferably this should be UTF-8 if the XML files contain multilingual metadata.

3.16A.9 Temporal extent encoding

In ISO 19115, temporal extents are of type TM_Primitive (abstract type from ISO 19108). In ISO 19139, this type (and its sub-types) are mapped to ISO 19136 temporal types and W3C built-in types. In the INSPIRE Metadata Element Set for discovery, the concrete TM_Period subtype of TM_Primitive is used as type for the XML element temporalExtent. It is implemented as type TimePeriod from ISO 19136.

TimePeriod offers three options to express a time interval:

Use two TimePosition elements for beginPosition and endPosition. Date and time information is contained in-line and cannot be referenced from another XML Element. Only the TimePeriod element can, through its gml:id.

<?xml version="1 0" encoding="UTF-8"?><gmd:MD_Metadata><gmd:extent> <gmd:EX_Extent> <gmd:temporalElement> <gmd:EX_TemporalExtent> <gmd:extent> <gml:TimePeriod gml:id="extent">

<gml:beginPosition>1977-03-10T11:45:30</gml:beginPosition><gml:endPosition>2005-01-15T09:10:00</gml:endPosition>

</gml:TimePeriod> </gmd:extent> </gmd:EX_TemporalExtent> </gmd:temporalElement> </gmd:EX_Extent> </gmd:extent></gmd:MD_Metadata>

162

1

234567

89

10111213141516

17181920

2122232425262728293031323334353637383940414243444546474849505152535455

1

Use two TimeInstant elements: Date and time information is here contained by reference and the TimeInstant elements can be re-used through a reference from another XML element in the XML file. The TimePeriod element can also be re-used.

<?xml version="1.0" encoding="UTF-8"?><gmd:MD_Metadata><gmd:extent> <gmd:EX_Extent> <gmd:temporalElement>.........<gmd:EX_TemporalExtent>............<gmd:extent>...............<gml:TimePeriod gml:id="extent">…...............<gml:begin>.....................<gml:TimeInstant gml:id="t11">

<gml:timePosition>1977-03-10T11:45:30</gml:timePosition>

.....................</gml:TimeInstant>

..................</gml:begin>

..................<gml:end>

.....................<gml:TimeInstant gml:id="t12"><gml:timePosition>2005-01-15T09:10:00</gml:timePosition>

.....................</gml:TimeInstant>

..................</gml:end>

...............</gml:TimePeriod>

............</gmd:extent>

.........</gmd:EX_TemporalExtent>

......</gmd:temporalElement>

...</gmd:EX_Extent></gmd:extent></gmd:MD_Metadata>

The two previous methods can be used in combination: one TimePeriod limit can be expressed as a TimePosition and the other as a TimeInstant:

<?xml version="1 0" encoding="UTF-8"?><gmd:MD_Metadata><gmd:extent> <gmd:EX_Extent> <gmd:temporalElement> <gmd:EX_TemporalExtent> <gmd:extent> <gml:TimePeriod gml:id="extent"> <gml:begin> <gml:TimeInstant gml:id="t11">

<gml:timePosition>1977-03-10T11:45:30</gml:timePosition>

</gml:TimeInstant> </gml:begin>

<gml:endPosition>2005-01-15T09:10:00</gml:endPosition>

</gml:TimePeriod> </gmd:extent> </gmd:EX_TemporalExtent> </gmd:temporalElement> </gmd:EX_Extent></gmd:extent></gmd:MD_Metadata>

163

123456789

10111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364

1

3.17A.10 Spatial resolution encoding

The spatial resolution of a dataset or dataset series can be expressed as an equivalent scale or as a resolution distance: Expression as an equivalent scale:

<?xml version="1.0" encoding="UTF-8"?><gmd:MD_Metadata><gmd:identificationInfo><gmd:spatialResolution> <gmd:MD_Resolution> <gmd:equivalentScale> <gmd:MD_RepresentativeFraction> <gmd:denominator> <gco:Integer>25000</gco:Integer> </gmd:denominator> </gmd:MD_RepresentativeFraction> </gmd:equivalentScale> </gmd:MD_Resolution></gmd:spatialResolution></gmd:identificationInfo></gmd:MD_Metadata>

In this case, the spatial resolution is expressed as the denominator of the scale of a comparable hardcopy map or chart.

Expression as a resolution distance:

<?xml version="1.0" encoding="UTF-8"?><gmd:MD_Metadata><gmd:identificationInfo><gmd:spatialResolution> <gmd:MD_Resolution> <gmd:distance>..........<gco:Distance uom="#cm">25</gco:Distance> </gmd:distance> </gmd:MD_Resolution></gmd:spatialResolution></gmd:identificationInfo></gmd:MD_Metadata>

In this case, the spatial resolution is expressed as the ground sample distance, implemented through the gco:Distance type. The unit of measure is either a conventional unit of measure symbol or a link to a definition. The latter case is illustrated above.

164

123456789

1011121314151617181920212223242526272829303132333435363738394041424344454647484950515253

1

If needed, the two options can be used in conjunction:

<?xml version="1 0" encoding="UTF-8"?><gmd:MD_Metadata><gmd:identificationInfo><gmd:spatialResolution> <gmd:MD_Resolution> <gmd:distance> <gco:Distance uom="#cm">25</gco:Distance> </gmd:distance> </gmd:MD_Resolution></gmd:spatialResolution><gmd:spatialResolution> <gmd:MD_Resolution> <gmd:equivalentScale> <gmd:MD_RepresentativeFraction> <gmd:denominator> <gco:Integer>25000</gco:Integer> </gmd:denominator> </gmd:MD_RepresentativeFraction> </gmd:equivalentScale> </gmd:MD_Resolution></gmd:spatialResolution></gmd:identificationInfo></gmd:MD_Metadata>

N.B. In this case, the property spatialResolution needs to be instantiated twice.

3.18A.11 Codelists

The two recommended ways to reference codelists are those expressed in the examples shown in 2.2.7 Resource LanguageThere are two recommended ways to reference codelists most interoperable: the element value repeats the codeListValue most compliant: the element value is the name of the codeListValue expressed in the

default language of the metadata (eg: if the metadata is filled in French, the element value should be in French)

Examples of XML encoding for language codes

1) Most interoperable: the element value repeats the codeListValue

<gmd:language> <gmd:LanguageCode codeList="http://www.loc.gov/standards/iso639-2/" codeListValue="eng">eng</gmd:LanguageCode> </gmd:language>

2) Most compliant: the element value is the name of the codeListValue expressed in the default language of the Metadata

<gmd:language> <gmd:LanguageCode codeList="http://www.loc.gov/standards/iso639-2/ " codeListValue="eng">English</gmd:LanguageCode> </gmd:language>.

165

123456789

101112131415161718192021222324252627282930313233

3435363738394041

424344454647484950515253545556575859

1

3.19A.12 Example of ISO 19139 XML Metadata Sets

3.19.1 A.12.1 Dataset

3.19.1.1 A.12.1.1 INSPIRE view

+ Part B 1 Identification:+ Part B 1.1 Resource Title: SPI: Standardized Precipitation Index + Part B 1.2 Resource

Abstract:The Standardized Precipitation Index (SPI-n) is a statistical indicator comparing the total precipitation received at a particular location during a period of n months with the long-termrainfall distribution for the same period of time at that location. SPI is calculated on a monthly basis for a moving window of n months, where n indicates the rainfall accumulation period, which is typically 1, 3, 6, 9, 12, 24 or 48 months. The corresponding SPIs are denoted as SPI-1, SPI-3, SPI-6, etc.In order to allow for the statistical comparison of wetter and drier climates, SPI is based on a transformation of the accumulated precipitation into a standard normal variable with zero mean and variance equal to one. SPI results are given in units of standard deviation from the long-term mean of the standardized distribution.In 2010 WMO selected the SPI as a key meteorological drought indicator to be producedoperationally by meteorological services

+ Part B 1.3 Resource Type: dataset+ Part B 1.4 Resource

Locator:http://edo.jrc.ec.europa.eu/chm/ows.php?VERSION=1.3.0&SERVICE=WMS&REQUEST=GetCapabilities

+ Part B 1.5 Resource Unique Identifier:+ code: e24425e1-b073-11e1-9105-0017085a97ab+ codeSpace: edo

+ Part B 1.7 Resource language: eng+ Part B 2 Classification of data and services:

+ Part B 2.1 Topic category: climatologyMeteorologyAtmosphere+ Part B 3 Keyword:

+ Part B 3.1 Keyword value: Atmospheric conditions+ Part B 3.2 Originating Controlled Vocabulary:

+ title: GEMET - INSPIRE themes, version 1.0 + reference date:

+ date: 2008-06-01+ date type: publication

+ Part B 4 Geographic Location:+ Part B 4.1 Bounding Box:

+ West: -15.00+ East: 45.00+ North: 35.00+ South: 72.00

+ Part B 5 Temporal Reference:+ Part B 5.2 Date of publication: 2012-02-20

+ Part B 6 Quality and validity:

+ Part B 6.1 Lineage:

Computation of the SPI involves fitting a probability density function to a givenfrequency distribution of precipitation totals for a station or grid point and foran accumulation period. We use the gamma probability density function. The statistics for the frequency distribution are calculated on the basis of a reference period of at least 30 years.The parameters of the probability density function are then used to find the cumulative probability of the observed precipitation for the required month and temporal scale. This cumulative probability is then transformed to the standardised normal distribution with mean zero and variance one, which results in the value of the SPI. The SPI values are computed using the so-called MARS weather stations as rainfall input data. Refer the MARS weather catalogue for characteristics of the quality and quantity of these data. We only rely on the rainfall data input.

+ Part B 6.2 Spatial Resolution: 0.25+ Part B 7.1 Specification:

+ title: COMMISSION REGULATION (EU) No 1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards

166

12

3

456

1

interoperability of spatial data sets and services+ publication date: 2010-12-08

+ Part B 7.2 Degree: not evaluated+ Part B 8 Constraints related to access and use:

+ Part B 8.2 Limitation on public access: no limitations+ Part B 8 Constraints related to access and use:

+ Part B 8.1 Condition applying to access and use:

Reproduction for non-commercial purposes is authorised, provided the source is acknowledged. Commercial use is not permitted without prior written consent of the JRC. Reports, articles, papers, scientific and non-scientific works of any form, including tables, maps, or any other kind of output, in printed or electronic form, based in whole or in part on the data supplied, must contain an acknowledgement of the form: Data re-used from the European Drought Observatory (EDO) http://edo.jrc.ec.europa.eu The SPI data were created as part of JRC's research activities. Although every care has been taken in preparing and testing the data, JRC cannot guarantee that the data are correct; neither does JRC accept any liability whatsoever for any error, missing data or omission in the data, or for any loss or damage arising from its use. The JRC will not be responsible for any direct or indirect use which might be made of the data. The JRC does not provide any assistance or support in using the data

+ Part B 9 Responsible Organisation:+ Part B 9.1 Responsible party:

+ organisation: European Commission, Joint Research Centre+ e-mail: [email protected]

+ Part B 9.2 Responsible party role: custodian+ Part B 10 Metadata on metadata:

+ Part B 10.1 Metadata point of contact:+ organisation: European Commission, Joint Research Centre+ e-mail: [email protected]

+ Part B 10.2 Metadata date: 2012-02-20

+ Part B 10.3 Metadata language: eng

167

1

1

3.19.1.2 A.12.1.2 ISO/TS 19139 XML File

NOTE: This file is an ISO compliant metadata record extracted from the INSPIRE geo-portal and tested through the INSPIRE Validator. It may contain more elements than the minimum required to comply with the INSPIRE metadata Regulation.

<?xml version="1.0" encoding="UTF-8"?><gmd:MD_Metadata xmlns:gmd="http://www.isotc211.org/2005/gmd" xmlns:gmx="http://www.isotc211.org/2005/gmx" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:gml="http://www.opengis.net/gml" xmlns:gco="http://www.isotc211.org/2005/gco" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:geonet="http://www.fao.org/geonetwork" xsi:schemaLocation="http://www.isotc211.org/2005/gmd http://schemas.opengis.net/iso/19139/20060504/gmd/gmd.xsd http://www.isotc211.org/2005/gmx http://schemas.opengis.net/iso/19139/20060504/gmx/gmx.xsd"> <gmd:fileIdentifier> <gco:CharacterString>f9ee6623-cf4c-11e1-9105-0017085a97ab</gco:CharacterString> </gmd:fileIdentifier> <gmd:language> <gmd:LanguageCode codeList="http://www.loc.gov/standards/iso639-2/" codeListValue="eng"/> </gmd:language> <gmd:characterSet> <gmd:MD_CharacterSetCode codeSpace="ISOTC211/19115" codeListValue="MD_CharacterSetCode_utf8" codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#MD_CharacterSetCode"/> </gmd:characterSet> <gmd:hierarchyLevel> <gmd:MD_ScopeCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#MD_ScopeCode" codeListValue="dataset"/> </gmd:hierarchyLevel> <gmd:contact> <gmd:CI_ResponsibleParty> <gmd:organisationName> <gco:CharacterString>European Commission, Joint Research Centre</gco:CharacterString> </gmd:organisationName> <gmd:contactInfo> <gmd:CI_Contact> <gmd:address> <gmd:CI_Address> <gmd:electronicMailAddress> <gco:CharacterString>[email protected]</gco:CharacterString> </gmd:electronicMailAddress> </gmd:CI_Address> </gmd:address> </gmd:CI_Contact> </gmd:contactInfo> <gmd:role> <gmd:CI_RoleCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#CI_RoleCode" codeListValue="pointOfContact"/> </gmd:role> </gmd:CI_ResponsibleParty> </gmd:contact> <gmd:dateStamp> <gco:DateTime>2013-02-07T15:15:06</gco:DateTime> </gmd:dateStamp> <gmd:metadataStandardName> <gco:CharacterString>ISO19115</gco:CharacterString> </gmd:metadataStandardName> <gmd:metadataStandardVersion> <gco:CharacterString>2003/Cor.1:2006</gco:CharacterString> </gmd:metadataStandardVersion> <gmd:referenceSystemInfo> <gmd:MD_ReferenceSystem> <gmd:referenceSystemIdentifier> <gmd:RS_Identifier> <gmd:code>

168

123456

789

1011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768

1

http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#CI_RoleCode




http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#MD_ScopeCode


http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#MD_CharacterSetCode

http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#MD_CharacterSetCode


http://schemas.opengis.net/iso/19139/20060504/gmx/gmx.xsd

http://www.isotc211.org/2005/gmx


http://www.isotc211.org/2005/gmd

http://www.fao.org/geonetwork

http://www.w3.org/1999/xlink

http://www.isotc211.org/2005/gco


http://www.w3.org/2001/XMLSchema-instance

http://www.isotc211.org/2005/gmx


<gco:CharacterString>ETRS:89</gco:CharacterString> </gmd:code> </gmd:RS_Identifier> </gmd:referenceSystemIdentifier> </gmd:MD_ReferenceSystem> </gmd:referenceSystemInfo> <gmd:referenceSystemInfo> <gmd:MD_ReferenceSystem> <gmd:referenceSystemIdentifier> <gmd:RS_Identifier> <gmd:code> <gco:CharacterString>WGS:84</gco:CharacterString> </gmd:code> </gmd:RS_Identifier> </gmd:referenceSystemIdentifier> </gmd:MD_ReferenceSystem> </gmd:referenceSystemInfo> <gmd:identificationInfo> <gmd:MD_DataIdentification id="ccm2.1_lakes"> <gmd:citation> <gmd:CI_Citation> <gmd:title> <gco:CharacterString>River and Catchment Database, version 2.1 (CCM2) - Lakes</gco:CharacterString> </gmd:title> <gmd:date> <gmd:CI_Date> <gmd:date> <gco:Date>2007-06-01</gco:Date> </gmd:date> <gmd:dateType> <gmd:CI_DateTypeCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#CI_DateTypeCode" codeListValue="publication"/> </gmd:dateType> </gmd:CI_Date> </gmd:date> <gmd:date> <gmd:CI_Date> <gmd:date> <gco:Date>2008-07-01</gco:Date> </gmd:date> <gmd:dateType> <gmd:CI_DateTypeCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#CI_DateTypeCode" codeListValue="revision"/> </gmd:dateType> </gmd:CI_Date> </gmd:date> <gmd:identifier> <gmd:RS_Identifier> <gmd:code> <gco:CharacterString>http://rdsi.jrc.ec.europa.eu/id/dataset/ccm2.1/lakes</gco:CharacterString> </gmd:code> <gmd:codeSpace> <gco:CharacterString>rdsi</gco:CharacterString> </gmd:codeSpace> </gmd:RS_Identifier> </gmd:identifier> <gmd:identifier> <gmd:RS_Identifier> <gmd:code> <gco:CharacterString>ccm2.1_lakes</gco:CharacterString> </gmd:code> <gmd:codeSpace> <gco:CharacterString>urn:eu:europa:ec:jrc:rdsi:id:dataset:ccm2.1</gco:CharacterString> </gmd:codeSpace> </gmd:RS_Identifier>

169

123456789

101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172

1

http://rdsi.jrc.ec.europa.eu/id/dataset/ccm2.1/lakes%3C/gco:CharacterString%3E

http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#CI_DateTypeCode




</gmd:identifier> </gmd:CI_Citation> </gmd:citation> <gmd:abstract> <gco:CharacterString>The Catchment Characterisation Model (CCM2) database covers the entire European continent, including the Atlantic islands, Iceland and Turkey. It allows for analysis from the regional to the continental scale, corresponding to traditional mapping scales of up to 1:500,000. CCM2 covers an area of about 12,000,000 square kilometres and includes more than 2,000,000 primary catchments. These can be aggregated to drainage basins at different hierarchical levels, forming, for example, about 650 river basins of more than 1000 square kilometres. CCM2 further includes a coastline, fully congruent with the river basins, and some 70,000 lakes. The layers are generated from a 100 metres resolution digital terrestrial elevation model. The following layers are available: Seaoutlets: the major river basins, Main drains: the major rivers, Lakes: all surface water larger than 25x25 metres, Coastlines: coast line extracted from Image2000 imagery, River segments: Drainage channels from the primary catchments, Catchments: Primary catchments. This dataset concerns the Lakes layers.</gco:CharacterString> </gmd:abstract> <gmd:pointOfContact> <gmd:CI_ResponsibleParty> <gmd:organisationName> <gco:CharacterString>European Commission, Joint Research Centre</gco:CharacterString> </gmd:organisationName> <gmd:contactInfo> <gmd:CI_Contact> <gmd:address> <gmd:CI_Address> <gmd:electronicMailAddress> <gco:CharacterString>[email protected]</gco:CharacterString> </gmd:electronicMailAddress> </gmd:CI_Address> </gmd:address> </gmd:CI_Contact> </gmd:contactInfo> <gmd:role> <gmd:CI_RoleCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#CI_RoleCode" codeListValue="author"/> </gmd:role> </gmd:CI_ResponsibleParty> </gmd:pointOfContact> <gmd:descriptiveKeywords> <gmd:MD_Keywords> <gmd:keyword> <gco:CharacterString>Hydrography</gco:CharacterString> </gmd:keyword> <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> <gmd:dateType> <gmd:CI_DateTypeCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#CI_DateTypeCode" codeListValue="publication"/> </gmd:dateType> </gmd:CI_Date> </gmd:date> </gmd:CI_Citation> </gmd:thesaurusName> </gmd:MD_Keywords> </gmd:descriptiveKeywords> <gmd:descriptiveKeywords> <gmd:MD_Keywords> <gmd:keyword>

170

123456789

101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172

1






<gco:CharacterString>river basin development</gco:CharacterString> </gmd:keyword> <gmd:keyword> <gco:CharacterString>river management</gco:CharacterString> </gmd:keyword> <gmd:keyword> <gco:CharacterString>lake</gco:CharacterString> </gmd:keyword> <gmd:thesaurusName> <gmd:CI_Citation> <gmd:title> <gco:CharacterString>GEMET - Concepts, version 2.3</gco:CharacterString> </gmd:title> <gmd:date> <gmd:CI_Date> <gmd:date> <gco:Date>2009-07-13</gco:Date> </gmd:date> <gmd:dateType> <gmd:CI_DateTypeCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#CI_DateTypeCode" codeListValue="publication"/> </gmd:dateType> </gmd:CI_Date> </gmd:date> </gmd:CI_Citation> </gmd:thesaurusName> </gmd:MD_Keywords> </gmd:descriptiveKeywords> <gmd:descriptiveKeywords> <gmd:MD_Keywords> <gmd:keyword> <gco:CharacterString>Feature coding</gco:CharacterString> </gmd:keyword> <gmd:keyword> <gco:CharacterString>River network</gco:CharacterString> </gmd:keyword> </gmd:MD_Keywords> </gmd:descriptiveKeywords> <gmd:resourceConstraints> <gmd:MD_Constraints> <gmd:useLimitation> <gmx:Anchor xlink:href="http://ccm.jrc.ec.europa.eu/php/index.php?action=view&id=26">License conditions apply, please consult http://ccm.jrc.ec.europa.eu/php/index.php?action=view&id=26</gmx:Anchor> </gmd:useLimitation> </gmd:MD_Constraints> </gmd:resourceConstraints> <gmd:resourceConstraints> <gmd:MD_LegalConstraints> <gmd:accessConstraints> <gmd:MD_RestrictionCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#MD_RestrictionCode" codeListValue="otherRestrictions"/> </gmd:accessConstraints> <gmd:otherConstraints> <gco:CharacterString>(e) intellectual property rights</gco:CharacterString> </gmd:otherConstraints> </gmd:MD_LegalConstraints> </gmd:resourceConstraints> <gmd:spatialResolution> <gmd:MD_Resolution> <gmd:equivalentScale> <gmd:MD_RepresentativeFraction> <gmd:denominator> <gco:Integer>500000</gco:Integer>

171

123456789

101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172

1

http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#MD_RestrictionCode


http://ccm.jrc.ec.europa.eu/php/index.php?action=view&id=26%3C/gmx:Anchor%3E

http://ccm.jrc.ec.europa.eu/php/index.php?action=view&id=26



</gmd:denominator> </gmd:MD_RepresentativeFraction> </gmd:equivalentScale> </gmd:MD_Resolution> </gmd:spatialResolution> <gmd:spatialResolution> <gmd:MD_Resolution> <gmd:distance> <gco:Distance uom="metres">100</gco:Distance> </gmd:distance> </gmd:MD_Resolution> </gmd:spatialResolution> <gmd:language> <gmd:LanguageCode codeList="http://www.loc.gov/standards/iso639-2/" codeListValue="eng"/> </gmd:language> <gmd:topicCategory> <gmd:MD_TopicCategoryCode>inlandWaters</gmd:MD_TopicCategoryCode> </gmd:topicCategory> <gmd:topicCategory> <gmd:MD_TopicCategoryCode>elevation</gmd:MD_TopicCategoryCode> </gmd:topicCategory> <gmd:topicCategory> <gmd:MD_TopicCategoryCode>oceans</gmd:MD_TopicCategoryCode> </gmd:topicCategory> <gmd:extent> <gmd:EX_Extent> <gmd:geographicElement> <gmd:EX_GeographicBoundingBox> <gmd:westBoundLongitude> <gco:Decimal>-31.269538</gco:Decimal> </gmd:westBoundLongitude> <gmd:eastBoundLongitude> <gco:Decimal>60.607986</gco:Decimal> </gmd:eastBoundLongitude> <gmd:southBoundLatitude> <gco:Decimal>27.63664</gco:Decimal> </gmd:southBoundLatitude> <gmd:northBoundLatitude> <gco:Decimal>71.185654</gco:Decimal> </gmd:northBoundLatitude> </gmd:EX_GeographicBoundingBox> </gmd:geographicElement> </gmd:EX_Extent> </gmd:extent> </gmd:MD_DataIdentification> </gmd:identificationInfo> <gmd:distributionInfo> <gmd:MD_Distribution> <gmd:distributionFormat> <gmd:MD_Format> <gmd:name> <gco:CharacterString>ESRI File Geodatabase (proprietary format)</gco:CharacterString> </gmd:name> <gmd:version> <gco:CharacterString>9.2</gco:CharacterString> </gmd:version> </gmd:MD_Format> </gmd:distributionFormat> <gmd:transferOptions> <gmd:MD_DigitalTransferOptions> <gmd:onLine> <gmd:CI_OnlineResource> <gmd:linkage> <gmd:URL>http://ccm.jrc.ec.europa.eu</gmd:URL> </gmd:linkage> <gmd:name> <gco:CharacterString>CCM web

172

123456789

101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172

1


page</gco:CharacterString> </gmd:name> <gmd:description> <gco:CharacterString>Catchment Characterisation and Modelling (CCM) web site</gco:CharacterString> </gmd:description> <gmd:function> <gmd:CI_OnLineFunctionCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#CI_OnLineFunctionCode" codeListValue="information"/> </gmd:function> </gmd:CI_OnlineResource> </gmd:onLine> <gmd:onLine> <gmd:CI_OnlineResource> <gmd:linkage> <gmd:URL>http://ags-sdi-public.jrc.ec.europa.eu/arcgis/services/CCM_WGS84/MapServer/WMSServer?request=GetCapabilities&service=WMS</gmd:URL> </gmd:linkage> <gmd:name> <gco:CharacterString>Catchment Characterisation Model (CCM) - Demo INSPIRE View Service</gco:CharacterString> </gmd:name> <gmd:description> <gco:CharacterString>Demonstrates implementation of the View Service according to the INSPIRE technical guidelines for the Catchment Characterisation Model (CCM) database. Drainage networks and associated drainage basins form complex functional entities not only for hydrological processes but also for environmental processes at large. This has been recognised in recent European legislation such as the Water Framework Directive (WFD). In order to study the underlying processes and cause-effect relationships at regional to European scales, comprehensive digital data of river networks, drainage basins (catchments) and their characteristics are required. JRC's Catchment Characterisation and Modelling (CCM) activity responded to this need through the development of a pan-European database of river networks and catchments. Version 1.0 of CCM has been published in 2003. In July 2007 an geographically extended and substantially improved CCM Version 2.0 has been released. The current Version 2.1 of July 2008 is an update of version 2.0. It includes the correction of noted errors as well additional functionality. A detailed report on the development of CCM 2.0 as well Release Notes for CCM 2.1 are provided on the CCM website</gco:CharacterString> </gmd:description> <gmd:function> <gmd:CI_OnLineFunctionCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#CI_OnLineFunctionCode" codeListValue="information">information</gmd:CI_OnLineFunctionCode> </gmd:function> </gmd:CI_OnlineResource> </gmd:onLine> <gmd:onLine> <gmd:CI_OnlineResource> <gmd:linkage> <gmd:URL>http://vap-xgeodev.jrc.it/ccm/democcmdownloadservice.atom.en.xml </ gmd:URL > </gmd:linkage> <gmd:name> <gco:CharacterString>Catchment Characterisation Model (CCM) - Demo INSPIRE Download Service</gco:CharacterString> </gmd:name> <gmd:description> <gco:CharacterString>Download Facility for the Lakes data from the CCM2 database</gco:CharacterString> </gmd:description> <gmd:function> <gmd:CI_OnLineFunctionCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#CI_OnLineFunctionCode" codeListValue="download"/> </gmd:function> </gmd:CI_OnlineResource> </gmd:onLine> <gmd:onLine> <gmd:CI_OnlineResource> <gmd:linkage> <gmd:URL>http://ags-sdi-

173

123456789

101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172

1

http://ags-sdi-public.jrc.ec.europa.eu/arcgis/services/CCM2_Danube/MapServer/WMSServer?request=GetCapabilities&service=WMS%3C/gmd:URL%3E


http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#CI_OnLineFunctionCode


http://vap-xgeodev.jrc.it/ccm/democcmdownloadservice.atom.en.xml%3C/gmd:URL%3E





public.jrc.ec.europa.eu/arcgis/services/CCM2_Danube/MapServer/WMSServer?request=GetCapabilities&service=WMS </ gmd:URL > </gmd:linkage> <gmd:protocol gco:nilReason="missing"> <gco:CharacterString/> </gmd:protocol> <gmd:name> <gco:CharacterString>Catchment Characterisation Model (CCM2) - Danube INSPIRE View Service</gco:CharacterString> </gmd:name> <gmd:description> <gco:CharacterString>Danube View Service according to the INSPIRE technical guidelines for the Catchment Characterisation Model (CCM) database. Drainage networks and associated drainage basins form complex functional entities not only for hydrological processes but also for environmental processes at large. This has been recognised in recent European legislation such as the Water Framework Directive (WFD). In order to study the underlying processes and cause-effect relationships at regional to European scales, comprehensive digital data of river networks, drainage basins (catchments) and their characteristics are required. JRC's Catchment Characterisation and Modelling (CCM) activity responded to this need through the development of a pan-European database of river networks and catchments. Version 1.0 of CCM has been published in 2003. In July 2007 an geographically extended and substantially improved CCM Version 2.0 has been released. The current Version 2.1 of July 2008 is an update of version 2.0. It includes the correction of noted errors as well additional functionality. A detailed report on the development of CCM 2.0 as well Release Notes for CCM 2.1 are provided on the CCM website</gco:CharacterString> </gmd:description> </gmd:CI_OnlineResource> </gmd:onLine> </gmd:MD_DigitalTransferOptions> </gmd:transferOptions> </gmd:MD_Distribution> </gmd:distributionInfo> <gmd:dataQualityInfo> <gmd:DQ_DataQuality> <gmd:scope> <gmd:DQ_Scope> <gmd:level> <gmd:MD_ScopeCode codeListValue="dataset" codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#MD_ScopeCode"/> </gmd:level> </gmd:DQ_Scope> </gmd:scope> <gmd:report> <gmd:DQ_DomainConsistency xsi:type="gmd:DQ_DomainConsistency_Type"> <gmd:measureIdentification> <gmd:RS_Identifier> <gmd:code> <gco:CharacterString>Conformity_001</gco:CharacterString> </gmd:code> <gmd:codeSpace> <gco:CharacterString>INSPIRE</gco:CharacterString> </gmd:codeSpace> </gmd:RS_Identifier> </gmd:measureIdentification> <gmd:result> <gmd:DQ_ConformanceResult xsi:type="gmd:DQ_ConformanceResult_Type"> <gmd:specification xlink:href=""> <gmd:CI_Citation> <gmd:title> <gco:CharacterString>COMMISSION REGULATION (EU) No 1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services</gco:CharacterString> </gmd:title> <gmd:date> <gmd:CI_Date> <gmd:date> <gco:Date>2010-12-08</gco:Date> </gmd:date>

174

123456789

101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475

1





<gmd:dateType> <gmd:CI_DateTypeCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#CI_DateTypeCode" codeListValue="publication"/> </gmd:dateType> </gmd:CI_Date> </gmd:date> </gmd:CI_Citation> </gmd:specification> <gmd:explanation> <gco:CharacterString>See the referenced specification</gco:CharacterString> </gmd:explanation> <gmd:pass gco:nilReason="inapplicable"/> </gmd:DQ_ConformanceResult> </gmd:result> </gmd:DQ_DomainConsistency> </gmd:report> <gmd:lineage> <gmd:LI_Lineage> <gmd:statement> <gco:CharacterString>Drainage networks and associated drainage basins form complex functional entities not only for hydrological processes but also for environmental processes at large. This has been recognised in recent European legislation such as the Water Framework Directive (WFD). In order to study the underlying processes and cause-effect relationships at regional to European scales, comprehensive digital data of river networks, drainage basins (catchments) and their characteristics are required. JRC's Catchment Characterisation and Modelling (CCM) activity responded to this need through the development of a pan-European database of river networks and catchments. Version 1.0 of CCM has been published in 2003. In July 2007 an geographically extended and substantially improved CCM Version 2.0 has been released. The current Version 2.1 of July 2008 is an update of version 2.0. It includes the correction of noted errors as well additional functionality. Lakes is one of the five main feature classes in which CCM 2 is structured. A detailed report on the development of CCM 2.0 as well Release Notes for CCM 2.1 are provided at http://ccm.jrc.ec.europa.eu/documents/CCM2-Report_EUR-22920-EN_2007_STD.pdf.</gco:CharacterString> </gmd:statement> </gmd:LI_Lineage> </gmd:lineage> </gmd:DQ_DataQuality> </gmd:dataQualityInfo></gmd:MD_Metadata>

3.19.2 A.12.2 Dataset series

There is no significant difference between the metadata of a dataset and the metadata of a dataset series. See A.11.1.

3.19.3 A.12.3 Service

3.19.3.1 A.12.3.1 INSPIRE view

+ Part B 1 Identification:+ Part B 1.1 Resource Title: Catchment Characterisation Model (CCM) - Demo INSPIREView Service+ Part B 1.2 Resource

Abstract:Demonstrates implementation of the View Service according to the INSPIRE technical guidelines for the Catchment Characterisation Model (CCM) database. Drainage networks and associated drainage basins form complex functional entities not only for hydrological processes but also for environmental processes at large. This has been recognised in recent European legislation such as the Water Framework Directive (WFD). In order to study the underlying processes and cause-effect relationships at regional to European scales, comprehensive digital data of river networks, drainage basins (catchments) and their characteristics are required. JRC's Catchment Characterisation and Modelling (CCM) activity responded to this need through the development of a pan-European database of river

175

123456789

10111213141516171819202122232425262728293031323334353637383940

41

4243444546

47

4849

1

http://ccm.jrc.ec.europa.eu/documents/CCM2-Report_EUR-22920-EN_2007



networks and catchments. Version 1.0 of CCM has been published in 2003. In July 2007 an geographically extended and substantially improved CCM Version 2.0 has been released. The current Version 2.1 of July 2008 is an update of version 2.0. It includes the correction of noted errors as well additional functionality. A detailed report on the development of CCM 2.0 as well Release Notes for CCM 2.1 are provided on the CCM website.

+ Part B 1.3 Resource Type: service+ Part B 1.4 Resource

Locator:http://ags-sdi-public.jrc.ec.europa.eu/arcgis/services/CCM_WGS84/MapServer/WMSServer?request=GetCapabilities&service=WMS

+ Part B 1.4 Resource Locator:

+ Part B 1.6 Coupled Resource:+ ref: Code: http://rdsi.jrc.ec.europa.eu/id/dataset/ccm2.1/lakes, Namespace: rdsi

+ Part B 2 Classification of data and services:+ Part B 2.2 Spatial data service

type: View Service+ Part B 3 Keyword:

+ Part B 3.1 Keyword value: Geographic viewer (humanGeographicViewer)+ Part B 3 Keyword:

+ Part B 3.1 Keyword value: river basin development+ Part B 3 Keyword:

+ Part B 3.1 Keyword value: river management+ Part B 4 Geographic Location:

+ Part B 4.1 Bounding Box:+ West: -32.0+ East: +61.0+ North: +27.0+ South: +72.0

+ Part B 5 Temporal Reference:+ Part B 5.2 Date of publication: 2007-06-01

+ Part B 6 Quality and validity:+ Part B 7.1 Specification:

+ title: COMMISSION REGULATION (EU) No 1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services

+ publication date: 2010-03-29+ Part B 7.2 Degree: true+ Part B 7.1 Specification:

+ title: Commission Regulation (EC) No 976/2009 of 19 October 2009 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards the Network Services

+ publication date: 2009-10-19+ Part B 7.2 Degree: true

+ Part B 8 Constraint related to access and use:+ Part B 7.1 Specification:

+ title: Technical Guidance for the implementation of INSPIREView Services+ publication date: 2011-11-07

+ Part B 7.2 Degree: true+ Part B 8.1 Condition applying to access and

use:no condition apply

+ Part B 8.2 Limitation on public access: no limitations+ Part B 9 Responsible Organisation:

+ Part B 9.1 Responsible party:+ organisation: European Commission, Joint Research Centre+ e-mail: [email protected]

+ Part B 9.2 Responsible party role: custodian+ Part B 10 Metadata on metadata:

+ Part B 10.1 Metadata point of contact:+ organisation: European Commission Joint Research Centre+ e-mail: [email protected]

+ Part B 10.2 Metadata date: 2012-11-28

+ Part B 10.3 Metadata language: eng

3.19.3.2 A.12.3.2 ISO/TS 19139 XML File

176

1

23

1


<?xml version="1.0" encoding="UTF-8"?><gmd:MD_Metadata xmlns:gmd="http://www.isotc211.org/2005/gmd" 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:gco="http://www.isotc211.org/2005/gco" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:geonet="http://www.fao.org/geonetwork" xsi:schemaLocation="http://www.isotc211.org/2005/srv http://schemas.opengis.net/iso/19139/20060504/srv/srv.xsd"> <gmd:fileIdentifier> <gco:CharacterString>7565a299-cf25-11e1-9105-0017085a97ab</gco:CharacterString> </gmd:fileIdentifier> <gmd:language> <gmd:LanguageCode codeList="http://www.loc.gov/standards/iso639-2/" codeListValue="eng"/> </gmd:language> <gmd:hierarchyLevel> <gmd:MD_ScopeCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#MD_ScopeCode" codeListValue="service"/> </gmd:hierarchyLevel> <gmd:contact> <gmd:CI_ResponsibleParty> <gmd:organisationName> <gco:CharacterString>European Commission, Joint Research Centre</gco:CharacterString> </gmd:organisationName> <gmd:contactInfo> <gmd:CI_Contact> <gmd:address> <gmd:CI_Address> <gmd:electronicMailAddress> <gco:CharacterString>[email protected]</gco:CharacterString> </gmd:electronicMailAddress> </gmd:CI_Address> </gmd:address> </gmd:CI_Contact> </gmd:contactInfo> <gmd:role> <gmd:CI_RoleCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#CI_RoleCode" codeListValue="pointOfContact"/> </gmd:role> </gmd:CI_ResponsibleParty> </gmd:contact> <gmd:dateStamp> <gco:DateTime>2012-11-28T15:38:45</gco:DateTime> </gmd:dateStamp> <gmd:metadataStandardName> <gco:CharacterString>ISO19115</gco:CharacterString> </gmd:metadataStandardName> <gmd:metadataStandardVersion> <gco:CharacterString>2003/Cor.1:2006</gco:CharacterString> </gmd:metadataStandardVersion> <gmd:referenceSystemInfo> <gmd:MD_ReferenceSystem> <gmd:referenceSystemIdentifier> <gmd:RS_Identifier> <gmd:code> <gco:CharacterString>ETRS:89</gco:CharacterString> </gmd:code> </gmd:RS_Identifier> </gmd:referenceSystemIdentifier> </gmd:MD_ReferenceSystem> </gmd:referenceSystemInfo> <gmd:referenceSystemInfo> <gmd:MD_ReferenceSystem> <gmd:referenceSystemIdentifier> <gmd:RS_Identifier> <gmd:code> <gco:CharacterString>WGS:84</gco:CharacterString> </gmd:code> </gmd:RS_Identifier> </gmd:referenceSystemIdentifier> </gmd:MD_ReferenceSystem> </gmd:referenceSystemInfo>

177

123456789

101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172

1








http://schemas.opengis.net/iso/19139/20060504/srv/srv.xsd

http://www.isotc211.org/2005/srv

http://www.fao.org/geonetwork

http://www.w3.org/1999/xlink

http://www.isotc211.org/2005/gco


http://www.isotc211.org/2005/srv

http://www.w3.org/2001/XMLSchema-instance


<gmd:identificationInfo> <srv:SV_ServiceIdentification> <gmd:citation> <gmd:CI_Citation> <gmd:title> <gco:CharacterString>Catchment Characterisation Model (CCM) - Demo INSPIRE View Service</gco:CharacterString> </gmd:title> <gmd:date> <gmd:CI_Date> <gmd:date> <gco:Date>2007-06-01</gco:Date> </gmd:date> <gmd:dateType> <gmd:CI_DateTypeCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#CI_DateTypeCode" codeListValue="publication"/> </gmd:dateType> </gmd:CI_Date> </gmd:date> <gmd:date> <gmd:CI_Date> <gmd:date> <gco:Date>2008-07-01</gco:Date> </gmd:date> <gmd:dateType> <gmd:CI_DateTypeCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#CI_DateTypeCode" codeListValue="revision"/> </gmd:dateType> </gmd:CI_Date> </gmd:date> <gmd:identifier> <gmd:RS_Identifier> <gmd:code> <gco:CharacterString>dd3166d7-cf24-11e1-9105-0017085a97ab</gco:CharacterString> </gmd:code> </gmd:RS_Identifier> </gmd:identifier> </gmd:CI_Citation> </gmd:citation> <gmd:abstract> <gco:CharacterString>Demonstrates implementation of the View Service according to the INSPIRE technical guidelines for the Catchment Characterisation Model (CCM) database. Drainage networks and associated drainage basins form complex functional entities not only for hydrological processes but also for environmental processes at large. This has been recognised in recent European legislation such as the Water Framework Directive (WFD). In order to study the underlying processes and cause-effect relationships at regional to European scales, comprehensive digital data of river networks, drainage basins (catchments) and their characteristics are required. JRC's Catchment Characterisation and Modelling (CCM) activity responded to this need through the development of a pan-European database of river networks and catchments. Version 1.0 of CCM has been published in 2003. In July 2007 an geographically extended and substantially improved CCM Version 2.0 has been released. The current Version 2.1 of July 2008 is an update of version 2.0. It includes the correction of noted errors as well additional functionality. A detailed report on the development of CCM 2.0 as well Release Notes for CCM 2.1 are provided on the CCM website.</gco:CharacterString> </gmd:abstract> <gmd:pointOfContact> <gmd:CI_ResponsibleParty> <gmd:individualName> <gco:CharacterString>RDSI team</gco:CharacterString> </gmd:individualName> <gmd:organisationName> <gco:CharacterString>European Commission, Joint Research Centre</gco:CharacterString> </gmd:organisationName> <gmd:contactInfo> <gmd:CI_Contact> <gmd:phone> <gmd:CI_Telephone/> </gmd:phone> <gmd:address> <gmd:CI_Address>

178

123456789

101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172

1





<gmd:electronicMailAddress> <gco:CharacterString>[email protected]</gco:CharacterString> </gmd:electronicMailAddress> </gmd:CI_Address> </gmd:address> </gmd:CI_Contact> </gmd:contactInfo> <gmd:role> <gmd:CI_RoleCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#CI_RoleCode" codeListValue="custodian"/> </gmd:role> </gmd:CI_ResponsibleParty> </gmd:pointOfContact> <gmd:descriptiveKeywords> <gmd:MD_Keywords> <gmd:keyword> <gco:CharacterString>river basin development</gco:CharacterString> </gmd:keyword> <gmd:keyword> <gco:CharacterString>river management</gco:CharacterString> </gmd:keyword> <gmd:keyword> <gco:CharacterString>hydrography</gco:CharacterString> </gmd:keyword> <gmd:keyword> <gco:CharacterString>Feature coding</gco:CharacterString> </gmd:keyword> <gmd:keyword> <gco:CharacterString>River network</gco:CharacterString> </gmd:keyword> <gmd:keyword> <gco:CharacterString>humanGeographicViewer</gco:CharacterString> </gmd:keyword> <gmd:keyword> <gco:CharacterString>Seaoutlet</gco:CharacterString> </gmd:keyword> <gmd:keyword> <gco:CharacterString>drainage basins</gco:CharacterString> </gmd:keyword> </gmd:MD_Keywords> </gmd:descriptiveKeywords> <gmd:descriptiveKeywords> <gmd:MD_Keywords> <gmd:keyword> <gco:CharacterString>lake</gco:CharacterString> </gmd:keyword> <gmd:keyword> <gco:CharacterString>coast</gco:CharacterString> </gmd:keyword> <gmd:keyword> <gco:CharacterString>river</gco:CharacterString> </gmd:keyword> <gmd:keyword> <gco:CharacterString>catchments</gco:CharacterString> </gmd:keyword> <gmd:type> <gmd:MD_KeywordTypeCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#MD_KeywordTypeCode" codeListValue="theme"/> </gmd:type> <gmd:thesaurusName> <gmd:CI_Citation id="geonetwork.thesaurus.external.theme.gemet"> <gmd:title> <gco:CharacterString>GEMET -

179

123456789

101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172

1

http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#MD_KeywordTypeCode

http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#MD_KeywordTypeCode




Concepts, version 2.3</gco:CharacterString> </gmd:title> <gmd:date> <gmd:CI_Date> <gmd:date> <gco:Date>2009-07-13</gco:Date> </gmd:date> <gmd:dateType> <gmd:CI_DateTypeCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#CI_DateTypeCode" 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>no conditions apply</gco:CharacterString> </gmd:useLimitation> </gmd:MD_Constraints> </gmd:resourceConstraints> <gmd:resourceConstraints> <gmd:MD_LegalConstraints> <gmd:accessConstraints> <gmd:MD_RestrictionCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#MD_RestrictionCode" codeListValue="otherRestrictions"/> </gmd:accessConstraints> <gmd:otherConstraints> <gco:CharacterString>no limitations</gco:CharacterString> </gmd:otherConstraints> </gmd:MD_LegalConstraints> </gmd:resourceConstraints> <srv:serviceType> <gco:LocalName>view</gco:LocalName> </srv:serviceType> <srv:extent> <gmd:EX_Extent> <gmd:geographicElement> <gmd:EX_GeographicBoundingBox> <gmd:westBoundLongitude> <gco:Decimal>-32.0</gco:Decimal> </gmd:westBoundLongitude> <gmd:eastBoundLongitude> <gco:Decimal>61.0</gco:Decimal> </gmd:eastBoundLongitude> <gmd:southBoundLatitude> <gco:Decimal>27.0</gco:Decimal> </gmd:southBoundLatitude> <gmd:northBoundLatitude> <gco:Decimal>72.0</gco:Decimal> </gmd:northBoundLatitude> </gmd:EX_GeographicBoundingBox> </gmd:geographicElement> </gmd:EX_Extent> </srv:extent> <srv:couplingType> <srv:SV_CouplingType codeListValue="loose" codeList="http://www.isotc211.org/2005/iso19119/resources/Codelist/gmxCodelists.xml#SV_CouplingType"/> </srv:couplingType> <srv:containsOperations> <srv:SV_OperationMetadata> <srv:operationName> <gco:CharacterString>GetCapabilities</gco:CharacterString> </srv:operationName>

180

123456789

101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172

1

http://www.isotc211.org/2005/iso19119/resources/Codelist/gmxCodelists.xml#SV_CouplingType





<srv:DCP> <srv:DCPList codeListValue="WebServices" codeList="http://www.isotc211.org/2005/iso19119/resources/Codelist/gmxCodelists.xml#DCPList"/> </srv:DCP> <srv:connectPoint> <gmd:CI_OnlineResource> <gmd:linkage> <gmd:URL>http://ags-sdi-public.jrc.ec.europa.eu/arcgis/services/CCM_WGS84/MapServer/WMSServer?request=GetCapabilities&service=WMS</gmd:URL> </gmd:linkage> </gmd:CI_OnlineResource> </srv:connectPoint> </srv:SV_OperationMetadata> </srv:containsOperations> <srv:operatesOn uuidref="f9ee6623-cf4c-11e1-9105-0017085a97ab" xlink:href="http://vap-xgeodev.jrc.ec.europa.eu/geonetwork/srv/eng/csw?SERVICE=CSW&VERSION=2.0.2&REQUEST=GetRecordById&ID=f9ee6623-cf4c-11e1-9105-0017085a97ab&OUTPUTSCHEMA=http://www.isotc211.org/2005/gmd&ELEMENTSETNAME=full#ccm2.1_lakes"/> <srv:operatesOn uuidref="6b8c8cd4-cf4d-11e1-9105-0017085a97ab" xlink:href="http://vap-xgeodev.jrc.ec.europa.eu/geonetwork/srv/eng/csw?SERVICE=CSW&VERSION=2.0.2&REQUEST=GetRecordById&ID=6b8c8cd4-cf4d-11e1-9105-0017085a97ab&OUTPUTSCHEMA=http://www.isotc211.org/2005/gmd&ELEMENTSETNAME=full#ccm2.1_riverbasins"/> <srv:operatesOn uuidref="fe1878e8-7541-4c66-8453-afdae7469221" xlink:href="http://vap-xgeodev.jrc.ec.europa.eu/geonetwork/srv/eng/csw?SERVICE=CSW&VERSION=2.0.2&REQUEST=GetRecordById&ID=fe1878e8-7541-4c66-8453-afdae7469221&OUTPUTSCHEMA=http://www.isotc211.org/2005/gmd&ELEMENTSETNAME=full#ccm2.1"/> </srv:SV_ServiceIdentification> </gmd:identificationInfo> <gmd:distributionInfo> <gmd:MD_Distribution> <gmd:transferOptions> <gmd:MD_DigitalTransferOptions> <gmd:onLine> <gmd:CI_OnlineResource> <gmd:linkage> <gmd:URL>http://ags-sdi-public.jrc.ec.europa.eu/arcgis/services/CCM_WGS84/MapServer/WMSServer?request=GetCapabilities&service=WMS</gmd:URL> </gmd:linkage> <gmd:protocol> <gco:CharacterString>OGC:WMS-1.3.0-http-get-capabilities</gco:CharacterString> </gmd:protocol> <gmd:name> <gco:CharacterString>Catchment Characterisation Model (CCM) - Demo INSPIRE View Service</gco:CharacterString> </gmd:name> <gmd:description> <gco:CharacterString>Demonstrates implementation of the View Service according to the INSPIRE technical guidelines for the Catchment Characterisation Model (CCM) database. Drainage networks and associated drainage basins form complex functional entities not only for hydrological processes but also for environmental processes at large. This has been recognised in recent European legislation such as the Water Framework Directive (WFD). In order to study the underlying processes and cause-effect relationships at regional to European scales, comprehensive digital data of river networks, drainage basins (catchments) and their characteristics are required. JRC's Catchment Characterisation and Modelling (CCM) activity responded to this need through the development of a pan-European database of river networks and catchments. Version 1.0 of CCM has been published in 2003. In July 2007 an geographically extended and substantially improved CCM Version 2.0 has been released. The current Version 2.1 of July 2008 is an update of version 2.0. It includes the correction of noted errors as well additional functionality. A detailed report on the development of CCM 2.0 as well Release Notes for CCM 2.1 are provided on the CCM website</gco:CharacterString> </gmd:description> <gmd:function> <gmd:CI_OnLineFunctionCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#CI_OnLineFunctionCode" codeListValue="information">information</gmd:CI_OnLineFunctionCode> </gmd:function>

181

123456789

101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172

1



http://vap-xgeodev.jrc.ec.europa.eu/geonetwork/srv/eng/csw?SERVICE=CSW&VERSION=2.0.2&REQUEST=GetRecordById&ID=fe1878e8-7541-4c66-8453-afdae7469221&OUTPUTSCHEMA=http://www.isotc211.org/2005/gmd&ELEMENTSETNAME=full#ccm2.1



http://vap-xgeodev.jrc.ec.europa.eu/geonetwork/srv/eng/csw?SERVICE=CSW&VERSION=2.0.2&REQUEST=GetRecordById&ID=6b8c8cd4-cf4d-11e1-9105-0017085a97ab&OUTPUTSCHEMA=http://www.isotc211.org/2005/gmd&ELEMENTSETNAME=full#ccm2.1_riverbasins



http://vap-xgeodev.jrc.ec.europa.eu/geonetwork/srv/eng/csw?SERVICE=CSW&VERSION=2.0.2&REQUEST=GetRecordById&ID=f9ee6623-cf4c-11e1-9105-0017085a97ab&OUTPUTSCHEMA=http://www.isotc211.org/2005/gmd&ELEMENTSETNAME=full#ccm2.1_lakes



http://www.isotc211.org/2005/iso19119/resources/Codelist/gmxCodelists.xml#DCPList

</gmd:CI_OnlineResource> </gmd:onLine> </gmd:MD_DigitalTransferOptions> </gmd:transferOptions> </gmd:MD_Distribution> </gmd:distributionInfo> <gmd:dataQualityInfo> <gmd:DQ_DataQuality> <gmd:scope> <gmd:DQ_Scope> <gmd:level> <gmd:MD_ScopeCode codeListValue="service" codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#MD_ScopeCode"/> </gmd:level> </gmd:DQ_Scope> </gmd:scope> <gmd:report> <gmd:DQ_DomainConsistency> <gmd:result> <gmd:DQ_ConformanceResult> <gmd:specification xlink:href="http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=CELEX:32010R0268:EN:NOT"> <gmd:CI_Citation> <gmd:title> <gco:CharacterString>COMMISSION REGULATION (EU) No 1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services</gco:CharacterString> </gmd:title> <gmd:date> <gmd:CI_Date> <gmd:date> <gco:Date>2010-03-29</gco:Date> </gmd:date> <gmd:dateType> <gmd:CI_DateTypeCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#CI_DateTypeCode" codeListValue="publication"/> </gmd:dateType> </gmd:CI_Date> </gmd:date> </gmd:CI_Citation> </gmd:specification> <gmd:explanation> <gco:CharacterString>http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=CELEX:32010R0268:EN:NOT</gco:CharacterString> </gmd:explanation> <gmd:pass> <gco:Boolean>true</gco:Boolean> </gmd:pass> </gmd:DQ_ConformanceResult> </gmd:result> </gmd:DQ_DomainConsistency> </gmd:report> <gmd:report> <gmd:DQ_DomainConsistency> <gmd:result> <gmd:DQ_ConformanceResult> <gmd:specification> <gmd:CI_Citation> <gmd:title> <gco:CharacterString>Commission Regulation (EC) No 976/2009 of 19 October 2009 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards the Network Services</gco:CharacterString> </gmd:title> <gmd:date> <gmd:CI_Date>

182

123456789

101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172

1

http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=CELEX:32010R0268:EN:NOT%3C/gco:CharacterString%3E




http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=CELEX:32010R0268:EN:NOT

http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=CELEX:32010R0268:EN:NOT



<gmd:date> <gco:Date>2009-10-19</gco:Date> </gmd:date> <gmd:dateType> <gmd:CI_DateTypeCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#CI_DateTypeCode" codeListValue="publication"/> </gmd:dateType> </gmd:CI_Date> </gmd:date> </gmd:CI_Citation> </gmd:specification> <gmd:explanation> <gco:CharacterString>http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=CELEX:32009R0976:EN:NOT</gco:CharacterString> </gmd:explanation> <gmd:pass> <gco:Boolean>true</gco:Boolean> </gmd:pass> </gmd:DQ_ConformanceResult> </gmd:result> </gmd:DQ_DomainConsistency> </gmd:report> <gmd:report> <gmd:DQ_DomainConsistency> <gmd:result> <gmd:DQ_ConformanceResult> <gmd:specification> <gmd:CI_Citation> <gmd:title> <gco:CharacterString>Technical Guidance for the implementation of INSPIRE View Services</gco:CharacterString> </gmd:title> <gmd:date> <gmd:CI_Date> <gmd:date> <gco:Date>2011-11-07</gco:Date> </gmd:date> <gmd:dateType> <gmd:CI_DateTypeCode codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codelist/ML_gmxCodelists.xml#CI_DateTypeCode" codeListValue="publication"/> </gmd:dateType> </gmd:CI_Date> </gmd:date> </gmd:CI_Citation> </gmd:specification> <gmd:explanation> <gco:CharacterString>http://inspire.jrc.ec.europa.eu/documents/Network_Services/TechnicalGuidance_ViewServices_v3.1.pdf</gco:CharacterString> </gmd:explanation> <gmd:pass> <gco:Boolean>true</gco:Boolean> </gmd:pass> </gmd:DQ_ConformanceResult> </gmd:result> </gmd:DQ_DomainConsistency> </gmd:report> </gmd:DQ_DataQuality> </gmd:dataQualityInfo></gmd:MD_Metadata>

183

123456789

10111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970

71

1

http://inspire.jrc.ec.europa.eu/documents/Network_Services/TechnicalGuidance_ViewServices_v3.1.pdf%3C/gco:CharacterString%3E

http://inspire.jrc.ec.europa.eu/documents/Network_Services/TechnicalGuidance_ViewServices_v3.1.pdf%3C/gco:CharacterString%3E







Annex B(informative)

Metadata elements for interoperability

This Annex gives an overview of the additional metadata elements defined in the INSPIRE Implementing Rules on the Interoperability of Spatial Datasets and Services (Commission Regulation (EU) No 1089/2010) and in the Data Specifications Technical Guidelines for the Annex I-III spatial data themes.

For further details, see the Data Specifications Technical Guidelines16.

3.20B.1. Metadata elements required by the INSPIRE Implementing Rules on the Interoperability of Spatial Datasets and Services

The following metadata elements are defined as “metadata required for interoperability” in Article 13 of the Implementing Rules on the Interoperability of Spatial Datasets and Services. They are applicable to all Spatial Data Themes from Annexes I, II and III.

Metadata element Definition MultiplicityCondition


Description of the coordinate reference system(s) used in the data set.

1..*

Temporal reference system

Description of the temporal reference systems used in the dataset.

0..*

Mandatory, if the spatial data set or one of its feature types contains temporal information that does not refer to the Gregorian Calendar or the Coordinated Universal Time.

Encoding

Description of the computer language construct(s) specifying the representation of data objects in a record, file, message, storage device or transmission channel.

1..*

Character encodingThe character encoding used in the data set.

0..*Mandatory if an encoding is used that is not based on UTF-8.

Spatial representation type


1..*

Data Quality – Logical consistency – Topological consistency

Correctness of the explicitly encoded topological characteristics of the data set as described by the scope.

0..*

Mandatory if the data set includes types from the Generic Network Model and does not assure centreline topology (connectivity of centrelines) for the network.

16 Please note that the implementation guidelines for the common metadata elements have been revised during the work on the Annex II+III data specifications. The current guidelines are available in the common data specification document template (available in the “Framework Documents” section on http://inspire.jrc.ec.europa.eu/index.cfm/pageid/2). At the time of writing (October 2013), the Annex I data specifications are being updated to be consistent with this document template and the updated guidelines.

184

1234

56789

10

1112131415161718

19

12345

6

http://inspire.jrc.ec.europa.eu/index.cfm/pageid/2

3.21B.2. Metadata elements recommended in the INSPIRE Data Specifications Technical Guidelines

The following metadata elements are recommended as common metadata elements for all Spatial Data Themes from Annexes I, II and III.

Metadata element Multiplicity

Data Quality – Logical Consistency – Conceptual Consistency 0..*

Data Quality – Logical Consistency – Domain Consistency 0..*

Maintenance information 0..1

The following tables give an overview of additional metadata elements that are recommended for specific Spatial Data Themes from Annex II and III.

THEMES FROM ANNEX II

Elev

atio

n

Geo

logy

Land

cov

er

Ort

hoim

ager

y


Data Quality – Completeness - Commission 0..* 0..*

Data Quality – Completeness - Ommission 0..* 0..* 0..*

Data Quality – Logical Consistency – Format Consistency 0..* 0..1

Data Quality – Positional accuracy – Absolute or external accuracy 0..* 0..*

Data Quality – Positional accuracy – Gridded data position accuracy 0..* (C) 0..*

Data Quality –Thematic accuracy – Classification Correctness 0..*

Data Quality – Positional accuracy – Relative or Internal Accuracy 0..*

Data Quality – Temporal quality – Temporal Consistency 0..*

Data Quality – Temporal quality – Temporal Validity 0..*

Data Quality – Temporal quality – Accuracy of a time measurement

Data Quality – Thematic accuracy – Non-quantitative Attribute Accuracy 0..*

Data Quality – Thematic accuracy – Quantitative Attribute Accuracy 0..*

Data Quality – DQ_UsabilityElement

Spatial representation information 0..*

Supplemental information 0..1

Process step 0..* 0..*

Data source 0..* 0..*

Browse graphic information 0..* 0..*

185

123456

789

10

1

Digital transfer options information 0..* 0..*

Image description 0..*

Content Information

186

1

1

THEMES FROM ANNEX III (table 1/2)

Agr

icul

tura

l and

aq

uacu

lture

faci

litie

s

Are

a m

anag

emen

t/re

stric

tion/

regu

latio

n zo

nes

and

repo

rtin

g un

its

Atm

osph

eric

C

ondi

tions

-M

eteo

rolo

gica

l ge

ogra

phic

al

Bio

-geo

grap

hica

l re

gion

s

Bui

ldin

gs

Ener

gy R

esou

rces

Envi

ronm

enta

l m

onito

ring

Faci

litie

s

Hab

itats

and

bi

otop

es

Hum

an h

ealth

and

sa

fety


Data Quality – Completeness - Commission 0..*

Data Quality – Completeness - Ommission 0..* 0..*

Data Quality – Logical Consistency – Format Consistency

Data Quality – Positional accuracy – Absolute or external accuracy 0..* 0..* 0..*

Data Quality – Positional accuracy – Gridded data position accuracy

Data Quality –Thematic accuracy – Classification Correctness 0..*

Data Quality – Positional accuracy – Relative or Internal Accuracy

Data Quality – Temporal quality – Temporal Consistency

Data Quality – Temporal quality – Temporal Validity 0..* 0..*

Data Quality – Temporal quality – Accuracy of a time measurement

Data Quality – Thematic accuracy – Non-quantitative Attribute Accuracy

Data Quality – Thematic accuracy – Quantitative Attribute Accuracy 0..*

Data Quality – DQ_UsabilityElement 0..*

Spatial representation information

Supplemental information

Process step

Data source

Browse graphic information

Digital transfer options information

Image description

Content Information 0..1

187

12

3456789

1011

1

THEMES FROM ANNEX III (table 2/2)

Land

use

Min

eral

Res

ourc

es

Nat

ural

risk

zon

es

Oce

anog

raph

ic

geog

raph

ical

feat

ures

Popu

latio

n di

strib

utio

n -

dem

ogra

phy

Prod

uctio

n an

d In

dust

rial

Faci

litie

s

Sea

Reg

ions

Soil

Spec

ies

dist

ribut

ion

Stat

istic

al u

nits

Util

ity a

nd

gove

rnm

enta

lse

rvic

es


Data Quality – Completeness - Commission 0..* --- 0..1 0..*

Data Quality – Completeness - Ommission 0..* 0..* --- 0..* 0..* 0..1 0..*

Data Quality – Logical Consistency – Format Consistency --- 0..*

Data Quality – Positional accuracy – Absolute or external accuracy 0..* 0..* --- 0..* 0..* 0..1 0..*

Data Quality – Positional accuracy – Gridded data position accuracy ---

Data Quality –Thematic accuracy – Classification Correctness 0..* --- 0..* 0..1 0..*

Data Quality – Positional accuracy – Relative or Internal Accuracy --- 0..*

Data Quality – Temporal quality – Temporal Consistency --- 0..*

Data Quality – Temporal quality – Temporal Validity --- 0..* 0..1

Data Quality – Temporal quality – Accuracy of a time measurement --- 0..*

Data Quality – Thematic accuracy – Non-quantitative Attribute Accuracy 0..* --- 0..*

Data Quality – Thematic accuracy – Quantitative Attribute Accuracy --- 0..*

Data Quality – DQ_UsabilityElement 0..* --- 0..*

Spatial representation information ---

Supplemental information ---

Process step ---

Data source ---

Browse graphic information ---

Digital transfer options information ---

Image description ---

Content Information ---

188

1

2345

1

INSPIRE - Europa · Web view2015/09/10 · 2015-09-10 Subject INSPIRE Implementing Rules for...

Documents

Transcript of INSPIRE - Europa · Web view2015/09/10 · 2015-09-10 Subject INSPIRE Implementing Rules for...