Infrastructure for Spatial Information in Europe · sharing, access and use; coordination and monitoring mechanisms, processes and procedures. The guiding principles of INSPIRE are:

INSPIRE

Infrastructure for Spatial Information in Europe

Technical Guidance for INSPIRE Spatial Data Services and services allowing spatial data services to be invoked

Title Technical Guidance for INSPIRE Spatial Data Services and services allowing spatial data services to be invoked

Creator Network Services Drafting Team, MIG-T

Date of last update 2015-11-15

Subject Technical Guidance for INSPIRE Spatial Data Services and services allowing spatial data services to be invoked

Status Version 3.2rc1 – for review and comments by MIG-T

Publisher MIG-T

Type Text

Description This document defines technical guidance for INSPIRE Spatial Data Services and services allowing spatial data services to be invoked

Format MS Word (doc)

Source Network Services Drafting Team, MIG-T

Rights Reuse is authorised, provided the source is acknowledged. The reuse policy of the European Commission is implemented by a Decision of 12 December 2011.

Identifier TG_for_INSPIRE_SDS_3.2rc1.docx

Language EN

Relation Not applicable

Coverage Project duration

http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32011D0833

http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32011D0833

INSPIRE Technical Guidance for spatial data services and services allowing spatial data services to be invoked

2015-11-15 Page 2 of 98

Table of contents

Foreword .................................................................................................................................................. 4

1 Introduction ....................................................................................................................................... 6

2 Normative references ....................................................................................................................... 8

3 Terms and abbreviations ................................................................................................................ 10 3.1 Terms ...................................................................................................................................... 10 3.2 Symbols and abbreviations ..................................................................................................... 11 3.3 Verbal forms for the expression of provisions ......................................................................... 11 3.4 References .............................................................................................................................. 12

4 Technical Guidance ........................................................................................................................ 14 4.1 Categories of INSPIRE Spatial Data Services ........................................................................ 14 4.2 Requirements according to INSPIRE regulations ................................................................... 15

4.2.1 Requirements for Spatial Data Services ...................................................................... 15 4.2.2 Requirements for services allowing spatial data services to be invoked ..................... 16 4.2.3 Guiding flow chart ........................................................................................................ 16 4.2.4 Deadlines ..................................................................................................................... 18

4.3 Overview and generic requirements ....................................................................................... 19 4.3.1 Generic requirements on xPath, multiplicity, data types and code lists ....................... 21 4.3.2 Generic requirements on data quality metadata .......................................................... 22 4.3.3 Metadata element required by ISO 19119 ................................................................... 22

4.4 Invocable Spatial Data Services ............................................................................................. 23 4.4.1 Category ....................................................................................................................... 23 4.4.2 Resource Locator ......................................................................................................... 25 4.4.3 Specification ................................................................................................................. 27

4.5 Interoperable Spatial Data Services ....................................................................................... 30 4.5.1 Coordinate Reference Systems Identifier .................................................................... 30 4.5.2 Quality of Service ......................................................................................................... 33 4.5.3 Conditions applying to access and use ....................................................................... 38 4.5.4 Responsible party ........................................................................................................ 42

4.6 Harmonised spatial data services ........................................................................................... 44 4.6.1 Invocation metadata ..................................................................................................... 44 4.6.2 Quality of the Harmonised Spatial Data Service .......................................................... 51

4.6.2.1 Normalized testing procedure ................................................................................. 51 4.6.3 Encoding of the spatial objects in the Spatial Data Service ........................................ 51 4.6.4 Operations for Harmonised Spatial Data Services ...................................................... 52

4.6.4.1 Get Harmonised Spatial Data Service Metadata Description ................................. 52 4.6.4.2 Scenario 1 – Get Capabilities response – Metadata replication ............................. 53 4.6.4.3 Scenario 2 – Get Capabilities response – Metadata URL ...................................... 53

4.7 Services allowing spatial data services to be invoked ............................................................ 54 4.8 INSPIRE Metadata Codelists .................................................................................................. 54

4.8.1 Responsible party role ................................................................................................. 54 4.8.2 Resource locator function ............................................................................................ 55 4.8.3 Limitations on public access ........................................................................................ 55 4.8.4 Conditions applying to access and use ....................................................................... 56 4.8.5 Spatial data services categories .................................................................................. 56 4.8.6 Criteria .......................................................................................................................... 57 4.8.7 DCP List ....................................................................................................................... 57


2015-11-15 Page 3 of 98

Annex A – WSDL Example .................................................................................................................... 58

Annex B – Get Harmonized Spatial Data Service Metadata ................................................................. 65 B.1 Get Harmonized Spatial Data Service Metadata Request .......................................................... 65 B.2 Scenario 1 – Get Harmonized Spatial Data Service Metadata Response .................................. 66 B.3 Scenario 2 – Get Harmonized Spatial Data Service Metadata Response .................................. 69

Annex C – Metadata textual example.................................................................................................... 71

Annex D – Complete XML Encoding example ...................................................................................... 76

Table of Tables

Table 1 - Metadata elements mapping. C: conditional (refer to [INS MD] for the conditions), M: Mandatory, =: the obligation is the same as specified in [INS MD] .................................. 19

Table 2 - Recommended http URIs for the default coordinate reference systems ............................... 31 Table 3 - SV_OperationMetadata detail ................................................................................................ 46 Table 4 - SV_Parameter detail .............................................................................................................. 47 Table 5 - Get Harmonized Spatial Data Service Metadata request ...................................................... 65

Table of Figures

Figure 1 - relationship between the INSPIRE Implementing Rules and the associated Technical Guidance. ............................................................................................................................ 5

Figure 2 - Spatial data services in the context of INSPIRE and their relationships to different types and categories of services. Services that are not invocable are not within the scope of INSPIRE. ........................................................................................................................... 14

Figure 3 - Metadata required for SDS ................................................................................................... 15 Figure 4 - Flow chart illustrating the obligations for spatial data services ............................................. 17


2015-11-15 Page 4 of 98

Foreword

Directive 2007/2/EC of the European Parliament and of the Council [INS DIR], adopted on 14 March 2007 aims at establishing an Infrastructure for Spatial Information in the European Community (INSPIRE) for environmental policies, or policies and activities that have an impact on the environment. INSPIRE will make available relevant, harmonised and quality geographic information to support the formulation, implementation, monitoring and evaluation of policies and activities, which have a direct or indirect impact on the environment.

INSPIRE is based on the infrastructures for spatial information established and operated by the 27 Member States of the European Union. The Directive addresses 34 spatial data themes needed for environmental applications, with key components specified through technical implementing rules. This makes INSPIRE a unique example of a legislative “regional” approach.

To ensure that the spatial data infrastructures of the Member States are compatible and usable in a Community and trans-boundary context, the Directive requires that common Implementing Rules (IR) are adopted in the following areas.

Metadata;

The interoperability and harmonisation of spatial data and services for selected themes (as described in Annexes I, II, III of the Directive);

Network Services;

Measures on sharing spatial data and services;

Co-ordination and monitoring measures.

The Implementing Rules are adopted as Commission Decisions or Regulations, and are binding in their entirety.

In particular with respect the Network Services, Implementing Rules are required for the following services (Article 11(1) of the Directive):

a) “discovery services search for spatial datasets and spatial data services on the basis of the content of corresponding metadata, and display the metadata content;

b) view services as a minimum, display, navigate, zoom in/out, pan, or overlay spatial datasets and display legend information and any relevant content of metadata;

c) download services enabling copies of complete spatial datasets, or of parts of such sets, to be downloaded;

d) transformation services enabling spatial datasets to be transformed with a view to achieving interoperability;

e) invoke spatial data services "enabling data services to be invoked.”

In addition to the Implementing Rules, non-binding Technical Guidance documents describe detailed implementation aspects and relations with existing standards, technologies, and practices. They may need to be revised during the course of implementing the infrastructure to take into account the evolution of technology, new requirements, and cost benefit considerations. Figure 1 illustrates the relationship between the INSPIRE Regulations containing Implementing Rules and their corresponding Technical Guidance documents.


2015-11-15 Page 5 of 98

Figure 1 - relationship between the INSPIRE Implementing Rules and the associated Technical Guidance.

Technical Guidance documents define how Member States might implement the Implementing Rules described in a Commission Regulation. Technical Guidance documents may include non-binding technical requirements that must be satisfied if a Member State chooses to conform to the Technical Guidance. Implementing this technical guidance will maximise the interoperability of INSPIRE services.

This Technical Guidance relates to the INSPIRE Spatial Data Services and services allowing spatial data services to be invoked. The Technical Guidance contains detailed technical documentation highlighting the mandatory and the recommended elements related to the implementation of INSPIRE Spatial Data Services and services allowing spatial data services to be invoked. The technical provisions and the underlying concepts are often illustrated by use case diagrams and accompanied by examples.

Many of the examples in this document refer to a real service; the description of the spatial data service used in the document is provided in Annex G.

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

Legal Notice

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


2015-11-15 Page 6 of 98

1 Introduction

Directive 2007/2/EC of the European Parliament and of the Council of 14 March 2007 establishing an Infrastructure for Spatial Information in the European Community (INSPIRE) was published in the official Journal on the 25th April 2007. The INSPIRE Directive entered into force on the 15th May 2007.

The purpose of the infrastructure is to enable the formulation, implementation, monitoring activities and evaluation of Community environmental policies at all levels – European, national and local – and to provide public information.

INSPIRE builds on the infrastructures for spatial information that have already been created by the Member States. The components of those infrastructures include: metadata, spatial data themes (as described in Annexes I, II, III of the Directive), network services and technologies; agreements on data sharing, access and use; coordination and monitoring mechanisms, processes and procedures.

The guiding principles of INSPIRE are:

that the infrastructures for spatial information in the Member States should be designed to ensure that spatial data are stored, made available and maintained at the most appropriate level;

that it is possible to combine spatial data from different sources across the Community in a consistent way and share them between several users and applications;

that it is possible for spatial data collected at one level of public authority to be shared between all the different levels of public authorities;

that spatial data are made available under conditions that do not restrict their extensive use; and,

that it is easy to discover available spatial data, to evaluate their fitness for purpose and to know the conditions applicable to their use.

The text of the INSPIRE Directive is available from the European Union Law website (EU-LEX) http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=CELEX:32007L0002:EN:NOT . The Directive identifies what needs to be achieved, and Member States have two years from the date of adoption to bring into force national legislation, regulations, and administrative procedures that define how the agreed objectives will be met taking into account the specific situation of each Member State. To ensure that the spatial data infrastructures of the Member States are compatible and usable in a Community and trans-boundary context, the Directive requires that common Implementing Rules (IR) are adopted in a number of specific areas. Implementing Rules are adopted as Commission Decisions, and are binding in their entirety.

According to Article 5(4) of the Directive, the INSPIRE Implementing Rules shall take account of relevant, existing international standards and user requirements.

The scope of this document is to detail the INSPIRE technical requirements for Spatial Data Services and services allowing spatial data services to be invoked from the Implementing Rules, such that these services can be implemented consistently across Europe. These Implementing Rules are, as much as possible, in conformance with European and international standards, current practices in stakeholder communities and relevant European initiatives such as e-Government, and the EU interoperability framework.

NOTE It is planned to integrate the metadata-related aspects of this document into the updated version of the INSPIRE Technical Guidelines for metadata, that is currently (November 2015) under preparation by the MIG sub-group MIWP-8.

http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=CELEX:32007L0002:EN:NOT


2015-11-15 Page 7 of 98

This technical guidance document relates to developed services relating to harmonised spatial data sets and will not apply to the already specified INSPIRE Network Service.


2015-11-15 Page 8 of 98

2 Normative references

The 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.

INS DIR Directive 2007/2/EC of the European Parliament and of the Council of 14 March 2007 establishing an Infrastructure for Spatial Information in the European Community (INSPIRE), OJ L 108, 24.4.2007, p. 1

INS MD 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 (Text with EEA relevance), OJ L 326, 4.12.2008, p. 12

INS ISDSS 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 as amended by Commission Regulation (EU) No 1312/2014 of 10 December 2014, OJ L 354, 11.12.2014, p. 8–16

INS NS Commission Regulation (EU) 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 as amended by Commission Regulation (EU) No 1311/2014 of 10 December 2014, OJ L 354, 11.12.2014, p. 6–7

INS NS TG Technical Guidance for the implementation of INSPIRE Download Services, v3.1

(http://inspire.jrc.ec.europa.eu/documents/Network_Services/Technical_Guidance_Download_Services_v3.1.pdf)

INS MD TG INSPIRE Metadata Implementing Rules: Technical Guidelines based on EN ISO

19115 and EN ISO 19119, v1.3 (http://inspire.ec.europa.eu/documents/Metadata/MD_IR_and_ISO_20131029.pdf)

DC DS Common document collection provided for all INSPIRE Data Specifications

http://inspire.jrc.ec.europa.eu/index.cfm/pageid/2 OGC WS OGC Web Services Common Standard http://portal.opengeospatial.org/files/?artifact_id=38867 ISO 19115 ISO 19115:2003/Cor 1:2006, Geographic information – Metadata – Part 1:

Fundamentals http://www.iso.org/iso/catalogue_detail.htm?csnumber=26020 ISO 19119 ISO 19119:2005/Amd 1:2008, Geographic information – Services http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=4426

8 ISO 19139 ISO/TS 19139:2007, Geographic information – Metadata – XML schema

implementation http://www.iso.org/iso/catalogue_detail.htm?csnumber=32557 ISO 19108 ISO 19108:2002/Cor 1:2006, Geographic information - Temporal schema http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=4488

3 ISO 19111 ISO 19111:2007, Geographic information - Spatial referencing by coordinates http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=4112

6

http://inspire.jrc.ec.europa.eu/documents/Network_Services/Technical_Guidance_Download_Services_v3.1.pdf

http://inspire.jrc.ec.europa.eu/documents/Network_Services/Technical_Guidance_Download_Services_v3.1.pdf

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

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

http://www.iso.org/iso/catalogue_detail.htm?csnumber=26020

http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=44268


http://www.iso.org/iso/catalogue_detail.htm?csnumber=32557






2015-11-15 Page 9 of 98

ISO 19118 ISO 19118:2011Geographic information – Encoding http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=44

212 ISO 19127 ISO/TS 19127:2005, Geographic information - Geodetic codes and parameters http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=4178

4

http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=44212

http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=44212




2015-11-15 Page 10 of 98

3 Terms and abbreviations

3.1 Terms

(1) Access point: an internet address containing a detailed description of a spatial data service, including a list of endpoints to allow its execution.

(2) End point: the Internet address used to directly call an operation provided by a spatial data

service. (3) Spatial data services means the operations which may be performed, by invoking a computer

application, on the spatial data contained in spatial data sets or on the related metadata [INS DIR, Art. 3].

(4) Network services are services provided for in Article 11(1) of [INS DIR] for the discovery, viewing, download and transformation of spatial data sets and services. The service shall be conformant regarding the specific requirements in Commission Regulation (EC) 976/2009.

NOTE In [INS DIR, Art. 11] also a 5th type of network service is defined: “services allowing spatial data services to be invoked”. Since all services can be invoked when metadata is published and accessed through a discovery service, there is no need to have a special service to invoke other services. Instead the discovery service will take the role as making it possible to invoke a service. (see also section 4.2.2).

(5) Discovery service is a service that makes it possible to search for spatial data sets and services on the basis of the content of the corresponding metadata and to display the content of the metadata [INS DIR, Art. 11].

(6) View service is a service making it possible, as a minimum, to display, navigate, zoom in/out, pan, or overlay viewable spatial data sets and to display legend information and any relevant content of metadata [INS DIR, Art. 11].

(7) Download service is a service enabling copies of spatial data sets, or parts of such sets, to be downloaded and, where practicable, accessed directly [INS DIR, Art. 11].

(8) Transformation service is a service enabling spatial data sets to be transformed with a view to achieving interoperability [INS DIR, Art. 11].

(9) Invocable spatial data service is a spatial data service that (a) has metadata which fulfils the requirements of Commission Regulation (EC) 1205/2008, (b) has at least one resource locator that is an access point, (c) is conformant with a documented and publicly available set of technical specifications providing the information necessary for its execution. [INS ISDSS, Art. 1]

NOTE The technical specifications could e.g. be a web site documentation explaining how to use the service, or they could be more formal, e.g. a WSDL document or a description of a RESTful interface.

(10) Interoperable spatial data service means an invocable spatial data service which fulfils the requirements of Annex VI. [INS ISDSS, Art. 1]

(11) Harmonised spatial data service means an interoperable spatial data service which fulfils the requirements of Annex VII. [INS ISDSS, Art. 1]

(12) Conformant spatial data set means a spatial data set in conformity with Commission Regulation (EU) No 1089/2010. [INS ISDSS, Art. 1]


2015-11-15 Page 11 of 98

(13) Interface: named set of operations that characterise the behaviour of an entity as defined by ISO 19119:2005. [INS ISDSS, Art. 1]

(14) Operation: means an action supported by a spatial data service. [INS ISDSS, Art. 1]

3.2 Symbols and abbreviations

DT Drafting Team

MD Metadata

NS Network Services

ISO International Organization for Standardization1

OGC Open Geospatial Consortium2

QoS Quality of Service

SDS Spatial Data Services

ISDSS Interoperability of spatial data services

SOAP Simple Object Access Protocol3

MS Member state

URL Uniform Resource Locator

WSDL Web Services Description Language4

XSD XML Schema Definition

3.3 Verbal forms for the expression of provisions

In 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

1 http://www.iso.org/iso/home.htm

2 http://www.opengeospatial.org/ogc

3 http://www.w3.org/TR/soap12

4 http://www.w3.org/TR/wsdl

http://www.iso.org/iso/home.htm

http://www.opengeospatial.org/ogc









http://www.w3.org/TR/soap12

http://www.w3.org/TR/wsdl


2015-11-15 Page 12 of 98

Technical Guidance Conformance Classes notation

The Technical Guidance in this document is divided into Conformance Classes, so that it is possible to declare conformance to specific parts of the Technical Guidance. To conform to a Conformance Class it is necessary to meet all of the Requirements (see next section) in that Conformance Class.

Conformance Classes are identified in the document as follows:

TG Conformance Class #: [TITLE] conformance classes are shown using this style

Technical Guidance Requirements and Recommendations notation

Requirements and the recommendations for INSPIRE Spatial Data Services and services allowing spatial data services to be invoked within this technical guidance are highlighted and numbered as shown below:

TG Requirement # requirements are shown using this style

TG Recommendation # recommendations are shown using this style.

Requirements and recommendations belong to the conformance class in which they are found in this document.

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 Guidance are not legally binding. Therefore, within this technical guidance 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 notation

XML 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.

3.4 References

References within this document are denoted using “Section” or “Annex”. For example, Section 5.3.1 or Annex A.

References to other documents refer to the list of normative references in Section 1.1 and use the abbreviated title as indicated in Bold text. For example, [INS NS] uses the abbreviated title for the document as shown below:


2015-11-15 Page 13 of 98

Commission Regulation (EU) 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. OJ L 274, 20.10.2009, p. 9

References within other documents are shown as above using the reference code, together with the appropriate section within the document. For example, [INS NS, Section 2.2.3], refers to Section 2.2.3 within the document as listed above.


2015-11-15 Page 14 of 98

4 Technical Guidance

This section includes guidance related to categories of SDS (section 4.1), requirements from the different INSPIRE Implementing Rules and the Directive (section 4.2) and instructions on meeting the requirements for SDS included in [INS ISDSS] (sections 0 to 4.6) and for services allowing SDS to be invoked (section 4.7).

The technical guidance for the requirements included in [INS ISDSS] are structured according to conformance classes. The conformance classes for invocable SDS (section 0) and interoperable SDS (section 4.5) include only requirements on the creation of additional metadata. The conformance class for harmonised SDS includes requirements related to metadata, quality of service, output encoding and the Get Harmonised Spatial Data Service Metadata Operation

4.1 Categories of INSPIRE Spatial Data Services

Spatial data service (SDS) is a general term within INSPIRE for all services used for exchanging, sharing, access and use of spatial data or metadata. Based on the INSPIRE Directive and IRs, SDSs can be divided into two major groups, each of which is governed by separate Implementing Rules: SDS regulated by [INS NS] and SDS regulated by [INS ISDSS].

All SDSs within INSPIRE (i.e. SDS regulated by [INS NS] and SDS regulated by [INS ISDSS] and other SDSs) shall be discoverable, i.e. they shall be described in metadata, and they shall meet the requirements for data and service sharing laid down in Art. 17 of the Directive.

SDS regulated by [INS ISDSS] are then divided into three different categories depending on level of interoperability; Invocable spatial data service, Interoperable spatial data service and Harmonised spatial data service. SDS regulated by IR Network services consist of four different types of services; discovery services, view services, download services and transformation services.

A spatial data service within the scope of INSPIRE should correspond to at least one theme described in the Annexes I-III of the INSPIRE Directive. In addition, it could also include other data.

Figure 2 gives an overview of the different types of spatial data services.

Figure 2 - Spatial data services in the context of INSPIRE and their relationships to different types and categories of services. Services that are not invocable are not within the scope of INSPIRE.


2015-11-15 Page 15 of 98

4.2 Requirements according to INSPIRE regulations

4.2.1 Requirements for Spatial Data Services

For the spatial data sets and services for which metadata have been created, member states shall establish and operate at least one (but may decide to establish and operate more than one) of each type of network service defined in [INS DIR, Art. 11] for discovery, view, download and transformation.

Transformation services are not mandatory to implement as long as “spatial data sets are made available in conformity with the implementing rules [for data interoperability] through the adaptation of existing spatial data sets” [INS DIR, Art. 7(3)], i.e. if they are transformed into the INSPIRE data models through some other means (e.g. offline transformation or on-the-fly transformation in the download service).

These services shall follow the requirements of [INS NS].

All spatial data services, including network services, shall have metadata according to [INS MD] and [INS NS, Art. 2(7)]. Furthermore, Member States need to adopt measures for data sharing for all spatial data services according to [INS DIR, Art. 17].

If other spatial data services also have a technical specification providing information necessary for its execution (e.g. an API description), they shall also have additional metadata as described in Annex V and VI and, where practicable, meet the requirements related to metadata, quality of service, output encoding and the Get Harmonised Spatial Data Service Metadata Operation that are described in Annex VII of [INS ISDSS].

NOTE 1 These additional requirements do not have to be met by network services, as clarified by [INS ISDSS] ("This Regulation does not apply to the network services falling within the scope of Commission Regulation (EC) 976/2009").

The requirements related to metadata are illustrated in Figure 3.

Figure 3 - Metadata required for SDS


2015-11-15 Page 16 of 98

4.2.2 Requirements for services allowing spatial data services to be invoked

No specific Implementing Rules exist in INSPIRE that specify requirements for “services allowing spatial data services to be invoked” as defined in [INS DIR, Art. 11(1.e)].

However, in the latest amendment of [INS NS] (Commission Regulation (EU) No 1311/2014 of 10 December 2014), the definition of “INSPIRE metadata element” is extended beyond the metadata elements defined in [INS MD] to include also the metadata elements defined in Annexes V-VII of [INS ISDSS].

This means that discovery network services need to provide access also to the additional SDS metadata elements, which contain, among other things, information necessary for the invocation of SDS. Through the provision of these additional elements, the obligation to provide (network) “services allowing spatial data services to be invoked” is being fulfilled.

4.2.3 Guiding flow chart

In the INSPIRE scope it is required to set up Network services to be able to discovery, view, download and if necessary to transformation data that is described in the INSPIRE directive annex I-III. Specific regulations are published for setting up these services. But since other spatial data services can be of broad variation there is no detailed description. To support the understanding of SDS and its requirements the flow chart in Figure 4 can be used.

At the starting point there is an existing service already, it could be a service that was not initially intended as an INSPIRE service when it was set up.


2015-11-15 Page 17 of 98

Figure 4 - Flow chart illustrating the obligations for spatial data services


2015-11-15 Page 18 of 98

4.2.4 Deadlines

As for harmonisation of data sets, the fulfilments of the requirements for invocable spatial data services are done step-wise.

15-May-2009

Member States shall adopt measures for the sharing of spatial data sets and service, in accordance with [INS DIR, Art. 17].

03-Dec-2010

Metadata according to [INS MD] shall be available for spatial data services corresponding to Annex I and II themes

09-Nov-2011

Metadata for SDS shall be provided through INSPIRE discovery services, in accordance with [INS NS]

03-Dec-2013

Metadata according to [INS MD] shall be available for spatial data services corresponding to Annex III themes

10-Dec-2015

All invocable spatial data services shall be conformant to Annex V of [INS ISDSS]

10-Dec-2016

Invocable spatial data services related to newly collected and extensively restructured spatial data sets shall be conformant with Annex VI and, where practicable, Annex VII of [INS ISDSS]

10-Dec-2021

All invocable spatial data services shall be conformant with Annexes VI and (where practicable) VII of [INS ISDSS]

NOTE Also the additional metadata that has to be provided for SDS under [INS ISDSS] shall be provided through INSPIRE discovery services, in accordance with [INS NS]


2015-11-15 Page 19 of 98

4.3 Overview and generic requirements

Table 1 shows the requirements to provide different metadata elements for the different spatial data services conformance classes.

For each metadata element that is not already included in [INS MD] or for which there are additional requirements, the table contains a reference to the section describing the detailed requirements.

Table 1 - Metadata elements mapping. C: conditional (refer to [INS MD] for the conditions), M: Mandatory, =: the obligation is the same as specified in [INS MD]

Inspire Metadata element Reference to INSPIRE IRs

All SDS Invocable

SDS Interoperable

SDS Harmonised

SDS

Resource title [INS MD,

Annex B1.1] M = = =

Resource abstract [INS MD,

Annex B1.2] M = = =

Resource Type [INS MD,

Annex B1.3] M = = =

Resource Locator

[INS MD,

Annex B1.4]

[INS ISDSS,

Annex V D1]

C M (4.4.2) M (4.4.2) M (4.4.2)

Coupled Resource [INS MD,

Annex B1.6] C = = =

Spatial data service type [INS MD,

Annex B2.2] M = = =

Keyword value [INS MD,

Annex B3.1] M = = =

Geographic Bounding Box [INS MD,

Annex B4.1] C = = =

Temporal extent [INS MD,

Annex B5.1] C = = =

Date of publication [INS MD,

Annex B5.2] C = = =

Date of last revision [INS MD,

Annex B5.3] C = = =

Date of creation [INS MD,

Annex B5.4] C = = =

Spatial Resolution [INS MD,

Annex B6.2] C = = =

Specification

[INS MD,

Annex B7.1]

[INS ISDSS,

Annex V D2]

M M (4.4.3) M (4.4.3) M (4.4.3)

Degree

[INS MD,

Annex B7.2]

[INS ISDSS,

M M (4.4.3) M (4.4.3) M (4.4.3)


2015-11-15 Page 20 of 98

Inspire Metadata element Reference to INSPIRE IRs

All SDS Invocable

SDS Interoperable

SDS Harmonised

SDS

Annex V D2]

Conditions applying to access and use

[INS MD,

Annex B8.1]

[INS ISDSS,

Annex VI A1]

M = M(4.5.3) M(4.5.3)

Limitations on public access [INS MD,

Annex B8.2] M = = =

Responsible party

[INS MD,

Annex B9.1]

[INS ISDSS,

Annex VI A2]

M = M (4.5.4) M (4.5.4)

Responsible party role

[INS MD,

Annex B9.2]

[INS ISDSS,

Annex VI A2

M = M (4.5.4) M (4.5.4)

Metadata point of contact [INS MD,

Annex B10.1] M = = =

Metadata Date [INS MD,

Annex B10.2] M = = =

Metadata Language [INS MD,

Annex B10.3] M = = =

Category [INS ISDSS,

Annex V B1] M (4.4.1) M (4.4.1) M (4.4.1)

Coordinate Reference System [INS ISDSS,

Annex VI B3] M (4.5.1) M (4.5.1)

Quality of Service - Criteria [INS ISDSS,

Annex VI B4.1] M (4.5.2) M (4.5.2)

Quality of Service - Measurement

[INS ISDSS,

Annex VI B4.2] M (4.5.2) M (4.5.2)

Invocation metadata [INS ISDSS,

Annex VII B3] M (4.6.1)

As explained above, all SDS shall have metadata which fulfils the requirements of [INS MD TG]. The availability of such [INS MD TG]-compliant metadata is assumed, but since the corresponding requirements, mapping rules and metadata elements are already detailed in [INS MD TG], they are not repeated in this TG.

In the following paragraphs you can find the details of the new or extended metadata elements, including a specific encoding example. For details on the other elements, please refer to [INS MD TG].

The requirements are structured in three conformance classes, according to the three categories of SDS.

The following generic requirements hold for all metadata elements described in this document. In addition to these generic requirements, some conformance classes contain additional requirements.


2015-11-15 Page 21 of 98

4.3.1 Generic requirements on xPath, multiplicity, data types and code lists

TG Requirement 1 Each metadata element shall be present in the metadata document at the XPath defined in the table for that element and shall match the INSPIRE multiplicity of the metadata element, unless the element is conditional and

the condition does not hold.

TG Requirement 2 Each metadata element shall use the data type or code list specified in the table for that element.

Section 4.8 includes the value domains (code lists) to be used for the INSPIRE metadata elements described in this technical guidance. For every code list, each value is defined by:

a numerical identifier (No. ID), if any, corresponding, in most cases, to the numerical identifier defined in [INS MD] or to ISO domain code;

a textual name;

a language neutral name, if any;

an optional definition/description;

an URI identifier

TG Requirement 3 Where these technical guidance requires a textual metadata element to be filled with a value from one of these code lists, either the language-neutral name or a combination of the language-neutral name and a xlink:href reference to the URI identifier from the INSPIRE registry (using gmx:Anchor)

shall be used.

EXAMPLE 1 Implementation using only the language-neutral name

<gmd:title>

<gco:CharacterString>invocable</gco:CharacterString>

</gmd:title>

EXAMPLE 2 Implementation using a combination of the language-neutral name and a reference to the http URI identifier from the INSPIRE registry

<gmd:title>

<gmx:Anchor xlink:href=" http://inspire.ec.europa.eu/metadata-codelist/Category/invocable">invocable</gmx:Anchor>

</gmd:title>


2015-11-15 Page 22 of 98

Open issue: Is there the need to also include requirements and examples for the encoding of code lists coming from [ISO 19115] and [ISO 19119]? E.g. the following example from [ISO 19139], adapted for the new (official?) location of the ISO 19139 code list catalogue (http://standards.iso.org/iso/19139/resources/codelist/) EXAMPLE 5 Here is a full instance of CI_DateTypeCode expressed in the default language of the metadata (e.g. English): <CI_DateTypeCode

codeList="http://standards.iso.org/iso/19139/resources/codelist/gmxCodelist

s.xml#CI_DateTypeCode" codeListValue="creation">Creation</CI_DateTypeCode>

What to do with code lists from [ISO 19119] that are not included in the ISO 19139 code list catalogue, e.g. DCPlist? An alternative solution could be to add the ISO code lists to the INSPIRE registry and use the http URIs instead, e.g. <CI_DateTypeCode codeList="http://inspire.ec.europa.eu/metadata-

codelist/DateType" codeListValue="http://inspire.ec.europa.eu/metadata-

codelist/DateType/creation">Creation</CI_DateTypeCode>

4.3.2 Generic requirements on data quality metadata

The dataQualityInfo element is used for the implementation of several INSPIRE metadata elements. A single ISO 19115/19119 metadata set may comprise more than one dataQualityInfo element.

TG Requirement 4 For each spatial data service, there shall be one and only one set of quality information (dataQualityInfo element) scoped to “service”.

4.3.3 Metadata element required by ISO 19119

In addition to the metadata elements required by INSPIRE, the containsOperation metadata element is required to be compliant with [ISO 19119]. According to [INS MD TG], this element is not required for all SDS; it becomes conditional only at for harmonised SDS to provide invocation metadata (as indicated in the table above and further specified section 4.6.1). For all the other conformance classes (invocable and interoperable spatial data services) this element is optional. If there is no data to fill it, it should be filled with the gco:nilReason element; you can find an encoding example below (taken from [INS MD TG, Section A.12.3.2]):

<srv:containsOperations gco:nilReason="missing"/>

http://standards.iso.org/iso/19139/resources/codelist/


2015-11-15 Page 23 of 98

4.4 Invocable Spatial Data Services

TG Conformance Class 1: Implementation of Invocable Spatial Data Services

This conformance class is inclusive of:

TG Requirement 1 to TG Requirement 8

TG Recommendation 1 to TG Recommendation 3

TG Requirement 5 If a spatial data service (a) has metadata which fulfils the requirements of [INS MD], (b) has at least one resource locator that is an access point, and (c) is conformant with a documented and publicly available set of technical specifications providing the information necessary for its execution, the metadata document for the spatial data service shall include the metadata elements and meet the additional requirements for metadata elements

specified in this section.

4.4.1 Category

[INS ISDSS] requires a Category metadata element containing a citation of the status of the spatial data service versus invocability.

The Category metadata element is implemented using the specification and pass sub-element of the DQ_ConformanceResult from [ISO 19115].

TG Recommendation 1 In order to be machine-readable, the specification metadata element should be provided using the gmx:Anchor element.

TG Requirement 6 The value of the pass element shall be set to true.

Metadata element name Category

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

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

INSPIRE obligation / condition Mandatory for invocable spatial data services

INSPIRE multiplicity [1]

NOTE 1 The multiplicity is specified as [0..1] in [INS ISDSS], with the condition: “mandatory for an invocable spatial data service”. Since the metadata element is only required for invocable SDS, the multiplicity is factually [1].

NOTE 2 Since the multiplicity is [1], only the most comprehensive


2015-11-15 Page 24 of 98

category should be documented, e.g. interoperable (implying that also the invocable conformance class is met).

NOTE 3 The INSPIRE multiplicity refers to the Category metadata element. This does not affect the fact that in ISO 19115 more than one conformity statement is allowed.

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

Domain For the title sub-element, the values of the Category code list (section 4.8.5) shall be used. NOTE [ISO 19115] requires a date for the specification. For consistency, it is recommended to use the date of publication of the [INS ISDSS], i.e. 2014-12-11.

Example CI_Citation

title: invocable (http://inspire.ec.europa.eu/metadata-codelist/Category/invocable)

CI_Date

o date: 2014-12-11

o type: publication

Comments

Example of XML encoding:

<gmd:dataQualityInfo>

<gmd:DQ_DataQuality>

<gmd:scope>

<gmd:DQ_Scope>

<gmd:level>

<gmd:MD_ScopeCode

codeList="http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#

MD_ScopeCode" codeListValue="service"/>

</gmd:level>

</gmd:DQ_Scope>

</gmd:scope>

...

<gmd:report>

<gmd:DQ_DomainConsistency>

<gmd:result>

<gmd:DQ_ConformanceResult>

<gmd:specification>

<gmd:CI_Citation>

<gmd:title>

<gmx:Anchor xlink:href="

http://inspire.ec.europa.eu/metadata-

codelist/Category/invocable">invocable</gmx:Anchor>

</gmd:title>

<gmd:date>

<gmd:CI_Date>

<gmd:date>

<gco:Date>2014-12-11</gco:Date>

</gmd:date>

<gmd:dateType>

<gmd:CI_DateTypeCode

codeList="http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml

#CI_DateTypeCode" codeListValue="publication"/>

http://inspire.ec.europa.eu/metadata-codelist/Category/invocable



2015-11-15 Page 25 of 98

</gmd:dateType>

</gmd:CI_Date>

</gmd:date>

</gmd:CI_Citation>

</gmd:specification>

<gmd:explanation>

<gco:CharacterString>Conformant to the conformance class

"invocable SDS"</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>

4.4.2 Resource Locator

[INS MD] requires a resource locator to be provided “if linkage to the service is available”. [INS ISDSS] requires that the resource locator metadata element also contains all access points from the spatial data service provider, and these access points shall be unambiguously identified as such. This information, that a resource locator represents an access point, is provided through the description element.

TG Requirement 7 There shall be at least one Resource Locator metadata element that contains a locator that is identified as an access point, by providing the value “accessPoint” in the description element of the CI_OnlineResource containing the resource locator.

TG Recommendation 2 In order to be machine readable, the description metadata element shall be provided using the gmx:Anchor element.

Metadata element name Resource locator

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

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 multiplicity [1..*]

Data type (and ISO 19115 no.) URL


2015-11-15 Page 26 of 98

Domain URL (IETF RFC1738 and IETF RFC 2056)

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

Comments

Metadata element name Function


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 Reosurce locator function code list (4.8.2)

Example accessPoint (http://inspire.ec.europa.eu/metadata-codelist/ResourceLocatorFunction/accessPoint)

Comments


<gmd:MD_Metadata …

…

<gmd:distributionInfo>

<gmd:MD_Distribution>

…

<gmd:transferOptions>

<gmd:MD_DigitalTransferOptions>

<gmd:onLine>

<gmd:CI_OnlineResource>

<gmd:linkage>

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

1/Geo3DModelService?wsdl</gmd:URL>

</gmd:linkage>

<gmd:description>

<gmx:Anchor

xlink:href="http://inspire.ec.europa.eu/registry/metadata-

codelist/ResourceLocatorFunction/accessPoint">accessPoint</gmx:Anchor>

</gmd:description>

<gmd:function>

<gmd:CI_OnLineFunctionCode


#CI_OnLineFunctionCode"

codeListValue="information"></gmd:CI_OnLineFunctionCode>

</gmd:function>

</gmd:CI_OnlineResource>

</gmd:onLine>

</gmd:MD_DigitalTransferOptions>

</gmd:transferOptions>

http://inspire.ec.europa.eu/metadata-codelist/ResourceLocatorFunction/accessPoint



2015-11-15 Page 27 of 98

</gmd:MD_Distribution>

</gmd:distributionInfo>

…

</gmd:MD_Metadata>

4.4.3 Specification

[INS ISDSS] requires that the Specification metadata element 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. If the Specification metadata element does not refer to or contain at least one technical specification to which the invocable spatial data service fully conforms, providing all the necessary technical elements, the service is not an invocable spatial data service.

TG Requirement 8 The Specification metadata element shall at least refer to or contain one technical specification to which the invocable spatial data service fully conforms, providing all the necessary technical elements, to actually invoke

the service and enable its usage.

TG Recommendation 3 In order to be machine readable, the specification title metadata element shall be provided using the gmx:Anchor element.

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 revision

date: an effective date

Example title: EN ISO 19128:2005(E) : Geographic information — Web map server interface

date: o dateType: publication


2015-11-15 Page 28 of 98

o date: 2005-12-01

Comments

The metadata element degree contains the degree of conformity of the resource to the 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.) Boolean5

Domain true if conformant

Example true

Comments

The specification metadata element needs to provide sufficient information to actually invoke the service and enable its usage.

This might include:

- A description of the service interface;

- A WSDL description;

Example of XML encoding of technical specification (conformity references):

<gmd:MD_Metadata…

…



…

<gmd:specification>

<gmd:CI_Citation>

<gmd:title>

<gmx:Anchor xlink:href="

http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnu

mber=32546"> EN ISO 19128:2005(E) : Geographic information — Web map server

interface

</gmx:Anchor>


2015-11-15 Page 29 of 98

</gmd:title>

<gmd:date>

<gmd:CI_Date>

<gmd:date>


</gmd:date>

<gmd:dateType>



#CI_DateTypeCode" codeListValue="publication"/>

</gmd:dateType>

</gmd:CI_Date>

</gmd:date>

</gmd:CI_Citation>


http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml

<gmd:explanation>

<gco:CharacterString>See the referenced

specification</gco:CharacterString>

</gmd:explanation>

<gmd:pass>


</gmd:pass>


…



…

<gmd:MD_Metadata>

Example of XML encoding of technical specification (WSDL):

<gmd:specification>

<gmd:CI_Citation>

<gmd:title>

<gmx:Anchor

xlink:href="http://www.dinoservices.nl:80/geo3dmodelwebservices-

1/Geo3DModelService?wsdl">Webservice for making virtual boreholes in the

Digital Subsurface Models of the Netherlands</gmx:Anchor>

</gmd:title>

<gmd:date>

<gmd:CI_Date>

<gmd:date>


</gmd:date>

<gmd:dateType>

<gmd:CI_DateTypeCode codeList

http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#CI_DateTyp

eCode" codeListValue="publication">publication</gmd:CI_DateTypeCode>

</gmd:dateType>

</gmd:CI_Date>

</gmd:date>

</gmd:CI_Citation>



2015-11-15 Page 30 of 98

4.5 Interoperable Spatial Data Services

TG Conformance Class 2: Implementation of interoperable Spatial data services


TG Conformance class 1



TG Requirement 9 If at least one of the data sets, to which a spatial data service is related, has been harmonised according to [INS ISDSS], the metadata document for the spatial data service shall include the metadata elements and meet the additional requirements for metadata elements from [INS MD], as specified

in this section.

4.5.1 Coordinate Reference Systems Identifier

[INS ISDSS] requires a Coordinate Reference Systems Identifier metadata element, describing, where appropriate, this is the list of coordinate reference systems supported by the spatial data service.

The Coordinate Reference Systems Identifier metadata element is implemented using the RS_Identifier element from [ISO 19115].

TG Requirement 10 Each supported coordinate reference system shall be expressed using an identifier.

TG Requirement 11 Only identifiers contained in a common register shall be used for referring to

the coordinate reference systems listed in this Section.

Metadata element name Coordinate Reference System

Reference 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 if relevant for interoperable spatial data services

INSPIRE multiplicity [0..*] - mandatory if relevant NOTE In [INS ISDSS], the multiplicity is given as [1..*] with the


2015-11-15 Page 31 of 98

condition “mandatory if relevant”. In all other cases of conditional metadata elements in [INS MD] and [INS ISDSS], the minimum cardinality is given with 0.

Data type (and ISO 19115 no.) 186.MD_ReferenceSystem

Domain To identify the reference system, the referenceSystemIdentifier (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

Example referenceSystemIdentifier:

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

Comments

TG Recommendation 4 In order to be machine readable, the coordinate reference system identifier metadata element shall be provided using the gmx:Anchor element.

TG Recommendation 5 It is recommended to use the http URIs provided by the Open Geospatial Consortium as coordinate reference system identifiers (see identifiers for the default CRSs in Table 2). These are based on and redirect to the definition in the EPSG Geodetic Parameter Registry (http://www.epsg-registry.org/).

Table 2 - Recommended http URIs for the default coordinate reference systems

Coordinate reference system Short name http URI identifier

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

2D geodetic in ETRS89 on GRS80 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, ETRS89-TM29N http://www.opengis.net/def/crs/EPSG/0/3041

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

http://www.epsg-registry.org/











2015-11-15 Page 32 of 98

zone 29N (12°W to 6°W)

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



<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














2015-11-15 Page 33 of 98

4.5.2 Quality of Service

This is the minimum quality of service estimated by the spatial data service responsible party.

[INS ISDSS] requires three quality of service criteria to be reported in the metadata:

- 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.

All the quality of service metadata elements contain only static information about the parameters for quality of service, which are in general valid for the service for a long time period.

The Quality of Service metadata elements are implemented using DQ_ConceptualConsistency elements from [ISO 19115].

NOTE It has been agreed by the MIG to use the ISO “dataQuality” element to document quality of service, even if this may not be entirely correct semantically. The rationale for this decision was the goal not to have to extend the ISO metadata schema, but to use existing elements.

TG Requirement 12 There shall be at least one quality result consisting of Description, Value and Unit reported in the metadata for each criterion (availability, performance,

capacity).

Metadata element name Description

Reference COMMISSION REGULATION (EU) No 1089/2010, Annex VI Part B

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

INSPIRE multiplicity not specified in [INS ISDSS]

ISO multiplicity is: 1 per criterion

Data type (and ISO 19115 no.) Free text

Domain Criteria code list (4.8.6)

Example availability (http://inspire.ec.europa.eu/metadata-codelist/Criteria/availability)

Comments The identifier of the measure is enough to retrieve all information about the quality measure. This element enable direct understanding of the metadata

http://inspire.ec.europa.eu/metadata-codelist/Criteria/availability



2015-11-15 Page 34 of 98

4.2.1

Definition Code identifying a registered standard procedure

ISO 19115 number and name 101. measureIdentification

ISO/TS 19139 path dataQualityInfo/*/report/DQ_ConceptualConsistency/measureIdentification



ISO multiplicity is: 1 per criterion

Data type (and ISO 19115 no.) MD_Identifier/code

Domain Identifier of the quality measure as defined in the quality measure tables

Example INSPIRE_service_performance

Comments

Metadata element name Value

Reference COMMISSION REGULATION (EU) No 1089/2010, Annex VI Part B 4.2.2

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



ISO multiplicity is: [1..*] per criterion

Data type (and ISO 19115 no.) As defined for each measure in the quality measure tables

Domain

Example 1

Comments

Metadata element name Unit

Reference COMMISSION REGULATION (EU) No 1089/2010, Annex VI Part B 4.2.3

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


INSPIRE multiplicity [1] for each criteria


2015-11-15 Page 35 of 98

Data type (and ISO 19115 no.) UnitOfMeasure

Domain Value unit for the measure as described in the quality measure tables

Example second (implemented by reference in XML : <gmd:valueUnit xlink:href=" http://www.opengis.net/def/uom/SI/second"/>)

Comments

The three tables below describe quality measures for each quality of service criteria: availability, performance and capacity. The tables are formalised as data quality measures following the ISO 19157

data quality measure structure.

TG Recommendation 6 It is recommended to use either these measures or, if other measures are used, to make these publicly available, ideally through a register and following the [ISO 19157] data quality measure structure.

Service availability

Component Measure Description

Name Service availability

Alias –

Data quality element Conceptual consistency (or Usability, if ISO 19115-1 and ISO 19157 is used)

Data quality basic measure -

Definition percentage of time the service is available.

Description Availability on yearly basis, expressed as percentage of time.

The reported value unit should be “unity” (http://www.opengis.net/def/uom/OGC/1.0/unity).

Parameter –

Data quality value type Real

Data quality value structure –

Source reference –

Example 90%

Identifier INSPIRE_service_availability

http://www.opengis.net/def/uom/SI/second

http://www.opengis.net/def/uom/OGC/1.0/unity


2015-11-15 Page 36 of 98

Service performance


Name Service performance

Alias Average response time


Data quality basic measure

Definition Performance describes how fast a request to the spatial data service can be completed, expressed in second.

Description Average response time, expressed as seconds

(http://www.opengis.net/def/uom/SI/second)

Parameter –

Data quality value type Integer



Example 1 s

Identifier INSPIRE_service_performance

Service capacity


Name Service capacity

Alias –


Data quality basic measure

Definition maximum number of simultaneous requests that can be completed with the declared performance

Description Maximum number of simultaneous requests per second meeting the performance criteria, expressed as number of requests per second

Parameter –

Data quality value type Integer



Example 50 requests per second

Identifier INSPIRE_service_capacity


<gmd:MD_Metadata>

…



http://www.opengis.net/def/uom/SI/second


2015-11-15 Page 37 of 98

<gmd:scope>

<gmd:DQ_Scope>

<gmd:level>

<gmd:MD_ScopeCode

codeList=http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#M

D_ScopeCode codeListValue="service"/>

</gmd:level>

</gmd:DQ_Scope>

</gmd:scope>

<gmd:report>

<gmd:DQ_ConceptualConsistency>

<gmd:nameOfMeasure>

<gmx:Anchor>

xlink:href="http://inspire.ec.europa.eu/metadata-

codelist/Criteria/availability">availability</gmx:Anchor>

</gmd:nameOfMeasure>

<gmd:measureIdentification>

<gmd:MD_Identifier>

<gmd:code>

<gco:CharacterString>INSPIRE_service_availability</gco:CharacterString>

</gmd:code>

</gmd:MD_Identifier>

</gmd:measureIdentification>

<gmd:result>

<gmd:DQ_QuantitativeResult>

<gmd:valueUnit

xlink:href="http://www.opengis.net/def/uom/OGC/1.0/unity”/>

<gmd:value>

<gco:Record>90</gco:Record>

</gmd:value>

</gmd:DQ_QuantitativeResult>

</gmd:result>

</gmd:DQ_ConceptualConsistency>

</gmd:report>

<gmd:report>


<gmd:nameOfMeasure>

<gmx:Anchor>


codelist/Criteria/performance">performance</gmx:Anchor>



<gmd:MD_Identifier>

<gmd:code>

<gco:CharacterString>

INSPIRE_service_performance</gco:CharacterString>

</gmd:code>



<gmd:result>


<gmd:valueUnit xlink:href="

http://www.opengis.net/def/uom/SI/second"/>

<gmd:value>

<gco:Record>0.5</gco:Record>

</gmd:value>


</gmd:result>



2015-11-15 Page 38 of 98

</gmd:report>

<gmd:report>


<gmd:nameOfMeasure>

<gmx:Anchor>


codelist/Criteria/capacity">capacity</gmx:Anchor>



<gmd:MD_Identifier>

<gmd:code>

<gco:CharacterString>INSPIRE_service_capacity

</gco:CharacterString>

</gmd:code>



<gmd:result>


<gmd:valueUnit gco:nilReason="inapplicable"/>

<gmd:value>

<gco:Record>50</gco:Record>

</gmd:value>


</gmd:result>


</gmd:report>

…

</gmd:MD_Metadata

4.5.3 Conditions applying to access and use

The access to the spatial data service may have technical restrictions applying to the access and use of the spatial data service.

[INS ISDSS] requires the technical restrictions applying to the access and use of the spatial data service to be documented in the metadata element “conditions applying to access and use”.

TG Requirement 13 Conditions applying to access and use shall be represented by at least one of the following:

- a combination of one instance of MD_LegalConstraints.accessConstraints and one instance of MD_LegalConstraints.otherConstraints. In that case, the element MD_LegalConstraints.accessConstraints shall be set at the value “otherRestrictions”.

- a combination of one instance of MD_LegalConstraints.useConstraints and one instance of MD_LegalConstraints.otherConstraints. In that case, the element MD_LegalConstraints.useConstraints shall be set at the value “otherRestrictions”.

- The otherConstraints element 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.


2015-11-15 Page 39 of 98

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

TG Recommendation 7 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.

Conditions applying to access

Metadata element name Conditions applying to access

Reference Part B 8.1

Definition Restrictions on the access of a resource or metadata

ISO 19115 number and name 70. accessConstraints

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

INSPIRE obligation / condition Conditional. Mandatory if useConstraints is not documented.

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

Data type (and ISO 19115 no.) MD_RestrictionCode

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

19115)

Example otherRestrictions (limitation not listed).

Comments

Metadata element name Conditions applying to access (other constraints)


Definition Other restrictions and legal prerequisites for accessing 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 conditions applying to access. Mandatory

if accessConstraints is set at the value “otherRestrictions”

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

Data type (and ISO 19115 no.) CharacterString

Domain Free text

If the values “no conditions apply” or “conditions unknown” are

used, the corresponding value from the code list Conditions

applying to access and use (4.8.4) shall be used.


2015-11-15 Page 40 of 98

Example Example if no conditions apply:

noConditionsApply

(http://inspire.ec.europa.eu/registry/metadata-

codelist/ConditionsApplyingToAccessAndUse/noConditionsA

pply)

Example if there is information about restrictions:

The JRC does not provide any assistance or support in using

the service

Comments

The domain of the metadata element otherConstraints is free text.

This makes it hard to unambiguously define some common values

in all official languages in the Communiy.

Therefore it is required to refer to code lists in the INSPIRE

registry for some specific values like “no conditions apply” and

“conditions unknown” (see Domain).

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 Conditional. Mandatory if accessConstraints is not documented.

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

Data type (and ISO 19115 no.) MD_RestrictionCode

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

19115)

Example otherRestrictions (limitation not listed).

Comments

Metadata element name Conditions applying to use (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 conditions applying to use. Mandatory if

useConstraints is set at the value “otherRestrictions”

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

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




2015-11-15 Page 41 of 98


Domain Free text

or

if the values “no conditions apply” or “conditions unknown” is used

then an Anchor to the codelist in the Inspire Registry should be

used.

Example Example if no conditions apply:

noConditionsApply

(http://inspire.ec.europa.eu/registry/metadata-

codelist/ConditionsApplyingToAccessAndUse/NoConditions

Apply)

Example if there is information about restrictions:

The JRC does not provide any assistance or support in using

the service

Comments The domain of the metadata element otherConstraints is free text.

This makes it hard to unambiguously define some common values

in all official languages in the Communiy.

Therefore it is required to refer to code lists in the INSPIRE

registry for some specific values like “no conditions apply” and

“conditions unknown” (see Domain).

Conditions applying to access and use (access and use restrictions apply)


…

<gmd:identificationInfo>

<srv:SV_ServiceIdentification>

…



<ws:definitions xmlns:ws="http://schemas.xmlsoap.org/wsdl/"

xmlns:types="http://ws.geo3dmodel.dino.nitg.tno.nl/types"

xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"

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

xmlns:tns="http://ws.geo3dmodel.dino.nitg.tno.nl/"

xmlns:xs="http://www.w3.org/2001/XMLSchema"

xmlns:xmime="http://www.w3.org/2005/05/xmlmime"

xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"

xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"

xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"

targetNamespace="http://ws.geo3dmodel.dino.nitg.tno.nl/"

name="Geo3DModelService">

<ws:documentation>

This WSDL describes a webservice for making "virtual" boreholes in the

Digital Subsurface Models of DINO.

The following operations are provided:

1. sampleColumn creates a synthetic borehole for the specified

location using the specified model.

See the documentation in the schema for the types (available at the

schemaLocation below) for additional details.

2. listModels lists all models available for sampling.

</ws:documentation>

<ws:types>

<xs:schema>

<xs:import namespace="http://ws.geo3dmodel.dino.nitg.tno.nl/types"

schemaLocation="http://www.dinoservices.nl:80/geo3dmodelwebservices-

1/Geo3DModelService?xsd=1"/>

</xs:schema>

</ws:types>

<ws:message name="sampleColumn">

<ws:part name="parameters" element="types:sampleColumn"/>

</ws:message>

<ws:message name="sampleColumnResponse">

<ws:part name="parameters" element="types:sampleColumnResponse"/>

</ws:message>

<ws:message name="drawColumn">

<ws:part name="parameters" element="types:drawColumn"/>

</ws:message>

<ws:message name="drawColumnResponse">

<ws:part name="parameters" element="types:drawColumnResponse"/>

</ws:message>

<ws:message name="listModels">

<ws:part name="parameters" element="types:listModels"/>

</ws:message>

<ws:message name="listDocuments">

<ws:part name="parameters" element="types:listDocuments"/>

</ws:message>

http://www.dinoservices.nl/geo3dmodelwebservices-1/Geo3DModelService?wsdl


2015-11-15 Page 59 of 98

<ws:message name="listRasters">

<ws:part name="parameters" element="types:listRasters"/>

</ws:message>

<ws:message name="listModelsResponse">

<ws:part name="parameters" element="types:listModelsResponse"/>

</ws:message>

<ws:message name="listDocumentsResponse">

<ws:part name="parameters" element="types:listDocumentsResponse"/>

</ws:message>

<ws:message name="listRastersResponse">

<ws:part name="parameters" element="types:listRastersResponse"/>

</ws:message>

<ws:message name="describeModel">

<ws:part name="parameters" element="types:describeModel"/>

</ws:message>

<ws:message name="describeModelResponse">

<ws:part name="parameters" element="types:describeModelResponse"/>

</ws:message>

<ws:message name="sampleDepth">

<ws:part name="parameters" element="types:sampleDepth"/>

</ws:message>

<ws:message name="sampleDepthResponse">

<ws:part name="parameters" element="types:sampleDepthResponse"/>

</ws:message>

<ws:message name="drawDepthSection">

<ws:part name="parameters" element="types:drawDepthSection"/>

</ws:message>

<ws:message name="drawDepthSectionResponse">

<ws:part name="parameters" element="types:drawDepthSectionResponse"/>

</ws:message>

<ws:message name="drawVerticalSection">

<ws:part name="parameters" element="types:drawVerticalSection"/>

</ws:message>

<ws:message name="drawVerticalSectionResponse">

<ws:part name="parameters"

element="types:drawVerticalSectionResponse"/>

</ws:message>

<ws:message name="userInputErrorResponse">

<ws:part name="parameters" element="types:userInputErrorResponse"/>

</ws:message>

<ws:portType name="Geo3DModelPortType">

<ws:operation name="sampleColumn">

<ws:input message="tns:sampleColumn"

wsaw:Action="http://ws.geo3dmodel.dino.nitg.tno.nl/sampleColumnRequest"/>

<ws:output message="tns:sampleColumnResponse"

wsaw:Action="http://ws.geo3dmodel.dino.nitg.tno.nl/sampleColumnResponse"/>

<ws:fault name="fault" message="tns:userInputErrorResponse"/>

</ws:operation>

<ws:operation name="drawColumn">

<ws:input message="tns:drawColumn"

wsaw:Action="http://ws.geo3dmodel.dino.nitg.tno.nl/drawColumnRequest"/>

<ws:output message="tns:drawColumnResponse"

wsaw:Action="http://ws.geo3dmodel.dino.nitg.tno.nl/drawColumnResponse"/>


</ws:operation>

<ws:operation name="listModels">

<ws:input message="tns:listModels"

wsaw:Action="http://ws.geo3dmodel.dino.nitg.tno.nl/listModelsRequest"/>

<ws:output message="tns:listModelsResponse"

wsaw:Action="http://ws.geo3dmodel.dino.nitg.tno.nl/listModelsResponse"/>


2015-11-15 Page 60 of 98


</ws:operation>

<ws:operation name="listDocuments">

<ws:input message="tns:listDocuments"

wsaw:Action="http://ws.geo3dmodel.dino.nitg.tno.nl/listDocumentsRequest"/>

<ws:output message="tns:listDocumentsResponse"

wsaw:Action="http://ws.geo3dmodel.dino.nitg.tno.nl/listDocumentsResponse"/>


</ws:operation>

<ws:operation name="listRasters">

<ws:input message="tns:listRasters"

wsaw:Action="http://ws.geo3dmodel.dino.nitg.tno.nl/listRastersRequest"/>

<ws:output message="tns:listRastersResponse"

wsaw:Action="http://ws.geo3dmodel.dino.nitg.tno.nl/listRastersResponse"/>


</ws:operation>

<ws:operation name="describeModel">

<ws:input message="tns:describeModel"

wsaw:Action="http://ws.geo3dmodel.dino.nitg.tno.nl/describeModelRequest"/>

<ws:output message="tns:describeModelResponse"

wsaw:Action="http://ws.geo3dmodel.dino.nitg.tno.nl/describeModelResponse"/>


</ws:operation>

<ws:operation name="sampleDepth">

<ws:input message="tns:sampleDepth"

wsaw:Action="http://ws.geo3dmodel.dino.nitg.tno.nl/sampleDepthRequest"/>

<ws:output message="tns:sampleDepthResponse"

wsaw:Action="http://ws.geo3dmodel.dino.nitg.tno.nl/sampleDepthResponse"/>


</ws:operation>

<ws:operation name="drawDepthSection">

<ws:input message="tns:drawDepthSection"

wsaw:Action="http://ws.geo3dmodel.dino.nitg.tno.nl/drawDepthSectionRequest"

/>

<ws:output message="tns:drawDepthSectionResponse"

wsaw:Action="http://ws.geo3dmodel.dino.nitg.tno.nl/drawDepthSectionResponse

"/>


</ws:operation>

<ws:operation name="drawVerticalSection">

<ws:input message="tns:drawVerticalSection"

wsaw:Action="http://ws.geo3dmodel.dino.nitg.tno.nl/drawVerticalSectionReque

st"/>

<ws:output message="tns:drawVerticalSectionResponse"

wsaw:Action="http://ws.geo3dmodel.dino.nitg.tno.nl/drawVerticalSectionRespo

nse"/>


</ws:operation>

</ws:portType>

<ws:binding name="Geo3DModelServicePortBinding"

type="tns:Geo3DModelPortType">

<soap:binding transport="http://schemas.xmlsoap.org/soap/http"

style="document"/>

<ws:operation name="sampleColumn">

<soap:operation soapAction="sampleColumn"/>

<ws:input>

<soap:body use="literal"/>

</ws:input>

<ws:output>



2015-11-15 Page 61 of 98

</ws:output>

<ws:fault name="fault">

<soap:fault name="fault"/>

</ws:fault>

</ws:operation>

<ws:operation name="drawColumn">

<soap:operation soapAction="drawColumn"/>

<ws:input>


</ws:input>

<ws:output>


</ws:output>



</ws:fault>

</ws:operation>

<ws:operation name="listModels">

<soap:operation soapAction="listModels"/>

<ws:input>


</ws:input>

<ws:output>


</ws:output>



</ws:fault>

</ws:operation>

<ws:operation name="listDocuments">

<soap:operation soapAction="listDocuments"/>

<ws:input>


</ws:input>

<ws:output>


</ws:output>



</ws:fault>

</ws:operation>

<ws:operation name="listRasters">

<soap:operation soapAction="listRasters"/>

<ws:input>


</ws:input>

<ws:output>


</ws:output>



</ws:fault>

</ws:operation>

<ws:operation name="describeModel">

<soap:operation soapAction="describeModel"/>

<ws:input>


</ws:input>

<ws:output>



2015-11-15 Page 62 of 98

</ws:output>



</ws:fault>

</ws:operation>

<ws:operation name="sampleDepth">

<soap:operation soapAction="sampleDepth"/>

<ws:input>


</ws:input>

<ws:output>


</ws:output>



</ws:fault>

</ws:operation>

<ws:operation name="drawDepthSection">

<soap:operation soapAction="drawDepthSection"/>

<ws:input>


</ws:input>

<ws:output>


</ws:output>



</ws:fault>

</ws:operation>

<ws:operation name="drawVerticalSection">

<soap:operation soapAction="drawVerticalSection"/>

<ws:input>


</ws:input>

<ws:output>


</ws:output>



</ws:fault>

</ws:operation>

</ws:binding>

<ws:service name="Geo3DModelService">

<ws:port name="Geo3DModelServicePort"

binding="tns:Geo3DModelServicePortBinding">

<soap:address

location="http://www.dinoservices.nl:80/geo3dmodelwebservices-

1/Geo3DModelService"/>

</ws:port>

</ws:service>



<ws:message name="GetCapabilitiesRequest">

<ws:part name="Body" element="csw:GetCapabilities"/>

</ws:message>

<ws:message name="DescribeRecordRequest">

<ws:part name="Body" element="csw:DescribeRecord"/>

</ws:message>

<ws:message name="GetRecordsRequest">

<ws:part name="Body" element="csw:GetRecords"/>


2015-11-15 Page 63 of 98

</ws:message>

<ws:message name="GetRecordByIdRequest">

<ws:part name="Body" element="csw:GetRecordById"/>

</ws:message>

<ws:message name="GetDomainRequest">

<ws:part name="Body" element="csw:GetDomain"/>

</ws:message>

<ws:message name="HarvestRequest">

<ws:part name="Body" element="csw:Harvest"/>

</ws:message>

<ws:message name="TransactionRequest">

<ws:part name="Body" element="csw:Transaction"/>

</ws:message>

<ws:portType name="csw">

<ws:operation name="csw.getCapabilities">

<ws:input message="csw-req:GetCapabilitiesRequest"/>

<ws:output message="csw-resp:GetCapabilitiesResponse"/>

<ws:fault name="ServiceExceptionReport" message="csw-

resp:ServiceExceptionReport"/>

</ws:operation>

<ws:operation name="csw.describeRecord">

<ws:input message="csw-req:DescribeRecordRequest"/>

<ws:output message="csw-resp:DescribeRecordResponse"/>



</ws:operation>

<ws:operation name="csw.getRecords">

<ws:input message="csw-req:GetRecordsRequest"/>

<ws:output message="csw-resp:GetRecordsResponse"/>



</ws:operation>

<ws:operation name="csw.getRecordById">

<ws:input message="csw-req:GetRecordByIdRequest"/>

<ws:output message="csw-resp:GetRecordByIdResponse"/>



</ws:operation>

<ws:operation name="csw.getDomain">

<ws:input message="csw-req:GetDomainRequest"/>

<ws:output message="csw-resp:GetDomainResponse"/>



</ws:operation>

</ws:portType>

<ws:binding name="csw-GET" type="csw-req:csw">

<ws:documentation>CSW interface bound to the HTTP/1.1 GET

method.</ws:documentation>

<http:binding verb="GET"/>

<ws:operation name="csw.getCapabilities">

<http:operation location="GetCapabilities"/>

<ws:input>

<http:urlEncoded/>

</ws:input>

<ws:output>

<mime:mimeXml/>

</ws:output>

<ws:fault name="ServiceExceptionReport">

<soap:fault use="literal" name="ServiceExceptionReport"/>

</ws:fault>


2015-11-15 Page 64 of 98

</ws:operation>

<ws:operation name="csw.getRecordById">

<http:operation location="GetRecordById"/>

<ws:input>

<http:urlEncoded/>

</ws:input>

<ws:output>

<mime:mimeXml/>

</ws:output>

<ws:fault name="ServiceExceptionReport">

<soap:fault use="literal" name="ServiceExceptionReport"/>

</ws:fault>

</ws:operation>

</ws:binding>

<ws:service name="CSW">

<ws:documentation>

This is an example

</ws:documentation>

<ws:port binding="csw-http-kvp:csw-GET" name="csw-GET-Port">

<http:address

location="http://someurl.com/example/services/CSWDiscovery"/>

</ws:port>

</ws:service>

</ws:definitions>


2015-11-15 Page 65 of 98

Annex B – Get Harmonized Spatial Data Service Metadata

NOTE This annex still needs to be updated once the remainder of the document has been finalised.

This is an example of the Get Harmonized Spatial Data Service Metadata operation as described at chapter 4.6.4.

B.1 Get Harmonized Spatial Data Service Metadata Request

This section contains a description about the get capabilities Request, including a table specifying the parameters needed by the request.

In this capabilities request there is no need to provide the “service” information (this is a deviation from the standard OWS capabilities).

Table 5 - Get Harmonized Spatial Data Service Metadata request

Request Parameter Mandatory / optional

Description

Request=GetCapabilities M Operation name (text).

Fixed value: GetCapabilities.

AcceptVersions=version O Request version: 2.0.2

[INS NS] requires that multilingual aspects for network services are supported. As there is no standard way to deal with multilingualism within the [OGC WS] specifications, the HTTP/GET binding of the GetCapabilities-Operation is extended by an additional parameter that indicates the client’s preferred language.

Request Parameter Parameter value Description

LANGUAGE 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 23 official EU languages and EFTA Countries is:

Bulgarian – bul Italian – ita

Czech – cze Latvian – lav

It is optional for a Client Request.

It is mandatory to be supported for the service and shall be processed if the parameter is present in a client’s request with a supported language code. If the parameter is absent in a client’s request or it requested an unsupported language the service shall response in the service default


2015-11-15 Page 66 of 98

Danish – dan Liechenstein – ger

Dutch – dut Lithuanian – lit

English – eng Maltese – mlt

Polish – pol Norwegian – nor

Estonian – est Portuguese – por

Finnish – fin Romanian – rum

French – fre Romansh - roh

German – ger Slovak – slo

Greek – gre Slovenian – slv

Hungarian – hun Spanish – spa

Irish – gle Swedish – swe

Icelandic – ice

The list of all the codes is defined at http://www.loc.gov/standards/iso639-2/

Regional languages also are included in this list.

language.

EXAMPLE GetCapabilities Request KPV Encoding:

http://www.example.com/srv?REQUEST=GetCapabilities&LANGUAGE=eng

B.2 Scenario 1 – Get Harmonized Spatial Data Service Metadata Response


<Capabilities xmlns="http://www.opengis.net/ows/1.1"

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

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

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

xmlns:ins_com="http://inspire.ec.europa.eu/schemas/common/1.0"

xmlns:ins_sds="http://inspire.ec.europa.eu/schemas/inspire_sds_ows11/1.0"

xmlns:ins_qos="http://to-be-provided/schemas/qos/1.0"

xmlns:ins_sdsc="http://to-be-provided/schemas/sdsc/1.0" version="1.0.0"

xsi:schemaLocation="http://www.opengis.net/ows/1.1

http://example/exampleCapabilities.xsd

http://inspire.ec.europa.eu/schemas/inspire_vs_ows11/1.0

http://example/inspire_sds_ows_11.xsd">

<ows:ServiceIdentification>

<ows:Title>Geo 3D Model service</ows:Title>

<ows:Abstract>This Spatial Data Service supports various operations on

the Digital Subsurface Models (Regis, DGM and GeoTop) provided by the

Geological Survey of the Netherlands. There is for example an operation to

create a “virtual borehole” through one of the subsurface models for any

given location in the Netherlands. The result can either be returned as Xml

data or as a graphical representation. There is also supported for creating

a VerticalSection a depthSection and many others. All operations and

http://www.example.com/srv?REQUEST=GetCapabilities&LANGUAGE=eng


2015-11-15 Page 67 of 98

returned values are in the EPSG:28992 (RDNew) coordinate reference

system.</ows:Abstract>

<ows:Keywords>

<ows:Keyword>infoCoverageAccessService</ows:Keyword>

<ows:Keyword>subsurface</ows:Keyword>

<ows:Keyword>geology</ows:Keyword>

<ows:Keyword>Netherlands</ows:Keyword>

<ows:Keyword>3D model</ows:Keyword>

</ows:Keywords>

<ows:ServiceType>other</ows:ServiceType>

<ows:ServiceTypeVersion>1.0.0</ows:ServiceTypeVersion>

<ows:Fees>none</ows:Fees>

<ows:AccessConstraints>TNO terms and conditions

apply</ows:AccessConstraints>

</ows:ServiceIdentification>

<ows:ServiceProvider>

<ows:ProviderName>Geological Survey of the

Netherlands</ows:ProviderName>

<ows:ServiceContact>

<ows:IndividualName>Servicedesk Geological Survey of the

Netherlands</ows:IndividualName>

<ows:ContactInfo>

<ows:Address>

<ows:ElectronicMailAddress>[email protected]</ows:ElectronicMailAddress>

</ows:Address>

</ows:ContactInfo>

</ows:ServiceContact>

</ows:ServiceProvider>

<ows:OperationsMetadata>

<ows:Operation name="GetCapabilities">

<ows:DCP>

<ows:HTTP>

<ows:Get xlink:href="http://www.example.com/service.cgi?">

<ows:Constraint name="GetEncoding">

<ows:AllowedValues>

<ows:Value>KVP</ows:Value>

</ows:AllowedValues>

</ows:Constraint>

</ows:Get>

<ows:Post xlink:href="http://www.example.com/service.cgi?">

<ows:Constraint name="PostEncoding">

<ows:AllowedValues>

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


</ows:Constraint>

</ows:Post>

</ows:HTTP>

</ows:DCP>

</ows:Operation>

<ows:Operation name="sampleColumn">

<ows:DCP>

<ows:HTTP>

<ows:Post

xlink:href="http://www.dinoservices.nl/geo3dmodelwebservices-

1/Geo3DModelService?wsdl">


<ows:AllowedValues>



</ows:Constraint>


2015-11-15 Page 68 of 98

</ows:Post>

</ows:HTTP>

</ows:DCP>

</ows:Operation>

<ows:Operation name="drawColumn">

<ows:DCP>

<ows:HTTP>

<ows:Post




<ows:AllowedValues>



</ows:Constraint>

</ows:Post>

</ows:HTTP>

</ows:DCP>

</ows:Operation>

...







<ins_sds:ExtendedCapabilities>

<ins_com:ResourceLocator>

<ins_com:URL/>

</ins_com:ResourceLocator>

<ins_com:ResourceType>service</ins_com:ResourceType>

<ins_com:TemporalReference/>

<ins_com:Conformity>

<ins_com:Specification>

<ins_com:Title>Webservice for making virtual boreholes in the

Digital Subsurface Models of the Netherlands</ins_com:Title>

<ins_com:DateOfPublication>2011-11-

03</ins_com:DateOfPublication>

</ins_com:Specification>

<ins_com:Degree>notEvaluated</ins_com:Degree>

</ins_com:Conformity>

<ins_com:MetadataPointOfContact>

<ins_com:OrganisationName/>

<ins_com:EmailAddress>[email protected]</ins_com:EmailAddress>

</ins_com:MetadataPointOfContact>

<ins_com:MetadataDate>2010-12-08</ins_com:MetadataDate>

<ins_com:SpatialDataServiceType>other</ins_com:SpatialDataServiceType>

<ins_com:MandatoryKeyword>

<ins_com:KeywordValue>infoCoverageAccessService</ins_com:KeywordValue>



</ins_com:MandatoryKeyword>

<ins_com:SupportedLanguages>

<ins_com:DefaultLanguage>

<ins_com:Language>dan</ins_com:Language>

</ins_com:DefaultLanguage>

<ins_com:SupportedLanguage>

<ins_com:Language>eng</ins_com:Language>

</ins_com:SupportedLanguage>

</ins_com:SupportedLanguages>

<ins_com:ResponseLanguage>


</ins_com:ResponseLanguage>


2015-11-15 Page 69 of 98



<ins_qos:QualityOfService>

<ins_qos:criteria>availability</ins_qos:criteria>

<ins_qos:unit>percentage of time</ins_qos:unit>

<ins_qos:value>99.0</ins_qos:value>

<ins_qos:measurementDescription> Availability on yearly basis,

expressed as percentage of time</ins_qos:measurementDescription>

</ins_qos:QualityOfService>


<ins_qos:criteria>performance</ins_qos:criteria>

<ins_qos:unit>seconds</ins_qos:unit>

<ins_qos:value>1.457</ins_qos:value>

<ins_qos:measurementDescription>Average response time in

seconds</ins_qos:measurementDescription>



<ins_qos:criteria>capacity</ins_qos:criteria>

<ins_qos:unit>number of requests per second</ins_qos:unit>

<ins_qos:value>20</ins_qos:value>

<ins_qos:measurementDescription> Maximum number of simultaneous

requests per second meeting the performance

criteria</ins_qos:measurementDescription>




<ins_sdsc:Category>invocable</ins_sdsc:Category>

</ins_vs:ExtendedCapabilities>

</ows:OperationsMetadata>

</Capabilities>

B.3 Scenario 2 – Get Harmonized Spatial Data Service Metadata Response


<Capabilities xmlns="http://www.opengis.net/ows/1.1"

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



xmlns:ins_com="http://inspire.ec.europa.eu/schemas/common/1.0"

xmlns:ins_vs="http://inspire.ec.europa.eu/schemas/inspire_vs_ows11/1.0"

version="1.0.0" xsi:schemaLocation="http://www.opengis.net/ows/1.1

http://schemas.opengis.net/ows/1.1.0/Examples/exampleCapabilities.xsd

http://inspire.ec.europa.eu/schemas/inspire_vs_ows11/1.0

http://inspire.ec.europa.eu/schemas/inspire_vs_ows11/1.0/inspire_vs_ows_11.

xsd">

<ows:OperationsMetadata>

<ows:Operation name="GetCapabilities">

<ows:DCP>

<ows:HTTP>

<ows:Get xlink:href="http://www.example.com/service.cgi?">


<ows:AllowedValues>

<ows:Value>KVP</ows:Value>


</ows:Constraint>

</ows:Get>

<ows:Post xlink:href="http://www.example.com/service.cgi?">


2015-11-15 Page 70 of 98


<ows:AllowedValues>



</ows:Constraint>

</ows:Post>

</ows:HTTP>

</ows:DCP>

</ows:Operation>

<ows:Operation name="DescribeServiceOperation">

<ows:DCP>

<ows:HTTP>

<ows:Get




<ows:AllowedValues>



</ows:Constraint>

</ows:Get>

</ows:HTTP>

</ows:DCP>

</ows:Operation>







<ins_vs:ExtendedCapabilities>

<ins_com:MetadataUrl>

<ins_com:URL>http://link-to/discovery-metadata</ins_com:URL>

</ins_com:MetadataUrl>

<ins_com:SupportedLanguages>

<ins_com:DefaultLanguage>

<ins_com:Language>dan</ins_com:Language>

</ins_com:DefaultLanguage>

<ins_com:SupportedLanguage>


</ins_com:SupportedLanguage>

</ins_com:SupportedLanguages>

<ins_com:ResponseLanguage>


</ins_com:ResponseLanguage>

</ins_sds:ExtendedCapabilities>

</ows:OperationsMetadata>

</Capabilities>


2015-11-15 Page 71 of 98

Annex C – Metadata textual example

NOTE This example still needs to be updated once the remainder of the document has been finalised.

The following spatial service description is the source for the content of the majority of the examples provided in this document.

The orange elements are the elements not present in the original example.

Geo 3D Model service

Resource title

Geo 3D Model service.

Resource abstract

This Spatial Data Service supports various operations on the Digital Subsurface Models (Regis, DGM and GeoTop) provided by the Geological Survey of the Netherlands. There is for example an operation to create a “virtual borehole” through one of the subsurface models for any given location in the Netherlands. The result can either be returned as Xml data or as a graphical representation. There is also supported for creating a VerticalSection a depthSection and many others. All operations and returned values are in the EPSG:28992 (RDNew) coordinate reference system.

Resource type

Spatial Data Service

Resource locator (URL)

Service access point: http://www.dinoservices.nl/geo3dmodelwebservices-1/Geo3DModelService

WSDL available at: http://www.dinoservices.nl/geo3dmodelwebservices-1/Geo3DModelService?wsdl

Resource Locator Function Code

accessPoint-selfDescribing

Coupled resource

N/A

Spatial data service type

Coverage access service (infoCoverageAccessService)

Keyword

subsurface, geology, Netherlands, 3D model.

Geographic Location

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



2015-11-15 Page 72 of 98

Netherlands.

Bounding box

EPSG:28992 (-10421, 300413, 280019, 626762)

WGS84 (3.047, 50.670, 7.276, 53.612)

Temporal reference

N/A

Spatial resolution

The models have a resolution of 100x100 meters horizontally and have varying vertical resolutions.

Conformity

Specification

N/A

Degree

N/A

Conditions applying to access and use

Creative commons Free culture license conditions apply.

Limitations on public access

There are no limitations on public access.

Responsible organization

Geological Survey of the Netherlands

Metadata Point of contact

Servicedesk Geological Survey of the Netherlands

[email protected]

Metadata date

2012-08-14

Metadata language

English

Country Name

Netherlands

Spatial Data Service Class


2015-11-15 Page 73 of 98

invocable

Coordinate Reference System

EPSG:28992

EPSG:23031

EPSG:32631

EPSG:4230

EPSG:4326

Spatial data themes

Geology

Quality of service

99% uptime.

Specific Indicators

The service provides 9 different operations. It does not access any related Spatial Data Services.

Deviation from INSPIRE regulation

Resource description

The Geological Survey of the Netherlands creates and maintains the following models of the subsurface of the Netherlands:

DGM Digital Geological Model, covering Neogene and Quaternary units

REGIS A 3D hydrogeological schematisation of the Dutch subsurface describing the geometry and hydraulic properties of ~160 hydrogeological units (horizontal and vertical conductivity of sandy and clayey units respectively).

Geotop GeoTOP schematises the subsurface in voxels of 100 x 100 x 0.5 m (x, y, z) down to depths of 30 to 50 meters, covering the main zone of human activity. The model provides estimates of lithostratigraphy and lithology (including grain-size classes), as well as physical and chemical parameters such as hydraulic conductivity and chemical element concentrations. The layermodel of Geotop is available through the here described service.

This Spatial Data Service offers the following operations on these models:

sampleColumn Virtually drills through a specified model on a specified location returning the occurring model-units in depth and their properties for the specific location.


2015-11-15 Page 74 of 98

drawColumn Virtually drills through a specified model on a specified location returning a visualization of the occurring model-units.

listModels Lists all available models (in a specified area)

listDocuments Lists all available documentation on the specified model-unit

listRasters Lists references to all available data (depth, property, etc.) on which the specified model-unit is based. These data are rastermaps in WMS, preview or ZIP-download

describeModel Describes a specified model including all contained model-units and available properties.

drawVerticalSection Draws a vertical cross-section through a specified model along a specified line. These cross-section show model-units, lateral variation of a specified property or the result of a filter on depth, thickness and property value.

Standards

SOAP webservice with GML 3.1 messages.

Software

The SOAP service is an own Java based development of the Geological Survey of the Netherlands.

Distribution

Not defined.

Hardware/System Software

Linux based server park, JBoss application server with JAXWS Reference Implementation, Oracle database.

Topology

Real time.

Service end point

WSDL available at: http://www.dinoservices.nl/geo3dmodelwebservices-1/Geo3DModelService?wsdl

Lessons learned

For building and maintaining SOAP and REST services there is a rich set of open source tools available that work well, are well supported and understood worldwide. SOAP and REST services are fully capable of handling geographic data and operations. Because of the wide adoption of these standards it is also easy to use these services in applications as spreadsheets and word processors. The extreme complexity of the opengis Xsd’s and the element naming used in GML 3.1 sometimes require a work around. This may well stand in the way of a wider adoption of GML. A refactoring of the Xsd’s with this in mind can make GML less academic and more practical and usable.

Future Plans



2015-11-15 Page 75 of 98

The Geological Survey of the Netherlands will provide many more services to unlock the vast quantities of data it has of the Dutch subsurface and their interpretations into 3D models. Additionally the Geological Survey of the Netherlands is preparing for a new law that will govern management and utilization of subsurface information. Under this law, a key register for the subsurface will be established: a single national database for the subsurface data and information, which will have to be both fed and consulted by all Dutch government bodies dealing with the subsurface. This key register will use webservices as means of acquiring and delivering data and information to its users.

Best Practice Availability

This document may be made publicly available.


2015-11-15 Page 76 of 98

Annex D – Complete XML Encoding example

NOTE This example still needs to be updated once the remainder of the document has been finalised.

The code below shows a complete example of Inspire SDS. The colours used are related to the metadata to be provided for each class of conformance presented in the TG.

The XML example provided below has been validated with the new XSD provided in Annex F using Altova XML Spy.

Invocable

Interoperable

Harmonised

Note: in this example the harmonisation level has the containsOperation filled. As you can see at paragraph 5.9.2, it is not mandatory but conditional: the choose is between providing containsOperation element or a WSDL (example at Annex D) in order to describe the service operations. H.1 XML encoding example with GML 3.2.1


<gmd:MD_Metadata xmlns:gco="http://www.isotc211.org/2005/gco"

xmlns:gmx="http://www.isotc211.org/2005/gmx"

xmlns:gmd="http://www.isotc211.org/2005/gmd"

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

xmlns:gsr="http://www.isotc211.org/2005/gsr"

xmlns:gss="http://www.isotc211.org/2005/gss"

xmlns:gts="http://www.isotc211.org/2005/gts"

xmlns:srv="http://www.isotc211.org/2005/srv"

xmlns:inspire_sds="http://inspire.ec.europa.eu/schemas/inspire_sds/1.0"



xsi:schemaLocation="http://inspire.ec.europa.eu/schemas/inspire_sds/1.0

http://inspire.ec.europa.eu/schemas/inspire/inspire_sds/1.0/inspire_sds.xsd

">

<gmd:fileIdentifier>

<gco:CharacterString>mysdsid1</gco:CharacterString>

</gmd:fileIdentifier>

<gmd:language>

<gmd:LanguageCode


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

</gmd:language>

<gmd:hierarchyLevel>

<gmd:MD_ScopeCode


MD_ScopeCode" codeListValue="service">service</gmd:MD_ScopeCode>

</gmd:hierarchyLevel>

<gmd:contact>






2015-11-15 Page 77 of 98


<gmd:contactInfo>

<gmd:CI_Contact>

<gmd:address>

<gmd:CI_Address>




</gmd:CI_Address>

</gmd:address>

</gmd:CI_Contact>

</gmd:contactInfo>

<gmd:role>

<gmd:CI_RoleCode


CI_RoleCode"

codeListValue="pointOfContact">pointOfContact</gmd:CI_RoleCode>

</gmd:role>


</gmd:contact>

<gmd:dateStamp>


</gmd:dateStamp>

<gmd:metadataStandardName>

<gco:CharacterString>INSPIRE Spatial Data Services Community Profile

of ISO 19115:2005/19139</gco:CharacterString>

</gmd:metadataStandardName>

<gmd:metadataStandardVersion>

<gco:CharacterString>1.0</gco:CharacterString>

</gmd:metadataStandardVersion>




<gmd:RS_Identifier>

<gmd:code>

<gco:CharacterString>http://www.opengis.net/def/crs/EPSG/0/28992</gco:Cha

racterString>

</gmd:code>

<gmd:codeSpace>

<gco:CharacterString>EPSG</gco:CharacterString>

</gmd:codeSpace>






<inspire_sds:SV_ServiceIdentification>

<gmd:citation>

<gmd:CI_Citation>

<gmd:title>

<gco:CharacterString>Geo 3D Model

service</gco:CharacterString>

</gmd:title>

<gmd:date>

<gmd:CI_Date>

<gmd:date>


</gmd:date>

<gmd:dateType>


2015-11-15 Page 78 of 98



CI_DateTypeCode"

codeListValue="publication">publication</gmd:CI_DateTypeCode>

</gmd:dateType>

</gmd:CI_Date>

</gmd:date>

</gmd:CI_Citation>

</gmd:citation>

<gmd:abstract>

<gco:CharacterString>This Spatial Data Service supports various

operations on the Digital Subsurface Models (Regis, DGM and GeoTop)

provided by the Geological Survey of the Netherlands. There is for example

an operation to create a â€œvirtual boreholeâ€• through one of the

subsurface models for any given location in the Netherlands. The result can

either be returned as Xml data or as a graphical representation. There is

also supported for creating a VerticalSection a depthSection and many

others. All operations and returned values are in the EPSG:28992 (RDNew)

coordinate reference system. The models have a resolution of 100x100 meters

horizontally and have varying vertical resolutions. </gco:CharacterString>

</gmd:abstract>




<gco:CharacterString>Geological Survey of the



<gmd:contactInfo>

<gmd:CI_Contact>

<gmd:address>

<gmd:CI_Address>




</gmd:CI_Address>

</gmd:address>

</gmd:CI_Contact>

</gmd:contactInfo>

<gmd:role>

<gmd:CI_RoleCode



</gmd:role>



<gmd:descriptiveKeywords>

<gmd:MD_Keywords>

<gmd:keyword>

<gco:CharacterString>infoCoverageAccessService</gco:CharacterString>

</gmd:keyword>

<gmd:keyword>

<gco:CharacterString>subsurface</gco:CharacterString>

</gmd:keyword>

<gmd:keyword>

<gco:CharacterString>geology</gco:CharacterString>

</gmd:keyword>

<gmd:keyword>

<gco:CharacterString>Netherlands</gco:CharacterString>


2015-11-15 Page 79 of 98

</gmd:keyword>

<gmd:keyword>

<gco:CharacterString>3D model</gco:CharacterString>

</gmd:keyword>

</gmd:MD_Keywords>

</gmd:descriptiveKeywords>


<gmd:MD_Constraints>

<gmd:useLimitation>

<gco:CharacterString>Creative Commons Free

Culture.</gco:CharacterString>

</gmd:useLimitation>

</gmd:MD_Constraints>




<gmd:useLimitation>

<gmx:Anchor

xlink:href="http://creativecommons.org/licenses/by/3.0/deed.nl">Creative

Commons - Attribution 3.0 Unported</gmx:Anchor>









MD_RestrictionCode"

codeListValue="otherRestrictions">otherRestrictions</gmd:MD_RestrictionCode

>



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




<srv:serviceType>

<gco:LocalName>other</gco:LocalName>

</srv:serviceType>

<srv:extent>

<gmd:EX_Extent>

<gmd:geographicElement>

<gmd:EX_GeographicBoundingBox>

<gmd:westBoundLongitude>

<gco:Decimal>3.047</gco:Decimal>

</gmd:westBoundLongitude>

<gmd:eastBoundLongitude>


</gmd:eastBoundLongitude>

<gmd:southBoundLatitude>


</gmd:southBoundLatitude>

<gmd:northBoundLatitude>


</gmd:northBoundLatitude>

</gmd:EX_GeographicBoundingBox>

</gmd:geographicElement>

</gmd:EX_Extent>

</srv:extent>


2015-11-15 Page 80 of 98

<srv:extent>

<gmd:EX_Extent>



<gmd:temporalElement>

<gmd:EX_TemporalExtent>

<gmd:extent>

<gml:TimeInstant gml:id="myid">

<gml:timePosition>2001</gml:timePosition>

</gml:TimeInstant>

</gmd:extent>

</gmd:EX_TemporalExtent>

</gmd:temporalElement>

</gmd:EX_Extent>

</srv:extent>

<srv:couplingType gco:nilReason="missing"/>



<srv:operationName>



<srv:DCP>

<srv:DCPList codeList="http://someurl#DCPList"

codeListValue="HTTPGet"/>

</srv:DCP>

<srv:parameters>

<srv:SV_Parameter>

<srv:name>

<gco:aName>


</gco:aName>

<gco:attributeType>

<gco:TypeName>

<gco:aName>


</gco:aName>

</gco:TypeName>


</srv:name>

<srv:direction>


</srv:direction>

<srv:optionality>


</srv:optionality>

<srv:repeatability>



<srv:valueType>

<gco:TypeName>

<gco:aName>

<gco:CharacterString>string</gco:CharacterString>

</gco:aName>

</gco:TypeName>

</srv:valueType>

</srv:SV_Parameter>

</srv:parameters>

<srv:parameters>

<srv:SV_Parameter>


2015-11-15 Page 81 of 98

<srv:name>

<gco:aName>


</gco:aName>

<gco:attributeType>

<gco:TypeName>

<gco:aName>


</gco:aName>

</gco:TypeName>


</srv:name>

<srv:direction>


</srv:direction>

<srv:optionality>


</srv:optionality>

<srv:repeatability>



<srv:valueType>

<gco:TypeName>

<gco:aName>

<gco:CharacterString>double</gco:CharacterString>

</gco:aName>

</gco:TypeName>

</srv:valueType>

</srv:SV_Parameter>

</srv:parameters>

<srv:parameters>

<srv:SV_Parameter>

<srv:name>

<gco:aName>


</gco:aName>

<gco:attributeType>

<gco:TypeName>

<gco:aName>


</gco:aName>

</gco:TypeName>


</srv:name>

<srv:direction>


</srv:direction>

<srv:optionality>


</srv:optionality>

<srv:repeatability>



<srv:valueType>

<gco:TypeName>

<gco:aName>


2015-11-15 Page 82 of 98


</gco:aName>

</gco:TypeName>

</srv:valueType>

</srv:SV_Parameter>

</srv:parameters>

<srv:parameters>

<srv:SV_Parameter>

<srv:name>

<gco:aName>


</gco:aName>

<gco:attributeType>

<gco:TypeName>

<gco:aName>


</gco:aName>

</gco:TypeName>


</srv:name>

<srv:direction>


</srv:direction>

<srv:optionality>


</srv:optionality>

<srv:repeatability>



<srv:valueType>

<gco:TypeName>

<gco:aName>

<gco:CharacterString>int</gco:CharacterString>

</gco:aName>

</gco:TypeName>

</srv:valueType>

</srv:SV_Parameter>

</srv:parameters>

<srv:parameters>

<srv:SV_Parameter>

<srv:name>

<gco:aName>


</gco:aName>

<gco:attributeType>

<gco:TypeName>

<gco:aName>


</gco:aName>

</gco:TypeName>


</srv:name>

<srv:direction>


</srv:direction>

<srv:optionality>


</srv:optionality>

<srv:repeatability>



2015-11-15 Page 83 of 98


<srv:valueType>

<gco:TypeName>

<gco:aName>

<gco:CharacterString>AvailableCoordinateSystemType</gco:CharacterString>

</gco:aName>

</gco:TypeName>

</srv:valueType>

</srv:SV_Parameter>

</srv:parameters>

<srv:connectPoint>


<gmd:linkage>



</gmd:linkage>

<gmd:description><gmx:Anchor

xlink:href="http://inspire.ec.europa.eu/metadata-codelist/function-

code/access-point">Access point</gmx:Anchor></gmd:description>


</srv:connectPoint>



<srv:operatesOn xlink:href="http://www.dinoservices.nl"/>

<inspire_sds:spatialResolution>

<gmd:MD_Resolution>

<gmd:equivalentScale>

<gmd:MD_RepresentativeFraction>

<gmd:denominator>

<gco:Integer>1</gco:Integer>

</gmd:denominator>

</gmd:MD_RepresentativeFraction>

</gmd:equivalentScale>

</gmd:MD_Resolution>

</inspire_sds:spatialResolution>


<gmd:MD_Resolution>

<gmd:distance>

<gco:Distance uom="m">1</gco:Distance>

</gmd:distance>



<inspire_sds:qualityOfService>

<inspire_sds:SV_QualityOfService>

<inspire_sds:criterion>

<inspire_sds:SV_QualityOfServiceCriteria>performance</inspire_sds:SV_Qual

ityOfServiceCriteria>

</inspire_sds:criterion>

<inspire_sds:unit>

<gco:CharacterString>seconds</gco:CharacterString>

</inspire_sds:unit>

<inspire_sds:value>


</inspire_sds:value>

<inspire_sds:measurementDescription>

<gco:CharacterString>Average response time in

seconds</gco:CharacterString>

</inspire_sds:measurementDescription>

</inspire_sds:SV_QualityOfService>



2015-11-15 Page 84 of 98


<inspire_sds:SV_QualityOfServiceCriteria>availability</inspire_sds:SV_Qua

lityOfServiceCriteria>


<inspire_sds:unit>

<gco:CharacterString>percentage of time</gco:CharacterString>

</inspire_sds:unit>

<inspire_sds:value>




<gco:CharacterString>Availability on yearly basis, expressed

as percentage of time</gco:CharacterString>





<inspire_sds:SV_QualityOfServiceCriteria>capacity</inspire_sds:SV_Quality

OfServiceCriteria>


<inspire_sds:unit>

<gco:CharacterString>number of requests per

second</gco:CharacterString>

</inspire_sds:unit>

<inspire_sds:value>

<gco:CharacterString>20</gco:CharacterString>



<gco:CharacterString>Maximum number of simultaneous requests

per second meeting the performance criteria</gco:CharacterString>



</inspire_sds:qualityOfService>

<inspire_sds:category>invocable</inspire_sds:category>

</inspire_sds:SV_ServiceIdentification>






<gmd:onLine>


<gmd:linkage>

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


</gmd:linkage>

<gmd:function>


codeList="http://inspire.ec.europa.eu/draft-

schemas/resources/Codelist/gmxCodelist.xml" codeListValue="accessPoint-

selfDescribing">accessPoint- selfDescribing</gmd:CI_OnLineFunctionCode>

</gmd:function>


</gmd:onLine>

<gmd:onLine>


<gmd:linkage>


2015-11-15 Page 85 of 98

<gmd:URL>http://link-to/get-service-metadata</gmd:URL>

</gmd:linkage>

<gmd:function>



schemas/resources/Codelist/gmxCodelist.xml#INSPIRE_CI_OnLineFunctionCode"

codeListValue="providesServiceMetadata">providesServiceMetadata</gmd:CI_OnL

ineFunctionCode>

</gmd:function>


</gmd:onLine>







<gmd:scope>

<gmd:DQ_Scope>

<gmd:level>

<gmd:MD_ScopeCode



</gmd:level>

</gmd:DQ_Scope>

</gmd:scope>

<gmd:report>

<gmd:DQ_DomainConsistency

xsi:type="gmd:DQ_DomainConsistency_Type">

<gmd:result>

<gmd:DQ_ConformanceResult

xsi:type="gmd:DQ_ConformanceResult_Type">

<gmd:specification>

<gmd:CI_Citation>

<gmd:title>


</gmd:title>

<gmd:date>

<gmd:CI_Date>

<gmd:date>


</gmd:date>

<gmd:dateType>



CI_DateTypeCode"


</gmd:dateType>

</gmd:CI_Date>

</gmd:date>

</gmd:CI_Citation>


<gmd:explanation>



</gmd:explanation>

<gmd:pass>


</gmd:pass>


2015-11-15 Page 86 of 98


</gmd:result>


</gmd:report>

<gmd:report>



<gmd:result>



<gmd:specification>

<gmd:CI_Citation>

<gmd:title>

<gco:CharacterString>invocable2</gco:CharacterString>

</gmd:title>

<gmd:date>

<gmd:CI_Date>

<gmd:date>


</gmd:date>

<gmd:dateType>



CI_DateTypeCode"


</gmd:dateType>

</gmd:CI_Date>

</gmd:date>

</gmd:CI_Citation>


<gmd:explanation>



</gmd:explanation>

<gmd:pass>


</gmd:pass>


</gmd:result>


</gmd:report>

<gmd:report>



<gmd:result>



<gmd:specification>

<gmd:CI_Citation>

<gmd:title>


</gmd:title>

<gmd:date>

<gmd:CI_Date>

<gmd:date>


</gmd:date>

<gmd:dateType>


2015-11-15 Page 87 of 98



CI_DateTypeCode"


</gmd:dateType>

</gmd:CI_Date>

</gmd:date>

</gmd:CI_Citation>


<gmd:explanation>



</gmd:explanation>

<gmd:pass gco:nilReason="unknown">

</gmd:pass>


</gmd:result>


</gmd:report>



</gmd:MD_Metadata>

H.2 XML encoding example with GML 3.2.0


<gmd:MD_Metadata xmlns:gco="http://www.isotc211.org/2005/gco"

xmlns:gmx="http://www.isotc211.org/2005/gmx"

xmlns:gmd="http://www.isotc211.org/2005/gmd"

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

xmlns:gsr="http://www.isotc211.org/2005/gsr"

xmlns:gss="http://www.isotc211.org/2005/gss"

xmlns:gts="http://www.isotc211.org/2005/gts"

xmlns:srv="http://www.isotc211.org/2005/srv"

xmlns:inspire_sds="http://inspire.ec.europa.eu/schemas/inspire_sds_2006/1.0

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


xsi:schemaLocation="http://inspire.ec.europa.eu/schemas/inspire_sds_2006/1.

0

http://inspire.ec.europa.eu/schemas/inspire/inspire_sds_2006/1.0/inspire_sd

s_2006.xsd">

<gmd:fileIdentifier>

<gco:CharacterString>mysdsid1</gco:CharacterString>

</gmd:fileIdentifier>

<gmd:language>

<gmd:LanguageCode


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

</gmd:language>

<gmd:hierarchyLevel>

<gmd:MD_ScopeCode



</gmd:hierarchyLevel>

<gmd:contact>




2015-11-15 Page 88 of 98




<gmd:contactInfo>

<gmd:CI_Contact>

<gmd:address>

<gmd:CI_Address>




</gmd:CI_Address>

</gmd:address>

</gmd:CI_Contact>

</gmd:contactInfo>

<gmd:role>

<gmd:CI_RoleCode


CI_RoleCode"

codeListValue="pointOfContact">pointOfContact</gmd:CI_RoleCode>

</gmd:role>


</gmd:contact>

<gmd:dateStamp>


</gmd:dateStamp>

<gmd:metadataStandardName>

<gco:CharacterString>INSPIRE Spatial Data Services Community Profile

of ISO 19115:2005/19139</gco:CharacterString>

</gmd:metadataStandardName>

<gmd:metadataStandardVersion>


</gmd:metadataStandardVersion>




<gmd:RS_Identifier>

<gmd:code>

<gco:CharacterString>http://www.opengis.net/def/crs/EPSG/0/28992</gco:Cha

racterString>

</gmd:code>

<gmd:codeSpace>

<gco:CharacterString>EPSG</gco:CharacterString>

</gmd:codeSpace>






<inspire_sds:SV_ServiceIdentification>

<gmd:citation>

<gmd:CI_Citation>

<gmd:title>

<gco:CharacterString>Geo 3D Model

service</gco:CharacterString>

</gmd:title>

<gmd:date>

<gmd:CI_Date>

<gmd:date>



2015-11-15 Page 89 of 98

</gmd:date>

<gmd:dateType>



CI_DateTypeCode"


</gmd:dateType>

</gmd:CI_Date>

</gmd:date>

</gmd:CI_Citation>

</gmd:citation>

<gmd:abstract>

<gco:CharacterString>This Spatial Data Service supports various

operations on the Digital Subsurface Models (Regis, DGM and GeoTop)

provided by the Geological Survey of the Netherlands. There is for example

an operation to create a â€œvirtual boreholeâ€• through one of the

subsurface models for any given location in the Netherlands. The result can

either be returned as Xml data or as a graphical representation. There is

also supported for creating a VerticalSection a depthSection and many

others. All operations and returned values are in the EPSG:28992 (RDNew)

coordinate reference system. The models have a resolution of 100x100 meters

horizontally and have varying vertical resolutions. </gco:CharacterString>

</gmd:abstract>




<gco:CharacterString>Geological Survey of the



<gmd:contactInfo>

<gmd:CI_Contact>

<gmd:address>

<gmd:CI_Address>




</gmd:CI_Address>

</gmd:address>

</gmd:CI_Contact>

</gmd:contactInfo>

<gmd:role>

<gmd:CI_RoleCode



</gmd:role>



<gmd:descriptiveKeywords>

<gmd:MD_Keywords>

<gmd:keyword>

<gco:CharacterString>infoCoverageAccessService</gco:CharacterString>

</gmd:keyword>

<gmd:keyword>

<gco:CharacterString>subsurface</gco:CharacterString>

</gmd:keyword>

<gmd:keyword>

<gco:CharacterString>geology</gco:CharacterString>

</gmd:keyword>


2015-11-15 Page 90 of 98

<gmd:keyword>

<gco:CharacterString>Netherlands</gco:CharacterString>

</gmd:keyword>

<gmd:keyword>

<gco:CharacterString>3D model</gco:CharacterString>

</gmd:keyword>

</gmd:MD_Keywords>

</gmd:descriptiveKeywords>



<gmd:useLimitation>

<gco:CharacterString>Creative Commons Free

Culture.</gco:CharacterString>






<gmd:useLimitation>

<gmx:Anchor

xlink:href="http://creativecommons.org/licenses/by/3.0/deed.nl">Creative

Commons - Attribution 3.0 Unported</gmx:Anchor>









MD_RestrictionCode"

codeListValue="otherRestrictions">otherRestrictions</gmd:MD_RestrictionCode

>



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




<srv:serviceType>

<gco:LocalName>other</gco:LocalName>

</srv:serviceType>

<srv:extent>

<gmd:EX_Extent>

<gmd:geographicElement>

<gmd:EX_GeographicBoundingBox>

<gmd:westBoundLongitude>


</gmd:westBoundLongitude>

<gmd:eastBoundLongitude>


</gmd:eastBoundLongitude>

<gmd:southBoundLatitude>


</gmd:southBoundLatitude>

<gmd:northBoundLatitude>


</gmd:northBoundLatitude>

</gmd:EX_GeographicBoundingBox>

</gmd:geographicElement>


2015-11-15 Page 91 of 98

</gmd:EX_Extent>

</srv:extent>

<srv:extent>

<gmd:EX_Extent>



<gmd:temporalElement>

<gmd:EX_TemporalExtent>

<gmd:extent>

<gml:TimeInstant gml:id="myid">

<gml:timePosition>2001</gml:timePosition>

</gml:TimeInstant>

</gmd:extent>

</gmd:EX_TemporalExtent>

</gmd:temporalElement>

</gmd:EX_Extent>

</srv:extent>

<srv:couplingType gco:nilReason="missing"/>



<srv:operationName>



<srv:DCP>

<srv:DCPList codeList="http://someurl#DCPList"

codeListValue="HTTPGet"/>

</srv:DCP>

<srv:parameters>

<srv:SV_Parameter>

<srv:name>

<gco:aName>


</gco:aName>

<gco:attributeType>

<gco:TypeName>

<gco:aName>


</gco:aName>

</gco:TypeName>


</srv:name>

<srv:direction>


</srv:direction>

<srv:optionality>


</srv:optionality>

<srv:repeatability>



<srv:valueType>

<gco:TypeName>

<gco:aName>

<gco:CharacterString>string</gco:CharacterString>

</gco:aName>

</gco:TypeName>

</srv:valueType>

</srv:SV_Parameter>

</srv:parameters>


2015-11-15 Page 92 of 98

<srv:parameters>

<srv:SV_Parameter>

<srv:name>

<gco:aName>


</gco:aName>

<gco:attributeType>

<gco:TypeName>

<gco:aName>


</gco:aName>

</gco:TypeName>


</srv:name>

<srv:direction>


</srv:direction>

<srv:optionality>


</srv:optionality>

<srv:repeatability>



<srv:valueType>

<gco:TypeName>

<gco:aName>


</gco:aName>

</gco:TypeName>

</srv:valueType>

</srv:SV_Parameter>

</srv:parameters>

<srv:parameters>

<srv:SV_Parameter>

<srv:name>

<gco:aName>


</gco:aName>

<gco:attributeType>

<gco:TypeName>

<gco:aName>


</gco:aName>

</gco:TypeName>


</srv:name>

<srv:direction>


</srv:direction>

<srv:optionality>


</srv:optionality>

<srv:repeatability>



<srv:valueType>


2015-11-15 Page 93 of 98

<gco:TypeName>

<gco:aName>


</gco:aName>

</gco:TypeName>

</srv:valueType>

</srv:SV_Parameter>

</srv:parameters>

<srv:parameters>

<srv:SV_Parameter>

<srv:name>

<gco:aName>


</gco:aName>

<gco:attributeType>

<gco:TypeName>

<gco:aName>


</gco:aName>

</gco:TypeName>


</srv:name>

<srv:direction>


</srv:direction>

<srv:optionality>


</srv:optionality>

<srv:repeatability>



<srv:valueType>

<gco:TypeName>

<gco:aName>

<gco:CharacterString>int</gco:CharacterString>

</gco:aName>

</gco:TypeName>

</srv:valueType>

</srv:SV_Parameter>

</srv:parameters>

<srv:parameters>

<srv:SV_Parameter>

<srv:name>

<gco:aName>


</gco:aName>

<gco:attributeType>

<gco:TypeName>

<gco:aName>


</gco:aName>

</gco:TypeName>


</srv:name>

<srv:direction>


2015-11-15 Page 94 of 98


</srv:direction>

<srv:optionality>


</srv:optionality>

<srv:repeatability>



<srv:valueType>

<gco:TypeName>

<gco:aName>

<gco:CharacterString>AvailableCoordinateSystemType</gco:CharacterString>

</gco:aName>

</gco:TypeName>

</srv:valueType>

</srv:SV_Parameter>

</srv:parameters>

<srv:connectPoint>


<gmd:linkage>



</gmd:linkage>


</srv:connectPoint>



<srv:operatesOn xlink:href="http://www.dinoservices.nl"/>


<gmd:MD_Resolution>

<gmd:equivalentScale>

<gmd:MD_RepresentativeFraction>

<gmd:denominator>

<gco:Integer>1</gco:Integer>

</gmd:denominator>

</gmd:MD_RepresentativeFraction>

</gmd:equivalentScale>




<gmd:MD_Resolution>

<gmd:distance>

<gco:Distance uom="m">1</gco:Distance>

</gmd:distance>



<inspire_sds:qualityOfService>



<inspire_sds:SV_QualityOfServiceCriteria>performance</inspire_sds:SV_Qual

ityOfServiceCriteria>


<inspire_sds:unit>

<gco:CharacterString>seconds</gco:CharacterString>

</inspire_sds:unit>

<inspire_sds:value>



2015-11-15 Page 95 of 98



<gco:CharacterString>Average response time in

seconds</gco:CharacterString>





<inspire_sds:SV_QualityOfServiceCriteria>availability</inspire_sds:SV_Qua

lityOfServiceCriteria>


<inspire_sds:unit>

<gco:CharacterString>percentage of time</gco:CharacterString>

</inspire_sds:unit>

<inspire_sds:value>




<gco:CharacterString>Availability on yearly basis, expressed

as percentage of time</gco:CharacterString>





<inspire_sds:SV_QualityOfServiceCriteria>capacity</inspire_sds:SV_Quality

OfServiceCriteria>


<inspire_sds:unit>

<gco:CharacterString>number of requests per

second</gco:CharacterString>

</inspire_sds:unit>

<inspire_sds:value>

<gco:CharacterString>20</gco:CharacterString>



<gco:CharacterString>Maximum number of simultaneous requests

per second meeting the performance criteria</gco:CharacterString>



</inspire_sds:qualityOfService>

<inspire_sds:category>invocable</inspire_sds:category>

</inspire_sds:SV_ServiceIdentification>






<gmd:onLine>


<gmd:linkage>

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


</gmd:linkage>

<gmd:function>




2015-11-15 Page 96 of 98


codeListValue="accessPoint-selfDescribing">accessPoint-

selfDescribing</gmd:CI_OnLineFunctionCode>

</gmd:function>


</gmd:onLine>

<gmd:onLine>


<gmd:linkage>

<gmd:URL>http://link-to/get-service-metadata</gmd:URL>

</gmd:linkage>

<gmd:function>




codeListValue="providesServiceMetadata">providesServiceMetadata</gmd:CI_OnL

ineFunctionCode>

</gmd:function>


</gmd:onLine>







<gmd:scope>

<gmd:DQ_Scope>

<gmd:level>

<gmd:MD_ScopeCode



</gmd:level>

</gmd:DQ_Scope>

</gmd:scope>

<gmd:report>



<gmd:result>



<gmd:specification>

<gmd:CI_Citation>

<gmd:title>


</gmd:title>

<gmd:date>

<gmd:CI_Date>

<gmd:date>


</gmd:date>

<gmd:dateType>



CI_DateTypeCode"


</gmd:dateType>

</gmd:CI_Date>


2015-11-15 Page 97 of 98

</gmd:date>

</gmd:CI_Citation>

<gmd:CI_Citation> <gmd:title> <gco:CharacterString>Spatial Data Service

Regulation</gco:CharacterString> </gmd:title> <gmd:date> <gmd:CI_Date> <gmd:date> <gco:Date>2014-02-21</gco:Date> </gmd:date> <gmd:dateType> <gmd:CI_DateTypeCode codeList

http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml#CI_DateTyp

eCode" codeListValue="publication">publication</gmd:CI_DateTypeCode> </gmd:dateType> </gmd:CI_Date> </gmd:date> </gmd:CI_Citation>


<gmd:explanation>



</gmd:explanation>

<gmd:pass>


</gmd:pass>


</gmd:result>


</gmd:report>

<gmd:report>



<gmd:result>



<gmd:specification>

<gmd:CI_Citation>

<gmd:title>


</gmd:title>

<gmd:date>

<gmd:CI_Date>

<gmd:date>


</gmd:date>

<gmd:dateType>



CI_DateTypeCode"


</gmd:dateType>

</gmd:CI_Date>

</gmd:date>

</gmd:CI_Citation>



2015-11-15 Page 98 of 98

<gmd:explanation>



</gmd:explanation>

<gmd:pass>


</gmd:pass>


</gmd:result>


</gmd:report>

<gmd:report>



<gmd:result>



<gmd:specification>

<gmd:CI_Citation>

<gmd:title>


</gmd:title>

<gmd:date>

<gmd:CI_Date>

<gmd:date>


</gmd:date>

<gmd:dateType>



CI_DateTypeCode"


</gmd:dateType>

</gmd:CI_Date>

</gmd:date>

</gmd:CI_Citation>


<gmd:explanation>



</gmd:explanation>

<gmd:pass gco:nilReason="unknown">

</gmd:pass>


</gmd:result>


</gmd:report>



</gmd:MD_Metadata>