INSPIRE

Revision as of 13:37, 23 November 2016

Definition

1. INSPIRE is "an EU initiative to establish an infrastructure for spatial information in Europe that is geared to help to make spatial or geographical information more accessible and interoperable for a wide range of purposes supporting sustainable development".

The INSPIRE directive lays down a general framework for a Spatial Data Infrastructure (SDI) for the purposes of European Community environmental policies and policies or activities which may affect the environment. The INSPIRE Directive entered into force on 15 May 2007.

Abbreviation

Synonyms

Superterms

Subterms

Sources

https://en.wikipedia.org/wiki/Infrastructure_for_Spatial_Information_in_the_European_Community

INSPIRE Metadata Implementing Rules

From the Technical Guidelines based on EN ISO 19115 and EN ISO 19119

Conclusion (Page 13):

The conformance of an ISO 19115 metadata set to the ISO 19115 Core does not guarantee the conformance to INSPIRE;
The use of these guideline to create INSPIRE metadata ensures that the metadata is not in conflict with ISO 19115. However, full conformance to ISO 19115 implies the provision of additional metadata elements which are not required by the INSPIRE Implementing Rule on Metadata. Additional metadata elements are required by the INSPIRE Implementing Rules for the Interoperability of Spatial Datasets and Services.

2.2.1 Resource title [Mandatory]

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

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

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

2.2.2 Resource abstract [Mandatory]

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

TG Recommendation 3
The resource abstract is a succinct description that can include:
- A brief summary with the most important details that summarise the data or service
- Coverage: linguistic transcriptions of the extent or location in addition to the bounding box
- Main attributes
- Data sources
- Legal references
- Importance of the work

TG Recommendation 4
Do not use unexplained acronyms.

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

2.2.3 Resource Type [Mandatory]

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

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

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

TG Recommendation 6
The choice between the values should follow these recommendations
- dataset: is an identifiable data that can be accessed separately. A dataset can be a part of a whole (series) or a segregate resource
- series: is a collection of resources or related datasets that share the same product specification
- service: technologies providing availability and access to spatial information, for example, web map services, web feature services, web coverage services, web processing services, catalogue web services, etc

2.2.4 Resource locator

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

TG Requirement 3
If a linkage for data is available, the Resource Locator shall be a valid URL providing one of the following:
- a link to a web with further instructions
- a link to a service capabilities document
- a link to the service WSDL document (SOAP Binding)
- a link to a client application that directly accesses the service

TG Requirement 4
If a linkage for a service is available, the Resource Locator shall be a valid URL providing one of the following:
- a link to a web with further instructions
- a link to a service capabilities document
- a link to the service WSDL document (SOAP Binding)
- a link to a client application that directly accesses the service

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

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

2.2.5 Unique resource identifier [Mandatory]

This element is a value uniquely identifying the resource.

TG Requirement 5
The code property is required (see B.2.7.3 of ISO 19115).

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

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

2.2.6 Coupled resource

If the resource is a spatial data service, this metadata element refers to, where relevant, the target spatial data set(s) of the service. It is implemented by reference, i.e. through a URL that points to the metadata record of the data on which the service operates. It helps therefore linking services to the relevant datasets.

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

2.2.7 Resource language [Mandatory]

It refers to the language(s) used within the resource (dataset, series, or service if relevant).
Example: English - eng [Default] / German - ger / French - fre

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

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

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

2.3.1 Topic category

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

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

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

2.3.2 Spatial data service type

This is a classification to assist in the search of available spatial data services.

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

2.4 Keyword

An INSPIRE Keyword is defined by:

a keyword value (see 2.4.1), which in ISO standard is referred to as “Keyword”;
an optional originating controlled vocabulary (see 2.4.2), which in ISO standard is referred to as “Thesaurus”.
It is possible to add as many keywords as relevant to the resource.

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

TG Requirement 14
If only one keyword is used, then for spatial dataset or spatial dataset series, the keyword:
- shall describe the relevant INSPIRE Spatial Data Theme (as defined in Annex I, II and III of the INSPIRE Directive)
- shall be expressed in the language of the metadata for the 34 INSPIRE Spatial Data Themes (please use the terms in each of the official languages in which the INSPIRE Directive has been translated) or a neutral language values such as a URI.

TG Requirement 15
For spatial services, the keyword:
- shall at least define the category or subcategory of the service using its language neutral name as defined in Part D 4 of the INSPIRE Metadata Regulation 1205/2008/EC - shall be expressed as neutral language values such as the neutral language values defined in Part D.4 of the INSPIRE Metadata Regulation 1205/2008/EC for spatial data services)

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

2.4.1 Keyword value [Mandatory]

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

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

TG Recommendation 12
It is suggested to choose a minimum of two keywords in addition to
the required keyword from the GEMET - INSPIRE themes (for
dataset and dataset series) or the categories from part D 4 of the
INSPIRE Metadata Regulation 1205/2008/EC (for services).
TG Recommendation 13
Ideally, both a code (neutral language value) and a human-readable
label (in any language) should be included in the metadata.

2.4.2 Originating controlled vocabulary

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

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

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

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

2.5.1 Geographic bounding box

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

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

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

2.6 Temporal reference

TG Requirement 22
The INSPIRE Metadata Regulation 1205/2008/EC requires at least one temporal reference chosen from one of these four categories:
- temporal extent
- date of publication
- date of last revision
- date of creation

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

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

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

2.6.1 Temporal extent

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

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

2.6.2 Date of publication

This is the date of publication of the resource when available, or the date of entry into force. There may be more than one date of publication.

2.6.3 Date of last revision

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

2.6.4 Date of creation

This date describes when the resource was created. Date of creation differs from the temporal extent.

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

2.7.1 Lineage

According to the Implementing Rules for Metadata, Lineage is “a statement on process history and/or overall quality of the spatial data set. Where appropriate it may include a statement whether the data set has been validated or quality assured, whether it is the official version (if multiple versions exist), and whether it has legal validity. The value domain of this element is free text.”
The process history may be described by information on the source data used and the main transformation steps that took place in creating the current data set (series).

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

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

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

2.7.2 Spatial resolution

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

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

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

2.8 Conformity

TG Requirement 28
In conformance to INSPIRE Directive 2007/2/EC, the metadata shall include information on the degree of conformity with the implementing rules on interoperability of spatial data sets and services.

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

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

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

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

2.8.1 Degree [Mandatory]

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

2.8.2 Specification [Mandatory]

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

2.9 Constraints related to access and use

ISO 19115 provides a general mechanism for documenting different categories of constraints applicable to the resource (or its metadata).

TG Requirement 30
There shall be at least one ISO 19115 metadata element representing a limitation on public access (see 2.9.1) and one ISO 19115 metadata element representing a condition applying to access and use (see 2.9.2) as part of the different instances of MD_Constraints and its subclasses.
TG Requirement 31
There shall be at least one instance of MD_Constraints or one of its subclasses (See SC12 in Section 1.2) even if there is no limitation on public access or no specific condition applies to access and use of the resource.

2.9.1 Limitations on public access

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

TG Requirement 32
Limitations on public access shall be represented by at least one of these metadata elements:
- MD_LegalConstraints. accessConstraints
- MD_LegalConstraints. otherConstraints
- MD_SecurityConstraints. classification

2.9.2 Conditions applying to access and use [Mandatory]

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

TG Requirement 33
If no conditions apply to the access and use of the resource, ‘no conditions apply’ shall be used. If conditions are unknown, ‘conditions unknown’ shall be used.
TG Requirement 34
Descriptions of terms and conditions, including where applicable, the corresponding fees shall be provided through this element or a link (URL) where these terms and conditions are described.
TG Recommendation 22
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.

2.10 Responsible organisation

Organisation responsible for the establishment, management, maintenance and distribution of spatial data sets and services. A responsible organisation is defined by:
• a responsible party (see 2.10.1);
• and a responsible party role (see 2.10.2).
There may be one to many responsible organisations for a single resource, but the multiplicity of the responsible and its role are expressed relative to a single responsible organisation.

2.10.1 Responsible party [Mandatory]

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

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

TG Requirement 36
See SC14 for more information about elements required for data and services.
TG Recommendation 23
The name of the organization should be given in full, without abbreviations. It is recommended to use institutional email instead of personal emails.

2.10.2 Responsible party role [Mandatory]

This is the role of the responsible organisation.

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

2.11.1 Metadata point of contact [Mandatory]

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

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

TG Requirement 38
The role of the responsible party serving as a metadata point of contact
is out of scope of the INSPIRE Metadata Regulation 1205/2008/EC,
but this property is mandated by ISO 19115. The default value is
pointOfContact. See SC15 and SC16
TG Recommendation 25
The name of the organization should be given in full, without
abbreviations. It is recommended to use institutional email instead of
personal emails.

2.11.2 Metadata date [Mandatory]

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

2.11.3 Metadata language [Mandatory]

This is the language in which the metadata elements are expressed.

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

@@ Line 89: / Line 89: @@
 <br/>
@@ Line 95: / Line 96: @@
 The topic category is a high-level classification scheme to assist in the grouping and topicbased search of available spatial data resources. A correct categorization is very important to help users to search and find the resources they are looking for.<br/>
-'''TG Requirement 10 '''<br/>The topic category has to be filled with a value from the enumeration<br/>MD_TopicCategoryCode (ISO 19115).<br/>
+'''TG Requirement 10 '''<br/>The topic category has to be filled with a value from the enumeration MD_TopicCategoryCode (ISO 19115).<br/>
+'''TG Requirement 11 '''<br/>The value saved in the XML metadata element shall be a language neutral name (see the value appearing in the “name” column of the table in B.5.27 of ISO 19115).<br/>
-'''TG Requirement 11 '''<br/>The value saved in the XML metadata element shall be a language<br/>neutral name (see the value appearing in the “name” column of the<br/>table in B.5.27 of ISO 19115).<br/>
 === 2.3.2 Spatial data service type<br/> ===

Log in / create account

About

Help

Search

Navigation