INSPIRE Rules Identification Data Identification Service Identification Keyword and INSPIRE themes INSPIRE Service taxonomy Geographic location Temporal reference Quality and validity Conformity Constraints related to access and use Responsible organisation Metadata on metadata

Resource title is missing.

Resource title found:

Resource abstract is missing.

Example:
Dataset contains large scale (1:1.000) topography, which covers the whole country.

Resource abstract is :

Resource type is missing or has a wrong value.

Implementing instructions:
The values of MD_ScopeCode in the scope of the directive (See SC4 in 1.2) are:

dataset for spatial datasets;
series for spatial dataset series;
services for spatial data services.

The hierarchyLevel property is not mandated by ISO 19115, but is mandated for conformance to the INSPIRE Metadata Implementing rules (See SC2 in 1.2).

Resource type is:

Unique resource identifier is missing

Implementing instructions
Mandatory for dataset and dataset series.
Example: 527c4cac-070c-4bca-9aaf-92bece7be902

Unique resource identifier is:

Unique resource identifier codespace is:

INSPIRE - ISO topic category is mandatory

The topic categories defined in Part D 2 of the INSPIRE Implementing rules for metadata are derived directly from the topic categories defined in B.5.27 of ISO 19115. INSPIRE Implementing rules for metadata define the INSPIRE data themes to which each topic category is Implementing instructions applicable, i.e., Administrative units (I.4) and Statistical units (III.1) are INSPIRE themes for which the boundaries topic category is applicable. The value of the ISO 19115/ISO 19119 metadata element is the value appearing in the “name” column of the table in B.5.27 of ISO 19115.

ISO topic category is:

INSPIRE theme is mandatory

INSPIRE theme(s) found.

INSPIRE - Geographic bounding box is mandatory

Mandatory for spatial dataset and dataset series.
Conditional for spatial services: Mandatory for services with an explicit geographic extent

Implementing instructions

There are as many bounding boxes defining the geographic location of the resource as instances of identificationInfo[1]/*/extent/*/geographicElement having the westBoundLongitude, eastBoundLongitude, southBoundLatitude and northBoundLatitude properties. The four coordinates of the bounding box originate from the same instance.
The bounding box shall be as small as possible.
If the bounding box crosses the 180 meridian, then the value of the westBoundLongitude will be greater than the eastBoundLongitude value.
The coordinates of the bounding box are expressed in any geographic coordinate reference system with a Greenwich Prime Meridian (See SC13 in 1.2).

NorthBoundLongitude is missing or has wrong value

SouthBoundLongitude is missing or has wrong value

EastBoundLongitude is missing or has wrong value

WestBoundLongitude is missing or has wrong value

NorthBoundLongitude found:

SouthBoundLongitude found:

EastBoundLongitude found:

WestBoundLongitude found:

INSPIRE - Temporal reference is mandatory

No instance of Temporal reference has been found. Implementing instructions
Each instance of the temporal extent may be an interval of dates or an individual date. The overall time period covered by the content of the resource may be composed of one or many instances.
Or a reference date of the cited resource (publication, last revision or creation).
Example: From 1977-03-10T11:45:30 to 2005-01-15T09:10:00

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)

Temporal extent (begin) found:

Temporal extent (end) found:

Date of publication of the resource found:

Date of creation of the resource found:

Date of revision of the resource found:

INSPIRE - Lineage is mandatory

Mandatory for spatial dataset and spatial dataset series.
Not applicable to services.

In addition to general explanation of the data producer’s knowledge about the lineage of a dataset it is possible to put data quality statements here.
A single ISO 19115 metadata set may comprise more than one set of Implementing instructions quality information, each of them having one or zero lineage statement. There shall be one and only one set of quality information scoped to the full resource and having a lineage statement (See SC6 in 1.2).
Example: Dataset has been digitised from the standard 1:5.000 map

Lineage is set.

INSPIRE - Conformity is mandatory (in DQ_DomainConsistency.result.DQ_ConformanceResult)

Implementing instructions
The first two degrees of conformity defined in Part D 5 of the INSPIRE Implementing rules for metadata map to two values of the Boolean domain of ISO 19115. The last value corresponds to the case where no conformance statement is expressed in the metadata for the related specification.
Example: title “INSPIRE Implementing rules laying down technical arrangements for the interoperability and harmonisation of administrative boundaries”.

