INSPIRE Metadata Implementing Rules: Technical Guidelines Based on EN ISO 19115 and EN
Total Page：16
File Type：pdf, Size：1020Kb
1 INSPIRE 2 Infrastructure for Spatial Information in 3 Europe 4 5 6 7 8
9INSPIRE Metadata Implementing 10Rules: Technical Guidelines based 11on EN ISO 19115 and EN ISO 19119 12 13 Title INSPIRE Metadata Implementing Rules: Technical Guidelines based on EN ISO 19115 and EN ISO 19119 Creator Drafting Team Metadata and European Commission Joint Research Centre. Updated by MIG-MIWP8 Creation date 2007-10-26 Date of last revision 20153-0510-0529 Subject INSPIRE Implementing Rules for Metadata Status V. 1.4 draft 0.2x Draft document for editing in subgroups for MIWP8 Publisher European Commission Joint Research Centre Type Text Description Guidelines based on EN ISO 19115 and EN ISO 19119 for Commission Regulation (EC) No 1205/2008 of 3 December 2008 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards metadata Contributor See Acknowledgements Format doc Source European Commission Joint Research Centre Rights Public Identifier 0fae8d8c7fd839d5ab6534861fe4d34e.doc0fae8d8c7fd839d5ab6534861f e4d34e.doc Language EN Relation Not applicable Coverage Not applicable Comments Current draft is updated at the following chapters 2.2.5 Unique resource identifier 2.3.6 Coupled resource 2.9 Contraints related to Access and use 2.11.3 Metadata Language 2.12 Metadata for interoperability 2.13 Theme specific metadata
Yet to be added/updated are the section below 2.14 Metadata for Spatial data services
1 1 14
2 2 15Table of Contents 16 17Acknowledgements...... 4 18Introduction...... 5 19Changes from Version 1.2 of 2010-06-06...... 7 20Normative references...... 8 21Verbal forms for expression of provisions...... 8 221 INSPIRE profile of ISO 19115 and ISO 19119...... 10 23 1.1 ISO Core Metadata Elements...... 10 24 1.1.1 Spatial dataset and spatial dataset series...... 10 25 1.1.2 Services...... 12 26 1.1.3 Conclusion...... 13 27 1.2 INSPIRE specific constraints (SC)...... 13 28 1.3 Extensions...... 14 29 1.3.1 Spatial data service type...... 14 30 1.3.2 Classification of spatial data services...... 15 312 Basic mapping...... 15 32 2.1 Introduction...... 15 33 2.1.1 Xpath expression...... 16 34 2.1.2 ISO Schemas Location...... 16 35 2.2 Identification...... 17 36 2.2.1 Resource title...... 17 37 2.2.2 Resource abstract...... 18 38 2.2.3 Resource Type...... 20 39 2.2.4 Resource locator...... 21 40 2.2.4.1 Resource Locator for data sets and dataset series...... 21 41 2.2.4.2 Resource Locator for Services...... 23 42 2.2.5 Unique resource identifier...... 24 43 2.2.6 Coupled resource...... 25 44 2.2.7 Resource language...... 26 45 2.3 Classification of spatial data and services...... 27 46 2.3.1 Topic category...... 27 47 2.3.2 Spatial data service type...... 29 48 2.4 Keyword...... 30 49 2.4.1 Keyword value...... 31 50 2.4.2 Originating controlled vocabulary...... 33 51 2.5 Geographic location...... 35 52 2.5.1 Geographic bounding box...... 35 53 2.6 Temporal reference...... 37 54 2.6.1 Temporal extent...... 37 55 2.6.2 Date of publication...... 38 56 2.6.3 Date of last revision...... 40 57 2.6.4 Date of creation...... 41 58 2.7 Quality and validity...... 42 59 2.7.1 Lineage...... 42 60 2.7.2 Spatial resolution...... 44 61 2.8 Conformity...... 47 62 2.8.1 Degree...... 48 63 2.8.2 Specification...... 49 64 2.9 Constraints related to access and use...... 51 65 2.9.1 Limitations on public access...... 51 66 2.9.2 Conditions applying to access and use...... 53 67 2.10 Responsible organisation...... 55 68 2.10.1 Responsible party...... 55 69 2.10.2 Responsible party role...... 57 70 2.11 Metadata on metadata...... 58 71 2.11.1 Metadata point of contact...... 58 72 2.11.2 Metadata date...... 60 73 2.11.3 Metadata language...... 60 743 Detailed mapping...... 62 75 3.1 Introduction...... 62 76 3.2 Resource MetadataSet...... 62
3 3 77 3.3 Identification Section...... 63 78 3.3.1 Sub-elements for spatial dataset and spatial dataset series...... 63 79 3.3.2 Sub-elements for service resources...... 64 80 3.4 Data Quality Section...... 65 81 3.4.1 Lineage...... 65 82 3.4.2 Conformity...... 65 83 3.5 Responsible Organisation...... 66 84 3.5.1 Resource responsible organisation...... 66 85 3.5.2 Metadata point of contact...... 66 86 3.6 Constraint section...... 66 87 3.7 Abbreviations...... 67 88Annex A – ISO/TS 19139 encoding of the INSPIRE metadata elements...... 68 89 A.1 Introduction...... 68 90 A.2 From the conceptual schema to XML File instances...... 68 91 A.3 Polymorphism...... 68 92 A.4 Management of polymorphism...... 68 93 A.4.1 Management of community extensions...... 68 94 A.4.2 Parsing of metadata files...... 68 95 A.5 Management of containment by reference...... 69 96 A.6 ISO 19139 and multilingual metadata...... 69 97 A.6.1 The default language...... 70 98 A.6.2 Alternate languages...... 71 99 A.6.3 Embedded translations...... 71 100 A.6.4 Use of translation files...... 72 101 A.7 Contexts of use...... 73 102 A.7.1 Use of ISO 19139 in the context of a Catalogue Service...... 73 103 A.7.2 Use of ISO 19139 in the context of the standard interchange by transfer...... 73 104 A.8 Character encoding...... 73 105 A.9 Temporal extent encoding...... 73 106 A.10 Spatial resolution encoding...... 75 107 A.11 Codelists...... 76 108 A.12 Example of ISO 19139 XML Metadata Sets...... 77 109 A.12.1 Dataset...... 77 110 A.12.2 Dataset series...... 86 111 A.12.3 Service...... 86 112Annex B (informative) Metadata elements for interoperability...... 95 113 B.1. Metadata elements required by the INSPIRE Implementing Rules on the 114 Interoperability of Spatial Datasets and Services...... 95 115 B.2. Metadata elements recommended in the INSPIRE Data Specifications Technical 116 Guidelines...... 96 117 118
4 4 119Acknowledgements 120 121Many individuals and organisations have contributed to the development of these Guidelines. 122 123The original Drafting Team on Metadata (2006-08) included: Marcel Reuvers (Netherlands), 124Nicolas Lesage (France), Kristian Senkler (Germany), Michael Gould (Spain), Gil Ross (UK), 125Stefano Nativi (Italy), Jan Hjelmager (Denmark), Franz Daffner (European Environment 126Agency), Per Ryghaud (Norway), Thomas Vögele and Fred Kruse (Germany), David Danko 127(USA). 128 129We are grateful for the comments received during the consultation (28 th May-15th June 2010) 130with the Member States via their Points of Contact. 131 132We also wish to acknowledge the contribution of Jesus Barrera and his team at 133GeoSpatiumLab who have provided editorial assistance in preparing this new version of the 134guidelines, as well as the precious contribution of Angelo Quaglia at JRC in checking the final 135draft. 136 137This version 1.3 of the Technical Guidelines clarifies some aspects of the implementation of 138the discovery metadata elements based on the experience built during the period of 139implementation 2010-13. It also includes an overview of the Metadata elements for Evaluation 140and Use defined in the INSPIRE Implementing Rules for the Interoperability of Spatial 141Datasets and Services 142 143This update has been funded by the EU Interoperability Solutions for European Public 144Adminstrations (ISA) Programme through ISA Action 1.17: A Reusable INSPIRE Reference 145Platform (ARE3NA), which is supporting the development of open source solutions and the 146technical guidelines that aid cross-sector and cross-border interoperability and the 147implementation of the INSPIRE Directive. 148 149 150 151Contact information 152 153Massimo Craglia (Editor) 154European Commission Joint Research Centre 155Institute for Environment and Sustainability 156Digital Earth and Reference Data Unit 157TP262, Via Fermi 2749 158I-21027 Ispra (VA) 159ITALY 160E-mail: [email protected] 161Tel.: +39-0332-786269 162Fax: +39-0332-786325 163 164http://ies.jrc.ec.europa.eu/ 165http://www.jrc.ec.europa.eu/ 166
5 5 167Introduction 168 169According to Article 5(1) of Directive 2007/2/EC, Member States shall ensure that metadata 170are created for the spatial data sets and services corresponding to the themes listed in 171Annexes I, II and III, and that those metadata are kept up to date. According to Article 5(4) of 172Directive 2007/2/EC, Implementing Rules shall be adopted taking account of relevant, existing 173international standards and user requirements. In the context of metadata for spatial data and 174spatial data services, the standards EN ISO 19115, EN ISO 19119, and ISO 15836 (Dublin 175Core) have been identified as important standards. 176 177Commission Regulation (EC) No. 1205/2008 implementing Directive 2007/2/EC of the 178European Parliament and of the Council as regards metadata was adopted on of 3rd 179December 2008, and published on the Official Journal of the European Union on 4 th 180December (OJ L 326, 4.12.2008, p. 12–30). Any reference in this document to “Implementing 181Rules for Metadata” refers to the above-mentioned Regulation. 182 183The Regulation sets out the requirements for the creation and maintenance of metadata for 184spatial data sets, spatial data set series and spatial data services corresponding to the 185themes listed in Annexes I, II and III to Directive 2007/2/EC. It defines a number of metadata 186elements, their multiplicities and the value domains to be used in the metadata. 187 188NOTE1 The metadata elements defined in the Implementing Rules for Metadata are usually 189called discovery metadata. 190 191In addition to these requirements, Commission Regulation (EU) No 1089/2010 of 23 192November 2010 implementing Directive 2007/2/EC of the European Parliament and of the 193Council as regards interoperability of spatial data sets and services (OJ L 323, 08/12/2010, p. 19411–102) and its sub-sequent amendments1,2 define six additional metadata elements for 195interoperability as well as some theme-specific requirements for the discovery metadata 196elements. Any reference in this document to “Implementing Rules for interoperability of spatial 197data sets and services” refers to the above-mentioned Regulation. 198 199NOTE 2 The metadata elements defined in the Implementing Rules for interoperability of 200spatial data sets and services are also sometimes referred to as evaluation and use 201metadata. 202 203The aim of this document is to define how the requirements of the Implementing Rules for 204Metadata can be implemented using EN ISO 19115 and EN ISO 19119. The following 205subsections describe for each element of the Implementing Rules its relation with the 206mentioned European standards. Furthermore, Annex B provides an overview of the additional 207metadata elements and requirements defined in the Implementing Rules for interoperability of 208spatial data sets and services as well as pointers to the INSPIRE Data Specifications, which 209provide guidance and recommendations for their implementation. 210 211The timelines relevant for the provision of discovery metadata are different from those for 212metadata for interoperability. The former need to be provided according to the deadlines 213specified in the INSPIRE Directive for the Implementing Rules for Metadata (2 years after 214adoption for Annex I and II and 5 years after adoption for Annex III), while the latter need to 215be provided according to the deadlines specified in the INSPIRE Directive for the 216Implementing Rules for interoperability of spatial data sets and services (2 years after 217adoption for newly created or extensively restructured data sets, and 7 years for all other data 218sets). Figure 1 gives an overview of the dates at which the requirements included in the two 219Implementing Rules for data sets related to Annex I, II or III have to be met. 220
61 Commission Regulation (EU) No 102/2011 of 4 February 2011 amending Regulation (EU) No 1089/2010 7 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of 8 spatial data sets and services (OJ L 31, 05/02/2011, p. 13–34) 92 Commission Regulation (EU) No …/.. of XXX amending Regulation (EU) No 1089/2010 implementing Directive 10 2007/2/EC as regards interoperability of spatial data sets and services (Annex II+III amendment).
11 6 5 0 1 2 0 2 3 7 0 0 1 1 1 1 2 2 0 0 0 0 2 2 2 n 2 n / / / / m m 2 1 2 1 1 1 1 u 1 u t t / / / / u u 3 3 3 3 0 2 0 A 2 A
Annex I
Annex II
Annex III
Discovery metadata shall be available for spatial data sets and services
Metadata for interoperabilityshall be available Metadata for interoperability shall be for newly collected and extensively available for all spatial data sets restructured spatial data sets 221 222Figure 1. Illustration of Implementation Roadmap for discovery metadata and metadata 223for interoperability3 224 225 226Note on Corrigenda to the Implementing Rules for Metadata 227 228Regulation 1205/2008 has been amended with the corrigenda published in the OJ L 328/83 of 22915.12.2009 as follows: 230 . On page 12 delete the subtitle “Text with EEA relevance” (European Economic Area) 231 . On page 20, Annex D, point 1.3 replace “Spatial data services (services)” with 232 “Spatial data services (service)”. 233 234PLEASE NOTE that in the course of this revision, another typing error has come to light in the 235Regulation 1205/2008 which will need a further amendment. In Part D 4, the language neutral 236name for element 501: Geoparameter calculation service should be 237(thematicGeoparameterCalculationService) and not 238(thematicGoparameterCalculationService) (part in bold is added to put in evidence the typing 239error). Still in Part D 4, a number of typos have been detected in the language-independent 240values when comparing the English version with those in other languages. These will be 241corrected in an amendment of the Regulation. 242 243Legal Notice 244 245 This document will be publicly available as a ‘non-paper’, as it does not represent an official 246 position of the Commission, and as such can not be invoked in the context of legal 247 procedures. 248 249Neither the European Commission nor any person acting on behalf of the Commission is 250responsible for the use that might be made of this publication. 251
12 3 Dates in this figure are accurate at the time of publication and are based on the assumption that the Annex II+III 13 amendment of the Implementing Rules for interoperability of spatial data sets and services will be adopted in 14 autumn 2013. For definitive dates refer to the roadmap published on the INSPIRE website 15 (http://inspire.jrc.ec.europa.eu/index.cfm/pageid/44).
16 7 252Changes from Version 1.2 of 2010-06-06 253 254This document is Version 1.3. The changes introduced since Version 1.2 includes: 255 Rewording to make the text clearer, 256 Introduction of boxes specifying what is a Requirement, from what is a 257 Reccomendation. 258 Inclusion of examples of good practice, 259 Recommendations on Conformity to include also conformity to INSPIRE Network 260 Service, 261 Overview table of the elements of metadata for evaluation and use defined in the 262 INSPIRE Implementing Rules for the Interoperability of Spatial Datasets and 263 Services. 264 265Throughout the document we have also corrected a typo from the previous version that 266referred to: 267 268http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/Codel 269ist/gmxCodelists.xml 270 271Whereas the live path is: 272 http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/ c odeli 273st/gmxCodelists.xml 274 275Most significant changes in V. 1.3 are: 276 Page no. Issue 17 Change in Note to update links from Osor to Join-up 21 Section 2.2.4: separation between Resource locator for datasets and dataset series (2.2.4.1) and services (2.2.4.2) 24 Section 2.2.5: suggest use of code and codespace and provided working example 25 Section 2.2.6: Clarified definition and provided working example 26 Section 2.2.7: added Croatian to the domain 29 Section 2.3.2: clarified that if a spatial data service is also an INSPIRE Network service, then it is necessary to include in the Metadata element 2.8.2 Specifications, reference to the relevant INSPIRE Network Service Implementing Rule or amendment (see also 2.8.2) 48 Section 2.8: Recommended to avoid using “Not Evaluated” for the element Conformity now that all Technical Specifications for Datasets and Services are available. Therefore, it is recommended to evaluate and declare the conformity of all data sets (i.e. as “conformant” or “not conformant”). 49 Section 2.8.2: If a spatial data service is an INSPIRE Network service, use this element to report the relevant INSPIRE Network Implementing Rule to which it conforms.
Example of how to cite correctly an INSPIRE Specification is provided 60-61 Section 2.11.3: added Croatian to the domain 79- Section A.12: Changed examples throughout 95 Section B: new section summarising the additional metadata elements required by the Implementing Rules for the Interoperability of Spatial Datasets and Services. 277
17 8 278Normative references 279 280The following referenced documents are indispensable for the application of this document. 281For dated references, only the edition cited applies. For undated references, the latest edition 282of the referenced document (including any amendments) applies. 283 284[ISO 19108] EN ISO 19108:2005, Geographic Information – Temporal Schema 285 286[ISO 19108-c] ISO 19108:2002/Cor 1:2006, Geographic Information – Temporal Schema, 287Technical Corrigendum 1 288 289[ISO 19115] EN ISO 19115:2005, Geographic information – Metadata (ISO 19115:2003) 4 290 291[ISO 19119] EN ISO 19119:2005, Geographic information – Services (ISO 19119:2005) 292 293[ISO 639-2] EN ISO 639-2:1998, Codes for the representation of names of languages – Part 2942: Alpha-3 code 295 296[ISO 8601] EN ISO 8601:2004, Data elements and interchange formats – Information 297interchange – Representation of dates and times 298 299[ISO 19139] ISO/TS 19139:2007, Geographic information – Metadata – XML schema 300implementation 301 302[CSW2 AP ISO] OpenGIS Catalogue Services Specification 2.0.2 - ISO Metadata Application 303Profile, Version 1.0.0, OGC 07-045, 2007 304 305[ISO 10646-1] ISO/IEC 10646-1:2000, Information technology ― Universal Multiple-Octet 306Coded Character Set (UCS) ― Part 1: Architecture and Basic Multilingual Plane 307 308[IR MDTG] INSPIRE Metadata Implementing Rules. Guidelines based on EN ISO 19115 and 309EN ISO 19119 for Commission Regulation (EC) No 1205/2008 of 3 December 2008 310implementing Directive 2007/2/EC of the European Parliament and of the Council as regards 311metadata 312 313[INSPIRE Directive] INSPIRE, Implementing Directive 2007/2/EC of the European Parliament 314and of the Council as regards interoperability of spatial datasets and services 315 316[Regulation 1205/2008/EC] Regulation 1205/2008/EC implementing Directive 2007/2/EC of 317the European Parliament and of the Council as regards metadata 318 319 320
321Verbal forms for expression of provisions 322 323In accordance with the ISO rules for drafting, the following verbal forms shall be interpreted in 324the given way: 325 “shall” / “shall not”: a requirement, mandatory to comply with the technical guidance 326 “ should” / “should not”: a recommendation, but an alternative approach may be 327 chosen for a specific case if there are reasons to do so 328 “may” / “need not”: a permission 329 330 331 332Technical Guideline Requirements and Recommendations notation 333
184 EN ISO 19115:2005 is the adoption by CEN of ISO 19115:2003
19 9 334Requirements and the recommendations for INSPIRE Metadata Implementing Rules within 335this technical guideline are highlighted and numbered as shown below: 336 337
338 TG Requirement #requirements are shown using this style
339 340 TG Recommendation #recommendations are shown using this style. 341 342It is important to note that, implementation requirements and implementation 343recommendations may refer to either data or services. 344 345Note: It is worth noting that requirements as specified in the INSPIRE Regulations and 346Implementing Rules are legally binding, and that requirements and recommendations as 347specified in INSPIRE Technical Guideline are not legally binding. Therefore, within this 348technical guideline we have used the terms ‘TG requirement’ and ‘TG recommendation’ to 349indicate what is technically required or recommended to conform to the Technical Guidance. 350 351 352XML Example notation 353XML Examples are shown using Courier New on a grey background with yellow for emphasis 354as below: 355 356
20 10 3661 INSPIRE profile of ISO 19115 and ISO 19119
3671.1 ISO Core Metadata Elements
3681.1.1 Spatial dataset and spatial dataset series 369 370The table below compares the core requirements of ISO 19115 (see Table 3 in 6.5 of ISO 37119115:2003) to the requirements of INSPIRE for spatial dataset and spatial dataset series as 372defined in the Implementing Rules for metadata. 373 ISO 19115 Core INSPIRE Implementing Comments Rules for Metadata
Dataset title (M) Part B 1.1 Resource Title -
Dataset reference date Part B 5 Temporal ISO 19115 is more demanding. The (M) Reference metadata shall contain a date of publication, revision or creation of the resource, while in INSPIRE the Temporal Reference can also be expressed through Temporal Extent.
Dataset responsible party Part B 9 Responsible INSPIRE is more demanding by mandating (O) organisation both the name of the organisation, and a contact e-mail address
Geographic location of the Part B 4.1 Geographic INSPIRE is more restrictive. A Geographic dataset (C) Bounding Box bounding box is mandated
Dataset language (M) Part B 1.7 Resource ISO 19115 is more demanding. It mandates Language the dataset language, even if the resource does not include any textual information. The ISO 19115 Dataset language is defaulted to the Metadata language.
Dataset character set (C) - ISO 19115 is more demanding. The dataset character set has to be documented in ISO 19115 when ISO 10646-1 is not used. The ISO 19115 element maps to the conditional “Character Encoding” metadata element defined in Art. 13(5) of the Implementing Rules on interoperability of spatial data sets and services. This element is mandatory only if an encoding is used that is not based on UTF-8 (the dominant encoding of ISO 10646-1).
Dataset topic category (M) Part B 2.1 Topic Category -
Spatial resolution of the Part B 6.2 Spatial - dataset (O) Resolution
Abstract describing the Part B 1.2 Resource - dataset (M) abstract
Distribution format (O) - The ISO 19115 element maps to the mandatory “Encoding” metadata element defined in Art. 13(3) of the Implementing Rules on interoperability of spatial data sets and services.
Additional extent Part B 5.1 Temporal extent INSPIRE is more demanding. A temporal information for the dataset reference is mandated, and can be (vertical and temporal) (O) expressed as a temporal extent.
21 11 ISO 19115 Core INSPIRE Implementing Comments Rules for Metadata
Spatial representation - The ISO 19115 element maps to the type (O) mandatory “Spatial Representation Type” metadata element defined in Art. 13(6) of the Implementing Rules on interoperability of spatial data sets and services5.
Reference system (O) - The ISO 19115 element maps to the mandatory “Coordinate Reference System” and the conditional “Temporal Reference System” metadata elements defined in Art. 13(1) and (2) of the Implementing Rules on interoperability of spatial data sets and services set.
Lineage (O) Part B 6.1 Lineage INSPIRE is more demanding. A general lineage statement is mandated.
On-line resource (O) Part B 1.4 Resource - Locator
Metadata file identifier (O) - -
Metadata standard name - - (O)
Metadata standard version - - (O)
Metadata language (C) Part B 10.3 Metadata INSPIRE is more demanding. The metadata Language language is mandated even if it is defined by the encoding.
Metadata character set - ISO 19115 is more demanding. The (C) metadata character set has to be documented in ISO 19115 when ISO 10646- 1 is not used.
Metadata point of contact Part B 10.1 Metadata point INSPIRE is more demanding by mandating (M) of contact both the name of the organisation, and a contact e-mail address.
Metadata date stamp (M) Part B 10.2 Metadata Date ISO is more restrictive because this element shall contain the “date that the metadata was created” and INSPIRE may contain the “date when the metadata record was created or updated
- Part B 1.3 Resource Type INSPIRE is more demanding
Part B 1.5 Unique INSPIRE is more demanding Resource Identifier
Part B 3 Keyword INSPIRE is more demanding
- Part B 7 Conformity INSPIRE is more demanding
- Part B 8.1 Conditions for INSPIRE is more demanding access and use
- Part B 8.2 Limitations on INSPIRE is more demanding public access
22 5 This element will be introduced in the Annex II+III amendment to the Implementing Rules on interoperability of 23 spatial data sets and services.
24 12 3741.1.2 Services 375 376The table below compares the core requirements of ISO 19115 (see Table 3 in 6.5 of ISO 37719115:2003) to the requirements of INSPIRE for services as defined in the Implementing 378Rules for metadata. The greyed lines correspond to core metadata elements not applicable to 379services. 380 ISO 19115 Core INSPIRE Comments
Dataset title (M) Part B 1.1 Resource Title -
Dataset reference date Part B 5 Temporal ISO 19115 is more demanding. Despite its (M) Reference name, this ISO 19115 Core metadata element applies to services. A reference date of the service (date of publication, revision or creation …) is mandated.
Dataset responsible party Part B 9 Responsible - (O) organisation
Geographic location of the - See INSPIRE Geographic Bounding Box dataset (C)
- Part B 4.1 Geographic The Geographic Bounding Box is handled in Bounding Box ISO 19119 with a different metadata element from the one corresponding to “Geographic location of the dataset”
Dataset language (M) - Not applicable to services
Dataset character set (C) - Not applicable to services
Dataset topic category (M) - Not applicable to services
Spatial resolution of the Part B 6.2 Spatial In the current version of ISO 19119, it is not dataset (O) Resolution possible to express the restriction of a service concerning the spatial resolution
Abstract describing the Part B 1.2 Resource - dataset (M) abstract
Distribution format (O) - -
Additional extent - - information for the dataset (O)
Spatial representation - - type (O)
Reference system (O) - -
Lineage (O) - -
On-line resource (O) Part B 1.4 Resource - Locator
Metadata file identifier (O) - -
Metadata standard name - - (O)
Metadata standard version - - (O)
Metadata language (C) Part B 10.3 Metadata INSPIRE is more demanding. The metadata Language language is mandated.
25 13 ISO 19115 Core INSPIRE Comments
Metadata character set - ISO 19115 is more demanding. The (C) metadata character set has to be documented in ISO 19115 when ISO 10646- 1 is not used.
Metadata point of contact Part B 10.1 Metadata point - (M) of contact
Metadata date stamp (M) Part B 10.2 Metadata Date ISO is more restrictive because this element shall contain the “date that the metadata was created” and INSPIRE may contain the “date when the metadata record was created or updated
- Part B 1.3 Resource Type INSPIRE is more demanding
- Part B 1.6 Coupled Optional in INSPIRE Resource
- Part B 2.2 Spatial Data INSPIRE is more demanding Service Type
Part B 3 Keyword INSPIRE is more demanding
- Part B 7 Conformity INSPIRE is more demanding
- Part B 8.1 Conditions for INSPIRE is more demanding access and use
- Part B 8.2 Limitations on INSPIRE is more demanding public access 381
3821.1.3 Conclusion 383 384 The conformance of an ISO 19115 metadata set to the ISO 19115 Core does not 385 guarantee the conformance to INSPIRE; 386 The use of these guideline to create INSPIRE metadata ensures that the metadata is 387 not in conflict with ISO 19115. However, full conformance to ISO 19115 implies the 388 provision of additional metadata elements which are not required by the INSPIRE 389 Implementing Rule on Metadata. Additional metadata elements are required by the 390 INSPIRE Implementing Rules for the Interoperability of Spatial Datasets and 391 Services. An overview list of these additional elements is provided in Annex B. 392 393Over the structural requirements formalised through the mappings, the conformance to 394INSPIRE is also a matter of semantic of the information provided. If it is acceptable that the 395ISO 19115/ISO 19119 contain information which are not strictly bounded to the definition of 396the corresponding INSPIRE metadata elements, the minimum requirements expressed in the 397implementing rules have also to be met semantically, i.e. with metadata contents strictly 398satisfying the INSPIRE requirements.
3991.2 INSPIRE specific constraints (SC) 400 401Here is an initial list of INSPIRE Regulation 1205/2008/EC constraints applicable to an ISO 40219115/ISO 19119 metadata set (i.e. an instance of MD_Metadata) describing a resource: 403SC1. MD_Metadata.language is mandatory; 404SC2. MD_Metadata.hierarchyLevel is mandatory; 405SC3. INSPIRE only considers the first instance of MD_Metadata.hierarchyLevel (i.e. 406 MD_Metadata.hierarchyLevel[1]) when there are many; 407SC4. If the value of MD_Metadata.hierarchyLevel[1] is not service, dataset or series, the 408 metadata set is out of scope of the directive;
26 14 409SC5. When there are many instances of MD_Metadata.identificationInfo, only the first one 410 (i.e. MD_Metadata.identificationInfo[1]) concerns the current INSPIRE Resource; 411SC6. INSPIRE only considers the instance of MD_Metadata.dataQualityInfo applicable to the 412 whole resource; 413SC7. There shall not be more than one instance of 414 MD_Metadata.identificationInfo[1].MD_Identification.citation.CI_Citation.date declared 415 as a creation date (i.e. CI_Date.dateType having the creation value); 416SC8. MD_Metadata.identificationInfo[1].MD_DataIdentification.citation.CI_Citation.identifier is 417 mandatory for metadata sets related to spatial dataset and spatial dataset series; 418SC9. The data type of MD_Metadata.identificationInfo.MD_DataIdentification.language is the 419 codelist LanguageCode from ISO/TS 19139; 420SC10.There is at least one instance of 421 MD_Metadata.identificationInfo[1].MD_DataIdentification.extent defining the geographic 422 location of the resource as a geographic bounding box (i.e. an instance of 423 EX_GeographicBoundingBox or one of its subclasses). 424SC11.MD_Metadata.identificationInfo[1].SV_ServiceIdentification.operatesOn shall be 425 instantiated by reference 426SC12.There shall be at least one instance of 427 MD_Metadata.identificationInfo[1].MD_Identification.resourceConstraints 428SC13.The coordinates of the bounding boxes (instance of EX_GeographicBoundingBox) shall 429 be expressed in any geodetic coordinate reference system with the Greenwich Prime 430 Meridian 431SC14.For datasets and series: 432 MD_Metadata.identificationInfo[1].MD_DataIdentification.pointOfContact[1].CI_Respon 433 sibleParty.organisationName and 434 MD_Metadata.identificationInfo[1].MD_DataIdentification.pointOfContact[1].CI_Respon 435 sibleParty.contactInfo.CI_Contact.address.CI_Address.electronicMailAddress are 436 mandatory. 437 For services these elements are also mandatory but they are referred as follows: 438 MD_Metadata.identificationInfo[1].SV_ServiceIdentification.pointOfContact[1].CI_Resp 439 onsibleParty.organisationName and 440 MD_Metadata.identificationInfo[1].SV_ServiceIdentification.pointOfContact[1].CI_Resp 441 onsibleParty.contactInfo.CI_Contact.address.CI_Address.electronicMailAddress. 442SC15.MD_Metadata.contact[1].CI_ResponsibleParty.organisationName and 443 MD_Metadata.contact[1].CI_ResponsibleParty.contactInfo.CI_Contact.address.CI_Add 444 ress.electronicMailAddress are mandatory. 445SC16.The value of MD_Metadata.contact[1].CI_ResponsibleParty.role.CI_RoleCode shall be 446 pointOfContact. 447SC17.For datasets and series at least one keyword of GEMET thesaurus shall be 448 documented using 449 MD_Metadata.identificationInfo[1].MD_DataIdentification.descriptiveKeywords. 450SC18.For services at least one keyword of Part D.4 of Commission Regulation (EC) No. 451 1205/2008 shall be documented using 452 MD_Metadata.identificationInfo[1].SV_ServiceIdentification.descriptiveKeywords
4531.3 Extensions
4541.3.1 Spatial data service type 455 456For spatial data service types, the INSPIRE Metadata Regulation 1205/2008/EC mandate the 457use of the value domain of Part D 3. This information is handled using the serviceType 458attribute (See 2.3.2) of the class SV_ServiceIdentification (See ISO 19119). 459 460The Table below defines the values of the serviceType property. In brackets are the language 461neutral names to be used. 462
27 15 SPATIAL DATA SERVICE TYPE Discovery Service (discovery) View Service (view) Download Service (download) Transformation Service (transformation) Invoke Spatial Data Service (invoke) Other Services (other) 463
4641.3.2 Classification of spatial data services 465 466For classification of spatial data services, the Implementing Rules mandate the use of the 467value domain of Part D 4 of Regulation 1205/2008/EC. In order to ensure a language 468independent expression of the classification of spatial data services, the language neutral 469name is to be used as the value of the ISO 19115 keywords (See 2.4).
4702 Basic mapping
4712.1 Introduction 472 473The following tables describe the mapping between the metadata elements of INSPIRE, as 474defined in the INSPIRE implementing rules for metadata, and ISO 19115/ISO 19119. For 475each of the INSPIRE Metadata element, the mapping is composed of the main characteristics 476of the metadata element as they are defined6 in the INSPIRE implementing rules (IR) for 477metadata and the main characteristics of the corresponding metadata element of ISO 19115 478or ISO 19119: 479 The metadata element name as used in the INSPIRE implementing rules; 480 The reference to the paragraph of the INSPIRE implementing rules describing the 481 metadata element; 482 The definition, which gives the current ISO 19115 or ISO 19119 terms for describing 483 the metadata element (Annex B of ISO 19115 standard: Data Dictionary for 484 geographic metadata or Annex C of ISO 19119: Data dictionary for geographic 485 service metadata); 486 The number and the name that identifies the metadata element inside tables in ISO 487 19115 (or ISO 19119) published standard; 488 An XPath expression indicating the metadata element within the ISO 19115 / ISO 489 19119 UML model (see 2.1.1); 490 The INSPIRE obligation/condition applicable to the metadata element; 491 The INSPIRE multiplicity of the metadata element; 492 The Data Type and the Domain required by the metadata element; 493 An example that illustrates the description of the metadata element by providing a 494 concrete case 495 Some comments, which give more information about the metadata element 496 497Apart from the tables collecting the main significant aspects, additional information is provided 498regarding: the description of the metadata element, advices on its fulfilment and important 499requirements and recommendations, as well as an example of XML encoding, i.e. a fragment 500of the XML of a metadata record created and validated with the INSPIRE Metadata Editor 501available from the EU Geoportal (http://inspire-geoportal.ec.europa.eu). 502 503The overall structure of an ISO 19115/ISO 19119 metadata set supporting the requirements 504expressed in the INSPIRE Implementing rules for metadata is defined in Section 3 of this 505document.
286 In case of discrepancy, the INSPIRE Implementing rules take precedence
29 16 5062.1.1 Xpath expression 507 508This compact notation allows many defaults and abbreviations for common cases. The 509simplest XPath takes a form such as /A/B/C which selects C elements that are children of B 510elements that are children of the A element that forms the outermost element of the model. 511More complex expressions can be constructed by specifying an axis other than the default 512'child' axis, a node test other than a simple name, or predicates, which can be written in 513square brackets after any step. The main rules are the following ones: 514 * selects all element children of the context node; 515 text() selects all text node children of the context node; 516 @name selects the name attribute of the context node; 517 @* selects all the attributes of the context node; 518 . selects the context node; 519 .//para selects the para element descendants at any level of the context node; 520 .. selects the parent of the context node. 521 522Hereafter, the root element of the XPath expression is an instance of MD_Metadata or one of 523its subclasses. The possible subelements of a class are its properties. The possible 524subelement of a property is its data type or a subtype of its data type. In order to manage the 525polymorphism, the XPath expression deals with the data type in a generic way (e.g., 526property_element_name/*/datatype_property_name).
5272.1.2 ISO Schemas Location 528 529Official ISO schemas (ISO AP or ISO 19139) are currently found in two separate locations: 530 5311) ISO repository for public available standards. The ISO 19139 schemas can be found here: 532http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/ 533Date of schemas: 2007-08-11. 534 5352.) OGC Schema repository. The ISO 19139 schemas are located here: 536http://schemas.opengis.net/iso/19139/20070417/ 537Date of schemas: 2007-04-17. 538and here: http://schemas.opengis.net/iso/19139/20060504/ 539Date of schemas: 2006-06-04. 540 541ISO AP schemas are located here: http://schemas.opengis.net/csw/2.0.2/profiles/apiso/ 542Date of schemas: 2007-07-19. 543 544The ISO AP schemas are bound to http://schemas.opengis.net/iso/19139/20060504/ 545 546The difference in the schemas located in the OGC repository is the GML version. The version 547dated "2007-04-17" uses GML 3.2.1, the version dated "2006-06-04" use GML 3.2.0. The 548version "2006-06-04" provides gml in a separate directory (/gml) whereas the version "2007- 54904-17" directly refers to http://schemas.opengis.net/gml/3.2.1/. The major difference is that 550GML 3.2.0 schemas are defined in the namespace http://www.opengis.net/gml whereas GML 5513.2.1 schemas are defined in the namespace http://www.opengis.net/gml/3.2. 552 553The schemas located in the ISO repository for public available standards are comparable to 554OGC schemas located here: http://schemas.opengis.net/iso/19139/20070417/. 555 556In conclusion: 557To Validate XML against ISO AP 1.0: 558http://schemas.opengis.net/csw/2.0.2/profiles/apiso/1.0.0/apiso.xsd 559 560To Validate XML against ISO 19139 with GML 3.2.0: 561http://schemas.opengis.net/iso/19139/20060504/gmd/gmd.xsd 562 563To Validate XML against ISO 19139 with GML 3.2.1: 564http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/gmd.xsd or 565http://schemas.opengis.net/iso/19139/20070417/gmd/gmd.xsd
30 17 566 567INSPIRE Validator Service: A RESTful Web service that can be invoked by http request to 568validate INSPIRE Metadata. The purpose of the INSPIRE Metadata Validator is to test 569compliance of INSPIRE metadata with the INSPIRE Metadata Regulation. The validator 570accepts metadata that follow the Metadata Technical Guidance encoded in EN ISO 19139 571schema. The INSPIRE Metadata Validator is implemented by ISO Schematron (2006). 572 573The web application and service are provided for testing. Please report any issues you find so 574that they can be improved at [email protected] 575 576End point: http://inspire-geoportal.ec.europa.eu/validator2/ 577Supported method: POST 578Supported response formats: XML, HTML (The response format is returned according to the 579Accept value of the http request header) 580Request parameter: dataFile (This is the name of the parameter associated with the metadata 581record xml file that should be added to the request) 582 583PLEASE NOTE: The validator is a proof of concept that has been developed to test 584these guidelines. It is not intended to be an operational tool, and at the present time 585works in English only. All the files of the Validator including documentation are 586available under EU Public License from the JoinUp Platform 587(https://joinup.ec.europa.eu/software/validator/home). Interested stakeholders are 588welcome to adapt the current Validator to their own language, and contribute it back 589through JoinUp to enrich the collective portfolio of tools supporting the 590implementation of INSPIRE, currently being explored by the ISA Action A Reusable 591INSPIRE Reference Platform (ARE3NA: 592https://joinup.ec.europa.eu/community/are3na/description). A new validator is being 593developed and will also be added to JoinUp. 594
5952.2 Identification
5962.2.1 Resource title 597 598This is a characteristic, and often unique, name by which the resource is known. The title is 599the most informative element of a metadata record and usually the highest priority as search 600engines go to this element. 601 602 TG Recommendation 1 The Resource Title has to be concise and to the point. It should not 603 contain unexplained acronyms or abbreviations. It is recommended 604 a maximum length of 250 characters and keeping the similarity with 605 the original title of the resource, in the sense of the ‘official naming’.
606 607 TG Recommendation 2 If the data or service is part of a larger project, it is recommended to 608 indicate the Project at the end of the title, in brackets. In case of 609 Project names, abbreviations are allowed, as long as the rest of the 610 title follows the guidelines above and the abbreviation is spelled out 611 immediately in the abstract.
612 Metadata element name Resource title Reference Part B 1.1 Definition Name by which the cited resource is known ISO 19115 number and name 360. title ISO/TS 19139 path identificationInfo[1]/*/citation/*/title INSPIRE obligation / condition Mandatory
31 18 INSPIRE multiplicity [1] Data type (and ISO 19115 no.) CharacterString Domain Free text Example SPI: Standardized Precipitation Index Comments 613 614 615 616 617Example of XML encoding: 618 619
6362.2.2 Resource abstract 637 638This is a brief narrative summary of the content of the resource. The abstract provides a clear 639and concise statement that enables the reader to understand the content of the data or 640service 641 Metadata element name Resource abstract Reference Part B 1.2 Definition Brief narrative summary of the content of the resource(s) ISO 19115 number and name 25. abstract ISO/TS 19139 path identificationInfo[1]/*/abstract INSPIRE obligation / condition Mandatory INSPIRE multiplicity [1] Data type (and ISO 19115 no.) CharacterString Domain Free text Example The Standardized Precipitation Index (SPI-n) is a statistical indicator comparing the total precipitation received at a particular location during a period of n months with the long- term rainfall distribution for the same period of time at that location. SPI is calculated on a monthly basis for a moving window of n months, where n indicates the rainfall accumulation period, which is typically 1, 3, 6, 9, 12, 24 or 48 months. The corresponding SPIs are denoted as SPI-1, SPI-3, SPI-6, etc. In order to allow for the statistical comparison of wetter and drier climates, SPI is based on a transformation of
32 19 the accumulated precipitation into a standard normal variable with zero mean and variance equal to one. SPI results are given in units of standard deviation from the long-term mean of the standardized distribution. In 2010 WMO selected the SPI as a key meteorological drought indicator to be produced operationally by meteorological services Comments 642 643 644 TG Recommendation 3 The resource abstract is a succinct description that can include: 645 - A brief summary with the most important details that summarise 646 the data or service 647 - Coverage: linguistic transcriptions of the extent or location in 648 addition to the bounding box 649 - Main attributes 650 - Data sources 651 - Legal references 652 - Importance of the work
653 654 TG Recommendation 4 Do not use unexplained acronyms.
655 656 TG Recommendation 5 Summarise the most important details in the first sentence or first 657 100 characters.
658 659Example of XML encoding: 660 661
33 20 6902.2.3 Resource Type 691 692This is the type of resource being described by the metadata and it is filled in with a value 693from a classification of the resource based on its scope. The choice of Resource Type will be 694probably the first decision made by the user and it will define the metadata elements that 695should be filled. 696 Metadata element name Resource type Reference Part B 1.3 Definition Scope to which metadata applies ISO 19115 number and name 6. hierarchyLevel ISO/TS 19139 path hierarchyLevel INSPIRE obligation / condition Mandatory INSPIRE multiplicity [1] Data type (and ISO 19115 no.) MD_ScopeCode Domain CodeList (see annex B.5.25 of ISO 19115) Example dataset Comments 697 698
699 TG Requirement 1 The hierarchyLevel property is not mandated by ISO 19115 but 700 is mandated for conformance to the INSPIRE Metadata 701 Regulation 1205/2008/EC (See 2 in 1.2).
702
703 TG Requirement 2 The values of MD_ScopeCode in the scope of the INSPIRE 704 Directive (See 4 in 1.2) are: 705 - dataset for spatial datasets; 706 - series for spatial dataset series; 707 - service for spatial data services
708 709 TG Recommendation 6 The choice between the values should follow these 710 recommendations 711 - dataset: is an identifiable data that can be accessed separately. 712 A dataset can be a part of a whole (series) or a segregate resource 713 - series: is a collection of resources or related datasets that share 714 the same product specification 715 - service: technologies providing availability and access to spatial 716 information, for example, web map services, web feature services, 717 web coverage services, web processing services, catalogue web 718 services, etc
719 720 721 722 723 724 725Example of XML encoding:
34 21 726 727
7382.2.4 Resource locator
7392.2.4.1 Resource Locator for data sets and dataset series 740 741The Resource Locator is the ‘navigation section’ of a metadata record which point users to 742the location (URL) where the data can be downloaded, or to where additional information 743about the resource may be provided. 744Setting up the correct resource locators is important for the connection between the data and 745the services that provide access to them or for providing additional information concerning the 746resource. 747 Metadata element name Resource locator Reference Part B 1.4 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 Conditional for spatial dataset and spatial dataset series: Mandatory if a URL is available to obtain more information on the resources and/or access related services. INSPIRE multiplicity [0..*] Data type (and ISO 19115 no.) URL Domain URL (IETF RFC1738 and IETF RFC 2056) Example http://edo.jrc.ec.europa.eu/chm/ows.php? VERSION=1.3.0&SERVICE=WMS&REQUEST=GetCapabilities Comments A Resource Locator could be described, moreover, by other additional elements as a Title, a Description and a Function. In that case, the Title and the Description shall be free text and the Function shall be filled by the CI_OnLineFunctionCode (ISO 19115 codelist). Example of Resource Locator with these additional elements: Linkage: http://edo.jrc.ec.europa.eu/chm/ows.php? VERSION=1.3.0&SERVICE=WMS&REQUEST=GetCapabilitie s Title: JRC EDO (European Drought Observatory) - Drought Indexes WMS Description: WMS delivering maps of drought indexes provided by the European Drought Observatory (EDO). Function: information 748 749
35 22 750 TG Requirement 3 If a linkage for data is available, the Resource Locator shall be a 751 valid URL providing one of the following: 752 - a link to a web with further instructions 753 - a link to a service capabilities 754 document 755 - a link to the service WSDL document 756 (SOAP Binding) 757 - a link to a client application that directly 758 accesses the service
759 760 761 TG Recommendation 7 If no direct link to a resource is available, provide link to a contact 762 point where more information about the resource is available.
763 764 765 766Example of XML encoding: 767 768
36 23 8082.2.4.2 Resource Locator for Services 809 810The Resource Locator for Services, if available, provides the access point of the service, that 811is an Internet address containing a detailed description of a spatial data service, including a 812list of endpoints to allow an automatic execution. 813 814 Metadata element name Resource locator Reference Part B 1.4 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 Conditional for services: Mandatory if linkage to the service is available INSPIRE multiplicity [0..*] Data type (and ISO 19115 no.) URL Domain URL (IETF RFC1738 and IETF RFC 2056) Example http://www.dinoservices.nl/geo3dmodelwebservices- 1/Geo3DModelService Comments 815 816
817 TG Requirement 4 If a linkage for a service is available, the Resource Locator shall 818 be a valid URL providing one of the following: 819 - a link to a web with further instructions 820 - a link to a service capabilities 821 document 822 - a link to the service WSDL document 823 (SOAP Binding) 824 - a link to a client application that directly 825 accesses the service
826 827 828 TG Recommendation 8 If no direct link to a resource is available, provide link to a contact 829 point where more information about the resource is available.
830 831Example of XML encoding: 832 833
37 24 843
8552.2.5 Unique resource identifier 856 857This element is a value uniquely identifying the resource. Within the INSPIRE infrastructure 858this is used as a reference to realize the data-service-coupling (2.2.6). 859 860 Metadata element name Unique resource identifier Reference Part B 1.5 Definition Value uniquely identifying an object within a namespace ISO 19115 number and name 365. identifier ISO/TS 19139 path identificationInfo[1]/*/citation/*/identifier INSPIRE obligation / condition Mandatory for dataset and dataset series INSPIRE multiplicity [1..*] for dataset and series Data type (and ISO 19115 no.) 205. MD_Identifier Domain See B.2.7.3 of ISO 19115 Example namespace: https://example.org/ identifier: ab749859
code: https://example.org/ab749859(unique identifier with code + codeSpace) code: lakes codeSpace: urn:eu:europa:ec:jrc:rdsi:id:dataset:ccm2.1
Comments 861 862
863 TG Requirement 5 The code property is required (see B.2.7.3 of ISO 19115). It 864 consists of a namespace and an identifier that is unique within 865 the context of the namespace.
866
867
868 TG Requirement 6 If a value for codeSpace is provided, then the data type for the 869 identifier shall be RS_Identifier, which is substitutable for the 870 usual MD_Identifier.
871
38 25 872 TG Recommendation 9 Never delete an existing identifier for a resource. If a change in 873 resource identification is needed, add a new identifier but also keep 874 the old one.
875
39 26 876Example of XML encoding: 877 878
9112.2.6 Coupled resource 912 913If the resource is a spatial data service, this metadata element refers to, where relevant, the 914target spatial data set(s) of the service. It is implemented by reference, , i.e. by giving the 915resource identifier for the datasets on which the service operates on. Recommended is also 916to give a URL that points to the metadata record of the data on which the service operates. It 917helps therefore linking services to the relevant datasets. 918 919To reference the dataset(s) that the service operates on the attribute uuidref shall be used. 920
921 TG Requirement 7 The property shall be implemented by reference using the 922 attribute uuidref to reference the resource identifier of dataset 923 (see 11 in 1.2).
924Since only giving a uuidref will not be enough to find the resource in case the identifier is not a 925URL it is recommended to in addition to having a uuidref to also add a xlink:href with the URL 926to the metadata record for the dataset. 927This can either be done using a GetRecords request using the OperatesOn queryable with 928the resource identifier 929(example ..)
931If a GetRecords request is not possible, (eg in the case the CSW-catalogue does not support 932the GET request for OperatesOn) then a URL to the metadata record could be given (eg a 933GetrecordsByID could be given with the datasets fileIdentifier as argument). 934(example ..)
40 27 935 TG Reccomendation xx(9b ?) Add a url to the metadata record that 936 describes the dataset the service operates on. If possible use a 937 GetRecords query against a CSW using the OperatesOn queryable. 938 If that is not possible use a GetrecordsById request using the 939 metadata fileIdentifier as argument or reference directly a physical 940 xml-file. 941 942i.e. through a URL that points to the metadata record of the data on which the service 943operates. It helps therefore linking services to the relevant datasets. 944 Metadata element name Coupled resource Reference Part B 1.6 Definition Provides information about the datasets that the service operates on. ISO 19119 number and name 9 of table C.1. operatesOn ISO/TS 19139 path identificationInfo[1]/*/operatesOn INSPIRE obligation / condition Not applicable to dataset and dataset series Conditional to services: Mandatory if linkage to datasets on which the service operates are available. INSPIRE multiplicity [0] for datasets and series [0..*] for services Data type (and ISO 19115 no.) 36. MD_DataIdentification Domain A unique resource identifier or locator (URL) of the MD_DataIdentification object Example http://vap-xgeodev.jrc.ec.europa.eu/geonetwork/srv/eng/csw? SERVICE=CSW&VERSION=2.0.2&REQUEST=GetRecordById& ID=f9ee6623-cf4c-11e1-9105- 0017085a97ab&OUTPUTSCHEMA=http://www.isotc211.org/20 05/gmd&ELEMENTSETNAME=full#lakes Comments 945
946 TG Requirement 8 The property shall be implemented by reference (see 11 in 1.2).
947 948Example of XML encoding: 949 950
41 28 Definition Provides information about the datasets that the service operates on. ISO 19119 number and name 9 of table C.1. operatesOn ISO/TS 19139 path identificationInfo[1]/*/operatesOn INSPIRE obligation / condition Not applicable to dataset and dataset series Conditional to services: Mandatory if linkage to datasets on which the service operates are available. INSPIRE multiplicity [0] for datasets and series [0..*] for services Data type (and ISO 19115 no.) 36. MD_DataIdentification.citation.CI_Citation.identifier. MD_Identifier.code Domain A unique resource identifier and optionally a locator (URL) to the metadata record for the dataset (from where the MD_DataIdentification object can retrieved) Example The mandatory uuidref
GetRecords request using OperatesOn attribute https://www.geodata.se/geonetwork/srv/swe/csw? request=GetRecords&service=CSW&version=2.0.2&resu ltType=results&typeNames=gmd:MD_Metadata&outputSc hema=http://www.isotc211.org/2005/gmd&elementSetN ame=full&constraintLanguage=CQL_TEXT&constraint_l anguage_version=1.1.0&constraint=ResourceIdentifi er like ‘https://example.org/ab749859'
GetrecordById request https://www.geodata.se/geonetwork/srv/en/csw? request=GetRecordById&service=CSW&version=2.0.2&e lementSetName=full&id=a20dee7a-ca67-4dc0-8426- 11dbfa16c94e&outputSchema=csw:IsoRecord
Comments 966 967 968Example of XML encoding: 969In the example a service operates on a dataset with 970resource identifier = https://example.org/ab749859 and where metadata for the 971resource have the fileidentifier=a20dee7a-ca67-4dc0-8426-11dbfa16c94e 972 973First example is with only a uuidref to resource identifier 974
42 29 988Second example is with both the mandatory uuidref and the recommended xlink:href to a 989GetRecords request using the OperatesOn argument pointing to the same resource identifier. 990
44 31 1056
10602.3 Classification of spatial data and services
10612.3.1 Topic category 1062 1063The topic category is a high-level classification scheme to assist in the grouping and topic- 1064based search of available spatial data resources. 1065A correct categorization is very important to help users to search and find the resources they 1066are looking for. 1067 1068 1069 Metadata element name Topic category Reference Part B 2.1 Definition Main theme(s) of the dataset ISO 19115 number and name 41. topicCategory ISO/TS 19139 path identificationInfo[1]/*/topicCategory INSPIRE obligation / condition Mandatory for datasets and dataset series Not applicable to services INSPIRE multiplicity [1..*] for datasets and dataset series [0] for services Data type (and ISO 19115 no.) MD_TopicCategory Domain Enumeration (See B.5.27 of ISO 19115 or Part D 2 of the INSPIRE Metadata Regulation 1205/2008/EC) Example climatologyMeteorologyAtmosphere Comments The topic categories defined in Part D 2 of the INSPIRE Metadata Regulation 1205/2008/EC are derived directly from the topic categories defined in MD_TopicCategoryCode (B.5.27 of ISO 19115) 1070 1071
1072 TG Requirement 11 The topic category has to be filled with a value from the 1073 enumeration MD_TopicCategoryCode (ISO 19115).
1074
1075 TG Requirement 12 The value saved in the XML metadata element shall be a 1076 language neutral name (see the value appearing in the “name” 1077 column of the table in B.5.27 of ISO 19115).
1078 1079 1080Example of XML encoding: 1081 1082
45 32 1088
46 33 10992.3.2 Spatial data service type 1100 1101This is a classification to assist in the search of available spatial data services. The list of 1102language-neutral values as in Part D3 of the INSPIRE Metadata Regulation 1205/2008/EC 1103includes: discovery, view, download, transformation, invoke and other. 1104 1105If the service is also an INSPIRE Network Services, then it is necessary to include in the 1106Metadata element 2.8.2 Specifications, reference to the relevant INSPIRE Network Service 1107Implementing Rule or amendment (see also 2.8.2) 1108 1109 Metadata element name Spatial data service type Reference Part B 2.2 Definition A service type name from a registry of services ISO 19119 number and name 1 of table C.1. serviceType ISO/TS 19139 path identificationInfo[1]/*/serviceType INSPIRE obligation / condition Not applicable to datasets and dataset series Mandatory for services
INSPIRE multiplicity [1] for services [0] for datasets and dataset series Data type (and ISO 19115 no.) GenericName Domain List of values. See section 1.3.1 in this document Example view Comments 1110
1111 TG Requirement 13 Use language neutral name from table in 1.3.1.
1112 1113Example of XML encoding: 1114 1115
47 34 11282.4 Keyword 1129 1130An INSPIRE Keyword is defined by: 1131 a keyword value (see 2.4.1), which in ISO standard is referred to as “Keyword”; 1132 an optional originating controlled vocabulary (see 2.4.2), which in ISO standard is 1133 referred to as “Thesaurus”. 1134 It is possible to add as many keywords as relevant to the resource. 1135
1136 TG Requirement 14 The INSPIRE Metadata Regulation 1205/2008/EC mandate the 1137 presence of at least one keyword.
1138
1139 TG Requirement 15 If only one keyword is used, then for spatial dataset or 1140 spatial dataset series, the keyword: 1141 - shall describe the relevant INSPIRE 1142 Spatial Data Theme (as defined in Annex I, II and III of the 1143 INSPIRE Directive) 1144 - shall be expressed in the language of 1145 the metadata for the 34 1146 INSPIRE Spatial Data Themes (please use the terms in each of the 1147 official languages in which the INSPIRE Directive has been 1148 translated) or a neutral language values such as a URI.
1149 1150The titles and definitions of all 34 INSPIRE Spatial Data Themes have been integrated into a 1151dedicated branch of the General Environmental Multilingual Thesaurus (GEMET) in the 24 1152official Community languages (see http://www.eionet.europa.eu/gemet/inspire_themes). This 1153special branch is known as “GEMET - INSPIRE themes”. 1154
1155 TG Requirement 16 For spatial services, the keyword: 1156 - shall at least define the category or 1157 subcategory of the service using its language neutral name as 1158 defined in Part D 4 of the INSPIRE Metadata Regulation 1159 1205/2008/EC 1160 - shall be expressed as neutral language values such as the neutral 1161 language values defined in Part D.4 of the INSPIRE Metadata 1162 Regulation 1205/2008/EC for spatial data services)
1163 1164In addition to the mentioned thesaurus also other keywords might be added. These may be 1165described as a free text or may originate from any Controlled Vocabulary. 1166
1167 TG Requirement 17 If other keywords are added and they originate from a Controlled 1168 Vocabulary (thesaurus or ontology), for example GEMET - 1169 Concepts, EUROVOC or AGROVOC, then the citation of the 1170 originating Controlled Vocabulary shall be provided.
1171 1172For example, a keyword that comes from GEMET - Concepts shall be cited as follows: 1173 keyword: freshwater 1174 thesaurus title: GEMET - Concepts, version 2.4 1175 thesaurus date: 2010-01-13 1176 thesaurus date type: publication
48 35 1177 1178Or a keyword that comes from AGROVOC shall be cited as follows: 1179 keyword: water springs 1180 thesaurus title: AGROVOC 1181 thesaurus date: 2008-04-14 1182 thesaurus date type: publication 1183
11842.4.1 Keyword value 1185 1186The keyword value is a commonly used word, formalised word or phrase used to describe the 1187subject. While the topic category is too coarse for detailed queries, keywords help narrowing 1188a full text search and they allow for structured keyword search 1189 1190 Metadata element name Keyword value Reference Part B 3.1 Definition Commonly used word(s) or formalised word(s) or phrase(s) used to describe the subject ISO 19115 number and name 53. keyword ISO/TS 19139 path identificationInfo[1]/*/descriptiveKeywords/*/keyword INSPIRE obligation / condition Mandatory INSPIRE multiplicity [1..*] Data type (and ISO 19115 no.) CharacterString Domain Free text Example Atmospheric conditions (INSPIRE Spatial Data Theme) humanCatalogueViewer (spatial data service subcategory) water springs (AGROVOC) rain water (GEMET Concepts) Comments Each instance of ISO 19115 keyword may originate from a controlled vocabulary described through the thesaurusName property of the instance of descriptiveKeywords to which the keyword pertains 1191 1192 TG Recommendation 11It is better to select keyword values from a collection of terms 1193 linked and predefined (controlled vocabularies).
1194 1195 TG Recommendation 12It is suggested to choose a minimum of two keywords in addition to 1196 the required keyword from the GEMET - INSPIRE themes (for 1197 dataset and dataset series) or the categories from part D 4 of the 1198 INSPIRE Metadata Regulation 1205/2008/EC (for services).
1199 1200 TG Recommendation 13Ideally, both a code (neutral language value) and a human- 1201 readable label (in any language) should be included in the 1202 metadata.
1203 1204Here is an example of XML encoding of the keyword value for a spatial data services 1205category or subcategory as defined in Part D.4 of the INSPIRE Metadata Regulation 12061205/2008/EC.
49 36 1207 1208
50 37 12602.4.2 Originating controlled vocabulary 1261
1262 TG Requirement 18 If the keyword value originates from a controlled vocabulary 1263 (thesaurus, ontology), for example GEMET - Concepts, the 1264 citation of the originating controlled vocabulary shall be 1265 provided.
1266
1267 TG Requirement 19 The thesaurusName identification shall include at least the title 1268 and a reference date (date of publication, date of last revision or 1269 of creation) of the originating controlled vocabulary.
1270 Metadata element name Originating controlled vocabulary Reference Part B 3.2 Definition Name of the formally registered thesaurus or a similar authoritative source of keywords ISO 19115 number and name 55. thesaurusName ISO/TS 19139 path identificationInfo[1]/*/descriptiveKeywords/*/thesaurusName INSPIRE obligation / condition Conditional: Mandatory if the keyword value originates from a controlled vocabulary INSPIRE multiplicity [0..1] relative to a single Keyword, but there may be many keywords originating from different controlled vocabularies Data type (and ISO 19115 no.) CI_Citation Domain The following properties are expected: Title (characterString and free text) Reference date (CI_Date): o dateType: creation, publication or revision o date: an effective date Example Identification for a keyword originating from GEMET- INSPIRE themes: title: GEMET - INSPIRE themes, version 1.0 date: o dateType: publication o date: 2008-06-01
Identification for a keyword originating from GEMET - Concepts: title: GEMET - Concepts, version 2.4 date: o dateType: publication o date: 2010-01-13
Identification for a keyword originating from AGROVOC: title: AGROVOC date: o dateType: publication o date: 2008-04-14
Comments 1271
51 38 1272
1273 TG Requirement 20 In order to be consistent with ISO 19115, all the keyword values 1274 originating from a single version of a single controlled 1275 vocabulary shall be grouped in a single instance of the ISO 1276 19115 descriptiveKeywords property. See also 17 for datasets 1277 and series, and 18 for Services.
1278 1279 TG Recommendation 14It is important to specify which version of the thesaurus was used 1280 to take the keyword value from.
1281 1282 1283Example of XML encoding for keyword referring to an INSPIRE Spatial Data Theme 1284 1285
52 39 13252.5 Geographic location 13262.5.1 Geographic bounding box 1327 1328This is the extent of the resource in the geographic space, given as a bounding box. Defining 1329the coordinates of a rectangle representing the resource area on a map allows the discovery 1330by geographical area 1331 Metadata element name Geographic bounding box Reference Part B 4.1 Definition Western-most coordinate of the limit of the dataset extent, expressed in longitude in decimal degrees (positive east). Eastern-most coordinate of the limit of the dataset extent, expressed in longitude in decimal degrees (positive east) Northern-most coordinate of the limit of the dataset extent, expressed in latitude in decimal degrees (positive north) Southern-most coordinate of the limit of the dataset extent, expressed in latitude in decimal degrees (positive north). ISO 19115 number and name 344. westBoundLongitude 345. eastBoundLongitude 346. southBoundLatitude 347. northBoundLatitude ISO/TS 19139 path identificationInfo[1]/*/extent/*/geographicElement/*/westBoundLon gitude identificationInfo[1]/*/extent/*/geographicElement/*/eastBoundLong itude identificationInfo[1]/*/extent/*/geographicElement/*/southBoundLati tude identificationInfo[1]/*/extent/*/geographicElement/*/northBoundLatit ude INSPIRE obligation / condition Mandatory for datasets and spatial dataset series Conditional for spatial services: mandatory for services with an explicit geographic extent
INSPIRE multiplicity [1..*] for spatial data sets and spatial dataset series [0..*] for spatial data services Data type (and ISO 19115 no.) Decimal Domain -180.00 ≤ westBoundLongitude ≤ 180.00 -180.00 ≤ eastBoundLongitude ≤ 180.00 -90.00 ≤ southBoundingLatitude ≤ 90.00 -90.00 ≤ northBoundingLatitude ≤ 90.00 Example -15.00 (westBoundLongitude ) 45.00 (eastBoundLongitude ) 35.00 (southBoundLatitude) 72.00 (northBoundLatitude) Comments There may be 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.
53 40 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 (See 13 in 1.2). 1332
1333 TG Requirement 21 The bounding box shall be as small as possible.
1334
1335 TG Requirement 22 The bounding box shall be expressed in decimal degree with a 1336 precision of at least 2 decimals.
1337 1338 1339Example of XML encoding: 1340 1341
54 41 13722.6 Temporal reference 1373
1374 TG Requirement 23 The INSPIRE Metadata Regulation 1205/2008/EC requires at 1375 least one temporal reference chosen from one of these four 1376 categories: 1377 - temporal extent 1378 - date of publication 1379 - date of last revision 1380 - date of creation
1381ISO 19115 is more demanding than INSPIRE. Therefore, whilst providing a temporal extent 1382would suffice to satisfy the INSPIRE Metadata Regulation 1205/2008/EC it is not enough to 1383be compliant with ISO 19115. 1384
1385 TG Requirement 24 To be compliant with ISO 19115 it is necessary to use at least 1386 one among date of publication, date of last revision, or the date 1387 of creation.
1388 1389TG Recommendation 15 In case of spatial data set, report at least the date of the last 1390 revision of the spatial data set
1391
1392 TG Requirement 25 The default reference system shall be the Gregorian calendar, 1393 with dates expressed in accordance with ISO 8601 (yyyy-mm-dd 1394 where yyyy is the year, mm is the month and dd is the day).
1395
13962.6.1 Temporal extent 1397 1398The temporal extent defines the time period covered by the content of the resource. This time 1399period may be expressed as: 1400 an individual date 1401 an interval of dates (starting date and ending date) 1402 a mix of individual dates and intervals of dates 1403 Metadata element name Temporal extent Reference Part B 5.1 Definition Time period covered by the content of the dataset ISO 19115 number and name 351. extent ISO/TS 19139 path identificationInfo[1]/*/extent/*/temporalElement/*/extent INSPIRE obligation / condition Conditional: At least one temporal reference is required INSPIRE multiplicity [0..*] for temporal extent but at least one temporal reference is required Data type (and ISO 19115 no.) TM_Primitive7
557 ISO19108 describes other domains which might support the INSPIRE requirements for temporal metadata. There 56are no implementations currently known. ISO19108 allows ordinal temporal extents (TM_Position values of 57TM_OrdinalEras defined within a TM_OrdinalReferenceSystem) and an indeterminate value of “now” is valid under
58 42 Domain As described in ISO 19108 Example From 2008-01-01T11:45:30 to 2008-12-31T09:10:00 Comments The overall time period covered by the content of the resource may be composed of one or many instances 1404 1405 1406Example of XML encoding: 1407 1408
14382.6.2 Date of publication 1439 1440This is the date of publication of the resource when available, or the date of entry into force. 1441There may be more than one date of publication. 1442Date of publication differs from the temporal extent. For example, a dataset might have been 1443published in March 2009 (2009-03-15) but the covered information was collected over the 1444year 2008 (temporal extent from 2008-01-01 to 2008-12-31) 1445 Metadata element name Date of publication Reference Part B 5.2 Definition Reference date for the cited resource - publication ISO 19115 number and name 392. date ISO/TS 19139 path identificationInfo[1]/*/citation/*/date[./*/dateType/*/text()='publicatio n']/*/date INSPIRE obligation / condition Conditional: at least one date of publication / date of creation / date of revision is required INSPIRE multiplicity [0..*] but at least one date of publication / date of creation / date of
59TM_Position. ISO 19108 TM_PeriodDuration also defines the distance in the temporal dimension
60 43 revision or one temporal extent is required Data type (and ISO 19115 no.) 393. CI_Date Domain Described in ISO 19108 and ISO 8601 Example 2009-03-15 2009-03-15T11:15:00 Comments 1446 1447 1448 1449Example of XML encoding: 1450 1451
61 44 14832.6.3 Date of last revision 1484 1485This date describes when the resource was last revised, if the resource has been revised. 1486Date of revision differs from the temporal extent. For example, a dataset might have been 1487revised in April 2009 (2009-04-15) but the covered information was collected over the year 14882008 (temporal extent from 2008-01-01 to 2008-12-31) 1489 Metadata element name Date of last revision Reference Part B 5.3 Definition Reference date for the cited resource - revision ISO 19115 number and name 392. date ISO/TS 19139 path identificationInfo[1]/*/citation/*/date[./*/dateType/*/text()='publicatio n']/*/date INSPIRE obligation / condition Conditional: at least one date of publication / date of creation / date of revision is required INSPIRE multiplicity [0..1] but at least one date of publication / date of creation / date of revision or one temporal extent is required Data type (and ISO 19115 no.) 393. CI_Date Domain Described in ISO 19108 and ISO 8601 Example 2009-04-15 2009-04-15T11:15:00 Comments There may be more than one revision date provided in an ISO 19115 metadata, but INSPIRE will consider as date of last revision the more recent one 1490 1491Example of XML encoding: 1492 1493
62 45 1521
15222.6.4 Date of creation 1523 1524This date describes when the resource was created. 1525Date of creation differs from the temporal extent. For example, a dataset might have been 1526created in February 2009 (2009-02-15) but the covered information was collected over the 1527year 2008 (temporal extent from 2008-01-01 to 2008-12-31) 1528 1529 Metadata element name Date of creation Reference Part B 5.4 Definition Reference date for the cited resource - creation ISO 19115 number and name 392. date ISO/TS 19139 path identificationInfo[1]/*/citation/*/date[./*/dateType/*/text()='publicatio n']/*/date INSPIRE obligation / condition Conditional: at least one date of publication / date of creation / date of revision is required INSPIRE multiplicity [0..1] but at least one date of publication / date of creation / date of revision or one temporal extent is required Data type (and ISO 19115 no.) 393. CI_Date Domain Described in ISO 19108 and ISO 8601 Example 2009-02-15 2009-02-15T11:15:00 Comments 1530
1531 TG Requirement 26 There shall be a single creation date for the resource (See 7 in 1532 1.2).
1533
63 46 1534 1535Example of XML encoding: 1536 1537
15662.7 Quality and validity
15672.7.1 Lineage 1568 1569According to the Implementing Rules for Metadata, Lineage is “a statement on process 1570history and/or overall quality of the spatial data set. Where appropriate it may include a 1571statement whether the data set has been validated or quality assured, whether it is the official 1572version (if multiple versions exist), and whether it has legal validity. The value domain of this 1573element is free text.” 1574 1575The process history may be described by information on the source data used and the main 1576transformation steps that took place in creating the current data set (series). 1577 1578 Metadata element name Lineage Reference Part B 6.1 Definition General explanation of the data producer’s knowledge about the lineage of a dataset ISO 19115 number and name 83. statement ISO/TS 19139 path dataQualityInfo/*/lineage/*/statement INSPIRE obligation / condition Mandatory for spatial dataset and spatial dataset series. Not applicable to services. INSPIRE multiplicity [1] for datasets and data set series [0] for spatial data services Data type (and ISO 19115 no.) CharacterString
64 47 Domain Free text Example Computation of the SPI involves fitting a probability density function to a given frequency distribution of precipitation totals for a station or grid point and for an accumulation period. We use the gamma probability density function. The statistics for the frequency distribution are calculated on the basis of a reference period of at least 30 years. The parameters of the probability density function are then used to find the cumulative probability of the observed precipitation for the required month and temporal scale. This cumulative probability is then transformed to the standardised normal distribution with mean zero and variance one, which results in the value of the SPI. The SPI values are computed using the so-called MARS weather stations as rainfall input data. Refer the MARS weather catalogue for characteristics of the quality and quantity of these data. We only rely on the rainfall data input Comments 1579 1580A single ISO 19115 metadata set may comprise more than one set of quality information 1581(dataQualityInfo elements), each of them having one or zero lineage elements. 1582
1583 TG Requirement 27 There shall be one and only one set of quality information 1584 scoped to the full resource and having a lineage statement 1585 (dataQualityInfo element). This element shall be scoped to the 1586 full data set (series) and have one lineage element (See 6 in 1587 1.2). The statement sub-element of the lineage element shall be 1588 used to implement the Lineage element defined in the 1589 Implementing Rules for Metadata.
1590 1591 TG Recommendation 16If a data provider has a procedure for the quality management of 1592 their spatial data set (series) then the appropriate ISO data quality 1593 elements and measures should be used to evaluate and report (in 1594 the metadata) the results. If not, the Lineage metadata element 1595 (defined in the Implementing Rules for Metadata) should be used to 1596 describe the overall quality of a spatial data set (series).
1597 1598 1599 TG Recommendation 17The use of acronyms should be avoided. If used, their meaning 1600 should be explained.
1601 1602NOTE: The INSPIRE data specifications contain further recommendations for documenting 1603the sources and process steps used for the creation of the data set (series), including its 1604transformation to make it compliant with the Implementing Rules on interoperability of spatial 1605data sets and services (see Annex B). 1606
65 48 1607 1608Example of XML encoding: 1609 1610
16492.7.2 Spatial resolution 1650 1651Spatial resolution refers to the level of detail of the data set. It shall be expressed as a set of 1652zero to many resolution distances (typically for gridded data and imagery-derived products) or 1653equivalent scales (typically for maps or map-derived products). 1654An equivalent scale is generally expressed as an integer value expressing the scale 1655denominador. A resolution distance shall be expressed as a numerical value associated with 1656a unit of length 1657 Metadata element name Spatial resolution Reference Part B 6.2 Definition Equivalent scale: level of detail expressed as the scale denominator of a comparable hardcopy map or chart Distance: ground sample distance ISO 19115 number and name 60. equivalentScale 61. distance ISO/TS 19139 path identificationInfo[1]/*/spatialResolution/*/equivalentScale/*/den ominator (equivalent scale)
66 49 identificationInfo[1]/*/spatialResolution/*/distance (distance) INSPIRE obligation / condition Conditional: Mandatory if an equivalent scale or a resolution distance can be specified. Conditional: Mandatory when there is a restriction on the spatial resolution for service. INSPIRE multiplicity [0..*] Data type (and ISO 19115 no.) Integer (equivalent scale) Distance (distance) Domain positive integer (equivalent scale) number expressing the distance value and a unit of measure of the distance value (distance) Example 50000 (e.g. 1:50000 scale map) 0.25 (degrees) Comments 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 1658
1659 TG Requirement 28 Each spatial resolution is either an equivalent scale OR a 1660 ground sample distance. Each spatialResolution element must 1661 contain either an equivalent scale or a distance but not both
1662 1663 TG Recommendation 18When two equivalent scales or two ground sample distances are 1664 expressed, the spatial resolution is an interval bounded by these 1665 two values
1666
67 50 1667 1668Example of XML encoding (equivalentScale): 1669 1670
68 51 1730
17312.8 Conformity
1732 TG Requirement 29 In conformance to INSPIRE Directive 2007/2/EC, the metadata 1733 shall include information on the degree of conformity with the 1734 implementing rules on interoperability of spatial data sets and 1735 services8.
1736 1737 1738NOTE 1 All Data Specifications Technical Guidelines include an Abstract Test Suite (ATS) in 1739Annex A describing through a number of tests how to evaluate conformity with the 1740Implementing Rules on interoperability of spatial data sets and services. 1741 1742NOTE 2 The ATS consists of several conformance classes that can be tested independently. 1743This enables data providers to also report conformity to different aspects of the Implementing 1744Rules in detail (see section 8 of the Data Specifications Technical Guidelines9). 1745 1746 TG Recommendation 19If a spatial data service is also an INSPIRE Network Service, it is 1747 recommended to include in its metadata information on the degree 1748 of conformity with the implementing rules provided in Art 11 1749 (Network Services).
1750 1751ISO 19115 provides an element (DQ_ConformanceResult) for reporting about the evaluation 1752of the conformity of the resource against a given specification. This element is used to handle 1753the requirements to report on the conformity with the Implementing Rules on interoperability 1754of spatial data sets and services or other specifications and standards. 1755
1756 TG Requirement 30 The INSPIRE Metadata Regulation 1205/2008/EC defines in 1757 Part D 5 When the conformity to any specification has been 1758 evaluated, it shall be reported as a domain consistency element 1759 (i.e. an instance of DQ_DomainConsistency) in ISO 19115 1760 metadata
1761 1762NOTE: The TG Requirement above applies to any specification against which the data has 1763been tested, not just those established by INSPIRE. In other words, if a dataset is produced 1764or transformed according to an external specification that includes specific quality assurance 1765procedures, the conformity with this specification should be documented using the Conformity 1766metadata element. 1767 1768The Conformity element defined in section 7 of Part B of the INSPIRE Implementing Rules for 1769metadata includes two sub-elements: the Specification (a citation of the specification against 1770which conformity was tested), and the Degree of conformity. The Degree of conformity can 1771take either of the following three values (see Part D.5 of the Implementing Rules): 1772 i. conformant (if the dataset is fully conformant with the cited specification), 1773 ii. not conformant (if the dataset does not conform to the cited specification) 1774 iii. not evaluated (if the conformance has not been evaluated) 1775 1776The case “not evaluated” was introduced as a transition measure because at the time of 1777adoption of the Metadata Implementing Rules (2008) there were no INSPIRE specifications
698 Commission Regulation (EU) No 1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the 70 European Parliament and of the Council as regards interoperability of spatial data sets and services, OJ L 323, 71 08/12/2010, p. 11–102. 729 See http://inspire.jrc.ec.europa.eu/index.cfm/pageid/2
73 52 1778(Implementing rules on the interoperability of spatial datasets and services) against which 1779conformance could be tested. 1780 TG Recommendation 20Now that the Implementing Rules on the interoperability of spatial 1781 datasets and services are in place, it is recommended to evaluate 1782 and declare the conformity of all data sets (i.e. as “conformant” or 1783 “not conformant”). 1784 1785NOTE: It is still possible to declare in the metadata that the conformity with the Implementing 1786Rules on interoperability of spatial data sets and services was “not evaluated”. This however 1787is difficult to implement using ISO 19115 which has only two degrees of conformity: 1788conformant (true) or not conformant (false). The previous version of these guidelines have 1789recommended to represent the value “not evaluated” by leaving the Conformity element 1790empty. This makes the metadata record compliant with ISO but not with INSPIRE as the 1791multiplicity of the Conformity element in the Metadata Implementing Rules is (1..*). 1792 1793ISO 19139 provides a mechanism to provide a null value with an explanation (using the 1794nilReason attribute). 1795 1796 TG Recommendation 21To declare that the conformity with the Implementing Rules on the 1797 interoperability of spatial datasets and services has not yet been 1798 evaluated, a null value should be provided with a nilReason of 1799 “unknown”.
1800 1801NOTE: A metadata record containing a null value for the Boolean-typed Pass element is not 1802compliant with ISO 19115. However, it is compliant with ISO 19139 and widely implemented. 1803In order to be sure to comply both with INSPIRE and ISO 19115, you are advised to 1804follow TG Recommendation 22 above. 1805
18062.8.1 Degree 1807 1808This is the degree of conformity of the resource to the implementing rules adopted under 1809Article 7(1) of INSPIRE Directive 2007/2/EC or other specification. 1810 Metadata element name Degree Reference Part B 7.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 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.) Boolean10 Domain true if conformant false if not conformant null (with nilReason = “unknown”) if not evaluated11
7410 75 7611 ISO/TS 19103 defines Boolean as a value defining TRUE or FALSE (EXAMPLE: true or false), while ISO 77 19115:2003 clearly states that the domain of value of the Boolean properties is 0="no", 1="yes". In the meantime, 78 ISO/TS 19139 implements the Boolean class using the XML build-in type xs:boolean (values are true or false), but 79 allows the provision of null values (together with a nilReason explaining why the actual value cannot be provided) 80 also for Boolean-type properties (see sections 8.4.1 and 9.7.3.4 in ISO 19139).
81 53 Example true Comments 1811Example of XML encoding 1812 1813… 1814
18312.8.2 Specification 1832 1833This is a citation of the implementing rules adopted under Article 7(1) of INSPIRE Directive 18342007/2/EC or other specificationto which a particular resource conforms. 1835 1836If a spatial data service is an INSPIRE Network service, use this element to report the 1837relevant INSPIRE Network Implementing Rule to which it confirms. 1838 1839A resource may conform to more than one implementing rules adopted under Article 7(1) of 1840INSPIRE Directive 2007/2/EC or other specification. 1841 Metadata element name Specification Reference Part B 7.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 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 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: COMMISSION REGULATION (EU) No 1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services date:
82 54 o dateType: publication o date: 2010-12-08 Comments 1842 1843Example of XML encoding: 1844 1845
83 55 1902
84 56 1903
19042.9 Constraints related to access and use 1905 1906ISO 19115 provides a general mechanism for documenting different categories of constraints 1907applicable to the resource (or its metadata). This mechanism is supported by the class 1908MD_Constraints and its subclasses: 1909 MD_LegalConstraints for legal constraints; 1910 MD_SecurityConstraints for security constraints. 1911 1912There are two major requirements expressed in INSPIRE Directive 20007/2/EC in terms of 1913documentation of the constraints as part of the metadata: 1914 The conditions applying to access and use of the resource, and where applicable, the 1915 corresponding fees as required by Articles 5-2(b) and 11-2(f). 1916 The limitations on public access: the Member States may limit public access to spatial 1917 datasets and spatial data services in a set of cases defined in Article 13. These cases 1918 include public security or national defence, i.e. more generally the existence of a 1919 security constraint. 1920 1921The current implementation guidelines (version 1.3) in chapter 2.9.1 and chapter 2.9.2 is not 1922fully inline with the intentions of ISO 19115 since the use of Uselimitation is used here also for 1923legal constraints. To give an option for thoose wanting an implementation closer to ISO 19115 1924we here describe an alternative solution. To fulfil the requirements of these technical 1925guidelines an implementation can select to either use 2.9.1 and 2.9.2 or to select the 1926implementation defined in 2.9.3 and 2.9.4. 1927 1928A metadata record that is using the implementation based on 2.9.3 and 2.9.4 is identified by 1929it’s reference in otherRestrictions to the the codelist in Inspire Registry at 1930http://inspire.ec.europa.eu/registry/metadata-codelist/LimitationsOnPublicAccess/ 1931 1932(Comment, we have to fully investigate consequences for discovery services queryables by 1933this alternative solution) 1934 1935Each instance of MD_Constraints expresses: 1936 Zero or One condition applying to access and use (see 2.9.2 or 2.9.4); 1937 Zero or More limitations on public access (see 2.9.1 or 2.9.2); 1938 Or, both one or more limitations on public access and a condition applying to access 1939 and use. 1940
1941 TG Requirement 31 There shall be at least one ISO 19115 metadata element 1942 representing a limitation on public access (see 2.9.1 or 2.9.3) 1943 and one ISO 19115 metadata element representing a condition 1944 applying to access and use (see 2.9.2 or 2.9.4) as part of the 1945 different instances of MD_Constraints and its subclasses.
1946
1947 TG Requirement 32 There shall be at least one instance of MD_Constraints or one of 1948 its subclasses (See 12 in Section 1.2) even if there is no 1949 limitation on public access or no specific condition applies to 1950 access and use of the resource.
1951
19522.9.1 Limitations on public access 1953 1954This metadata element shall provide information on the limitations and the reasons for them. 1955If there are no limitations on public access, use the free text available in
85 57 1956MD_LegalConstraints. otherConstraints to enter “No Limitations” in the language used for the 1957metadata. 1958
1959 TG Requirement 33 Limitations on public access shall be represented by at least one 1960 of these metadata elements: 1961 - MD_LegalConstraints. 1962 accessConstraints 1963 - MD_LegalConstraints. otherConstraints 1964 - MD_SecurityConstraints. classification
1965 1966 Metadata element name Limitations on public access (access constraints) Reference Part B 8.2 Definition access constraints applied to assure the protection of privacy or intellectual property, and any special restrictions or limitations on obtaining the resource ISO 19115 number and name 70. accessConstraints ISO/TS 19139 path identificationInfo[1]/*/resourceConstraints/*/accessConstraints INSPIRE obligation / condition Conditional: referring to limitations on public access. Mandatory if otherConstraints or classification are not documented INSPIRE multiplicity [0..*] for accessConstraints per instance of MD_LegalConstraints Data type (and ISO 19115 no.) MD_RestrictionCode Domain Codelist (strictly limited ti the value defined in B.5.24 of ISO 19115) Example otherRestrictions (limitation not listed). Comments 1967 1968 Metadata element name Limitations on public access (other constraints) Reference Part B 8.2 Definition Other restrictions and legal prerequisites for accessing and using the resource or metadata ISO 19115 number and name 72. otherConstraints ISO/TS 19139 path identificationInfo[1]/*/resourceConstraints/*/otherConstraints INSPIRE obligation / condition Conditional: referring to limitations on public access. Mandatory if accessConstraints or classification are not documented INSPIRE multiplicity [0..*] for otherConstraints per instance of MD_LegalConstraints Data type (and ISO 19115 no.) CharacterString Domain Free text Example No limitations Comments 1969 1970 Metadata element name Limitations on public access (classification) Reference Part B 8.2
86 58 Definition Name of the handling restrictions on the resource ISO 19115 number and name 74. classification ISO/TS 19139 path identificationInfo[1]/*/resourceConstraints/*/classification INSPIRE obligation / condition Conditional: referring to limitations on public access. Mandatory if accessConstraints or otherConstraints are not documented INSPIRE multiplicity [1] for classification per instance of MD_SecurityConstraints Data type (and ISO 19115 no.) MD_ClassificationCode Domain Codelist (see B.5.11 of ISO 19115) Example unclassified Comments 1971 1972In relation to MD_Constraints class, there may be three scenarios according to the tables 1973above: 1974 There may be no limitation on public access; 1975 There may be only a classification property when expressing a security constraint (i.e., 1976 this is an instance of MD_SecurityConstraints or one of its subclasses); 1977 There may be one or more instances of the accessConstraints property, possibly 1978 associated with one or more instances of otherRestrictions property (i.e, this is an 1979 instance of MD_LegalConstraints); 1980 1981Example of XML encoding: 1982 1983
87 59 2019 2020… 2021 2022 2023 2024 2025
20262.9.2 Conditions applying to access and use 2027 2028Conditions for access and use of spatial data sets and services, and where applicable, 2029corresponding fees as required by Article 5(2)(b) and Article 11(2)(f) of INSPIRE Directive 20302007/2/EC 2031 Metadata element name Conditions applying to access and use Reference Part B 8.1 Definition Restrictions on the access and use of a resource or metadata ISO 19115 number and name 68. useLimitation ISO/TS 19139 path identificationInfo[1]/*/resourceConstraints/*/useLimitation INSPIRE obligation / condition Mandatory INSPIRE multiplicity [1..*] Data type (and ISO 19115 no.) CharacterString Domain Free text Example Example if no conditions apply: no conditions apply Example if there is information about restrictions: Reproduction for non-commercial purposes is authorised, provided the source is acknowledged. Commercial use is not permitted without prior written consent of the JRC. Reports, articles, papers, scientific and non-scientific works of any form, including tables, maps, or any other kind of output, in printed or electronic form, based in whole or in part on the data supplied, must contain an acknowledgement of the form: Data re-used from the European Drought Observatory (EDO) http://edo.jrc.ec.europa.eu The SPI data were created as part of JRC's research activities. Although every care has been taken in preparing and testing the data, JRC cannot guarantee that the data are correct; neither does JRC accept any liability whatsoever for any error, missing data or omission in the data, or for any loss or damage arising from its use. The JRC will not be responsible for any direct or indirect use which might be made of the data. The JRC does not provide any assistance or support in using the data Comments 2032
2033 TG Requirement 34 If no conditions apply to the access and use of the resource, ‘no 2034 conditions apply’ shall be used. If conditions are unknown, 2035 ‘conditions unknown’ shall be used.
2036
88 60 2037 TG Requirement 35 Descriptions of terms and conditions, including where 2038 applicable, the corresponding fees shall be provided through this 2039 element or a link (URL) where these terms and conditions are 2040 described.
2041 2042 TG Recommendation 22For detailed information it is recommended to provide a link to a 2043 license type (e.g. http://creativecommons.org/licenses/by/3.0), a 2044 website or to a document containing the necessary information.
2045 2046
89 61 2047 2048Example of XML encoding: 2049 2050
20882.9.3 Limitations on public access – Alternative solution 2089 2090In Article 13 in INSPIRE Directive 20007/2/EC there is a list of cases where limitations to 2091public acess can be set. 2092 2093These are: 2094 (a) the confidentiality of the proceedings of public auth 2095 where such confidentiality is provided for by law ; 2096 (b) international relations, public security or national defence; 2097 (c) the course of justice, the ability of any person to receive a 2098 fair trial or the ability of a public authority to conduct an 2099 enquiry of a criminal or disciplinary nature; 2100 (d) the confidentiality of commercial or industr ial infor mation, 2101 where such conf identiality is provided for by national or 2102 Community law to protect a legitimate economic interest, 2103 including the public interest in maintaining statistical 2104 confidentiality and tax secrecy ; 2105 (e) intellectual property rights; 2106 (f) the confidentiality of personal data and/or files relating to a 2107 natural person where that person has not consented to the
90 62 2108 disclosure of the information to the public, where such 2109 confidentiality is provided for by national or Community 2110 law ; 2111 (g) the interests or protection of any person who supplied the 2112 infor mation requested on a voluntary basis without being 2113 under, or capable of being put under, a legal obligation to 2114 do so, unless that person has consented to the release of the 2115 information concerned; 2116 (h) the protection of the environment to which such information relates, such as the 2117 location of rare species. 2118 2119 2120
2121 TG Requirement 36 Limitations on public access shall be represented by one 2122 instance of 2123 MD_LegalConstraints.accessConstraints 2124 and at least one instance of 2125 MD_LegalConstraints. otherConstraints 2126 containing a link to the code list for Limitations on Public Access 2127 in Inspire registry describing the limitation. 2128 (http://inspire.ec.europa.eu/registry/metadata-codelist /Limitatio 2129 nsOnPublicAccess/) 2130
2131To separate the Limitations on public access from other access restrictions the description of 2132the access restriction in element otherRestrictions shall be implemented using an Anchor 2133element linking to the Inspire registry referencing the specific restriction. 2134The url to this code list is 2135 2136 http://inspire.ec.europa.eu/registry/metadata-codelist /LimitationsOnPublicAccess/ 2137 2138To reference a specific Public Limitations eg “( e ) intellectual property rights”; 2139the following codevalue should be used 2140 http://inspire.ec.europa.eu/registry/metadata-codelist / 2141LimitationsOnPublicAccess/INSPIRE_Directive_Article13_e 2142 2143If no limitation on public access exists then the value no limitations shall be used 2144 http://inspire.ec.europa.eu/registry/metadata-codelist / 2145LimitationsOnPublicAccess/noLimitations 2146 2147
91 63 2166
92 64 2184 2185
21862.9.4 Conditions applying to access and use - alternative 2187 implementation 2188 2189Conditions for access and use of spatial data sets and services, and where applicable, 2190corresponding fees as required by Article 5(2)(b) and Article 11(2)(f) of INSPIRE Directive 21912007/2/EC 2192 2193
2194 TG Requirement 37 Contitions applying to access and use shall be represented by 2195 one instance of 2196 MD_LegalConstraints.otherConstraints 2197 This shall NOT contain a link to the code 2198 list for Limitations on Public Access in Inspire registry since that 2199 is reserved for documenting Limitations on public access ( see 2200 2.9.3) 2201
2202 2203 2204Conditions applying to access 2205 Metadata element name Conditions applying to access Reference Part B 8.1 Definition Restrictions on the access and use of a resource or metadata ISO 19115 number and name 70. accessConstraints ISO/TS 19139 path identificationInfo[1]/*/resourceConstraints/*/accessConstraints INSPIRE obligation / condition INSPIRE multiplicity [0..*] for accessConstraints per instance of MD_LegalConstraints Data type (and ISO 19115 no.) MD_RestrictionCode Domain Codelist (strictly limited ti the value defined in B.5.24 of ISO 19115) Example otherRestrictions (limitation not listed). Comments 2206 2207 Metadata element name Conditions applying to access (other constraints) Reference Part B 8.1 Definition Other restrictions and legal prerequisites for accessing and using the resource or metadata ISO 19115 number and name 72. otherConstraints ISO/TS 19139 path identificationInfo[1]/*/resourceConstraints/*/otherConstraints INSPIRE obligation / condition Conditional: referring to limitations on public access. Mandatory if accessConstraints or classification are not documented INSPIRE multiplicity [0..*] for otherConstraints per instance of MD_LegalConstraints Data type (and ISO 19115 no.) CharacterString
93 65 Domain Free text or if the values “no conditions apply” or “conditions unknown” is used then a an Anchor to the codelist in the Inspire Registry should be used. Example http://inspire.ec.europa.eu/registry /metadata-codelist/ ConditionsApplyingToAccessAndUse/ NoConditionsApply
Comments The domain of the metadata element otherConstraints is Free text. This makes it hard to unambiguous define some common values in all official languages in the Communiy. Therefore it is recommended to refer to codelists in the Inspire registry for some specific values like “no conditions apply” and “conditions unknown”.
2208 2209 2210Conditions applying to use 2211 Metadata element name Conditions applying to use Reference Part B 8.1 Definition Restrictions on the use of a resource or metadata ISO 19115 number and name 70. useConstraints ISO/TS 19139 path identificationInfo[1]/*/resourceConstraints/*/useConstraints INSPIRE obligation / condition INSPIRE multiplicity [0..*] for useConstraints per instance of MD_LegalConstraints Data type (and ISO 19115 no.) MD_RestrictionCode Domain Codelist (strictly limited to the value defined in B.5.24 of ISO 19115) Example otherRestrictions (limitation not listed). Comments 2212 2213 Metadata element name Conditions applying to use (other constraints) Reference Part B 8.1 Definition Other restrictions and legal prerequisites for accessing and using the resource or metadata ISO 19115 number and name 72. otherConstraints ISO/TS 19139 path identificationInfo[1]/*/resourceConstraints/*/otherConstraints INSPIRE obligation / condition Conditional: referring to limitations on public access. Mandatory if accessConstraints or classification are not documented INSPIRE multiplicity [0..*] for otherConstraints per instance of MD_LegalConstraints Data type (and ISO 19115 no.) CharacterString Domain Free text or if the values “no conditions apply” or “conditions unknown” is used then a an Anchor to the codelist in the Inspire Registry should be used.
94 66 Example http://inspire.ec.europa.eu/registry/metadata-codelist/ ConditionsApplyingToAccessAndUse/NoConditionsApply Comments The domain of the metadata element otherConstraints is Free text. This makes it hard to unambiguous define some common values in all official languages in the Communiy. Therefore it is recommended to refer to codelists in the Inspire registry for some specific values like “no conditions apply” and “conditions unknown”. 2214 2215 2216 2217Examples 2218 2219No conditions apply for either Access or Use restrictions. 2220(note we could have also added both elements gmd:accessConstraints and 2221gmd:useConstraints with codelistvalue OtherConstraints. But these are optional.) 2222
2249
95 67 2268… 2269 2270 2271… 2272 2273 2274 2275No conditions apply for either Access or Use restrictions using a language neutral 2276identifier - in Swedish
2278
2307
96 68 2331articles, papers, scientific and non-scientific works of any form, 2332including tables, maps, or any other kind of output, in printed or 2333electronic form, based in whole or in part on the data supplied, must 2334contain an acknowledgement of the form: Data re-used from the 2335European Drought Observatory (EDO) http://edo.jrc.ec.europa.eu The 2336SPI data were created as part of JRC's research activities. Although 2337every care has been taken in preparing and testing the data, JRC 2338cannot guarantee that the data are correct; neither does JRC accept 2339any liability whatsoever for any error, missing data or omission in 2340the data, or for any loss or damage arising from its use. The JRC 2341will not be responsible for any direct or indirect use which might be 2342made of the data. The JRC does not provide any assistance or support 2343in using the data 2344
2345 2347 2348 2349 2350… 2351 2352 2353… 2354 2355 2356 2357An access and use restriction apply
2359
3593A.4.2 Parsing of metadata files 3594 3595To accommodate polymorphism of the data types, parsing of metadata files has to be driven 3596by the XML elements corresponding to the properties of the UML models (look rather for the 3597metadata elements named identificationInfo, than the metadata elements named 3598MD_DataIdentification or SV_ServiceIdentification). The elements corresponding to the data 3599type can generally be skipped.
141 110 3600 3601When it is necessary to evaluate the XML element representing data types (e.g., because the 3602application needs to consider the data identification info, but not the service identification 3603info), it is important to look for the XML element corresponding to the expected ISO data type 3604(e.g., gmd:MD_DataIdentification) or the XML element for which the value of gco:isotype is 3605the expected data type (e.g. MD_DataIdentification). There is no namespace indication in the 3606value of the isoType attribute. 3607
3608A.5 Management of containment by reference 3609 3610Any instance of a UML property can be implemented: 3611 by value, i.e. the instance of its datatype is a subelement of the property instance; 3612 3613
3635A.6 ISO 19139 and multilingual metadata 3636 3637An optional but repeatable attribute “locale” has been added to the class MD_Metadata. Two 3638cases are to be considered: 3639- When this attribute is not implemented, the metadata set is expected to be monolingual: 3640 the language of the metadata is defined by the language attribute of MD_Metadata. 3641- When this attribute is implemented, each instance represents a locale (language, country 3642 and character encoding) in which the metadata elements may be translated. The 3643 language attribute still defines the default language of the metadata, i.e. the language in 3644 which all the metadata elements are expressed. Then each metadata element can be 3645 translated in some of the locales define for the metadata set. 3646
142 111 MD_Metadata PT_Locale + fileIdentifier [0..1] : CharacterString + language : LanguageCode + language [0..1] : CharacterString + country [0..1] : CountryCode + characterSet [0..1] : MD_CharacterSetCode = "utf8" + characterEncoding : MD_CharacterSetCode + parentIdentifier [0..1] : CharacterString + hierarchyLevel [0..*] : MD_ScopeCode = "dataset" + hierarchyLevelName [0..*] : CharacterString + contact [1..*] : CI_ResponsibleParty <
<
3652 3653 3654Support of free text is enabled via a subtype of CharacterString called PT_FreeText which 3655aggregates a set of localised character strings through its textGroup property. Each localised 3656character string provides a translation of the character string in the related locale. 3657 <
PT_FreeText LocalisedCharacterString
1 1..* +textGroup 1 +locale
PT_Locale + language : LanguageCode + country [0..1] : CountryCode + characterEncoding : MD_CharacterSetCode 3658 3659 3660The following clauses define the way multilingual metadata are implemented. 3661
3662A.6.1 The default language 3663 3664The default language of a metadata set is defined by the language property of MD_Metadata 3665while the characterSet property defines the corresponding character encoding. Here is a 3666sample instance of the class MD_Metadata illustrating the use of both properties. 3667 3668
143 112 3671
3684A.6.2 Alternate languages 3685 3686Each metadata alternate language of the metadata is defined through the locale property of 3687MD_Metadata. In the following example, some of these metadata are translated into French13: 3688 3689
3710A.6.3 Embedded translations 3711 3712Any metadata element having a free text domain (e.g. the abstract property of 3713MD_DataIdentification) can then be instantiated like this: 3714 3715
14413 Please note that both “fre” and “fra” are compatible with ISO 639-2 which distinguishes the 145bibliography codes (e.g. fre) from the terminology codes (e.g. fra). This issue concerns also any 146language having different codes for bibliography and terminology. The Drafting team has chosen the 147bibliography codes.
148 113 3726 3727The xsi:type attribute indicates that this instance of the abstract property is not instantiated 3728through a simple CharacterString, but rather as a free text. As a consequence, the element 3729contains a complementary PT_FreeText subelement containing one or more textGroup 3730elements (one per translation). 3731
3732A.6.4 Use of translation files 3733 3734In the preceding example, the definition of the locale property is provided by value which 3735implies that the translations are embedded with default language metadata. It is also possible 3736to store the translations corresponding to a given language into a translation file using the 3737PT_LocaleContainer class. In such case, it is easier to define the locale within the translation 3738file (e.g. fr-fr.xml) and to express the instance of the MD_Metadata locale property by 3739reference. 3740
149 114 3783A.7 Contexts of use
3784A.7.1 Use of ISO 19139 in the context of a Catalogue Service 3785 3786When the data being passed through a cataloguing service is XML encoded, the catalogue 3787service interface defines the different XML Schemas to be used as a response to the user 3788queries. When the geographic metadata XML Schema is used, there should be one or many 3789MD_Metadata instances in the returned XML File.
3790A.7.2 Use of ISO 19139 in the context of the standard interchange by 3791transfer 3792 3793The transfer aggregate and transfer dataset concepts are the two major components of an 3794interchange by transfer. There may be one or many XML Files composing the interchange, 3795but the root element of at least one of the files is an XML instance of MX_Dataset, 3796MX_Aggregate or one of their extensions. From such an element, the parsing of the 3797interchange is model driven and it follows the principles described in 7.4 of ISO 19139. See 3798ISO 19139 for details about MX_Dataset and MX_Aggregate.
3799A.8 Character encoding 3800 3801Character encoding is defined in MD_Metadata.characterEncoding and MD_Metadata.locale. 3802Preferably this should be UTF-8 if the XML files contain multilingual metadata.
3803A.9 Temporal extent encoding 3804 3805In ISO 19115, temporal extents are of type TM_Primitive (abstract type from ISO 19108). In 3806ISO 19139, this type (and its sub-types) are mapped to ISO 19136 temporal types and W3C 3807built-in types. In the INSPIRE Metadata Element Set for discovery, the concrete TM_Period 3808subtype of TM_Primitive is used as type for the XML element temporalExtent. It is 3809implemented as type TimePeriod from ISO 19136. 3810 3811TimePeriod offers three options to express a time interval: 3812 3813 Use two TimePosition elements for beginPosition and endPosition. Date and time 3814 information is contained in-line and cannot be referenced from another XML Element. Only 3815 the TimePeriod element can, through its gml:id. 3816 3817 3818
150 115 3838 3839 Use two TimeInstant elements: Date and time information is here contained by 3840 reference and the TimeInstant elements can be re-used through a reference from another 3841 XML element in the XML file. The TimePeriod element can also be re-used. 3842 3843 3844
151 116 3901
3902A.10 Spatial resolution encoding 3903 3904The spatial resolution of a dataset or dataset series can be expressed as an equivalent scale 3905or as a resolution distance: 3906 Expression as an equivalent scale: 3907 3908 3909
152 117 3955 3956 If needed, the two options can be used in conjunction: 3957 3958 3959
3988A.11 Codelists 3989 3990The two recommended ways to reference codelists are those expressed in the examples 3991shown in 2.2.7 Resource Language.
153 118 3992A.12 Example of ISO 19139 XML Metadata Sets 3993
3994A.12.1 Dataset
3995A.12.1.1 INSPIRE view 3996 3997 + Part B 1 Identification: + Part B 1.1 Resource Title: SPI: Standardized Precipitation Index + Part B 1.2 Resource The Standardized Precipitation Index (SPI-n) is a statistical Abstract: indicator comparing the total precipitation received at a particular location during a period of n months with the long-term rainfall distribution for the same period of time at that location. SPI is calculated on a monthly basis for a moving window of n months, where n indicates the rainfall accumulation period, which is typically 1, 3, 6, 9, 12, 24 or 48 months. The corresponding SPIs are denoted as SPI-1, SPI-3, SPI-6, etc.In order to allow for the statistical comparison of wetter and drier climates, SPI is based on a transformation of the accumulated precipitation into a standard normal variable with zero mean and variance equal to one. SPI results are given in units of standard deviation from the long-term mean of the standardized distribution.In 2010 WMO selected the SPI as a key meteorological drought indicator to be producedoperationally by meteorological services + Part B 1.3 Resource Type: dataset + Part B 1.4 Resource http://edo.jrc.ec.europa.eu/chm/ows.php?VERSION=1.3.0&SERVICE= Locator: WMS&REQUEST=GetCapabilities + Part B 1.5 Resource Unique Identifier: + code: e24425e1-b073-11e1-9105-0017085a97ab + codeSpace: edo + Part B 1.7 Resource language: eng + Part B 2 Classification of data and services: + Part B 2.1 Topic category: climatologyMeteorologyAtmosphere + Part B 3 Keyword: + Part B 3.1 Keyword value: Atmospheric conditions + Part B 3.2 Originating Controlled Vocabulary: + title: GEMET - INSPIRE themes, version 1.0 + reference date: + date: 2008-06-01 + date type: publication + Part B 4 Geographic Location: + Part B 4.1 Bounding Box: + West: -15.00 + East: 45.00 + North: 35.00 + South: 72.00 + Part B 5 Temporal Reference: + Part B 5.2 Date of publication: 2012-02-20 + Part B 6 Quality and validity: Computation of the SPI involves fitting a probability density function to a given frequency distribution of precipitation totals for a station or grid point and for an accumulation period. We use the gamma probability density function. The statistics for the frequency distribution are calculated on the basis of a reference period of at least 30 years.The parameters of the probability Part B 6.1 density function are then used to find the cumulative probability of the + Lineage: observed precipitation for the required month and temporal scale. This cumulative probability is then transformed to the standardised normal distribution with mean zero and variance one, which results in the value of the SPI. The SPI values are computed using the so-called MARS weather stations as rainfall input data. Refer the MARS weather catalogue for characteristics of the quality and quantity of these data. We only rely on the rainfall data input. + Part B 6.2 Spatial Resolution: 0.25
154 119 + Part B 7.1 Specification: + title: COMMISSION REGULATION (EU) No 1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services + publication date: 2010-12-08 + Part B 7.2 Degree: not evaluated + Part B 8 Constraints related to access and use: + Part B 8.2 Limitation on public access: no limitations + Part B 8 Constraints related to access and use: + Part B 8.1 Condition applying to access and use: Reproduction for non-commercial purposes is authorised, provided the source is acknowledged. Commercial use is not permitted without prior written consent of the JRC. Reports, articles, papers, scientific and non-scientific works of any form, including tables, maps, or any other kind of output, in printed or electronic form, based in whole or in part on the data supplied, must contain an acknowledgement of the form: Data re- used from the European Drought Observatory (EDO) http://edo.jrc.ec.europa.eu The SPI data were created as part of JRC's research activities. Although every care has been taken in preparing and testing the data, JRC cannot guarantee that the data are correct; neither does JRC accept any liability whatsoever for any error, missing data or omission in the data, or for any loss or damage arising from its use. The JRC will not be responsible for any direct or indirect use which might be made of the data. The JRC does not provide any assistance or support in using the data + Part B 9 Responsible Organisation: + Part B 9.1 Responsible party: + organisation: European Commission, Joint Research Centre + e-mail: [email protected] + Part B 9.2 Responsible party role: custodian + Part B 10 Metadata on metadata: + Part B 10.1 Metadata point of contact: + organisation: European Commission, Joint Research Centre + e-mail: [email protected] + Part B 10.2 Metadata date: 2012-02-20 + Part B 10.3 Metadata language: eng 3998
155 120 3999A.12.1.2 ISO/TS 19139 XML File 4000 4001NOTE: This file is an ISO compliant metadata record extracted from the INSPIRE geo-portal 4002and tested through the INSPIRE Validator. It may contain more elements than the minimum 4003required to comply with the INSPIRE metadata Regulation. 4004
4005 4006
156 121 4067
157 122 4139 4140
158 123 4211
160 125 4358
161 126 4430
162 127 4502
163 128 4574 feature classes in which CCM 2 is structured. A detailed report on the development of CCM 2.0 as 4575 well Release Notes for CCM 2.1 are provided at http://ccm.jrc.ec.europa.eu/documents/CCM2- 4576 Report_EUR-22920-EN_2007_STD.pdf. 4577 4578 4579 4580 4581 4582
4583
4584A.12.2 Dataset series 4585 4586There is no significant difference between the metadata of a dataset and the metadata of a 4587dataset series. See A.11.1. 4588
4589A.12.3 Service
4590A.12.3.1 INSPIRE view 4591 + Part B 1 Identification: + Part B 1.1 Resource Title: Catchment Characterisation Model (CCM) - Demo INSPIREView Service + Part B 1.2 Resource Demonstrates implementation of the View Service according to the Abstract: INSPIRE technical guidelines for the Catchment Characterisation Model (CCM) database. Drainage networks and associated drainage basins form complex functional entities not only for hydrological processes but also for environmental processes at large. This has been recognised in recent European legislation such as the Water Framework Directive (WFD). In order to study the underlying processes and cause-effect relationships at regional to European scales, comprehensive digital data of river networks, drainage basins (catchments) and their characteristics are required. JRC's Catchment Characterisation and Modelling (CCM) activity responded to this need through the development of a pan-European database of river networks and catchments. Version 1.0 of CCM has been published in 2003. In July 2007 an geographically extended and substantially improved CCM Version 2.0 has been released. The current Version 2.1 of July 2008 is an update of version 2.0. It includes the correction of noted errors as well additional functionality. A detailed report on the development of CCM 2.0 as well Release Notes for CCM 2.1 are provided on the CCM website. + Part B 1.3 Resource Type: service + Part B 1.4 Resource http://ags-sdi-public.jrc.ec.europa.eu/arcgis/services/CCM_WGS84/MapServer/WMSServer? Locator: request= GetCapabilities&service=WMS + Part B 1.4 Resource Locator: + Part B 1.6 Coupled Resource: + ref: Code: http://rdsi.jrc.ec.europa.eu/id/dataset/ccm2.1/lakes, Namespace: rdsi + Part B 2 Classification of data and services: + Part B 2.2 Spatial data service type: View Service + Part B 3 Keyword: + Part B 3.1 Keyword value: Geographic viewer (humanGeographicViewer) + Part B 3 Keyword: + Part B 3.1 Keyword value: river basin development + Part B 3 Keyword: + Part B 3.1 Keyword value: river management + Part B 4 Geographic Location: + Part B 4.1 Bounding Box: + West: -32.0 + East: +61.0 + North: +27.0
164 129 + South: +72.0 + Part B 5 Temporal Reference: + Part B 5.2 Date of publication: 2007-06-01 + Part B 6 Quality and validity: + Part B 7.1 Specification: + title: COMMISSION REGULATION (EU) No 1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services + publication date: 2010-03-29 + Part B 7.2 Degree: true + Part B 7.1 Specification: + title: Commission Regulation (EC) No 976/2009 of 19 October 2009 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards the Network Services + publication date: 2009-10-19 + Part B 7.2 Degree: true + Part B 8 Constraint related to access and use: + Part B 7.1 Specification: + title: Technical Guidance for the implementation of INSPIREView Services + publication date: 2011-11-07 + Part B 7.2 Degree: true + Part B 8.1 Condition applying to access and use: no condition apply + Part B 8.2 Limitation on public access: no limitations + Part B 9 Responsible Organisation: + Part B 9.1 Responsible party: + organisation: European Commission, Joint Research Centre + e-mail: [email protected] + Part B 9.2 Responsible party role: custodian + Part B 10 Metadata on metadata: + Part B 10.1 Metadata point of contact: + organisation: European Commission Joint Research Centre + e-mail: [email protected] + Part B 10.2 Metadata date: 2012-11-28 + Part B 10.3 Metadata language: eng 4592
4593A.12.3.2 ISO/TS 19139 XML File 4594
4595 4596
165 130 4622
166 131 4694 4695
167 132 4766 4767 4768
168 133 4838 169 134 4913 codeList="http://www.isotc211.org/2005/iso19119/resources/Codelist/gmxCodelists.xml#DCPList"/> 4914 170 135 4985 codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/c 4986 odelist/ML_gmxCodelists.xml#CI_OnLineFunctionCode" 4987 codeListValue="information">information 4988
171 136 5057
172 137 5129 5130 5131 5132 5133 5134
5150
173 138 5151 Annex B 5152 (informative) 5153 5154 Metadata elements for interoperability
5155This Annex gives an overview of the additional metadata elements defined in the INSPIRE 5156Implementing Rules on the Interoperability of Spatial Datasets and Services (Commission 5157Regulation (EU) No 1089/2010) and in the Data Specifications Technical Guidelines for the 5158Annex I-III spatial data themes. 5159 5160For further details, see the Data Specifications Technical Guidelines14.
5161B.1. Metadata elements required by the INSPIRE 5162Implementing Rules on the Interoperability of Spatial Datasets 5163and Services 5164The following metadata elements are defined as “metadata required for interoperability” in 5165Article 13 of the Implementing Rules on the Interoperability of Spatial Datasets and Services. 5166They are applicable to all Spatial Data Themes from Annexes I, II and III. 5167 5168 Condition Metadata element Definition Multiplicity Description of the Coordinate reference coordinate reference 1..* system system(s) used in the data set. Description of the Mandatory, if the spatial data set or temporal reference one of its feature types contains Temporal reference systems used in the 0..* temporal information that does not system dataset. refer to the Gregorian Calendar or the Coordinated Universal Time. Description of the computer language construct(s) specifying the representation of Encoding 1..* data objects in a record, file, message, storage device or transmission channel. The character Mandatory if an encoding is used Character encoding encoding used in the 0..* that is not based on UTF-8. data set. The method used to Spatial representation spatially represent 1..* type geographic information. Correctness of the Mandatory if the data set includes explicitly encoded types from the Generic Network Data Quality – Logical topological Model and does not assure consistency – 0..* characteristics of the centreline topology (connectivity of Topological consistency data set as described centrelines) for the network. by the scope. 5169
17414 Please note that the implementation guidelines for the common metadata elements have been revised during the 175 work on the Annex II+III data specifications. The current guidelines are available in the common data specification 176 document template (available in the “Framework Documents” section on 177 http://inspire.jrc.ec.europa.eu/index.cfm/pageid/2). At the time of writing (October 2013), the Annex I data 178 specifications are being updated to be consistent with this document template and the updated guidelines.
179 139 5170B.2. Metadata elements recommended in the INSPIRE Data 5171Specifications Technical Guidelines
5172 5173The following metadata elements are recommended as common metadata elements for all 5174Spatial Data Themes from Annexes I, II and III. 5175 Metadata element Multiplicity
Data Quality – Logical Consistency – 0..* Conceptual Consistency Data Quality – Logical Consistency – 0..* Domain Consistency
Maintenance information 0..1
5176 5177The following tables give an overview of additional metadata elements that are recommended 5178for specific Spatial Data Themes from Annex II and III. 5179 THEMES FROM ANNEX II y r r e e n y v g o g i a o t o c l a m i o v d o e e n l h G a t E r L
O Metadata element Multiplicity Data Quality – Completeness - 0..* 0..* Commission Data Quality – Completeness - 0..* 0..* 0..* Ommission Data Quality – Logical Consistency – 0..* 0..1 Format Consistency Data Quality – Positional accuracy – 0..* 0..* Absolute or external accuracy Data Quality – Positional accuracy – 0..* (C) 0..* Gridded data position accuracy Data Quality –Thematic accuracy – 0..* Classification Correctness Data Quality – Positional accuracy – 0..* Relative or Internal Accuracy Data Quality – Temporal quality – 0..* Temporal Consistency Data Quality – Temporal quality – 0..* Temporal Validity Data Quality – Temporal quality –
Accuracy of a time measurement Data Quality – Thematic accuracy – 0..* Non-quantitative Attribute Accuracy Data Quality – Thematic accuracy – 0..* Quantitative Attribute Accuracy Data Quality – DQ_UsabilityElement Spatial representation information 0..* Supplemental information 0..1 Process step 0..* 0..* Data source 0..* 0..* Browse graphic information 0..* 0..*
180 140 Digital transfer options information 0..* 0..* Image description 0..* Content Information
5180
181 141 5181 5182 THEMES FROM ANNEX III (table 1/2) d s n e a r
u s t e a - g s t n y e s t n f n n o i
s n e s l r e z o f e t
i o a s i o i a p m n t g c e t e n i i s i r o e e o
c u t n i h r d r
u g t d t o o l p n s u g a l i a s n l a a o g o n n u b e m a r i
c i
u
s a n c t i l C t g i d
i g r h e a a h l t o m d c i e t n o l
u l i R p r e i c a n r a / p a q a g s a u y e e e e r n e
a s e r l
F r g t h h B g o i m
r i a t d a p A o t i t n e n c l n i s i e c i a o n i a b o g g c r
r E i - l t a m a o m v f l a o s u H t i r n o e H A r u r B E / t o l e u t c e i r M
g A Metadata element Multiplicity Data Quality – Completeness - 0..* Commission Data Quality – Completeness - 0..* 0..* Ommission Data Quality – Logical Consistency –
Format Consistency Data Quality – Positional accuracy – 0..* 0..* 0..* Absolute or external accuracy Data Quality – Positional accuracy –
Gridded data position accuracy Data Quality –Thematic accuracy – 0..* Classification Correctness Data Quality – Positional accuracy –
Relative or Internal Accuracy Data Quality – Temporal quality –
Temporal Consistency Data Quality – Temporal quality – 0..* 0..* Temporal Validity Data Quality – Temporal quality –
Accuracy of a time measurement Data Quality – Thematic accuracy –
Non-quantitative Attribute Accuracy Data Quality – Thematic accuracy – 0..* Quantitative Attribute Accuracy Data Quality – DQ_UsabilityElement 0..* Spatial representation information Supplemental information Process step Data source Browse graphic information Digital transfer options information Image description Content Information 0..1
5183 5184 5185 5186 5187 5188
182 142 5189 5190 5191
183 143 5192 THEMES FROM ANNEX III (table 2/2) n s s o e i e s c d l t l i t c - n i s y n a r u a h t n o l n a n n h d u c b e
p s n z i i s a s o u o o p n
o i i s r a e n i e i e h e t i l r t a a k r l s t u r t t o
i g c r p a a s i i s e m i g u l i s l u y i e t o a g c d i t v t n r o b i R u r d u c i
r i S R o r c t
n a l l n
l r p g i d u e e a s s a e t t a a a a i m o o f n s d v r e F t r s L I e e e i U i e P o o a u e c c d r S t t d g g n e a i O P S p N M
S Metadata element Multiplicity Data Quality – Completeness - 0..* --- 0..1 0..* Commission Data Quality – Completeness - 0..* 0..* --- 0..* 0..* 0..1 0..* Ommission Data Quality – Logical Consistency – --- 0..* Format Consistency Data Quality – Positional accuracy – 0..* 0..* --- 0..* 0..* 0..1 0..* Absolute or external accuracy Data Quality – Positional accuracy – --- Gridded data position accuracy Data Quality –Thematic accuracy – 0..* --- 0..* 0..1 0..* Classification Correctness Data Quality – Positional accuracy – --- 0..* Relative or Internal Accuracy Data Quality – Temporal quality – --- 0..* Temporal Consistency Data Quality – Temporal quality – --- 0..* 0..1 Temporal Validity Data Quality – Temporal quality – --- 0..* Accuracy of a time measurement Data Quality – Thematic accuracy – 0..* --- 0..* Non-quantitative Attribute Accuracy Data Quality – Thematic accuracy – --- 0..* Quantitative Attribute Accuracy Data Quality – DQ_UsabilityElement 0..* --- 0..* Spatial representation information --- Supplemental information --- Process step --- Data source --- Browse graphic information --- Digital transfer options information --- Image description --- Content Information ---
5193 5194 5195 5196
184 144