Overview and generic requirements Table 1 shows the requirements to provide different metadata elements for the different spatial data services conformance classes. For each metadata element that is not already included in [INS MD] or for there are additional requirements, the table contains a reference to the section describing the detailed requirements. Table 1 - Metadata elements mapping. C: conditional (refer to [INS MD] for the conditions), M: Mandatory, =: the obligation is the same as specified in [INS MD] Inspire Metadata element Reference to INSPIRE IRs All SDS Invocable SDS Interoperable SDS Harmonised SDS Resource title [INS MD, Annex B1.1] M = = = Resource abstract [INS MD, Annex B1.2] M = = = Resource Type [INS MD, Annex B1.3] M = = = Resource Locator [INS MD, B1.4] [INS ISDSS, Annex V D1] C M (4.4.2) M (4.4.2) M (4.4.2) Coupled Resource [INS MD, Annex B1.6] C = = = Spatial data service type [INS MD, Annex B2.2] M = = = Keyword value [INS MD, Annex B3.1] M = = = Geographic Bounding Box [INS MD, Annex B4.1] C = = = Temporal extent [INS MD, Annex B5.1] C = = = Date of publication [INS MD, Annex B5.2] C = = = Date of last revision [INS MD, Annex B5.3] C = = = Date of creation [INS MD, Annex B5.4] C = = = Spatial Resolution [INS MD, Annex B6.2] C = = = Specification [INS MD, Annex B7.1] [INS ISDSS, Annex V D2] M M (4.4.3) M (4.4.3) M (4.4.3) Degree [INS MD, Annex B7.2] M M (4.4.3) M (4.4.3) M (4.4.3)
NOTE 3 The INSPIRE multiplicity refers to the Category metadata element. This does not affect the fact that in ISO 19115 more than one conformity statement is allowed. Data type (and ISO 19115 no.) 359. CI_Citation Domain For the title sub-element, the values of the Category code list (section 4.8.3) shall be used. NOTE [ISO 19115] requires a date for the specification. For consistency, it is recommended to use the date of publication of the [INS ISDSS], i.e. 2014-12-11. Example CI_Citation title: invocable () CI_Date date: 2014-12-11 type: publication Comments Example of XML encoding: <gmd:dataQualityInfo> <gmd:DQ_DataQuality> <gmd:scope> <gmd:DQ_Scope> <gmd:level> <gmd:MD_ScopeCode codeListValue="service"/> </gmd:level> </gmd:DQ_Scope> </gmd:scope> ... <gmd:report> <gmd:DQ_DomainConsistency> <gmd:result> <gmd:DQ_ConformanceResult> <gmd:specification> <gmd:CI_Citation> <gmx:Anchor xlink:href=" </gmd:title> <gmd:date> <gmd:CI_Date> <gmd:date> <gco:Date>2014-12-11</gco:Date> </gmd:date> <gmd:dateType> <gmd:CI_DateTypeCode codeList="http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml #CI_DateTypeCode" codeListValue="publication"/> </gmd:dateType> </gmd:CI_Date> </gmd:date>
list for capturing alternate predecessor paths and sets for capturing parallel predecessor paths. The SV_Parameter is used to provide service parameters. 3 - SV_Parameter detail Attribute name / Role name Definition Obligation / Condition Maximum occurrence Attribute class or target class of role Name The name, as used by the service for this parameter. M 1 MemberName Direction Indication if the parameter is an input to the service, an output or both. O 1 ParameterDirection Description A narrative explanation of the role of the parameter O 1 CharacterString Optionality Indication if the parameter is required M 1 CharacterString Repeatability Indication if more than one value of the parameter may be provided. M 1 Boolean ValueType Operation parameters type O N Association Example of scenario 1 XML encoding: <gmd:MD_Metadata … … <gmd:identificationInfo> <srv:SV_ServiceIdentification> … <srv:containsOperations> <srv:SV_OperationMetadata> <srv:operationName> <gco:CharacterString>WSDL</gco:CharacterString> </srv:operationName> <srv:DCP> <srv:DCPList codeListValue=" services</srv:DCPList> </srv:DCP>
DCP List The DCP list is defined in [ISO 19119], to be used for the element “DCP” in the ISO class “SV_OperationMetadata”, required for the INSPIRE harmonized spatial data services. No. ID Textual name Language neutral name Description / definition URI identifier XML XML CORBA CORBA JAVA JAVA COM COM SQL SQL Web services WebServices Coordinate reference system Recommended http URIs for the default coordinate reference No. ID Textual name Short name Description / definition URI identifier 3D Cartesian in ETRS89 3D geodetic in ETRS89 on GRS80 2D geodetic in ETRS89 on GRS80 2D LAEA projection in ETRS89 on GRS80 2D LCC projection in ETRS89 on GRS80 2D TM projection in ETRS89 on zone 26N (30°W to 24°W) 2D TM projection in ETRS89 on GRS80, zone 27N (24°W to 18°W) 2D TM projection in ETRS89 on GRS80, zone 28N (18°W to 12°W) 2D TM projection in ETRS89 on GRS80,
A – Get Harmonized Spatial Data Service Metadata This is an example of the Get Harmonized Spatial Data Service Metadata operation as described at chapter 4.6.4. A.1 Get Harmonized Spatial Data Service Metadata Request This section contains a description about the GetCapabilities Request, including a table specifying the parameters needed by the request. In this request there is no need to provide the “service” information (this is a deviation from the standard OWS capabilities). Table 4 - Get Harmonized Spatial Data Service Metadata request Request Parameter Mandatory / optional Description Request=GetCapabilities M Operation name (text). Fixed value: GetCapabilities AcceptVersions=version O Request version: 2.0.2 [INS NS] requires that multilingual aspects for network services are supported. As is no standard way to deal with multilingualism within the [OGC WS] specifications, the HTTP/GET binding of the GetCapabilities-Operation is extended by an additional parameter that indicates the client’s preferred language. Request Parameter Parameter value Description LANGUAGE Codelist (See ISO/TS based on alpha-3 codes of ISO 639-2. Use only three-letter codes from in ISO (bibliographic codes), The list of codes for the 23 official EU languages and EFTA Countries is: Bulgarian – bul Italian – ita Czech – cze Latvian – lav Danish – dan Liechenstein – ger Dutch – dut Lithuanian – lit English – eng Maltese – mlt Polish – pol Norwegian – nor It is optional for a Client Request. It is mandatory to be supported for the service and shall be processed if the parameter is present in a client’s request with a supported language code. If the parameter is absent in a client’s request or it requested an unsupported language the service shall response in the service default language.