From Geostandards

The aim of the Technical Guidelines based on EN ISO 19115 and EN ISO 19119 is to define how the INSPIRE Implementing Rules for Metadata can be implemented using EN ISO 19115 and EN ISO 19119. The following subsections specify the encoding for each INSPIRE metadata element as per ISO 19115 and ISO 19119 accordingly.

This section explains in detail the structure and definition of the document "INSPIRE Metadata Implementing Rules: Technical Guidelines based on EN ISO 19115 and EN ISO 19119", see Technical Guidelines based on EN ISO 19115 and EN ISO 19119. After reading this section it should be clear, how to read and understand the guideline document. This section does not address every aspect of the guidelines but aims to give a detailled overview. To implement the INSPIRE metadata as per ISO 19000 series based standards, please refer directly to the Technical guidelines.

Contents 1 Normative references 2 INSPIRE profile of ISO 19115 and ISO 19119 2.1 ISO Core Elements 2.2 INSPIRE specific constraints 2.3 INSPIRE specific extensions 2.3.1 Spatial data service type 2.3.2 Classification of spatial data services 3 INSPIRE basic element mapping 4 INSPIRE detailed element mapping

Normative references

These are the referenced document that are mandatory within the context of the Technical Guidelines for ISO 19115/19119. The most important are, among others:

• EN ISO 19115:2005, Geographic information - Metadata
• ISO 19115/Cor.1:2006, Geographic information – Metadata, Technical Corrigendum 1
• ISO 19119:2005, Geographic information - Services
• ISO 19119:2005/Amd 1:2008, Extensions of the service metadata model
• ISO/TS 19139:2007, Geographic information - Metadata – XML Schema Implementation
• CSW2 AP ISO, OpenGIS Catalogue Services Specification 2.0.2 - ISO Metadata Application Profile, Version 1.0.0, OGC 07-045, 2007

INSPIRE profile of ISO 19115 and ISO 19119

The Technical Guidelines for ISO 19115/19119 define a profile of ISO 19115 and ISO 19119 in that the cardinalities of relevant elements are tightend with respect to the INSPIRE requirements. This is sometimes also called a level-0 profile.
In contrast, no extension (e.g. new data types or properties) have been specified for INSPIRE.

This means that any implementation of INSPIRE based on the Technical Guidelines for ISO 19115/19119 is always compliant with the underlying standards defined by the normative references section.

ISO Core Elements

To identify the specific differences between INSPIRE and pure EN ISO 19115/EN ISO 19119 at a glance, the Technical Guidelines for ISO 19115/19119 compares the core requirements of ISO 19115 (see Table 3 in 6.5 of ISO 19115:2003) to the requirements of INSPIRE for spatial dataset and spatial dataset series as defined in the Implementing Rules for Metadata.

dataset/series

service

INSPIRE specific constraints

Hence INSPIRE metadata according to the Technical Guidelines for ISO 19115/19119 is based on an ISO profile, a number of INSPIRE specific constraints have to be met. The following list shows INSPIRE constraints that are applicable to an ISO 19115/ISO 19119 metadata set (i.e. an instance of MD_Metadata) describing a resource.

1. MD_Metadata.language is mandatory
2. MD_Metadata.hierarchyLevel is mandatory
3. INSPIRE only considers the first instance of MD_Metadata.hierarchyLevel (i.e. MD_Metadata.hierarchyLevel[1]) when there are many
4. If the value of MD_Metadata.hierarchyLevel[1] is not service, dataset or series, the metadata set is out of scope of the directive
5. When there are many instances of MD_Metadata.identificationInfo, only the first one (i.e. MD_Metadata.identificationInfo[1]) concerns the current INSPIRE Resource
6. INSPIRE only considers the instance of MD_Metadata.dataQualityInfo applicable to the whole resource
7. There shall not be more than one instance of MD_Metadata.identificationInfo[1].MD_Identification.citation.CI_Citation.date declared as a creation date (i.e. CI_Date.dateType having the creation value)
8. MD_Metadata.identificationInfo[1].MD_DataIdentification.citation.CI_Citation.identifier is mandatory for metadata sets related to spatial dataset and spatial dataset series
9. The data type of MD_Metadata.identificationInfo.MD_DataIdentification.language is the codelist LanguageCode from ISO/TS 19139
10. There is at least one instance of MD_Metadata.identificationInfo[1].MD_DataIdentification.extent defining the geographic location of the resource as a geographic bounding box (i.e. an instance of EX_GeographicBoundingBox or one of its subclasses).
11. MD_Metadata.identificationInfo[1].SV_ServiceIdentification.operatesOn shall be instantiated by reference
12. There shall be at least one instance of MD_Metadata.identificationInfo[1].MD_Identification.resourceConstraints
13. The coordinates of the bounding boxes (instance of EX_GeographicBoundingBox) shall be expressed in any geographic coordinate reference system with the Greenwich Prime Meridian
14. For datasets and series: MD_Metadata.identificationInfo[1].MD_DataIdentification.pointOfContact[1].CI_ResponsibleParty.organisationName and MD_Metadata.identificationInfo[1].MD_DataIdentification.pointOfContact[1].CI_ResponsibleParty.contactInfo.CI_Contact.address.CI_Address.electronicMailAddress are mandatory. For services these elements are also mandatory but they are referred as follows: MD_Metadata.identificationInfo[1].SV_ServiceIdentification.pointOfContact[1].CI_Resp onsibleParty.organisationName and MD_Metadata.identificationInfo[1].SV_ServiceIdentification.pointOfContact[1].CI_Resp onsibleParty.contactInfo.CI_Contact.address.CI_Address.electronicMailAddress.
15. MD_Metadata.contact[1].CI_ResponsibleParty.organisationName and MD_Metadata.contact[1].CI_ResponsibleParty.contactInfo.CI_Contact.address.CI_Add ress.electronicMailAddress are mandatory.
16. The value of MD_Metadata.contact[1].CI_ResponsibleParty.role.CI_RoleCode shall be pointOfContact.
17. For datasets and series at least one keyword of GEMET thesaurus shall be documented using MD_Metadata.identificationInfo[1].MD_DataIdentification.descriptiveKeywords.
18. For services at least one keyword of Part D.4 of INSPIRE shall be documented using MD_Metadata.identificationInfo[1].SV_ServiceIdentification.descriptiveKeywords

INSPIRE specific extensions

As pointed out before, the INSPIRE profile does not extend the ISO 19115/19119 model. However, some domain specific values need to be extended to meet the requirements of the INSPIRE Directive. The extensions to domain values are defined as follows:

Spatial data service type

For spatial data service types, it is mandated by the Implementing Rules for Metadata to use the value domain of Part D 3. This information is handled using the serviceType attribute (See 2.3.2) of the class SV_ServiceIdentification (See ISO 19119).

INSPIRE defines the values of the serviceType property of the class SV_ServiceIdentification (See ISO 19119). This list complies with the value domain of Part D 3 of the INSPIRE metadata regulation. See Spatial data service types for the domain values accordingly.

Classification of spatial data services

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

The detailed list can be found here: Classification of spatial data services

INSPIRE basic element mapping

The mapping part of the ISO Guidelines is the most important one when it come to implement INSPIRE metadata element. Every single INSPIRE metadata element is mapped to a specific ISO element; any changes that apply to a specific mapping (e.g. extended value domains) will be indicated and examples for valid values will be given to clarify the encoding of each element.

With the example of the INSPIRE element Unique Resource Identifier the next figure depicts how the mapping tables are to be read.

An additional important point is how the XPath of each element is encoded. The ISO guidelines use a very compact notation which allows many defaults and abbreviations for common cases. The simplest XPath takes a form such as /A/B/C which selects C elements that are children of B elements that are children of the A element that forms the outermost element of the model.

More complex expressions can be constructed by specifying an axis other than the default 'child' axis, a node test other than a simple name, or predicates, which can be written in square brackets after any step. The main rules are the following ones:

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

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

The following list refers to the mapping for each INSPIRE metadata element as defined by the Technical Guidelines for ISO 19115/19119. Please note that the description is an overview of the mapping. For a detailed insight it is recommended to refer to the document directly (Technical Guidelines based on EN ISO 19115 and EN ISO 19119).

Identification Resource title Resource abstract Resource type Resource locator Unique resource identifier Coupled resource Resource language Classification of spatial data and services Topic category Spatial data service type Keyword Keyword value Originating controlled vocabulary

Geographic location Geographic bounding box Temporal reference Temporal extent Date of publication Date of last revision Date of creation Quality and validity Lineage Spatial resolution Conformity Degree Specification

Constraints related to access and use Limitations on public access Conditions applying to access and use Responsible organisation Responsible party Responsible party role Metadata on metadata Metadata point of contact Metadata date Metadata language

INSPIRE detailed element mapping

This section of the guidelines defines a set of template instances of ISO 19115 and ISO 19119 classes. It defines which properties are relevant for an INSPIRE Metadata Set and the adjacent INSPIRE elements defined in the basic mapping section.

A lot of additional information concerning the relationship between INSPIRE elements and further relevant ISO elements is provided in a note section.

The template only shows the properties in the scope of the INSPIRE metadata elements, which encompass the mandatory properties of ISO 19115 and ISO 19119. The other optional properties of ISO 19115 are not described, but can be present in a real instance.

Additional properties defined in a profile of ISO 19115 or ISO 19119 compliant with the INSPIRE metadata elements can be expressed but are not documented in this section.

← previous

Infrastructure for Spatial Information in the European Community (INSPIRE)

next →