Copy to the javadoc some relevant precision from INSPIRE


The implementing instructions provided by INSPIRE for some metadata elements may be worth to appear in the Javadoc. Most text below are copied from the "implementing instructions" boxes which appear in section 2, "Basic mapping".

2.2 Identification

2.2.4 Resource locator: CI_OnlineResource.linkage

  • 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

2.2.5 Unique resource identifier: MD_Identifier.code

If a value for a codeSpace is provided, then the data type for the identifier should be RS_Identifer, which is substitutable for the usual MD_Identifier.

2.4 Keyword

2.4.1 Keyword value: MD_Keywords.thesaurusName

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

2.4.2 Originating controlled vocabulary: MD_Keywords.thesaurusName

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 SV_ServiceIdentification.descriptiveKeywords property.


2.5.1 Geographic bounding box: EX_GeographicBoundingBox

  • There are as many bounding boxes defining the geographic location of the resource as instances of identificationInfo.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.
    * The bounding box shall be expressed in decimal degree with a precision of at least 2 decimals
    * If the bounding box crosses the 180 meridian, then the value of the westBoundLongitude will be greater than the
    eastBoundLongitude value.
    * The coordinates of the bounding box are expressed in any geodetic coordinate reference system with a Greenwich Prime Meridian.

2.6 Temporal reference

2.6.1 Temporal extent: EX_TemporalExtent.extent

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.

2.7.1 Lineage: LI_Lineage

  • Apart from describing the process history, the overall quality of the dataset (series) should be included in the Lineage metadata element. This statement should contain any quality information required for interoperability and/or valuable for use and evaluation of the data set (series).
    * A single ISO 19115 metadata set may comprise more than one set of 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.

2.7 Quality and validity

2.7.2 Spatial resolution: MD_Resolution

  • 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.
    * When two equivalent scales or two ground sample distances are expressed, the spatial resolution is an interval bounded by these two values.
    * For services, it is not possible to express the restriction of a service concerning the spatial resolution in the current version of ISO 19119. While the problem is addressed by the standardization community, spatial resolution restrictions for services shall be expressed in the Abstract.

2.9.1 Limitations on public access: MD_Constraints

  • Depending on the instance of MD_Constraints:

  • There may be no limitation on public access;
    * There may be only a classification property when expressing a security constraint (i.e., this is an instance of MD_SecurityConstraints or one of its subclasses);
    * There may be one or more instances of the accessConstraints property, possibly associated with one or more instances of otherRestrictions property (i.e, this is an instance of MD_LegalConstraints);

  • If the value of accessConstraints is otherRestrictions there shall be instances of otherConstraints expressing limitations on public access. This is because the limitations on public access required by the INSPIRE Directive may need the use of free text, and otherConstraints is the only element allowing this data type.

2.9.2 Conditions applying to access and use: MD_Constraints.useLimitation

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.

ISO 19139 and multilingual metadata

An optional but repeatable attribute "locale" has been added to the class MD_Metadata. Two cases are to be considered:

  • When this attribute is not implemented, the metadata set is expected to be monolingual: the language of the metadata is defined by the language attribute of MD_Metadata.
    * When this attribute is implemented, each instance represents a locale (language, country and character encoding) in which the metadata elements may be translated. The language attribute still defines the default language of the metadata, i.e. the language in which all the metadata elements are expressed. Then each metadata element can be translated in some of the locales define for the metadata set.

Other clarification

From Inspire A.6: "The metadata elements which may require translations are those of type CharacterString having a free text domain". This is consistent with GeoAPI practice and should be documented in the specification.