INSPIRE Spatial Data Services
Total Page：16
File Type：pdf, Size：1020Kb
INSPIRE spatial data services
Metadata elements table
(copy of 4.2 TG SDS)
1.1.1 Resource locator function code
The Resource Locator metadata element set out in Regulation (EC) No 1205/2008 shall also contain all access points from the spatial data service provider and these access points shall be unambiguously identified as such. This information wiil be handled extending/replacing the CI_OnlineFunctionCode (See Error: Reference source not found) with a new codelist;.
CI_OnlineFunctionCode <
Name Description accessPoint Used to describe an access point of the service accessPoint-selfDescribing Used to describe an access point of the service that describe itself in a machine readable format (e.g. WSDL) providesServiceMetadata Used to specify an address to a document that describe the service metadata (such as GetCapabilities or a WSDL containing a reference to the getCapabilities operation) Used to directly call an operation provided by a spatial data endPoint service information Used to call online information about the resource
1.2 Metadata for interoperable Spatial data services
1.2.1 Introduction
The following tables describe the mapping between the metadata elements of interoperable INSPIRE spatial data services (SDS), as defined in the INSPIRE Spatial data services Regulation (EU) No 1312/2014, and ISO 19115/ISO 19119. They are additional to the metadata elements for services as described here before in chapter 2. The interoperable SDS are divided into three different categories depending on level of interoperability; Invocable spatial data service, Interoperable spatial data service and Harmonised spatial data service. The INSPIRE obligation / condition in the tables contains the categorie for which the metadata shall be provided.
1.2.2 Category
This is a citation of the status of the spatial data service versus invocability. The existing conformance report metadata elements are used for this. In those elements the conformance levels for SDS category, invocable, interoperable or harmonised shall be reported, according to the different conformance levels of the data specifications.
TG Requirement 1 An invocable spatial data services shall be conform to one of the conformance levels; invocable, interoperable or harmonised 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] 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.) 359. CI_Citation Domain http://inspire.ec.europa.eu/conformanceClass/MD/1.4/SDS _Invocable http://inspire.ec.europa.eu/conformanceClass/MD/1.4/SDS _Interoperable http://inspire.ec.europa.eu/conformanceClass/MD/1.4/SDS _Harmonised Example xlink:href="http://inspire.ec.europa.eu/conformanceClass/ MD/1.4/SDS_Invocable" Comments The conformance class shall be referenced with a xlink.
The metadata element degree contains the degree of conformity of the spatial data service to the conformance class.
Metadata element name Degree Reference COMMISSION REGULATION (EU) No 1089/2010, Annex V, Part B 1 Definition Indication of the conformance result ISO 19115 number and name 132. pass ISO/TS 19139 path dataQualityInfo/*/report/*/result/*/pass INSPIRE obligation / condition Mandatory for invocable spatial data services 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.) Boolean1 Domain true if conformant Example true Comments
Example of XML encoding:
1 2 …
1.2.3 Resource locator
The Resource Locator metadata element set out in Regulation (EC) No 1205/2008 shall also contain all access points from the spatial data service provider and these access points shall be unambiguously identified as such, using the resource locator function code
The access point of the service, is an Internet address containing a detailed description of a spatial data service, including a list of endpoints to allow an automatic execution.
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 obligation / condition Mandatory for invocable spatial data services INSPIRE multiplicity [1..*]
3 Data type (and ISO 19115 no.) URL Domain URL (IETF RFC1738 and IETF RFC 2056) Example http://www.dinoservices.nl/geo3dmodelwebservices- 1/Geo3DModelService Comments
TG Requirement 2 An invocable spatial data service shall have at least one resource l ocator that is an access point.
TG Requirement 3 The Resource Locator metadata element set out in Regulation (EC) No 1205/2008 shall also contain all access points from the spatial d ata service provider and these access points shall be unambiguousl y identified as such.
Metadata element name Function code Reference COMMISSION REGULATION (EU) No 1089/2010, Annex V, Part D 1 Definition Code for function performed by the online resource ISO 19115 number and name 402. function ISO/TS 19139 path distributionInfo/*/transferOptions/*/onLine/*/function INSPIRE obligation / condition Mandatory for invocable spatial data services INSPIRE multiplicity [1..*] Data type (and ISO 19115 no.) CI_OnLineFunctionCode Domain Codelist, see section 1.3.2 Example accessPoint Comments
Example of XML encoding:
1.2.4 Specification
The Specification metadata element set out in Regulation (EC) No 1205/2008 shall also 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.
TG Requirement 4 Invocable spatial data services contains the specification metad ata element set out in Regulation (EC) No 1205/2008 that shall a lso refer to or contain technical specifications (such as INSPIRE technical guidance but not only), to which the invocable spatial d ata service fully conforms, providing all the necessary technical ele ments (human, and wherever relevant, machine readable) to allow it s invocation.’
TG Requirement 5 Invocable spatial data services are in conformity with a documen ted and publicly available set of technical specifications providin g the information necessary for its execution,
The metadata element specification contains a citation of technical specification (such as INSPIRE technical guidance but not only), to which the invocable spatial data service fully conforms.
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 Reference COMMISSION REGULATION (EU) No 1089/2010, Annex V, Part D 2 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] understood in the context of a conformity statement when reported in the metadata – there may be more than one conformity
5 statement 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 o date: 2005-12-01 Comments
In order to make a reference to or machine-readable, the documentation of the service interface (e.g. WSDL) the element gmx:Anchor could be used instead of gco:CharacterString. The backward compatibility is still valid because the human readable text is kept.
The metadata element degree contains the degree of conformity of the resource to the specification.
Metadata element name Degree Reference COMMISSION REGULATION (EU) No 1089/2010, Annex V, Part D 2 Definition Indication of the conformance result ISO 19115 number and name 132. pass ISO/TS 19139 path dataQualityInfo/*/report/*/result/*/pass INSPIRE obligation / condition Mandatory for invocable spatial data services 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.) Boolean2 Domain true if conformant Example true Comments
Example of XML encoding:
2
6
1.2.5 Coordinate Reference System Identifier
TG Requirement 6 Where appropriate, this is the list of coordinate reference system s supported by the spatial data service. Each supported coordin ate reference system shall be expressed using an identifier.
Description of the coordinate reference system(s) supported in the service.
7 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 [1..*] Data type (and ISO 19115 no.) 186.MD_ReferenceSystem Domain To identify the reference system, the referenceSystemIdentifier
(RS_Identifier) shall be provided. Example referenceSystemIdentifier:
code: 4258
codeSpace: EPSG Comments
TG Recommendation 1 It is recommended to use the http URIs provided by the Open Geos patial Consortium in combination with the coordinate reference syst em identifiers (see in Table 5). These are based on and redirect to t he definition in the EPSG Geodetic Parameter Registry (http://www. epsg-registry.org/). It is therefore recommended the use of “EPSG” as code in the “codeSpace” medatada element.
Example of XML encoding:
1.2.6 Quality of Service This is the minimum quality of service estimated by the spatial data service responsible party and expected to be valid over a period of time. There shall be three quality of service criteria reported to which the measurements refer; availability, performance and capacity. Availability 8 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. TG Requirement 7 This is the minimum quality of service estimated by the spatial d ata service responsible party and expected to be valid over a per iod of time. 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 [3..*] Data type (and ISO 19115 no.) Free text Domain Availability Performance Capacity Example availability Comments DQ_DataQuality/scope/DQ_Scope/level/MD_ScopeCode with the value “service” should be used Metadata element name Description Reference COMMISSION REGULATION (EU) No 1089/2010, Annex VI Part B 4.2.1 Definition Description of the measure ISO 19115 number and name 102. measureDescription ISO/TS 19139 path dataQualityInfo/*/report/DQ_ConceptualConsistency/measureDescripti on INSPIRE obligation / condition Mandatory for interoperable spatial data services INSPIRE multiplicity [1] Data type (and ISO 19115 no.) Free text Domain Example Average response time, expressed as seconds Comments DQ_DataQuality/scope/DQ_Scope/level/MD_ScopeCode with the value “service” should be used Metadata element name Value Reference COMMISSION REGULATION (EU) No 1089/2010, Annex VI Part B 9 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_Quantitativ eResult/value INSPIRE obligation / condition Mandatory for interoperable spatial data services INSPIRE multiplicity [1..*] Data type (and ISO 19115 no.) Record Domain Described in ISO 19103 Example 1 Comments DQ_DataQuality/scope/DQ_Scope/level/MD_ScopeCode with the value “service” should be used 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_Quantit ativeResult/valueUnit INSPIRE obligation / condition Mandatory for interoperable spatial data services INSPIRE multiplicity [1] Data type (and ISO 19115 no.) UnitOfMeasure Domain Described in ISO 19103 Example Example of XML encoding: 10 1.2.7 Conditions applying to access and use 11 Interoperable spatial data services have additional requirements on metadata. The technical restrictions applying to the access and use of the spatial data service shall also be documented in the metadata element “CONSTRAINT RELATED TO ACCESS AND USE” TG Requirement 8 The technical restrictions applying to the access and use of the s patial data service shall be documented in the metadata element “CONSTRAINT RELATED TO ACCESS AND USE” set out in Regulatio n (EC) No 1205/2008. See for the mapping table and the and XML example paragraph 2.9.2 1.2.8 Responsible party Interoperable spatial data services have additional requirements on metadata. The responsible party set out in Regulation (EC) No 1205/2008 shall at least describe the custodian responsible organisation, corresponding to the Custodian responsible party role set out in Regulation (EC) No 1205/2008. TG Requirement 9 The responsible party set out in Regulation (EC) No 1205/2008 shall at least describe the custodian responsible organisation, co rresponding to the Custodian responsible party role set out in Re gulation (EC) No 1205/2008. See for the mapping table and the and XML example paragraph 2.10 1.2.9 Invocation metadata A harmonised spatial data service shall have well documented interfaces and list the end points for each operation to enable machine to machine communication. TG Requirement 10 The invocation metadata element documents the interfaces of th e harmonised spatial data service and lists the end points to ena ble machine-to machine communication. To describe the invocation metadata the ISO 19119 operation metadata elements are used. At least the mandatory ISO elements shall be provided as in the mappings and example here. The XML example also provided additional information in optional metadata elements. SV_OperationMetadata describes the signature of one method provided by the service. There can be for each method an instances of SV_OperationMetadata. Metadata element name operationName Reference COMMISSION REGULATION (EU) No 1089/2010, Annex VII Part B 3 Definition A unique identifier for this interface ISO 19119 number and name Table C2 1. operationName CSW ISO Metadata AP path identificationInfo[1]/*/containsOperations/*/operationName INSPIRE obligation / condition Mandatory for harmonised spatial data services INSPIRE multiplicity [1] 12 Data type (and ISO 19115 no.) CharacterString Domain Example GetSampleColumn Comments Metadata element name DCP Reference COMMISSION REGULATION (EU) No 1089/2010, Annex VII Part B 3 Definition Distributed computing platforms on which the operation has been implemented. ISO 19119 number and name Table C2 2. DCP CSW ISO Metadata AP path identificationInfo[1]/*/containsOperations/*/DCP INSPIRE obligation / condition Mandatory for harmonised spatial data services INSPIRE multiplicity [1..*] Data type (and ISO 19115 no.) DCPlist Domain XML, CORBA, JAVA, COM, SQL, WebServices Example WebServices Comments Metadata element name connectPoint Reference COMMISSION REGULATION (EU) No 1089/2010, Annex VII Part B 3 Definition Handle for accessing the service interface. ISO 19119 number and name Table C2 6. connectPoint CSW ISO Metadata AP path identificationInfo[1]/*/containsOperations/*/connectPoint/*/linkage INSPIRE obligation / condition Mandatory for harmonised spatial data services INSPIRE multiplicity [1..*] Data type (and ISO 19115 no.) Domain Example http://www.dinoservices.nl:80/geo3dmodelwebservices- 1/Geo3DModelService Comments Example of XML encoding: 13 14 … …
15