The degree of conformity of the resource has not yet been evaluated.

Degree of conformity found:

Specification:

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

Limitation on public access (accessConstraints) found:

Limitation on public access (classification) found:

There shall be at least one instance of 'accessConstraints'

instance(s) of 'accessConstraints' found.

The value of 'accessConstraints' must be 'otherRestrictions', if there are instances of 'otherConstraints' expressing limitations on public access. Check access constraints list and other constraints text field.

Limitation on public access (otherConstraints) found:

Conditions applying to access and use is missing

Conditions applying to access and use found:

INSPIRE - Conditions for access and use is mandatory

INSPIRE - Limitations on public access is mandatory

INSPIRE - Responsible organisation for the resource is mandatory

Relative to a responsible organisation, but there may be many responsible organisations for a single resource. Organisation name and email are required.
See identification section / point of contact.

Responsible organisation for the resource found.

Organisation name and email not found for responsible organisation.

Organisation name and email found for :

INSPIRE - Metadata point of contact is mandatory

Implementing instructions:
The role of the responsible party serving as a metadata point of contact is out of scope of the INSPIRE Implementing Rules, but this property is mandated by ISO 19115. Its value can be defaulted to pointOfContact.
See metadata section.

Contact role is empty.

Metadata point of contact found.

Organisation name and email not found metadata point of contact.

Organisation name and email found for :

INSPIRE - Metadata language is mandatory

The language property is not mandated by ISO 19115, but is mandated for conformance to the INSPIRE Metadata Implementing rules

Metadata language is :

Metadata date stamp is missing

Metadata date stamp is :

INSPIRE (service) - Coupled resource is mandatory if linkage to data sets on which the service operates are available

Implementing instructions
Not applicable to dataset and dataset series
Conditional to services: Mandatory if linkage to datasets on which the service operates are available.

The property shall be implemented by reference (See SC11 in 1.2) and the MD_DataIdentification object reference value is the code of the Coupled resource metadata element.
For consistency, the code of the Couple resource metadata element should also be the code of one of the Unique resource identifiers of the corresponding coupled resource.

Coupled resources found:

INSPIRE - Resource locator is mandatory if linkage is available

See advanved view / distribution section / only resource element.
Implementing instructions:

Specify a valid URL to the resource. If no direct link to a resource is available, provide link to a contact point where more information about the resource is available.
For a service, the Resource Locator might be one of the following:

A link to the service capabilities document;
A link to the service WSDL document (SOAP Binding);
A link to a web page with further instructions
A link to a client application that directly accesses the service

Resource locator found:

INSPIRE - There may be zero or one condition applying to access and use

Access constraints applied to assure the protection of privacy or intellectual property, and any special restrictions or limitations on obtaining the resource.
Example: intellectualPropertyRights (rights to financial benefit from and control of distribution of non-tangible property that is a result of creativity).
Classification: Example: restricted (not for general disclosure)
Use limitation: Example: not to be used for navigation

INSPIRE - The value of accessConstraints is otherRestrictions, if and only if they are instances of otherConstraints expressing limitations on public access

INSPIRE (datasets and series) - Resource language is mandatory if the resource includes textual information

An instance of the language property is mandated by ISO 19115 ; it can be defaulted to the value of the Metadata Implementing instructions Language when the dataset or the dataset series does not contain textual information.
Implementing instructions:
Codelist (See ISO/TS 19139) based on alpha-3 codes of ISO 639-2.

Resource language is:

INSPIRE - Spatial resolution is mandatory if an equivalent scale or a resolution distance can be specified

Implementing instructions:

Each spatial resolution is either an equivalent scale OR a ground sample distance.
When two equivalent scales or two ground sample distances are expressed, the spatial resolution is an interval bounded by these two values.

Example: 5000 (e.g. 1:5000 scale map)

Spatial resolution is set.

[ISO19119 for services] - OperationName is mandatory

Missing service taxonomy information (select on or more keyword from "inspire-service-taxonomy.rdf" thesaurus)

service taxonomy classification defined.

[ISO19119 for services] - ConnectPoint is mandatory

[ISO19119 for services] - ServiceType is mandatory

Mandatory for services.
Not applicable to dataset and dataset series
Example: 'view', 'discovery', 'download', 'transformation', 'invoke', 'other'

Service type is: