Draft Technical Guidance for INSPIRE Download Services

Transcript

1 INSPIRE Infrastructure for Spatial Information in Europe the Technical Guidance for implementation of Download INSPIRE Services Title Technical Guidance for the implementation of INSPIRE Download Services Creator orce Initial Operating Capability Task F for Network Services Date - - 201 3 09 08 Subject INSPIRE Download Services Status 1 Published, Version 3. Publisher Initial Operating Capability Task Force Type Text Description This document defines technical guidance for INSPIRE Download Services Format PDF Source for the Implementation of INSPIRE Download Technical Guidance 1 ( ersion 3 . v ) Services Rights Public Identifier v3. 1 Technical_Guidance_Download_Services_ Language EN Relation COMMISSION REGULATION (EU) No 1088/2010 of 23 November 201 0 amending Regulation (EC) No 976/2009 as regards download services and transformation services Coverage Project duration

2 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - - 2013 Page 2 of 89 08 Table of contents ... ... 8 ... Acknowledgements ... ... ... ... ... Foreword ... 9 ... ... ... ... 11 tory Revision His Introduction ... ... ... ... 1 14 ... ... ... ... 15 2 Normative references Terms and abbreviations ... ... ... ... 16 3 . ... ... ... ... 16 3.1 Terms 3.2 tions ... ... ... ... 17 Abbrevia 3.3 Verbal forms for the expression of provisions ... ... ... 18 References ... ... ... ... 19 3.4 Future updates of this document ... ... ... 19 3.5 INSPIRE Downloa d Services ... ... ... ... 20 4 ... 4.1 ... 23 How the Technical Guidance maps to the Implementing Rules - based Technical Guidance to the Implementing Rules ... 24 4.1.1 Mapping the Atom Mapp ing the WFS - based Technical Guidance to the Implementing Rules 4.1.2 ... 26 4.1.3 Mapping of Spatial Data Set Identifier parameter ... ... 29 Conformance Classes for Download Services Technical Guidance 4.2 ... ... 30 4.3 ... ... ... ... 30 Language Requirements Implementation Roadmap for Download Services ... ... 31 4.4 Roadmap for ―non - interoperable‖ Download Services ... 4.4.1 31 ... Roadmap for ―interoperable‖ Download Services ... ... 32 4.4.2 Illustrative Roadmap for all Download Services ... ... 33 4.4.3 5 defined Dataset Download Service ... ... 34 Atom Implementation of Pre - Atom ―Download Service Feed‖ containing an entry for a Pre - defined dataset ... 36 5.1 Download Service Feed: feed ̳title‘ element ... ... 39 5.1.1 Download Service Feed: feed ̳subtitle‘ elemen t ... ... 39 5.1.2 5.1.3 Download Service Feed: feed ̳link‘ element – service metadata ... 40 5.1.4 – self - reference ... ... 40 Download Service Feed: feed ̳link‘ element e Feed: feed ̳link‘ element – 5.1.5 OpenSearch Description Document ... 41 Download Servic – alternative languages Download Service Feed: feed ̳link‘ element ... 41 5.1.6 5.1.7 Download Service Feed: feed ̳link‘ element – alte rnative representation formats ... 41 5.1.8 Download Service Feed: feed ̳id‘ element ... ... 43 5.1.9 Download Service Feed: feed ̳rights‘ element ... ... 43 5.1.10 Download Service Feed : feed ̳updated‘ element ... ... 43 5.1.11 Download Service Feed: feed ̳author‘ element ... ... 43

3 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - - 2013 Page 3 of 89 08 ... ... 44 Download Service Feed: feed ̳entry‘ element 5.1.12 ... ... Download Service Feed: 45 5.1.13 entry INSPIRE identifier elements ... 45 Download Service Feed: entry ̳link‘ to dataset metadata record 5.1.14 Download Service Feed: entry ̳link‘ to dataset feed ... ... 5.1.15 45 5.1.16 Download Service Feed: entry ̳link‘ to WFS implementation (only for ―hybrid ... ... 46 ... ... implementations‖) Download Service Feed: entry, additional elements ... ... 5.1.17 46 eed: entry ̳summary‘ element ... Download Service F 47 5.1.18 ... Download Service Feed: entry ̳georss‘ element ... ... 47 5.1.19 5.1.20 – CRSs ... ... 48 Download Service Feed: entry ̳category‘ element Atom ―Dat - defined dataset ... 48 5.2 aset feed‖ containing download links to a pre Dataset Feed: ̳link‘ element: link to Spatial Object descriptions . 51 5.2.1 ... Dataset Feed: optional ̳link‘ element: link to Dow ... ... 52 5.2.2 nload feed Dataset Feed: Entry ̳link‘ element: link to pre - defined dataset ... ... 52 5.2.3 5.2.4 ... 53 Dataset Feed: guidance for datasets which contain multiple files. .. 5 ... ... Dataset Feed: guidance on media types 55 5.2. Dataset Feed: entry ̳georss‘ element ... 5.2.6 ... 56 ... 5.2.7 Dataset Feed: entry ̳category‘ element ... ... 56 ... 5.3 Language Requirements fo r Atom Implementation ... ... 56 5.4 ... ... ... 58 OpenSearch Document structure. OpenSearch Description: ̳Url‘ element: link to self ... ... 59 5.4.1 OpenSearch Description: Generic se arch template ... ... 59 5.4.2 OpenSearch Description: Describe Spatial Data Set Operation template 5.4.3 ... 61 OpenSearch Description: Get Spatial Data Set Operation template ... 61 5.4.4 OpenSearch Description: Spatial Dataset Identifiers ... ... 62 5.4.5 5.4.6 ... 63 OpenSearch Description: Available Languages ... Web Feature Service and Filter Encoding Implementation of Pre - defined Datas et Download 6 ... ... ... ... ... 64 Service Conformance to ISO 19142 ̳Simple WFS‘ Conformance Class ... ... 64 6.1 Conformance to ISO 19143 ̳Query‘ Conformance Class ... ... 6.2 64 6.3 19142 ̳HTTP GET‘ Conformance Class ... ... 64 Conformance to ISO ... ... ... 6.4 ... 65 Stored Query Support INSPIRE Datasets and WFS Features ... ... ... 66 6.5 6.6 Publishing INSPIRE metadata using ows:ExtendedCapabili ties ... ... 66 6.7 Language Requirements for WFS/FE Implementation of Pre - defined Download. ... 69 6.7.1 GetCapabilities - Operation (language requirements) ... ... 69 6.7.2 Common concep t for other operations (optional) ... ... 73 6.7.3 Language support in OWS ... ... ... 75 7 Web Feature Service and Filter Encoding implementation of Direct Access Download Service. .. 77

4 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - - 2013 Page 4 of 89 08 .1 - based Pre - defined dataset download service Necessary elements from WFS ... 77 7 Conformance to ISO 19142 ̳Basic WFS‘ Conformance Class ... ... 7.2 77 lass ... ... 77 Conformance to ISO 19143 ̳Ad hoc Query‘ Conformance C 7.3 Conformance to ISO 19143 ̳Resource Identification‘ Conformance Class ... 78 7.4 Conformance to ISO 19143 ̳Minimum Standard Filter‘ Conformance Class 7.5 78 ... 7.6 Co nformance to ISO 19143 ̳Minimum Spatial Filter‘ Conformance Class ... 78 Conformance to ISO 19143 ̳Minimum Temporal Filter‘ Conformance Class 78 7.7 ... Conformance to ISO 19143 ̳Minimum XPath‘ Confor ... ... 78 7.8 mance Class Language requirements for Direct Access Download Services ... ... 7.9 79 7.9.1 DescribeFeatureType Operation (language requirements) ... ... 79 7.9.2 GetFeature Operat ion (language requirements) ... ... 79 7.10 WFS metadata for ―hybrid implementations‖ ... ... 79 8 ... ... ... ... 80 Quality of Service ... ... ... ... 80 8.1 General requirements Performance ... ... ... ... 81 8.2 ... 8.2.1 81 Implementation requirements mandated by the Implementing Rule ... ... ... 8.2.2 82 Normalized testing procedure ... 8.3 ... ... Capacity ... 84 8.3.1 Implementation requirements mandated by the Implementing Rule ... 84 8.3.2 ... ... ... 85 Normalized testing procedure ... 8.4 ... ... Availability ... 85 8.4.1 Implementation requirement s mandated by the Implementing Rule ... 85 8.4.2 Normalized testing procedure ... ... ... 85 Annex A: Example OpenSearch script ... ... ... 87 Annex B: UML Atom/OpenSearch Deployment Diagram ... ... ... 89

5 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - - 2013 Page 5 of 89 08 Examples Table of ... 34 Example 1: ... Sample Atom feed, containing two entries: ... 36 Example 2: Sample ―Download Service Feed‖ (Atom) with an entry for a Hydrography dataset Sample feed title ... ... ... Example 3: 39 ... ... ... ... . 40 Example 4: Sample feed subtitle Example service metadata link ... ... ... 40 Example 5: Example refere nce to feed ... ... Example 6: 40 ... Example 7: Alternative links to HTML versions of a document (in both English and German). ... 41 Example feed id element ... ... ... 43 Example 8: ... ... ... eed rights element 43 Example 9: Example f Example updated element ... ... ... 43 Example 10: Example 11: ... ... ... 44 Example feed author element ... Feed‖ ... Example 12: 44 Example entry showing a link to a single ―Dataset Example 13: Namespace declaration for inspire_dls ... ... ... 45 Example Spatial Dataset URI Example 14: ... ... ... 45 Example 15: ... ... 45 Example link to a dataset metadata record Example link to a single ―Dataset Feed‖ ... ... ... 45 Example 16: Example link to a WFS implementation for the Direct Access operations ... 46 Example 17: Example summary el ement ... ... ... 47 Example 18: ... Simple Point ... ... - 47 GeoRSS Example 19: GeoRSS - Simple Polygon ... ... ... 47 Example 20: Example CRS descriptions ... Example 21: ... 48 ... Example 22: Exa mple ―Dataset Feed‖ containing links to a pre - defined dataset ... 48 Example 23: ... 51 Links to the INSPIRE registry (for Watercourse and Standing Water) Example 24: ice feed ... ... 52 Optional upward link to download serv Example 25: Example link to pre - defined dataset ... ... ... 52 Example 26: Use of bbox and time attributes ... ... ... 54 Example 27: Multi - part dataset described by a content el ement ... ... 54 Example 28: Multi - part dataset described by an external document ... ... 55

6 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - - 2013 Page 6 of 89 08 ... ... ... ... 55 GML download Example 29: ... ... ... ... 56 Example 30: Zipped media Using the category element to refer to an EPSG code (registered at OGC) ... 56 Exa mple 31: ... 57 Example 32: Alternative representation is available in German (hreflang=―de‖) English feed with a ... ... 57 Example 33: lternative version in German German feed with alternative version in English ... ... 57 Example 34: Open Search description document ... ... Example 35: 58 ... Example 36: Example ref erence to self ... ... ... 59 Example generic URL search template ... ... ... 60 Example 37: Example Describe Spatial Data Set template ... ... 61 Example 38: Using an OpenSearch templat e for building a Describe Spatial Data Set request ... 61 Example 39: Example 40: Example Get Spatial Data Set template ... ... ... 61 ... ... Example 41: 62 OpenSearch URL template returning an Atom feed. Example 42: ... ... ... 62 Example Get Spatial Data Set template Example 43: Example Language support ... ... ... 63 Example 44: ... 65 Custom stored query requesting a dataset by ID and CRS (informative only) Extended capabilities ... ... ... 68 Example 45: ... ... ... 71 Example 46: Extended Capabilities structure Response to [OGC - GetCapabilities - Request]&LANGUAGE=eng ... 72 Example 47: Example 48: to [OGC - GetCapabilities - Request] or [OGC - GetCapabilities - Response ... Request]&LANGUAGE=fre ... ... 73 ... Example 49: Response to any GetCapabilities - Request (only German supported) ... 73 Exampl e 50: Service response including supported languages ... ... 74 Example 51: - GetCapabilities - Request]&LANGUAGE=eng or [OCG - Response to [OCG - 74 ... ... ... ... GetCapabilities Request] Request]&LANGUAGE=ger - GetCapab ilities - Example 52: ... 75 Response to [OCG Example 53: Performance tests for long - running operations ... ... 82 Example 54: Get Spatial Data Set operation ... ... ... 84 Example 55: Availability t ests for long - running operations ... ... 86

7 INSPIRE Technical Guidance for INSPIRE Download Services 3.1 - - 2013 09 Page 7 08 of 89 Table of Figures Figure 1: Relationship between INSPIRE Implementing Rules and Technical Guidance ... 10 Figure 2: Simple sequence diagram showi ng download of datasets via a pre - defined download service ... ... ... ... ... 22 Figure 3: Simple sequence diagram showing a typical sequence of operations to download spatial data objects from a direct access dataset download service. ... ... 22 Figure 4: Illustration of Implementation Roadmap* ... ... 33 ... ... ... ... 36 Figure 5 Overview of Atom feed structures ... ... Figure 6. Atom feed viewed in Firefox 42 ... Fig ure 7. Atom feed viewed in Internet Explorer ... ... ... 42 Figure 8. Download service integrated as a search engine in Internet Explorer ... .. 60 Figure 9: Detailed Sequence Diagram Download Service ... ... .. 81

8 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - - 2013 Page 8 of 89 08 Acknowledgements Many individuals and organisations have contributed to the development of these Guidelines. The Network Services Drafting Team responsible for the Technical Guidance v2.0 inc luded: Jean - Jacques Serrano, Graham Vowles, O laf Østensen, Didier Richard, Markus Müller, Lars Bernard, , Lassi Le hto, Christian Elfers , Roland - Michae Michel Grothe, Marek Brylski , Dominique l Wagner Flandr . oit, Tapani Sarjakoski The Initial Operating Capability Task Force has assumed responsibility of the Technical Guidance document following v2.0 and an IOC TF Service Team was tasked to update the Technical Guidance Document. The following members of the Initial Operating Capability Task Force or the Initial Operating Capability Task Force Service Tea m have greatly contributed to this version: Anders Friis - Christensen (DK), Bart Cosyn (BE), Andreas von Dömming (DE), Timothy Duffy (UK), Jani Kylmäaho (FI), Gianluca Luraschi (EMSA), Clemens Portele (DE), Didier Richard (FR), Wolfgang Tinkl (AT). at the Joint Research Centre of the European Commission that contributed to this version of The team the guidelines includes: Michele Chinosi, Ioannis Kanellopoulos, Michel Millot , Angelo Quaglia , Mich a el Lutz and Alexander Kotsev . We are grateful to all the IOC T ask Force Members who through their careful reviews and comments helped to correct a number of issues and made a valuable contribution to this edition. version 3.0 of the Special thanks go to Dominic Lowe (UK) for the tremendous job he did in editing guide lines. ld like to thank Debbie Wilson from Snowflake Software for her comments and Finally we wou suggestions . to version 3.0 Contact information Michael Lutz European Commission Joint Research Centre Institute for Environment and Sustainability a Fermi 2749 TP262, Vi I 21027 Ispra (VA) - ITALY E - mail: [email protected] Tel.: +39 0332 - 786759 - http://ec.europa.eu/dgs/jrc/ http://inspire.jrc.ec.europa.eu/

9 INSPIRE Technical Guidance for INSPIRE Download Services 3.1 - 2013 Page 9 - of 89 09 08 Foreword Directive 2007/2/EC Directive 2007/2/EC of the European Parliament and of the Council [ ], adopted on 14 March 2007 aims at establishing an Infrastructure for Spatial Information in the Europ ean Community (INSPIRE) for environmental policies, or policies and activities that have an impact on the environment. INSPIRE will make available relevant, harmonised and quality geographic information to support the formulation, implementation, monitorin g and evaluation of policies and activities, which have a direct or indirect impact on the environment. INSPIRE is based on the infrastructures for spatial information established and operated by the 27 Member States of the European Union. The Directive ad dresses 34 spatial data themes needed for environmental applications, with key components specified through technical implementing rules. This makes INSPIRE a unique example of a legislative ―regional‖ approach. To ensure that the spatial data infrastructu res of the Member States are compatible and usable in a - Community and trans boundary context, the Directive requires that common Implementing Rules (IR) are adopted in the following areas. Metadata; The interoperability and harmonisation of spatial data and services for selected themes (as described in Annexes I, II, III of the Directive); Network Services; Measures on sharing spatial data and services; Co - ordination and monitoring measures. The Implementing Rules are adopted as Commission Decisions or Regulations, and are binding in their entirety. In particular with respect the Network Services, Implementing Rules are required for the following services (Article 11(1) of the Directive): a) “discovery services search for spatial s and spatial da ta services on the basis of the dataset content of corresponding metadata, and display the metadata content; b) dataset s view services as a minimum, display, navigate, zoom in/out, pan, or overlay spatial and display legend information and any relevant content of met adata; c) dataset s, or of parts of such sets, to be download services enabling copies of complete spatial downloaded; d) transformation services enabling spatial dataset s to be transformed with a view to achieving interoperability; spatial data services" e) invoke enabling data services to be invoked.” In addition to the Implementing Rules, non - binding Technical Guidance documents describe detailed implementation aspects and relations with existing standards, technologies, and practices. They may need to be revised during the course of implementing the infrastructure to take into account the evolution of technology, new requirements, and cost benefit considerations. Figure 1 . illustrates the relationship between the INSPIRE Regulations cont aining Implementing Rules and their corresponding Technical Guidance documents.

10 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - 2013 Page 10 08 of 89 - Figure 1 Relationship between INSPIRE Implementing Rules and Technical Guidance : Technical Guidance documents define how Member States might impl ement the Implementing Rules - binding described in a Commission Regulation. Technical Guidance documents may include non technical requirements that must be satisfied if a Member State chooses to conform to the Technical Guidance. Implementing this technica l guidance will maximise the interoperability of INSPIRE services. e concerns the INSPIRE Download This Technical Guidanc The Technical Guidance Services. contains detailed technical documentation highlighting the mandatory and the recommended elements Download Services. The technical provisions and the ted to the implementation of INSPIRE rela underlying concepts are often illustrated by use case diagrams and accompanied by examples. e requirements for Annex I Note that while the guidance in this document meets all the download servic themes it may not be so suitable for some of the data in Annex II and III themes. If later data specifications relating to Annex II or Annex III themes should require additional functionality, like those covered by the OGC Web Co verage Service (WCS) or the OGC Sensor Observation Service (SOS), this Technical Guidance document will be extended accordingly. Likewise, other implementations (e.g. Linked Data) may be considered in future extensions of this Technical Guidance. This doc ument will be publicly available as a ̳non - paper‘, as it does not represent an official position of the Commission, and as such cannot be invoked in the context of legal procedures. Legal Notice Neither the European Commission nor any person acting on beh alf of the Commission is responsible for the use which might be made of this publication.

11 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - 2013 Page 11 of 89 - 08 Revision History Editor Date Description Relea se Sep 2009 2.0 25 Draft Technical Guidance (Published) Network Services Drafting Team Dec 2011 2.1 Aligned structure with View and Download guidance. Dominic Lowe 14 Added Atom guidance and mappings. General editorial changes. 2.2 Dominic Lowe Major restructuring following IOC TF meeting. 9 Jan 2012 Dominic Lowe 18 Jan 2012 2.3 Further Atom guidance and WFS guidanc e. General editorial changes and formatting. 2.4 Dominic Lowe 2 Feb 2012 Editing following telecon and review by IOC ference TF members. Significant edits to Atom section. Restructured language requirements. Added table of WFS to IR mapping. 2 .5 Dominic Lowe 10 Feb 2012 Numerous detail edits in preparation for wider review. Added implementation roadmap diagram and extended capabilities section. 2.6 17 Feb 2012 Dominic Lowe Substantially revised mapping to IR section. Fixed issues with numbering of require ments and recommendations. Dominic Lowe 2.6.5 02 Apr 2012 Interim version for internal review, following 2.6 consultation. Major changes to Atom chapter. 2.7 Dominic Lowe 05 Apr 2012 section , addressed many Added OpenSearch ction on Media outstanding comments, Added se types/compression. 2.8 Dominic Lowe 03 May 2012 Many editorial changes and clarifications, changes to GeoRSS, OpenSearch sections, Diagrams. 3.0rc Dominic Lowe 04 May 2012 Edits in response to JRC Updated milestones. comments. Dominic Lowe 2 3.0rc2 11 Jun 201 Edited in response to IOC TF comments. 12 Jun 2012 Dominic Lowe Minor final corrections. 3.0 16 Jul 2012 3. 0. 1 Dominic Lowe Corrected georss:polygon coordinates in examples Example 2: , Example 12: and Example 20: as follows: 47.202 5.755 55.183 5.755 55.183 15.253 47.202 15.253 47.202 5.755 Section 5.4 , Example 35: (previously not numbered), OpenSearch Description document: Changed from: to:

12 INSPIRE Technical Guidance for INSPIRE Download Services 3.1 - - 2013 Page 12 of 89 09 08 Date Description Editor Relea se 21 2013 3. 0.2 Feb Added Chapter 8 on Quality of Services Ioannis Kanellopoulos 9 Aug 2013 3.1 Angelo Quaglia, 4 and 4.2 to enable the possibility Updated sections Michael Lutz , of a ―hybrid implementation‖ based on Atom for Part Alexander Kotsev A and WFS for Parts B and C. Added pointer to the demo instance of an Atom based Download Service at the beginning of Chapter 5. Changed ―application/vnd.iso.19139+xml ‖ to ―application/xml‖ in text and examples in section 5.1.3. Added note on metadata in Atom and WFS for ―hybrid implementations‖ in section 5.1.3. Added motivation for html alternative representation in section 5.1.7. Removed reference to .ogc.csw.GetRecordByIdResponse_x ―application/vnd ml‖ in TG Requirement 6. Added new sub section 5.1.16. Download Service - Feed: entry ̳link‘ to WFS implementation, valid for hybrid implementations only. Added explanation about how the OpenSearch document is introduced to sa tisfy the Network Service Regulation and about the fact that no requirements are placed on the technology used to implement the search script. Added note about the fact that the sample script uses content negotiation in section 5.4. Extended section 5.4.2 on the generic search template; changed type to ―text/html‖ in TG Requirement 41. - - machine interaction for the Explained machine to Describe Spatial Data Set operation in section 5.4.3. Added default values for CRS and language parameters in section 5.4.5, TG Requirement 43 and Example 40:. Changed language code ̳en - GB‘ to ̳en‘ in Example 43:. Changed ̳application/zip‘ to ̳application/x - filegdb‘ in Example 35:, Example 40: and Annex A. Added ̳Croatian‘ language in Table 1 and Table 2. Added recommendation fo r single Stored Query with predefined identifier in Chapter 6.4 ―Stored Query Support‖. Modified TG Requirement 51 to include

13 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 13 09 08 - Page - of 89 2013 Date Description Editor Relea se ̳DataSetIdCode‘ and ̳DataSetIdNamespace‘ parameters instead of the previously existing ̳DataSetId‘. Added requirement for WFS - base d Predefined data set download services that they only serve one data set per endpoint in Chapter 6.5 ―INSPIRE Datasets and WFS Features‖. Removed dependency of Conformance class 3 on conformance class 2 in section 7 and TG Requirement 61. Moved subsection s 6.2.2 ―DescribeFeatureType Operation (language requirements)‖ and 6.6.3 ―GetFeature Operation (language requirements‖ to Chapter 7.9. Added new sub - section 7.10 for WFS metadata in case of hybrid Atom/WFS implementations.

14 INSPIRE Technical Guidance for INSPIRE Download Services 3.1 - of - 2013 Page 14 09 89 08 1 Introduction Directive 2007/2/EC of the European Parliament and of the Council of 14 March 2007 establishing an Infrastructure for Spatial Information in the European Community (INSPIRE) was published in the official Journal on the 25th April 2007. The INSPIRE Directive entered into force on the 15th May 2007. The purpose of the infrastructure is to enable the formulation, implementation, monitoring activities and evaluation of Community environmental policies at all – European, national and local – levels and to provide public information. INSPIRE builds on the infrastructures for spatial information that have already been created by the Member States. The components of those infrastructures include: metadata, spatial data themes (as described in Annexes I, II, III of the Directive), network services and technologies; agreements on data sharing, access and use; coordination and monitoring mechanisms, processes and procedures. The guiding principles of INSPIRE are: that the infrastructures for spatial information in the Member States should be designed to ensure that spatial data are stored, made available and maintained at the most appropriate level; oss the Community in a that it is possible to combine spatial data from different sources acr consistent way and share them between several users and applications; that it is possible for spatial data collected at one level of public authority to be shared between all the different levels of public authorities; that spatial data are made available under conditions that do not restrict their extensive use; and that it is easy to discover available spatial data, to evaluate their fitness for purpose and to know the conditions applicable to their use. irective is available from available from the European Union Law website The text of the INSPIRE D - LEX) The - lex.europa.eu/LexUriServ/LexUriServ.do?uri=CELEX:32007L0002:EN:NOT . (EU http://eur Directive identifies what needs to be achieved, and Member States have two years from the date of adoption to bring into force national legislation, regulations, and administrative procedures that define how the agreed objectives will be met taking int o account the specific situation of each Member State. To ensure that the spatial data infrastructures of the Member States are compatible and usable in a Community and trans - boundary context, the Directive requires that common Implementing Rules (IR) adopted in a number of specific areas. Implementing Rules are adopted as Commission are Decisions, and are binding in their entirety. According to Article 5(4) of the Directive, the INSPIRE Implementing Rules shall take account of relevant, existing internati onal standards and user requirements. The scope of this document is to detail the INSPIRE technical requirements for Download S ervices from the Implementing Rules, such that these services can be implemented consistently across Europe. These Implementing Rules are, as much as possible, in conformance with European and international standards, current practices in stakeholder communities and relevant European initiatives such as e - Government, and the EU interoperability framework.

15 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - - 2013 Page 15 of 89 08 2 Normative references following referenced documents are indispensable for the application of this document. For dated The references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. INSPIRE, Implementing Directive 2007/2/EC of the European Parliament and of the Council as dataset s and services, INSPIRE D irective regards interoperability of spatial IETF RFC 4287 The Atom Syndication Format, ATOM - , http://www.georss.org/simple GeoRSS GeoRSS Simple The Simple Serialization of GeoRSS http://www.opensearch.org/Specifications/OpenSearch/1.1 OpenSearch Description Document format, Op enSearch Geographic information -- ISO 19142:2010 Web Feature Service , ISO 19142 -- ISO 19143:2010 Geographic information Filter encoding , ISO 19143 INSPIRE Network Services Regulation INS NS, COMMISSION REGULATION (EU) No 976/2009 of , as amended by Regulation (EC) No 1088/2010 as regards download services and 23 November 2010 transformation services , INS MD, COMMISSION REGULATION (EC) No 1205/2008 of 3 INSPIRE Metadata Regulation d of the Council as December 2008 implementing Directive 2007/2/EC of the European Parliament an regards metadata. See also Corrigendum to INSPIRE Metadata Regulation. , Guidelines based on EN ISO 19115 and EN ISO IR MDTG, INSPIRE Metadata Implementing Rules 19119 for Commission Regulation (EC) No 1205/2008 of 3 December 2008 imple menting Directive 2007/2/EC of the European Parliament and of the Council as regards metadata INSPIRE spatial dataset s and services Regulation, INS SDS, COMMISSION REGULATION (EU) No 1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the Eur opean Parliament and of the Council as regards interoperability of spatial dataset s and services W3C Protocol for Web Description Resources (POWDER): Description Resources, http://www.w3.org/TR/powder - dr/ , P OWDER

16 INSPIRE Technical Guidance for INSPIRE Download Services 3.1 - - 2013 09 Page 16 08 of 89 3 Terms and ab breviations 3.1 Terms (1) download services enabling copies of spatial dataset s, or parts of such sets, to be downloaded and, where practicable, accessed directly [INSPIRE Directive] (2) INSPIRE registry the official registry containing definitions for terms and feature concepts in INSPIRE. http://inspire - registry.jrc.ec.europa.eu/ (3) metadata dataset information describing spatial s and spatial data services and making it possible to discover, inventory and use them [INSPIRE Directive] network service (4) s network services should make it possible to discover, transform, view and download spatial data and to invoke spatial data and e - commerce services [INSPIRE Directive] (5) spatial data data with a direct or indirect reference to a specific location or geogra phic area [INSPIRE Directive] (6) dataset spatial identifiable collection of spatial data [INSPIRE Directive] (7) dataset short term sometimes used instead of ̳spatial dataset ‘, same meaning as ̳spatial dataset ‘.

17 INSPIRE Technical Guidance for INSPIRE Download Services 3.1 - - 2013 09 Page 17 08 of 89 3.2 Abbreviations CRS Coordinate Reference System F E Filter Encoding, referring to ISO 19143 GeoRSS GeoRSS - Simple GET HTTP Get Method GML Geography Markup Language HTTP Hypertext Transfer Protocol Infrastructure for Spatial Information in Europe INSPIRE Implementing Rule IR International Organisation for Standardisation ISO JRC Joint Research Centre NS Network Services OGC Open Geospatial Consortium OWS OGC Web Services Common Specification WFS Web Feature Service, referring to ISO 19142

18 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 08 - 2013 Page 18 of 89 - 3.3 Verbal forms for the expression of provisions e ISO rules for drafting, the following verbal forms shall be interpreted in the In accordance with th given way: ―shall ” / ―shall not ” : a requirement, mandatory to comply with the technical guidance ―should ” / ―should not ” : a recommendation, but an alternative approach may be chosen for a specific case if there are reasons to do so ―may / ―need not ” : a permission ” Conformance Classes notation Technical Guidance The Technical Guidance in this document is divided into Conformance Classes, so that it is possible to declare confor mance to specific parts of the Technical Guidance. To conform to a Conformance Class it is necessary to meet all the Requirements (see next section) in that Conformance Class. of Conformance Classes are identified in the document as follows: TG Conformance Class #: [ TITLE] conformance classes are shown using this style Technical Guidance Requirements and Recommendations notation R equirements and the Services within this technical recommendations for INSPIRE Download are highlighted and numbered as shown below: guidance Requirement TG requirements a re shown using this style # Recommendation # recommendations a re shown using this style. TG It is important to note that, implementation requirements and implementation recommendations may refer to either service o Requirements and recommendations belong to the r client implementations. lass in which they are found in this document. conformance c Note : It is worth noting that requirements as specified in the INSPIRE Regulations and Implementing Rules are legally bind ing, and that requirements and recommendations as specified in INSPIRE not legally binding. Therefore, within this technical guidance we hav e used Technical Guidance are requirement‘ and ̳TG the terms ̳TG recommendation‘ to indicate what is technically req uired or recommended to conform to the Technical Guidance. XML Example notation XML Examples are shown using Courier New on a grey background with yellow for emphasis as below: Highlighted Text for emphasis Note : XML Examples are informative and are provided for information only and are expressly not normative.

19 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 89 09 - 2013 Page 19 of 08 - 3.4 References ferences within this document are denoted using ―Section‖ or ―Annex‖. For example, Section 5.3.1 Re . or Annex A References to other documents refer to the list of normative references in Section 3 and use the abbreviated title as indicated in text. For example, [ INS NS ] uses the abbreviated title for the Bold document as shown below: INSPIRE Network Services Regul INS NS, COMMISSION REGULATION (EU) No 1088/2010 ation, of 23 November 2010 amending Regulation (EC) No 976/2009 as regards download services and transformation services R eferences within other documents are show as above using the abbreviated title, toget her with the appropriate section within the document. For example, [ INS NS , Section 2 .2 .3 ], refers to Section 2.2.3 within the document as listed above. of this document 3.5 Future updates are not covered or only pa rtially covered in this version There are some issues that are foreseen, but of the Technical Guidance. These are: Pre - defined download of datasets contained in multiple physical files. o Although some provision for multiple links is given in the current Atom guidance, it is foreseen that this solutio very large numbers of files and also n may not be scalable for that there is no way to provide metadata for individual files (e.g. geographic, temporal coverage). Other solutions will be explored. More WFS examples for Stored Queries and Direct Download. G uidance for Spatial Object Types that may be more suited to delivery via Web Coverage Services or Sensor Observation Services.

20 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - - 2013 Page 20 of 89 08 INSPIRE Download Services 4 technical service interfaces for provides Technical Guidance for the implementation of This document I NSPIRE Do guidance is based on the abstract model established in the wnload Services. This [ INS NS ]. INSPIRE Network Services Regulation describes following the four download operations [ INS NS , Annex The Network Services Regulation must b that e implemented by Download Services : IV, Part A] Get Download Service Metadata Get Spatial Dataset Describe Spatial Dataset Link Download Service R egulation also state s that where practicable , the following two operations [ INS The Network Services be implemented , Annex IV, Part B] by Download Services : shall NS Get Spatial Object Describe Spatial Object Type if the Get Spatial Object and Describe Spatial Object Type Furthermore, operations are implemented then search capabilities [ INS NS , Annex IV, Part C] sh all also be implemented. These particular include the ability to search by: capabilities URI of Spatial Dataset Key attributes of spatial objects, including URI and date/time of update Bounding Box Spatial data theme Combinations of the above ; In practice therefore , this means there are two types o f Download S ervices that may be implemented those that s atisfy the minimum functional requirements [ INS NS , Annex IV, Part A] from the Regulation functional requirements [ NS NS , Annex IV, Pa rts A, B & C] . As stated in and those that satisfy the full I egulation , t he later should be implemented where practicable . the R of this docume nt these two types of Download Service are referred to as follows: For the remainder Pre - defined dataset download service ( s ) ‖ ; ― A pre - taset download service provides for the simple download of pre - defined da dataset s (or pre defined defined parts of a dataset ) with no ability to query dataset s or - select user - defined subsets of dataset s. A pre - defined dataset or a pre - defined part of a dataset could be (for example) a file stored in a dataset repository, which can be downloaded as a complete unity with no possibility to change content, whether encoding, the CRS of the coordinates, etc. ― Direct access download ( s ) ‖ ; service A direct access download service extends the functionality of a pre - defined dataset download service ability to query and download subsets of dataset s. to include the The direct access download service allows more control over the download than the simple download of a pre - defined dataset or pre - defined part of a dataset . It can therefore be considered to be more „advanced‟ than pre - defined dataset download. In this case, the spatial information is typically stored in a repository (e.g. a database) and only accessible through a mid dleware data management system (although the precise implementation may vary). The term direct access is used to mean the capability of a client application or client service to interact directly with the contents of

21 INSPIRE Technical Guidance for INSPIRE Download Services 3.1 89 - 2013 Page 21 of - 09 08 the repository, e.g. by retrieving part s of the repository based upon a query. The query can be based upon spatial or temporal criteria, or by specific properties of the instances of the spatial object types contained in the repository. defined part of a - defined datas et or a pre - pre dataset is In addition to the above definitions, a characterised by two conditions: It has a metadata record and can be discovered using an INSPIRE conformant discovery service. The metadata contains a link (URL uniform resource locator) whereby the dataset or par t of – request. The URL - protocol GET - dataset can be immediately downloaded by a simple HTTP can optionally link to a resource where rights management services can be invoked prior to the simple download by use of HTTP - protocol. to Furthermore, note that the phr (s) of a dataset‘ refers only ase ̳part logica l parts of a dataset. It does , for example where a large dataset has been split into multiple not refer to physical parts of a dataset files for storage or access reasons. could be a road network example a logical ̳ part of a dataset ‘ for a single administrative region. As an , record as described above and would effectively act This ̳part dataset‘ would have its own metadata as a normal dataset in the INSPIRE infrastructure. This is in contrast to say, if a roa d network was split latter into 100 tiles for storage efficiency. In the case, the physical parts of the logical dataset would not be exposed with metadata records. . Of course there may be a correspondence between the logical and physical parts of a dataset - defined dataset The precise definition of what constitutes a particular pre - defined part of or pre dataset s is a matter for individual data providers and will vary according to the context. However as indicated above an example of usage could be where th e pre - defined dataset is a dataset conforming to one of the INSPIRE themes covering the whole Member State, while a pre - defined part of the dataset could be a subset of this, covering for instance an administrative subdivision of the Member State. F or readability purposes, the short phrase NOTE: - defined dataset ” is often used in this document. “pre Whenever this phrase is encountered it should be inte rpreted as meaning the longer phrase “pre - defined or a pre - defined part of a dataset ”. dataset Where refere nce is made to physical parts of a dataset this is made explicit. Figure 2 shows a typical sequence of operations used when downloading data from a pre - defined dataset download service.

22 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 22 09 08 - 2013 Page - of 89 showing Figure 2 : Simple sequence diagram download of dataset s via a pre - defined download service Figure 3 shows a typical sequence of operations used when downloading data from a direct access dataset download service. Figure 3 : Simple sequence diagram showing a typ ical sequence of operations to download spatial data objects from a direct access dataset download service .

23 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - - 2013 Page 23 of 89 08 In both cases above, the end point for the Get Download Service Metadata Request (i.e. the Atom Download Service ISO Metadata retrieved from the feed or the WFS GetCapabilities) is taken from the Discovery Service . More specifically the Resource Locator Metadata element shall include the link to the Get Download Service Metadata Request. document provide detailed Techni cal Guidance for implementing T he following sections of this ards: ervices using existing stand Download S contains T echnical Guidance for implementing p re - defined dataset download Chapter 5 [ ATOM ] s ervices using the Atom syndication format Chapter 6 for implem enting p re - defined dataset download contains Technical Guidance e ISO 19142 Web Feature Service [ ISO 19142] and ISO 19143 Filter services using th ISO 19143] Encoding Specification [ Chapter 7 for implementing direct access download services contains Technical Guidance 142 Web Feature Service ISO 19142] and ISO 19143 Filter Encoding [ ISO e ISO 19 using th [ 19143] o ose Anybody implementing Download Services following this Technical Guidance should therefore ch for to do one provided : (or more, but at least one) of the following each Download Service Satisfy the minimum functional requirements of the Regulation [ , Annex IV, Part A] by INS NS following the T G uidance in Chapter 5 ( using Atom ). echnical Satisfy the minimum requirements of the Regulation [ INS NS , Annex IV, Part A] by functional following the T in Chapter 6 ( using WFS ). echnical Guidance by Satisfy the full functional requirements of the Regulation [ INS NS , Annex IV, Parts A, B & C] following the T echnical Guidance 6 and 7 ( using WFS & Filter Encoding ). in Chapters Satisfy the full functional requirements of the Regulation [ INS NS , Annex IV, Parts A, B & C] by Filter 7 5 Atom and WFS & and following the Technical Guidance in Chapters (using This case will be referred to as a ―hybrid implementation‖ in this Technical Encoding). Guidance. 1 illustrates the relationship between the par ts of the Regulation [ INS NS , Annex IV] and the Table . implementation choices presented in this document s Part A (mandatory) Parts B & C (where practicable) Implementation choice TOM A 5 Not possible with Atom Chapter WFS Chapter 6 7 Chapter Table 1 : Possible implementation choices for Download Services , R egulation contains requiremen ts for Quality of S ervice In addition INS NS , the Network Services [ Annex I] for this is given in Chapter 8 . Technical Guidance Technical Guidance must be and this followed in addition to any Technical Guidance given in Chapters 5 - 7 . 4.1 Implementing Rules How the Technical Guidance maps to the T of this Technical Guidance i s to provide practical guidance for implementation that is he purpose guided by, and satisfies, the requirements of the underlying legislation. The tables in the following three demonstrate how the A tom and WFS implementations described in this document sections satisfy the legal requirements of the Network Services Regulation [ INS NS ]. The underlying legislation is rarely referred to in the rest of this document, so these tables should be referred back to if necessary.

24 INSPIRE Technical Guidance for INSPIRE Download Services 3.1 of - 2013 Page 24 - 89 09 08 Mapping the Atom - based Technical Guidance to the Implementing Rules 4.1.1 set of table s how the guidance for Atom implementations given in Chapter 5 The following s show Each opera tion is in a separate table. satisfies the Network Services Regulation. 1 M/O/C Get Download Service Metadata (Annex IV, Part A) Description in INS NS s, and describes the service Dataset M Provides all necessary information about the service, the available Spatial capabilities. Request parameters Natural language to be used for the content of the response o Response parameters Download Service Metadata o Operations Metadata o o Languages Spatial Data Sets Metadata o Recommended Atom - based implementation - defined download only) (satisfies pre Metadata records for Download Services shall be available in a Discovery Service. The Resource Locator metadata element for the d Get Downloa f Download Service shall contain a link to the Atom eed. Service Metadata Request an HTTP GET The Get Download Service Metadata request is request to the Download Service to retrieve the Atom feed. The response from the Download Service will be an Atom feed Get Download INSPIRE which includes the download service metadata, Metadata Service operations metadata, response and supported languages, spatial Response 5.1 . data sets metadata and their corresponding CRS. See Section 2 – Atom Implementation : Get Download Service Metadata Table M/O/C Get Spatial Data Set n INS NS (Annex IV, Part A) Description i The Get Spatial Data Set operation allows the retrieval of a Spatial Dataset . M Request parameters o Language Spatial Data Set Identifier o Coordinate Reference System o Response parameters Requested Spatial Data Set in the requested language and CRS o Recommended Atom - based implementation - defined download only) pre (satisfies Get Spatial Data Set Pre - defined spatial datasets can be retrieved using the URL 1 Mandatory/Optional/Conditional to conform with Network Services Regulation [ INS NS ]

25 INSPIRE Technical Guidance for INSPIRE Download Services 3.1 of - 2013 Page 25 - 89 09 08 Request template identified by rel=‖results‖ in the OpenSearch description ocument. The request contains the CRS, Spatial et d Data S dentifier and language as parameters. I Pre - defined spatial datasets can also be retrieved by following link scribed in Section 5.2.2 elements in Atom feed entries as de n HTTP GET request is made to the link target. A Data Set Get Spatial The response will be a pre - defined spatial dataset in the requested Response language and CRS . 3 : Get Spatial Data Set – Atom Implementation Table M/O/C Describe Spat Dataset ial (Annex IV, Part A) Description in INS NS This operation returns the description of all the types of Spatial Objects contained in the Spatial Dataset . M Request parameters o Language o Spatial Data Set Identifier Response parameters on of the Spatial Objects in the requested Spatial Data Set and requested language o Descripti based implementation Recommended Atom - defined download only) - (satisfies pre URL The Describe Spatial Data Set Request is issued using the template identified by rel=‖describedby‖ in the OpenSearch Describe Spatial Request et S Data description document. The request contains the Spatial Data Set dentifier and L anguage as parameters. I containing another Atom Feed (a ―Dataset Feed‖ ) The response is riptions of the Spatial Object T Describe Spatial ypes in the element. Reference to the INSPIRE Registry as described in Section 5.2.1 should be made where possible. Table 4 : Describe Spatial Data Set – Atom Implementation M/O/C Link Download Service Description in INS NS (Annex IV, Part A) Allows the declaration, by a Public Authority or a Third Party, of the availability of a Download Service for M ataset s or, where practicable, Spatial Objects, through the Member State‘s Download downloading Spatial D Service while maintaining the downloading capability at the Public Authority or the Third Party location. Recommended Atom - based implementation s atisfies pre - defined download only) ( To be implemented by uploading the appropriate metadata to the INSPIRE network as referred to in Article 11 using PublishMetadata function of an INSPIRE compliant the discovery service Table 5 : Link Download Service – Atom Implementation

26 INSPIRE Technical Guidance for INSPIRE Download Services 3.1 of 08 2013 - 26 - 89 09 Page Mapping the WFS - based Technical Guidance to the Implementing Rules 4.1.2 given in Chapters 6 and set of s shows how the guidance for WFS implementations table The following . Again, each operation is in a separate table. 7 satisfies the Network Services Regulation M/O/C Get Download Service Metadata Description in INS NS (Annex IV, Part A) Dataset s, and describes the service M Provides all necessary information about the service, the available Spatial capabilities. Request parameters o Natur al language to be used for the content of the response Response parameters o Download Service Metadata o Operations Metadata Languages o o Spatial Data Sets Metadata Recommended WFS - based implementation Metadata records f or Download Services shall be available in a Discovery Service. The Resource Locator metadata element for Get Download the Download Service shall contain a link to the GetCapabilities of Service Metadata the WFS .. Request The Get Download Service Metadata request is a GetCapabilities request t o the WFS indicated in the metadata record. The Get Download Service Metadata Response will be a WFS Get Download capabilities document, which includes the download service Service Metadata INSPIRE metadata, operations metadata, response and Response supp orted languages, spatial data sets metadata and their corresponding CRS. WFS/FE ISO 19142: Simple WFS, HTTP Get Conformance Classes Table 6 : Get Download Service Metadata - WFS Implementation M/O/C S et Get Spatial Data Descri ption in INS NS (Annex IV, Part A) The Get Spatial Data Set operation allows the retrieval of a Spatial Dataset. M Request parameters o Language o Spatial Data Set Identifier Coordinate Reference System o Response parameters o Requested Spatial Data Set in the req uested language and CRS

27 INSPIRE Technical Guidance for INSPIRE Download Services 3.1 of - 2013 Page 27 - 89 09 08 - based implementation Recommended WFS - defined spatial datasets in different CRS/DataSetIdCode/ Pre combinations can be retrieved DataSetIdNamespace/language Get Spatial Data Set using Stored Queries as described in Secti on 6.4 Request A GetFeature request shall be made to a WFS that uses a StoredQuery for the pre - defined dataset. Get Spatial Data Set - The WFS shall return a set of features corresponding to the pre Response ested language and CRS. defined dataset in the requ WFS/FE ISO 19142: Simple WFS, HTTP Get Conformance ISO 19143: Query Classes Table 7 : Get Spatial Data S et - WFS Implementation M/O/C Dataset Describe Spatial Description in INS NS (Annex IV, Part A) s operation returns the description of all the types of Spatial Objects contained in the Spatial Dataset. M Thi Request parameters o Language Spatial Data Set Identifier o Response parameters requested language. o Description of the Spatial Objects in the requested Spatial Data Set and - based implementation Recommended WFS The spatial object types are described in the GetCapabilities Describe Spatial response of the WFS. Data Set Request A GetCapabilities request is made to a WFS. The WFS shall return a valid Capabilities document in the Describe Spatial requested language, which identifies the Spatial Object types Data Set Respon se available. WFS/FE Conformance ISO 19142: Simple WFS, HTTP Get Classes Table 8 : Describe Spatial Data Set - WFS Implementation M/O/C Link Download Service Description in INS NS (Annex IV, Part A) Allows the declaration, by a Public Authority or a Third Party, of the availability of a Download Service for M tial Objects, through the Member State‘s Download s or, where practicable, Spa Dataset downloading Spatial Service while maintaining the downloading capability at the Public Authority or the Third Party location. Recommended WFS - based implementation To be implemented by uploading the Download Service INSPIR E metadata to the INSPIRE network as referred to in Article 11 using the PublishMetadata function of an INSPIRE compliant discovery service. The Resource Locator metadata element of the Download Service metadata record shall contain a link to the Atom Feed and/or the WFS GetCapabilities document. WFS/FE Conformance Classes None Table 9 : Link Download Service - WFS Implementation

28 INSPIRE Technical Guidance for INSPIRE Download Services 3.1 08 2013 Page 28 - 89 - 09 of M/O/C Get Spatial Object Description in INS NS (Annex IV, Part B) O This operation allows the retrieval of Spatial Objects based upon a query. (Direct Request parameters access download o Language only) Spatial Data Set Identifier o o Coordinate Reference System o Query Response parameters o Spatial Objects Set Spatial Objects Set Metadata o Recommended WFS - based implementation The WFS provides support for ad - hoc queries a s defined in TG Requirement 63 . Get Spatial Object Request A GetFeature request with required query arguments is made to the WFS . Get Spatial Object turns a set of features that meet the requirements of The WFS re Response the query expression. WFS/FE ISO 19142: Simple WFS, HTTP Get Conformance ISO 19143: Query , Ad hoc Query Classes 10 Table - WFS Implementation : Get Spatial Object M/O/C Describe Spat ial Object Type (Annex IV, Part B) Description in INS NS This operation returns the description of the types [sic] . O specified Spatial Objects (Direct Request parameters access Language o download only) o Spatial Object Type Response parameters in conformity with regulation (EU) No.1089/2010 o Description of the Spatial Object Type Recommended WFS - based implementation Request A De scribeFeatureType request is made to the WFS. The WFS responds with the XML schema for the requested Response Spatial Obje ct types WFS/FE Conformance ISO 19142: Simple WFS, HTTP Get Classes Table 11 : Describe Spatial Object Type - WFS Implementation

29 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 2013 Page 29 of 89 - - 08 M/O/C Search Criteria for the Get Spatial Object Operation (Annex IV, Part C) O Description in INS NS For the purposes of the Get Spatial Object Operation of the Download Service, (Direct access the following search criteria shall be implemented: download only) — Unique Resource Identifier * of Spatial Dataset , all relevant key attributes and the relationship between Spatial Objects a — s set out in Regulation (EU) No 1089/2010; in particular the Unique Identifier of Spatial Object and the temporal dimension characteristics, including the date of update, — bounding box, expressed in any of the Coordinate Reference Systems listed in Regula tion (EU) No 1089/2010, — Spatial Data Theme. To allow for discovering spatial objects through a combination of search criteria, logical and comparison operators shall be supported. in this Technical Guidance as being the The phrase 'Unique Identifier of Spatial Object' should be interpreted * [INS SDS] 'External unique object identifier' as set out in section 2.1 of Annex I of (EU) No 1089/2010 . - based implementation Recommended WFS e Filter Various ad hoc query c apabilitie s are provided by th Encoding Specification ( TG Requirement 63 to TG Requirement Request . 68 ) A GetFeature request may be made with Query arguments. The WFS returns a set of features that meet th e requirements of Response the query expression. , Basic WFS ISO 19142: Simple WFS, HTTP Get WFS/FE ISO 19143: Query, Ad hoc Query, Resource Identification, Conformance Minimum Standard Filter, Minimum Spatial Filter, Minimum Classes Temporal Filter, Minimum XPath 12 : Search Capabilities - WFS Implementation Table 4.1.3 Mapping of Spatial Data Set Identifier parameter i fier parameter is defined in the Network Service regulation [ INS NS ] as The Spatial Data Set Ident r parameter shall contain the Unique Resource Identifier of the Data “The Spatial Data Set Identifie Set” The following table demonstrates how the Spatial Data Set Identifier is mapped between the Atom and WFS based Technical Guidance and the corresponding ISO metadata of the spatial dat a set. The Spatial Data Set Identifier parameter maps to either the RS_Identifier or the MD_Identifier depending on what type of Spatial Data Set Identifier is used in the corresponding ISO metadata. RS_Identifier MD_Identifier INSPIRE Download Service gmd MD_Identifier inspire_dls:SpatialDataSetIdentifier/inspire_common gmd: :RS_Identifier /code :Code /code WFS inspire_dls:SpatialDataSetIdentifier/inspire_common gmd:RS_Identifier :Namespace /codespace gmd:MD_Identifier gmd:RS_Identifier spatial_dataset_identifier_code /code /code ATOM gmd:RS_Identifier spatial_dataset_identifier_namespace /codespace Table 13 : Mapping the Spatial Data Set Identifier parameter

30 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - - 2013 Page 30 of 89 08 Technical 4.2 Conformance Classes for Download Services Guidance declare a level of conformance with this Technical Guidance it is necessary to meet the In order to requirements of any conformance class to which conformance is declared. T es are defined in this document. he following conformance class Chapter M/O/C Description Conformance Class 5 defined Implementation of pre 1: P re - defined download - - C, shall be M if ― WFS pre service using Atom ‖ is not conformed to Atom defined 6 P defined ― - Implementation of pre - defined download re - C, s hall be M if 2: Atom pre ‖ service using WFS is not conformed to WFS defined irect WFS 7 3: D O Implementation of direct access download service using WFS 8 M Quality of Service criteria and 4: Quality of Service requirements 14 : Conformance Classes for Download Service Technical Guidance Table ISO 19139 metadata record. Since the Conformance may be declared in the Download Service metadata record requires conformance to a specification rather than a part of a specification , it is technicalGuidance#levelN is used, where technicalGuidance refers to this suggested that the form document and N refers to the conformance class (e.g. technicalGuidance#level2 ). lso the conformance with several conformance classes can be specified. For example, for A a ―hybrid‖ implementation based on Atom for Part A and WFS for Parts B and C , which meets the quality of requirements could declare service with technicalGu idance#level1 , conformance technicalGuidance#level3 and technicalGuidance#level4. I f a WFS service does not conform to P art A , it cannot on its own be considered of [ INS NS , Annex IV ] compliant with combination of an Atom o r WFS service . Only the the requirements of the Regulation conformant to Parts B and C can be considered compliant . conformant with part A with a WFS Language Requirements 4.3 The Network Services Regulation requires that multilingual aspects for network services are supported INS NS ]. As there is no s tandard way to deal with multilingualism within the current ISO or OGC [ specifications, the following basic principles shall be used for INSPIRE Network Services (including Download Services): A network service [Download Service] metadata response shall con tain a list of the natural languages supported by the service. This list shall contain one or more languages that are supported . A client may specify a specific language in a request. If the requested language is contained in the list of supported language s, the natural language fields of the service response shall be in the requested language. I f the requested language is not supported by the service, then this parameter shall be ignored. For each relevant Conformance Class in this document these statement s are defined as requirements and additional implementation guidance is given.

31 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - - 2013 Page 31 of 89 08 Implementation Roadmap for Download Services 4.4 is entirely informative and is here simply to assist with practical implementation . It s Note: This se ction has no legal basis and is not any way intended to supplement, modify or replace any legally binding statements made elsewhere. all INSPIRE Services are outlined in the The milestones (including dates) for implementation of Implementation Roadmap which can be found at: INSPIRE http://inspire.jrc.ec.europa.eu/index.cfm/pageid/44 In order to provide clear Technical Guidance for implementation it is useful to e xpand upon the practical implications meaning roadmap milestones that relate to Download Services . and of the the INSPIRE Implementation Roadmap does not make any distinction between pre - Note that defined dataset download services and direct access download services as described in this document. The and milestones for both are the same, the only discriminator being that direct access timescales download services should be implemented where practicable . Roadmap, datasets available via Download Implementation made In the initial stages of the INSPIRE Services are not required to be compliant with the thematic Data Specifications and may be provided is‘ via Download Services in existing formats ̳as - . So for convenience we shall refer to these here as non - int eroperable ‖ Download Services. ― IRE Implementation In later stages of the INSP Roadmap datasets made available via Download Services expected to be compliant with the thematic Data Specifications, i.e. the data delivered via are e requirements of the thematic Data S , again for these services must conform to th pecifications. So interoperable ‖ Download Services. convenience only, we shall refer to these here as ― ince S the timescales for Annex I, II and III themes differ there is some overlap between the implementation timescales of non - interoperable and interoperable Download Services . Sections 4.4.1 to 4.4.3 provide additional guidance milestones, to hel p with the interpretation of tho se which are relevant to the provision of Download Services. Roadmap for - i nteroperable ” on Download Services “n 4.4.1 milestones T Table 15 (below) can be interpreted to mean that datasets should be made he in do not have to be formatted according available for download via Download Services but the datasets INSPIRE Data Specifications * . to the This interpretation was clarified during the workshop on legal issues held on the 17th of June 2010 in * Brussels with Q&A available at: http://inspire.jrc.ec.europa.eu/documents/INSPIRE_/INSPIRE_legal_issues.PDF (page 18 , final and question part (c) page 28) question the latest dates of these milestones please refer to the INSPIRE Implementation Roadmap. For Milestone Article* Techni cal Guidance datasets, Download Services Member States shall Annex I and II For provide the Download shall be provided, although these services need not MS1 16 Services with initial comply with the Network Services fully delivered operating capability implementi ng rules at this point. The data by these services do not need to comply with the thematic Data Specifications. datasets, fully compliant (with IR and II Download services I Annex For operational NS) Download Services shall be provided. The MS2 16 data delivered by these services do not need to comply with the thematic Data Specifications.

32 INSPIRE Technical Guidance for INSPIRE Download Services 3.1 89 - Page 32 of 2013 08 09 - Article* Techni cal Guidance Milestone Metadata available for For Annex III datasets, fully compliant (with IR NS) dataset s and data vices shall be provided. The Download Ser spatial MS3 6(b) services corresponding to delivered by these services do not need to comply Annex III with the thematic Data Specifications. 15 Table - interoperable" Download Services : Milestones for "non *From the INSPIRE Directive 4.4.2 Roadmap for “i nte roperable ” Download Services T he m in Table 16 (below) can be interpreted to mean that datasets should be made ilestones compliant with the requirements of the available for download via Download Services in a way that is ata Spec ifica t D ons as well as the Network Services requirements . i Milestone Article* Technical Guidance Implementation of Commission Newly collected or extensively Regulation (EU) No 102/2011 of 4 restructured Annex I datasets shall MS4 7§3, 9(a) February 2011 amending Regulation be made available via Download (EU) No 1089/2010 implementing Services in a way that is compliant European Directive 2007/2/EC of the with both Data Specifications and Parliament and of the Council as Network Services requirements. regards interoperability of spatial s and services for newly dataset collected and extensively restructured dataset s available Annex I spatial Newly collected and extensively ected or extensively Newly coll restructured Annex II and III spatial restructured Annex II and III MS5 7§3, 9(b) s available dataset datasets shall be made available via Download Services in a way that is compliant with both Data Specifications and Network Services requirements. Implementation of Commission All Ann ex I datasets still in use shall /2010 of 23 Regulation (EU) No 1089 be made available via Download MS6 7§3, 9(a) November 2010 implementing Services in a way that is compliant Directive 2007/2/EC of the European with both Data Specifications and Parliament and of the Council as Network Services requirements. regards interoperability of spatial dataset s and services for other Annex dataset I spatial s still in use at the date of adoption s Other Annex II and III spatial dataset All Annex II and III datasets still in available in accordance with IRs for use shall be made available via MS7 7§3, 9(b) I and III Annex I Download Services in a way that is compliant with both Data Specifications and Network Services requirements. Table 16 : Milestones for "in teroperable" Download Services *From the INSPIRE Directive

33 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 89 09 08 - 2013 Page of - 33 4.4.3 Illustrative Roadmap for all Download Services The roadmap described above in sections 4.4.1 and 4.4.2 is further illustrated in Figure 4 : Figure 4 : Illustration of Implementation Roadmap * *Dates in this figure are accurate at the time of publication. For definitive dates refer to the roadmap published on the INSPIRE website: ( http://inspire.jrc.ec.europa.eu/index.cfm/pageid/44 )

34 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - - 2013 Page 34 of 89 08 re - defined Dataset D ownload 5 Atom Implementation of P S ervice defined Atom: - - Defined Dataset Download Ser vice TG Conformance Class 1: Pre Implement Pre (―Part A‖) using Atom This conformance class is inclusive of : TG Requirement 1 to TG Requirement 45 to TG Recommendation 12 TG Recommendation 1 An operational implementation of an INSPIRE Atom based Download Service implementation is available on the INSPIRE Geoportal: http://inspire geoportal.ec.europa.eu/demos/ccm/ Demo - feed Top http://inspire - geoportal.ec.europa.eu/demos/ccm/democcmdownloadservice.atom.en.xml http://inspire - geoportal.ec.europa.eu/demos/ccm/codeview.html Code inspector This web page displays the source code of the Atom feeds and of the OpenSearch description document of the demo. When clicking on specific rows of the code or descrip tion, the text of the relevant requirement is displayed. his Technical Guid ance recommends the Atom syndication format [ ATOM ] as one T way to implement pre - defined dataset download services with a minimal implementation cost and complexity. Section 4.1.1 and the contains a descriptive mapping between the Network Services Regulation [ INS NS ] guidance in this chapter. syndication format provides a simple, widely understood mechanism for publishing The Atom b in the form of feeds in a way that is compatible with existing web architecture information on the we tools. and many In addition Atom is supplemented in this guidance by OpenSearch which provides a - type interface to the static atom documents. service ed in the Atom standard [ ATOM ], At om is an XML - based document format that describes As describ . These feeds are then composed of a number of items, lists of related information known as "feeds" known as "entries", each with an extensible set of elements that contain information ab out the entry . Entries may also contain additional feeds. For example, each entry has a title. S ample At om feed, containing two entries: Example 1: utf - itle> Simple Atom feed example</t <link href="http://myexample.com/"/> - 12 - 14T13:16:32 Z</updated> <updated>2011 <author> <name>A. N. Other</name> </author> <id>urn:uuid:8fa70ca0 - 2659 - 11e1 - bfc2 - 0800200c9a66</id> <entry> <title>My first Atom entry

35 INSPIRE Technical Guidance for INSPIRE Download Services 3.1 - 2013 Page 35 of 89 - 09 08 urn:uuid:c53a6970 - 2659 - 11e1 - bfc2 - 0800200c9a66 - 12 - 14T13:15:02Z 2011

This is an entry in a feed My second Atom entry</t itle> <link href="http://myexample.com/atom456xyz"/> <id>urn:uuid: f80b23d0 - 2659 - 11e1 - bfc2 - 0800200c9a66 </id> - 12 - 14T13:16:32 Z</updated> <updated>2011 <summary>This is another entry in a feed</summary> </entry> </feed> This Technical G uidance recommends using Atom feeds to make available pre - defined dataset s in a consistent manner. The in this chapter can be summarised at a high - level as follows: guidance 2 A single eed is published as a top - level ― D ownload Service F eed ‖ . Atom f provides operations This feed contains a link to an OpenSearch description document which metadata for the Download Service . The OpenSearch description document provides the download service. information about the operations implemented by per contain one or more Atom e ntries: This feed s pre - defined data set. one Each of these Atom e ntries shall contain a link to a nother Atom Feed ( a ―Dataset F eed‖) that describes the pre - defined data set. particular ―Dataset F eeds‖ shall contain Atom Entries with lin ks to download the pre - Each of these defined dataset in different formats (e.g. in GML, Shape F ile , etc . ) and in different Coordinate Reference Systems. One link shall be provided for each format/CRS combination. Feeds may be provided in multiple languages (as described in Section 5.3 ) Figure 5 This pattern is illustrated further in . TG Requirement 1 Pre - defined Dataset Download Service implementations shall publish separate datasets as individual entries within an Atom feed. All At om feeds (and entries in feeds) shall conform to all the requirements in TG Requirement 2 the Atom specification, RFC 4287. In addition the Atom feeds are supplemented with GeoRSS information to enable integration in tools that support this format (e.g. Google Earth). TG Requirement 3 All GeoRSS information in Atom feeds shall conform to the GeoRSS - Simple specification. 2 the terms ―Download Service Feed(s)‖ and ―Dataset Feed(s)‖ are used in this chapter to differentiate between the two types of feed. However the terms have no wider meaning in INSPIRE (legally or otherwise).</p> <p><span class="badge badge-info text-white mr-2">36</span> INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - - 2013 Page 36 of 89 08 In addition the Atom feeds are supplemented with OpenSearch information to as a way to specify operations for the Download Service. information in Atom feeds OpenSearch TG Requirement 4 shall conform to the OpenSearch All specification. It is also possible to enrich the Atom feeds with XML content from other schemes although discussion of this is beyond the scope of the Technical Guidance. Figure Overview of Atom feed structures 5 Atom “Download Service F eed ” 5.1 containing an entry for a Pre - defined d ataset tom entry which points to the The following Download Service F eed example contains a single A . Dataset F defined dataset, in this case a Hydrography dat aset - The Dataset F eed is a pre eed for 5.2 . This example is conformant to the Pre - defined Atom conformance class and described in Section can be used as a template for implementation. Atom Sample “Download Service Feed ” ( ) Example 2: with an entry for a Hydrography dataset <! Example "Download Service Feed" -- > -- <feed xmlns="http://www.w3.org/2005/Atom" xmlns:georss="http://www.georss.org/georss" xmlns:inspire_dls="http://inspire.ec.europa.eu/schemas/inspire_dls/1.0" xml:lang="en"> <! -- feed ti tle -- > <title>XYZ Example INSPIRE Download Service

37 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - - 2013 Page 37 of 89 08 -- INSPIRE Download Service of organisation XYZ providing Hydrography data -- link to download service ISO 19139 metadata -- > rel="describedby" type= "application/xml" -- -- self - referencing link to this feed -- -- to this feed in another language link > http://xyz.org/download /en.xml -- s, access restrictions -- > right Copyright (c) 2012, XYZ; all rights reserved -- date/time this feed was last updated -- > 2012 - 03 - 31T13:45:03Z hn Doe Jo [email protected] Water network ABC Dataset Feed</ti tle> <! -- Spatial Dataset Unique Resour c e Identifier for this dataset > -- <inspire_dls: spatial_dataset_identifier_code >wn_id1</inspire_dls: spatial_ dataset_identifier_code > <inspire_dls: spatial_dataset_identifier_namespa ce >http://xyz.org/</inspire_ dls: > spatial_dataset_identifier_namespace <! -- link to dataset metadata record -- > <link href="http://xyz.org/metadata/abcISO19139.xml" " type= "application/xml" /> rel="describedby <! -- link to "Dataset Feed" f or pre - defined dataset -- ></p> <p><span class="badge badge-info text-white mr-2">38</span> INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - - 2013 Page 38 of 89 08 <link rel=" alternate " href="http://xyz.org/data/waternetwork_feed.xml" type="application/atom+xml" defined waternetwork hreflang="en" title="Feed containing the pre - > dataset (in one or more downloadable formats)"/ -- link to related WFS implementing Direct Access operations -- > <! <link rel=" " related http://xyz.org/wfs?request=GetCapabilities&service=WFS&versio href=" n=2.0.0 title=" Service implementing Direct Access " type="application/xml" "/> erations op <! identifier for "Dataset Feed" for pre - defined dataset -- > -- <id>http://xyz.org/data/waternetwork_feed.xml</id> <! -- rights, access info for pre - defined dataset -- > - 2011, XYZ; all rig hts reserved</rights> <rights>Copyright (c) 2002 <! -- last date/time this entry was updated -- > <updated>2012 - 03 - 31T13:45:03Z</updated> < ! -- summary -- > < summary>This is the entry for water network ABC Dataset</summary> <! optional GeoRSS - Simple poly gon outlining the bounding box of -- - defined dataset described by the . Must be lat lon -- > entry the pre <georss:polygon>47.202 5.755 55.183 5.755 55.183 15.253 47.202 15.253 47.202 5.755</georss:polygon> <! -- CRSs in which the pre - defined Dat aset is available -- > <category term="http://www.opengis.net/def/crs/EPSG/0/25832" label="ETRS89 / UTM zone 32N"/> <category term="http://www.opengis.net/def/crs/EPSG/0/4258" label="ETRS89"/> </entry> <! -- Any number of "Dataset Feeds" for different pre - defined datasets may be added here as separate entries -- > </feed> Note that only some of the mandatory INSPIRE Metadata elements for the Download service have been mapped to the Atom feed files. INSPIRE Metadata elements Atom implementation Condit (Mandatory - ional) Resource Title (M) /feed/title Resource Abstract (M) /feed/subtitle Resource Type (M) Not mapped Resource Locator (C) Feed level link in the top Atom feed /feed/link[@rel="self"] Coupled Resource (C) Entry level link in the top Atom feed /feed/entry/link[@rel="describedby"] Spatial Data Service Type (M) Not mapped Keyword (M) Not mapped</p> <p><span class="badge badge-info text-white mr-2">39</span> INSPIRE Technical Guidance for INSPIRE Download Services 3.1 - 2013 Page 39 - of 89 09 08 Atom implementation INSPIRE Metadata elements ional) (Mandatory Condit - Geographic Bounding Box (C) Not mapped Temporal Reference (M) Not mapped Spatial Resolution (C) Not mapped Conformity (M) Not mapped Not mapped Conditions for Access and Use (M) Limitations on Public Access (M) Feed level link in the top Atom feed /feed/rights Responsible Organisation (M) Feed level link in the top Atom feed /feed/author Metadata Point of Contact (M) Not mapped Metadata Date (M) Feed level link in the top Atom feed /feed/updated Metadata Language (M) Feed level link in the top Atom feed /feed/link[@rel="self"]/@hreflang : Mapping of INSPIRE Metadata elements to Atom 17 Table All the re quired INSPIRE metadata elements are to be found in the linked ISO 19139 metadata . document for the Download service as explained in Section 5.1.3 example Atom feed is form ed a nd what must be The following sections explain in more detail how this Technical Guidance requirements. done to meet particular Feed : feed „title‟ element Download Service 5.1.1 Typically this will correspond The title element shall be used to provide a title for the feed as a whole. the corresponding service metadata record. with the ̳Resource Title‘ in Example 3: Sample feed title <! feed title -- > -- <title>XYZ Example INSPIRE Download Service TG Requirement 5 The ̳title‘ element of an Atom feed shall be populated with a human readable title for the feed. sub 5.1.2 Download Service Feed : feed „ title‟ element The subtitle element may be used to provide a subtitle (containing additional information) for the feed as a whole. Typically this will correspond with the ̳Resource Abstract‘ in the corresponding service metadata record.

40 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - - 2013 Page 40 of 89 08 le feed subtitle Example 4: Samp -- feed subtitle -- > INSPIRE Download Service of organisation XYZ providing Hydrography data The ̳subtitle‘ element of an Atom TG Recommendation 1 may be populated with a human feed readable subtitle for the feed. Download Serv ice Feed : feed „link‟ element 5.1.3 service m etadata – Every Download Service must have a corresponding Metadata record in a discovery service. An Atom link element shall be provided that links to the metadata record for this Download Service. d iscovery service metadata record. The value of the ̳rel‘ attribute for this link shall be This should be a describedby ‖ [ POWDER ] The value of the ̳type‘ attribute shall be ―application/xml‖ ― or ―application/vnd.ogc.csw.GetRecordByIdResponse_xml ‖. ink Example 5: Example service metadata l TG Requirement 6 The ―Download Service Feed‖ shall contain a n Atom ̳link‘ element that links to for this Download Service. The value of the ̳rel‘ attribute the metadata record ‖ and the value of the ̳type‘ attribute shall describedby of this element shall be ― either "application/xml" . be In case of a ―hybrid implementation‖ based on Atom and WFS for Parts B and C, only the NOTE needs to be described through metadata in a discovery service. The link to the WFS Atom service shall be established through the ―related‖ link element in the Atom feed (see TG implementations uirement 16 ). Req - Download Service Feed : feed „link‟ element – self reference 5.1.4 The feed sh all have a link element which contains an HTTP URI for the feed document itself. This URI The value of the ̳rel‘ attribute for th is link shall provide the location of the feed and resolve to the feed. shall be ―self‖. Example 6: Example reference to feed TG Requirement 7 The ―Download Service F eed‖ shall contain a n Atom ̳link‘ element that contains an HTTP URI for the ―Download Service Feed‖ document. The value of the ̳rel‘ attribute of this element shall be ―self‖ , the ̳hreflang‘ attribute shall use the appropriate language code and the value o f the ̳type‘ attribute shall be ―application/atom+xml‖ .

41 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - - 2013 Page 41 of 89 08 – OpenSearch Description 5.1.5 Download Service Feed: feed „link‟ element Document document for A link element shall be provided that links to an OpenSearch description the Download The value of th e ̳rel‘ attribute of this link shall be ―search‖. The structure of the OpenSearch Service. separately in Section 5.4 . document is described description The ―Download Service Feed‖ shall contain a n Atom ̳link‘ element that TG Requirement 8 lin k to an OpenSearch description contains a the Download document for Service. The value of the ̳rel‘ attribute of this element shall be ―se arch ‖ , the ̳hreflang‘ attribute shall use the appropriate language code and the value of the ̳type‘ attribute shall be ―applicati . on/opensearchdescription+xml‖ Download Service Feed : feed „link‟ element – alternative languages 5.1.6 If the feed is available in different languages a link each alternative element shall be provided to (Language Requirements language version of the document. 5.3 This is described in de tail in Section for Atom Implementation ). representation 5.1.7 Download Service Feed : feed „li nk‟ element – alternative formats ative representations of the It is possible, although not a requirement of this guidance, to provide altern feeds, for example in HTML. In this case the ―alternate‖ value shall again be used for the rel ‘ attribute. ̳ A Example 7: ve links to HTML versions of a document ( in both English and German ) . lternati The HTML representation is useful to control how Atom feeds are displayed in diffe rent browsers and to be sure that all download links are easily accessible. For example, in Internet Explorer the link to dataset feeds are not clickable. illustrate that, when The two screenshots shown in 6 and Figure 7 Figure using the HTML representations , feed visualization is consistent between browsers, and download links (boxed in red) are accessible from the top feed.

42 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - 08 - 2013 Page 42 of 89 Figure 6 . Atom feed viewed in Firefox Figure . Ato m feed viewed in Internet Explorer 7 TG Recommendation 2 Alternative representations (for example HTML) should be provided as links. Where this is done the ̳ rel ‘ attribute should have the value ―alternate‖.

43 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - - 2013 Page 43 of 89 08 In the Apple Safari browser, Atom feed NOTE support has been removed starting in version 6. The http://www.vienna rss.org/ ) has been ( open source and free Vienna RSS/Atom feed reader application - successfully tested as a replacement of the functionality pre viously available in Safari. Download Service : feed „id‟ element 5.1.8 Feed This identifier shall be the same HTTP URI that An identifier shall be provided for the feed as a whole . d itself. dereference to the fee was used for the ̳self‘ reference and shall therefore also (In the Atom standard it is not required that the ̳id‘ matches the ̳self‘ reference but since this Download TG requires the use of HTTP URIs to identify feeds they are the same as a consequence). Example feed id element Example 8: -- identifier -- > http://xyz.org/download/en.xml The ̳id‘ element of a feed shall contain an HTTP URI which to TG Requirement 9 dereferences the feed Download Service Feed : feed „rights‟ element 5.1.9 to the ̳ ‘ element shall be used to capture any information about rights or restric tions rights The Download Service . Typically this will correspond with the value of ̳ accessConstraints ‘ in the Note that rights and restrictions may also be applied to corresponding service metadata record. individual pre - defined datasets in the linked ―Datase t feed‖. Example feed rights element Example 9: -- rights, access restrictions > Copyright (c) 2012, XYZ; all rights reserved The ̳ rights ‘ el ement of a feed shall contain information about rights or TG Requirement 10 or that feed. restrictions f Download Se rvice Feed : feed „updated‟ element 5.1.10 ̳ updated‘ element shall contain the date and time of the most recent changes to the feed. The ated el Example upd ement Example 10: -- 2012 - 03 - 31T13:45:03Z TG Requirement 11 The ̳ upd ated‘ element of a feed shall contain the date , time and timezone at which the feed was last updated. 5.1.11 Download Service Feed : feed „author‟ element The ‘author‘ element shall contain the contact information for the author of the feed. This may be contact in formation for an individual or organisation responsible for the feed . More than one author element may be provided .

44 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - - 2013 Page 4 4 of 89 08 Example feed author element Example 11: -- -- > John Doe mail> [email protected] The ̳ author‘ element of a feed TG Requirement 12 shall contain current contact information for an At the minimum, a name individual or organisation responsible for the feed. and email address shall be provided as contact information. Download Service Fee d : feed „ entry ‟ 5.1.12 element As per TG Requirement 1 a n entry shall be included for each pre - defined dataset . F link to a single “D ataset Example entry showing a eed ” Example 12: -- Water network ABC Dataset Feed spatial_ wn_id 1 >http://xyz.org/ dls: -- rel="describedby -- -- http://xyz.org/data/ abc/waternetwork -- Copyright (c) 2002 - 2011, XYZ; all rights reserved -- 2012 - 03 - 31T13:45:03Z -- optional GeoRSS - Simple polygon defin ing the bounding box of 47.202 5.755 55.183 5.755 55.183 15.253 47.202 15.253 47.202 5.755

45 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - - 2013 Page 45 of 89 08 load Service Feed: entry INSPIRE 5.1.13 identifier elements Down y in the download service feed shall contain the INSPIRE Spatial Dataset Unique Resource Each entr Identifier for the dataset described by that entry. This is the Spatial Dataset Unique Resource Identifier egulation [ as described ] . Th is shall be provided in two parts, the in the INSPIRE Metadata R INS MD inspire_dls: spatial_dataset_identifier_code ) and namespace ( inspire_dls: dsid_namspace ). code ( The inspire_dls namespace is defined as in the feed as follows: Namespace declaration for inspire_dls Example 13: ttp://inspire.ec.europa.eu/schemas/inspire_dls/1.0" xmlns:inspire_dls="h Example Spatial Dataset URI Example 14: — Spatial Dataset Unique Resourse Identifier for this dataset -- > wn_id1 taset_identifier_code spatial_dataset_identifier_namespace > TG Requirement 13 Each feed ̳entry‘ in a ―Download Service Feed‖ shall contain spatial_dataset_identifier_code spatial_dataset_ identifier_namespace and elements which together contain the Spatial Dataset Unique Resource Identifier for the dataset described by the feed. These elements are defined in schema inspire_dls which shall be included in the namespace declarations the of the fee d. Download Service Feed: entry „link‟ to dataset metadata record 5.1.14 Each entry shall contain a link to a (ISO 19139) dataset metadata record. There shall be only one such link in each feed entry. dataset metadata record Example 15: Example link to a -- TG Requirement 14 Each feed ̳entry‘ in a ―Download Service Feed‖ shall contain a link to a Dataset metadata record. This link shall have a ̳rel‘ attribute w ith a value of ―describedby‖ and a ̳type‘ attribute with a value ―application/xml‖ 5.1.15 Download Service Feed: entry „link‟ to dataset feed Each entry shall contain a link to a ―Dataset Feed‖ (Dataset Feeds are described in Section 5.2 ) . There shall be only one such link in each feed entry. Example 16: Example link to a single “Dataset Feed”

46 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - - 2013 Page 46 of 89 08 hreflang="en" title="Feed containing the pre defined waternetwork - dataset (in one or more downloadable formats)"/> TG Requirement 15 Each feed ̳entry‘ in a ―Download Service Feed‖ shall contain a single link to a ―Dataset Feed‖. This link shall have a ̳rel‘ attribu te with a value of ―alternate‖ and a ̳type‘ attribute with a value ―application/atom+xml‖ 5.1.16 „li nk‟ to WFS implementation (only for Download Service Feed: entry “hybrid implementations”) the Atom implementation is complemented by one or several WFS for th e Direct Access operations If Get Spatial Object and Describe Spatial Object Type (―hybrid implementation‖, see section 4 ), a link needs to be established to the service offering these additional operations. TG Requirement 16 mplementation‖ based on Atom for Part A of [ INS NS , In case of a ―hybrid i INS NS , Annex IV], a link shall be Annex IV] and WFS for Parts B and C of [ Where this is done the rel ‟ provided to the WFS Capabilities document. ̳ shall have the value ― related‖ and the „type‟ attribute shall have the attribute value ―application/xml‖ WFS implementation for the Direct Access operations Example 17: Example link to a -- link to related WFS implementing Direct Access operations operations Download Service Feed: entry, additional elements 5.1.17 e guidance for id , title and updated elements for each entry is equivalent to the guidance for the Th in the enclosing feed and can be summarised by the following r equirements and same elements recommendations: The ̳id‘ element of a feed entry in a Download Service F eed shall contain an TG Requirement 17 identifier for that feed entry. TG Requirement 18 The ̳title‘ element of a fee d entry eed shall be in a Download Service F populated with a human readable title for the feed entry. TG Requirement 19 The ̳updated‘ element of a feed entry in a Download Service F eed shall contain the date time and timezone at which the feed entry was last updated. , Sinc e the ̳rights‘ information may often be the same for all entries in a feed this element may be omitted for each individual entry if it is present in the enclosing feed . The rights in this case refer to the pre - defined dataset the feed entry describes.

47 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - - 2013 Page 47 of 89 08 ̳rights‘ element of a feed entry may contain information about rights or TG Recommendation 3 The feed entry. restrictions specific to that In the case where ̳rights‘ information is not given for individual entries, the entries assume the rights of enclosing feed. the the ̳author‘ information may often be the same for all entries in a feed so this element may Similarly, also be omitted for each individual entry. The ̳author‘ element of a feed entry may contain information about the TG Recommendation 4 author specific to that feed entry. Again, in the case where ̳author‘ information is not given for individual entries, the entries assume the enclosing feed. author properties of the 5.1.18 Download Service Feed: entry „summary‟ element ‘summary‘ - readable information abo ut the feed entry. element may contain additional human The Example summary element Example 18: -- summary -- > This is the entry for water network ABC Dataset entry should contain a summary TG Recommendation 5 The ̳summary‘ element of a feed entry . description of the feed Download Service Feed: e ntry „geors s‟ element 5.1.19 the To enable GeoRSS [ GeoRSS ] tools to display INSPIRE Atom feeds we recommend augment ing Atom feed entries with GeoRSS elements to show the geographic extent of the dataset s. GeoRSS Simple should be used in feed entries to indicate the geograph ic TG Recommendation 6 - extent of the dataset. Since georss:box is not well supported in common tools it is recommended to use georss:polygon to define bounding boxes, and georss:point when a dataset ‘s geometric extent is represented by a single . It is not recom mended to use georss:box. point location TG Recommendation 7 dataset described by a feed entry should be The bounding box of the provided using a georss:polygon, unless the geographic extent is a single point in which case georss:point should be used. ion, t he extent of the dataset must be As determined by the GeoRSS specificat lat - lon . This in WGS84 extent should correspond with the ̳Geographic Bounding Box‘ in the corresponding dataset metadata record. - Simple Point Example 19: GeoRSS — example GeoRSS 53.1 10.2 Example 20: GeoRSS - Simple Polygon 47.202 5.755 55.183 5.755 55.183 15.253 47.202 15.253 47.202 5.755

48 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - - 2013 Page 48 of 89 08 s five points, the last being the Note that the polygon describing a rectangular bounding box contain same as the first. Download Service Feed: entry „category‟ element – CRSs 5.1.20 defined - The category element shall be used within the feed entry to indicate the CRSs in which the pre dataset is available. Example 21: Example CRS description s -- CRSs in which the pre - defined Dataset is available -- > Each feed entry s hall contain an Atom ̳category‘ element for each CRS in TG Requirement 20 which the pre dataset is available . This category element shall refer to - defined well - known definition of a coordinate reference system. a This uidance places no requirements on the coordin ate reference systems in which data Technical G should be made available. Guidance and requirements for coordinate reference systems is given in dataset Data Specifications and the regulation on the spatial thematic s and the interoperability of services [ INS SDS] . re 5.2 Ato m “Dataset feed” containing download links to a p - defined dataset example contains - defined the description of the spatial objects in the pre The following ―Dataset feed‖ point to the pre - defined dataset in a variety of CRS and dataset and format entries, which This example is conformant to the Pre - defined Atom conformance class and can be combinations. used as a template for implementation. Example “Dataset Feed” containing links to a pre - defined dataset Example 22: -- Example "Dataset Feed" -- > -- XYZ Example INSPIRE Dataset ABC Download -- INSPIRE Download Service, of organisation XY Z providing ABC for the Hydrography theme dataset -

49 INSPIRE Technical Guidance for INSPIRE Download Services 3.1 09 - 2013 Page 49 of 89 - 08 link to this feed in another language -- http: //xyz.org/data/abc/waternetwork.xml rights, access restrictions Copyright (c) 2012, XYZ; all rights reserved - 03 - 31T13:45:03Z 2012 John Doe [email protected] - Water network in CRS EPSG:25832 (GML) zone 32N (http:/ http://xyz.org/data/abc/waternetwork_25832.gml 2011 - 06 - 15T11:12:34Z Water network in CRS EPSG:4258 (GML) -- http://xyz.org/data/abc/w aternetwork_WGS84.gml 2011 - 06 - 14T12:22:09Z 4258

50 INSPIRE Technical Guidance for INSPIRE Download Services 3.1 of - 2013 Page 50 - 89 09 08 , ShapeFile is in a single zip archive. Water network in CRS EPSG:25832 (ShapeFile) http://xyz.org/data/abc/waternetwork_25832. zip 2011 - 06 - 15T11:12:34Z Water network in CRS EPSG:4258 (ShapeFile) http://xyz.org/data/abc/waternetwork_WGS84. zip 2011 06 - 14T12:22:09Z - rights title , subtitle , id , , The guidance for the updated and author elements is the same as for the Dataset Download Feed and the correspond ing sections should be to. The requirements are referred summarised as follows: The ̳title‘ element of a ―Dataset TG Requirement 21 shall be populated with a human Feed‖ readable title for the feed. TG Recommendation 8 The ̳subtitle‘ element of a ―Dataset Feed‖ may be populated with a human r eadable subtitle for the feed. TG Requirement 22 The ̳id‘ element of a ―Dataset Feed‖ shall contain an HTTP URI which dereferences to the feed TG Requirement 23 The ̳rights‘ element of a ―Dataset Feed‖ shall contain information about rights or restrictions for that feed.

51 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - - 2013 Page 51 of 89 08 shall contain the date, time and ̳updated‘ ele ment of TG Requirement 24 F eed ‖ The a ―Dataset timezone at which the feed was last updated. The ̳author‘ element shall contain current contact TG Requirement 25 of a ―Dataset Feed‖ information for an individual or organisation responsible for the feed. At the nimum, a name and email address shall be provided as contact information. mi - defined datasets (e.g. as GML files) are made available for download within a feed ̳entry‘ of The pre . the Dataset Feed Each ― Dataset TG Requirement 26 Feed‖ shall contain at least one feed entry con taining links to - defined dataset (e.g. as a GML file). download the pre - If the pre defined dataset is available to download in different formats or different Coordinate Reference Systems then a separate entry must be provided for each available format/CRS combination. Each " Dataset Feed" shall contain separate entries for each format/CRS TG Requirement 27 - defined dataset is available to download. combination in which the pre 5.2.1 D ataset Feed: „ link ‟ element: link to Spatial Object descriptions For each Spatial Object e dataset Atom links shall be provided to the corresponding Spatial Type in th definition registry. Where a dataset is not an interoperable format Object Type in the INSPIRE should be used to identify the spati al object described by the Data Specificati ons then a local scheme These links shall use the ̳describedby‘ relation type and the appropriate media type type. for the resource . For definitions in the INSPIRE registry the media type shall be ―text/html‖. Links to the INSPIRE registry (for Watercourse and Standing Water) Example 23:

52 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - - 2013 Page 52 of 89 08 sh all contain an Atom ̳ link‘ element for each INSPIRE Spatial TG Requirement 28 Each feed INSPIRE Registry unless Object Type in the dataset. The link shall refer to the link to a the data does not conform to any Data Specification in which case a Type The value of shall be used instead. local definition of the Spatial Object y‖. For definitions in the the ̳rel‘ attribute of this element shall be ― describedb INSPIRE registry the value of the ̳type‘ attribute shall be ―text/html‖. Dataset Feed: optional „link‟ element: link to Download fe ed 5.2.2 In order to facilitate the reverse navigation between the Dataset feed and its ̳parent‘ Download feed it is recommended that a link element is included that links back to the parent in the Dataset feed of ―up‖ and a type attribute with a value Download feed. This link should have a ̳rel‘ value ―application/atom+xml‖ . Optional upward link to download service feed Example 24: ̳upward‘ link to the corresponding download service feed TG Recommendation 9 A link element should be included that links to the ̳parent‘ Dataset feed. This link should have a ̳rel‘ attribute with a value of ―up‖ and a ̳type‘ attribute with tom+xml‖. a value of ―application/a 5.2.3 Dataset Feed: Entry „link‟ element: link to pre - defined dataset The link element of an entry is also used to provide a link which resolves to the pre - defined dataset. . If the pre T his shall be a direct link to the dataset (e.g. to a file) dataset is available in different - defined encoding formats (e.g. GML, ShapeChange, NetCDF) or in different Coordinate Reference Systems (CRS) then separate entries shall be used for each available combination of CRS and format. Example link to pre - defined dataset Example 25: -- http://xyz.org/data/abc/waternetwork_25832.gml - 06 - 15T11:12:34Z 2011 Water network in CRS EPSG:4258 (ShapeFile) 53 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - - 2013 Page 53 of 89 08 WGS84 geographic coordinates (http://www.opengis.net/def/crs/OGC/1.3/CRS84)"/> ternetwork_WGS84. zip http://xyz.org/data/abc/wa - 06 - 14T12:22:09Z 2011 me other sub Note that if a dataset spans more than one physical file (e.g. if it is stored in tiles or so - division for practical purposes) then additional link elements may be provided within the entry for that dataset, one link per physical file according to the additional guidance in Section 5.2.4 . E ach feed entry sh all contain an Atom ̳link‘ element that links to the pre - TG Requirement 29 defined dataset file described by the entry. The value of the ̳rel‘ attribute of alternate and a ―length‖ attribute (providing the length this element shall be ― ‖ of the linked resource in octets*) sh be provided if possible. Where a all dataset is provided in multiple physical files, additional ̳link‘ elements shall be link provided in the feed entry , one for each physical file. *1 octet = 8 bits (usually synonymous with 1 byte) the link element shall be used to indicate the media type of the resource that will The ̳type‘ attribute of (see also Section below). be returned if the link is resolved. For example, ̳application/gml+xml‘ 5.2.4 The ̳type‘ attribute of the link eleme nt shall be used to indicate the media type TG Requirement 30 of resource that will be returned if the link is resolved. A valid media type must ; be used for the value of this attribute if the media type is not registered with IANA it should still follow the conventions for unregistered media types. pre - In the case where datasets are provided in multiple languages, a different link element defined shall be used for each language and the ̳hreflang‘ attribute shall be used with the appropriate language code. TG Requirement 31 Where alternative language representations of datasets are linked to, the ̳hreflang‘ attribute of the link element shall be used to indicate the language of the target dataset as described in the Atom specification. le files. 5.2.4 Dataset Feed: guidance for datasets which contain multip and it is not desirable or practical to deliver them Where a dataset is provided in multiple physical files within a single download (e.g. as a zip), then it is also possible to deliver the individual files separately by adding multiple ̳link‘ el ements to the feed entry. This may be useful, for example, if there are a large number of files. There should be a separate ̳link‘ element for each file. These links shall have a ̳rel‘ value equal to ―section‖. TG Requirement 32 Where a dataset is provided in multiple physi cal files: each file shall be linked to via a separate ̳link‘ element. Each of these ̳link‘ elements shall have a ̳rel‘ value equal to ―section‖. Additionally there is a need to provide a description of the structure of the collection of files. This ption shall either be provided as free text within a ̳content‘ element, or as another link, with a descri

54 INSPIRE Technical Guidance for INSPIRE Download Services 3.1 of - 2013 Page 54 - 89 09 08 ̳rel‘ value of ―alternate‖. This link shall point to a descriptive document that describes how the parts of places no restrictions on the type or contents of this the dataset fit together. This Technical Guidance shall be used descriptive document. However when such a link is added an appropriate media type for the ̳type‘ attribute. Where a dataset is provided in multiple physical files: a description of the TG Requirement 33 ataset structure shall be provided EITHER in a n d atom ̳content‘ element as free text, OR in an external document which is the target of another ̳link‘ element. Where a ̳link‘ element is used this element shall have a ̳rel‘ value equal to ―alternate‖ and a s uitable media type shall be used for the ̳type‘ value. For the purposes files , optional ̳bbox‘ and/or ̳time‘ attributes may be added of differentiating between ̳ to the link elements. Where a attribute is used the value of this shall be formatted in t he bbox same ‘ way as georss:box element, and when a ̳time‘ attribute is used it shall be formatted as a ISO 8601 time strings. Example 26: Use of bbox and time attributes — TG Recommendation 10 Where a dataset is provided in multiple physical files: a ̳bbox‘ attribute may . If this is used, be used to describe the geospatial extent of a particular file then the value of this attribute should be structured according to the georss:box structure. Where a dataset is provided in multiple physical files: a ̳time‘ attribute may TG Recommendation 11 this is used, be used to describe the temporal extent of a particular file. If then the value of this attribute should be structured according to the ISO 8601 standard. entry shows a dataset that is in three parts each with a separate bounding box , The following example content element describing the datas . et along with a Multi - part dataset described by a content element Example 27: Water network in GeoTIFF This dataset consists of three GeoTIFF files. Each file has data for a different geospatial area, identified by the bbox attribute.

55 INSPIRE Technical Guidance for INSPIRE Download Services 3.1 of - 2013 Page 55 - 89 09 08 GeoTiff http://xyz.org/data/abc/waternetwork_WGS84 - 06 - 14T12:22:09Z 2011 the ̳alternate‘ link instead of the ̳content‘ element. And here is the same example but using Multi - part dataset described by an external document Example 28: Water network in GeoTIFF – section" GeoTiff – GeoTiff http://xyz.org/data/abc/waternetwork_WGS84 2011 - 06 - 14T12:22:09Z 5.2.5 Dataset Feed: guidance on media type s (atom) The media type of a spatial data file referenced in a link shall be indicated in the type attribute of the link (as per TG Requirement 30 ). To facilitate interoperability in INSPIRE, only media types listed in the INSPIRE media type registry shall be used. This registry will be maintained at the following URI: http://inspire.ec.eu - types ropa.eu/media TG Requirement 34 Only media types listed in the INSPIRE media - types register shall be used. Example 29: GML download For example, t he media type for a GML file is "application/gml+xml" with additional (optional) parameters for the character set used and the GML v ersion.

56 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - - 2013 Page 56 of 89 08 - application/gml+xml;charset=utf 8;version=3.2 Zipped media Example 30: For example, no registered media type exists for zipped Esri Shape F iles or File Geodatabases so - media types such as application/x - filegdb might be used in INSPIR E as a shapefile or application/x stopgap until common practice emerges. (see the registry at - types http://inspire.ec.europa.eu/media for actual media types). - shapefile application/x - filegdb application/x If transfer of compr essed data is desirable for particular uncompressed files then compression as supported by HTTP 1.1 may be used. It is recommended that clients wishing to benefit from HTTP compression shall set their HTTP Accept - Encoding header to ―gzip, deflate‖. For fi TG Recommendation 12 les that are made available uncompressed, compression is offered by HTTP 1.1 server and clients. As spatial data sets may be large, clients should set their HTTP Accept Encoding header to include "gzip, deflate" in - each request for uncompressed files. Data set Feed: entry „georss‟ element 5.2.6 is also applicable to Dataset 5.1.19 The guidance on georss for Download Service Feeds in section Feeds. Any TG Requirements and TG Recommendations in this section also apply here. 5.2.7 entry „category‟ element Dataset Feed: Finally, each entry uses the category element to identify the CRS. Example 31: Using the category element to refer to an EPSG code (registered at OGC) Each CRS representation shall have a ̳category‘ element which refers to the TG Requirement 35 CRS definition and code. 5.3 Language Requirements for Atom Implementation The following two requirements are mandatory for all Download Services. In the case of the Atom impl 5.3 ) are ementation they are automatically met if the remaining requirements in this Section ( followed. TG Requirement 36 A Download Service metadata response shall contain a list of the natural languages supported by the service. This list shal l contain one or more languages that are supported.

57 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - - 2013 Page 57 of 89 08 TG Requirement 37 A client may specify a specific language in a request. If the requested language is contained in the list of supported languages, the natural language sted language. I f fields of the service response shall be in the reque the requested language is not supported by the service, then this parameter shall be ignored. If an Atom feed is available in different languages a link element shall be provided linking to each nt. The following guidance is applicable to ―Download alternative language version of the docume Service Feeds‖ and ―Dataset Feeds‖. The value of the ̳rel‘ attribute of these elements shall be ―alternate‖ and the ̳hreflang‘ attribute must be populated with the appropriate language code for the link ed document in each case. Example 32: Alternative representation is available in German (hreflang=“de”) download/de.xml " rel="alternate" TG Requirement 38 Where a feed is made available in alternative languages, links shall be provided to these alternative representations. These links shall each use the ̳hreflang‘ attribute to indicate the language of the alternative representation. ments this element shall be The value of the ̳rel‘ attribute for these link el e ―alternate‖. Note that where documents are available in multiple languages the ̳self‘ link refers to the version of the document in which it is found. So while an English feed may contain the followin g self and alternate link elements: Example 33: English feed with alternative version in German /download/en.xml " rel="self" The corresponding German version of the feed inverts the self and alternate link elements so that ̳self‘ refers to the German feed and ̳ alternate‘ to the English. Example 34: German feed with alternative version in English

58 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - - 2013 Page 58 of 89 08 OpenSearch Document structure. 5.4 to provide 'operations' and document them as required by the In order in a conventional sense INS NS ] , the Open Search standard is proposed , which Network Services Regulation [ makes it - operations with custom possible to specify, via an xml document with a well known structure, . also recognized by the major b rowsers parameters in an interoperable way OpenSearch engines are like Mozilla Firefox, Internet Explorer, Safari and Chrome. This Open Search description document is linked to from the ―Download Service Feed‖. In addition to service to satisfy the Ge the descriptive document it is necessary to implement a simple t Spatial Data Set and Describe Spatial Data Set operations. Example code can be found in Annex A. Technical Guidance does not place any requirements on the technology used to implement the This simple service. otiation to identify which operation to perform. This The example given in Annex A uses content neg means that even though the operation endpoint is only one, i.e. http://xyz.org/search.php , the client has to set the HTTP ―Accept‖ Header to the correct value in order to receive the expected result. A simple service to perform the Desc r ibe Spatial Dataset and TG Requirement 39 Get Spatial Data Set operations shall be provided and described by an OpenSearch description document. Open Search description document Example 35: ption xmlns="http://a9.com/ rtName>INSPIRE Demo Download Service. Search Description for Demo INSPIRE Download Service -- URL of this document > Dataset [email protected] waternetwork_abc WaterNetwork ABC from Organisation XYZ

59 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - - 2013 Page 59 of 89 08 http://xyz.org/waternetworkSearch.png -- European Commission Joint Research Centre - en - gb de 5.4.1 OpenSearch Description: „Url‟ element: link to self The OpenSearch Description shall contain a ̳Url‘ element which contains an HTTP URI for the ion of the document and resolve to the OpenSearch document itself. This URI shall provide the locat document. The value of the ̳rel‘ attribute for this link shall be ―self‖. Example reference to self Example 36: -- template="http://xyz.org/o TG Requirement 40 element that describes an The OpenSearch description shall contain a ̳Url‘ e OpenSearch Description document. The value of the ̳rel‘ HTTP URI for th attribute of this element shall be ―self‖ , the value of the ̳type‘ attribute sh all be ― application/opensearchdescription+xml ‖ and the value of the ̳template‘ attribute shall be the HTTP URI of the document. 5.4.2 OpenSearch Description: Generic search template A generic search template shall be supplied for browser integration. It enables search clients like Internet Explorer or Firefox to integrate the download service as an additional search engine.

60 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - - 2013 Page 60 of 89 08 Figure a search engine in Internet Explorer . Download service integrated as 8 engine can be advertised in an html page by adding a link element The availability of an OpenSearch page: html similar to the following one to the HEAD section of the link rel ="search" < ="application/opensearchdescription+xml" title ="CCM2" type href opensearchdescription.xml "> =" detection of the OpenSearch engine popular browsers . The automatic has been tested for a number of 18 gives an overview of the t estin g results. Table Browser Comments Platform Version Requires plugin tested Internet No 8 Windows Explorer Windows No Firefox 21.0 6.0.5 Mac OS X Safari Yes Automatic detection of the OpenSearch engine has been successfully tested with the plugin OpenSearchFo rSafari discovery Chrome 27.0 Windows No The OpenSearch engine is a utomatic ally only if the html page is at the root of the web site domain Table 18 : Testing of the detection of the OpenSearch engine in the most popular browsers Example generic URL search template Example 37: -- text/html " rel="results" TG Requirement 41 The OpenSearch description shall contain a ̳Url‘ element that describes a template URL for generic search queries. The value of the ̳rel‘ attribute of this element shall be ―results‖, the value of the ̳type‘ attribute shall be ― text/html ‖.

61 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - - 2013 Page 61 of 89 08 template Da ta S et Operation Describe Spatial 5.4.3 OpenSearch Description: Data all be supplied that provides the request mechanism for a Describe Spatial A search template sh Operation. Set Example Describe Spatial Data Set template Example 38: Describe Spatial et S -- Operation request URL template to be used in & guage?} The OpenSearch description shall contain a ̳Url‘ element that describes TG Requirement 42 a Data Set operation. This template shall template URL for the Describe Spatial the accept SPIRE parameters ― spatial_dataset_identifier_code ‖, IN ― ‖ and the OpenSearch ―language‖ spatial_dataset_identifier_namespace parameter. The ̳Url‘ element shall have an attribute ̳type‘ with a value of ―application/atom+xml‖ and an attribute ̳rel‘ with the valu e ―describedby‖ . Data Set The Describe Spatial response shall be the description of the Spatial Objects in the requested Spatial Dataset and in the requested language. i.e. it shall be the relevant atom ―Dataset to Feed‖ corresponding , the specified spatial _dataset_identifier_code spatial_dataset_identifier_namespace and language . to machine interaction, if a client wants to issue a Describe Spatial Data Set request , it - - In a machine Url ‘ element with the attr will read the Open Search document, extract the rel=‖describedby‖ ̳ ibutes . It will then replace the template arguments with the actual values for the and type=‖application/xml‖ Spatial Dataset Identifier code and namespace, and language . Using an OpenSearch template for building a Describe Spatial Data Set request Example 39: code “mycode” and f description of the Spatial Data Set identified by the looking for the the a client is I namespace “mynamespace” in the English language, the following template: patial_dataset_identifier_code http://xyz.org/search.php?spatial_dataset_identifier_code={inspire_dls:s ?}&spatial_dataset_identifier_namespace={inspire_dls:spatial_dataset_identifier_namespace?}&langu age={language?}&q={searchTerms?} will be used to form the actual URL as follows: http://xyz.org/search.php?spatial_dataset_identifier_code=mycode&spatial_dataset_identifier_namesp ace=mynamespace&language=eng The response will be the appropr iate data set atom feed. 5.4.4 Get Spatial Data S et Operation OpenSearch Description: template A search template shall be supplied that provides the request mechanism for a Get Spatial Data S et Operation. Example 40: Example Get Spatial Data S et template 62 INSPIRE Technical Guidance for INSPIRE Download Services 3.1 of - 2013 Page 62 - 89 09 08 spatial_dataset_identifier_code e_dls: }& spatial_dataset_identifier_name ? space inspire_dls: spatial_dataset_identifier_namespace ?}&crs={ inspire_ ={ crs?}&language={language?}&q={searchTerms?}"/> dls: TG Requirement 43 The OpenSearch description shall contain a ̳Url‘ element that describes a template UR L for the Get Spatial Data S et operation. This template shall accept the INSPIRE parameters ―crs‖ , ― ‖, spatial_dataset_identifier_code spatial_dataset_identifier_namespace OpenSearch ―language‖ ― ‖ and the The ̳Url‘ element shall have an attribute parameter. ̳type‘ with a value corresponding to the media type of the result and an attribute ̳rel‘ with the value ―results‖ . When a dataset is not downloadable as a single file, but is a multipart dataset, then the OpenSearch result for the Get Spatial Dataset opera tion allows for multiple results to be returned. In order to avoid an HTTP multipart response, which is not supported by browsers and would require specific clients, the Get Spatial Dataset operation shall return an Atom feed containing the links to the fi les to be downloaded instead of the files themselves as in the following example. Example 41: OpenSearch URL template returning an Atom feed. 5.4.5 OpenSearch Description: Spatial Dataset Identi fiers Available Spatial Dataset Identifiers shall be indicated using the OpenSearch ―example‖ query mechanism. Example Get Spatial Data S et template Example 42: -- -- > List of available Spatial Dataset Identifiers TG Requirement 44 For each dataset available the OpenSearch descri ption shall contain a ̳Query‘ element that has a ̳role‘ attribute with the value ―example‖ and spatial_dataset_identifier_code ‘ and ̳ spatial_dataset_identifier_namespace ̳ ‘ attributes together containing unique spatial dataset identifier. The value of the ̳ crs ‘ and ̳ language ‘ attributes shall be set to the values considered as the default ones by the service provider. The Get Spatial Data Set response shall be the file corresponding to the specified spatial_dataset_identifier_code , spatial_dataset_identifi er_namespace , crs and language, as declared in the relevant atom ―Dataset Feed‖.

63 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 08 - 2013 Page 63 of 89 - 5.4.6 OpenSearch Description: Available Languages The languages supported by the service shall be indicated in the OpenSearch description. The first language in the list is the def ault language. Example 43: Example Language support L -- en de TG Requirement 45 For each language supported by the download service, the OpenSearch description shall contain a ̳ element that contain s the language Language code. The first ̳L ‘ element shall contain the Default L anguage. anguage

64 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - - 2013 Page 64 of 89 08 Feature Service and 6 Encoding Filter Web defined Download aset - Implementation of Pre Dat ervice S - defined WFS: Implement Pre - Defined Dataset Download Service TG Conformance Class 2: Pre and 19143 Filter Encoding (―Part A‖) using ISO 19142 Web Feature Service . This conformance class is inclusive of : to TG Requirement 46 TG Requirement 60 to TG Recommendation 15 TG Recommendation 14 An alternative way to implement pre n ISO 19142 - defined dataset download services is by deploying a eature Service Web F [ ISO 19142 ] supporting ISO 19143 Filter Encoding [ ISO 19143 ] in line with the Technical Guidance contained in this chapter. Rather than repeat large parts of the WFS and FE specification s in this document , references are made to conformance classes from the WFS and FE specification s which shall be implemented . Where additional functionality is required, as is the case lingual requirements then this is described below. with multi - F eature Service 2.0 Note that ISO 19142 is also known as OGC W and ISO 19143 is also known as eb ilter Encoding 2.0 OGC F Conformance to ISO 19142 „ Simple WFS‟ Conformance Class 6.1 - and ISO 19143 FE it is ne cessary to defined access using ISO 19142 WFS In order to implement pre WFS‘ conformance classes as described in the 19142 standard [ ISO 19142 ]. conform to the ̳Simple Impl ementations shall conform to ISO 19142 TG Requirement 46 Conformance Class ̳Simple WFS‘ 6.2 Conformance to ISO 19143 „Query‟ Conformance Class - defined download services using ISO 19142 WFS and ISO 1 In order to implement pre 9143 FE it is necessary to conform to the ̳Query‘ conformance classes as described in the 19143 standard [ ISO 19143 ]. TG Requirement 47 Implementations shall conform to ISO 19143 Conformance Class ̳Query‘ 6.3 Conformance to ISO 19142 „HTTP GET‟ Conformance Class In order to im plement pre - defined download services using ISO 19142 WFS and ISO 19143 FE it is necessary to conform to the ̳ HTTP GET ‘ conformance classes as described in the 19142 standard [ ISO 19142 ]. TG Requirement 48 Impl ementations shall conform to ISO 19142 Conformance Class ̳HTTP G et ‘

65 INSPIRE Technical Guidance for INSPIRE Download Services 3.1 of - 2013 Page 65 - 8 9 09 08 Stored Quer y Support 6.4 ISO 19142 describes the use of pre defined stored queries in WFS to access features via a Web - - - defined dataset s it is necessary to provide some pre Feature Service. To enable the download of pre defined stored queries to access the pre - defined dataset s. ISO 19142 describes the operations ListStoredQueries and DescribeStoredQueries. The former is used to retrieve a list of stored queries that are available and the latter is used to request more uery (or queries) such as the parameter arguments that are information about a particular stored q required to make a GetFeature request using the stored query. Pre TG Requirement 49 defined Stored Queries shall be provided to make pre - defined datasets - available. Any implementation shall ensure that all possible (i.e. available) combinations of CRS/ DataSetIdCode / DataSetIdNamespace language should be available through a pre - defined stored query. / TG Requirement 50 Any possible (i.e. available) combinations of CRS/ DataSetIdCode / DataSetIdNamespace / language shall be made available t hrough pre - defined stored queries. efine only one Stored Every instance of a WFS - based pre - defined dataset download service should d Query for serving pre - in order to make it easier for clients who already know defined Spatial Data Sets e Stored Query. the identifier of th The following identifier should be used to identify the Stored Query for TG Recommendation 13 - defined Spatial serving Sets: pre Data http://inspire.ec.europa.eu/operation/download/GetSpatialDataSet he parameter names for the arguments of the Stored Query shall T be consistent as proposed in the following requirement: - defined Stored Queries shall use the parameter names ―CRS‖, TG Requirement 51 Pre DataSetIdCode ― , ― DataSetIdNamespace ‖ and ―Language‖ to identify the ‖ CRS, dataset ID code, dataset ID namespace and language components of a query. d ( mycode ) , For example the following stored query takes arguments for the parameters DataSetI Code mynamespace DatasetIdNamespace ( , CRS (EPSG:4326) and Language (English) . ) Example 44: Custom stored query requesting a dataset by ID and CRS (informative onl y) http://www.myinspirewfs.com/request=getFeature&storedquery_id= http://inspire.ec.europa.eu/operation/download/GetSpatialDataSet &DataSetIdCode= mycode &DataSetIdNamespace= &CRS=EPSG:4326 &Language mynamespace =eng Beyond these mandated parameter names t his Technical Guidance does not place any four dataset specific. requirements on other parameter names as they may be

66 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - - 2013 Page 66 of 89 08 6.5 INSPIRE Datasets and WFS Features WFS is designed around the feature paradigm (spatial objects in INSPIRE terminology). There is no concept o f ̳datasets‘, only a single data store that contains the features. Therefore, it is common practice that a separate WFS ̳endpoint‘ is provided for each dataset. An endpoint in this context G means the base URL of the WFS service i.e. the URL to which a pabilities request is made. etCa i.e: for a WFS service that can be called as follows: - wfs.com/mydata?request=getCapabilities&service=WFS& ... http://my would be: The endpoint in this context - wfs.com/mydata http://my A separate WFS endpoint shall be provided for each INSPIRE dataset thus TG Requirement 52 providing one dataset per GetCapabilities response. 6.6 Publishing INSPIRE metadata using Capabili ties ows:Extended In order to make the Download Service INSPIRE metadata elements available via a standard WFS it se ows:ExtendedCapabilites in the is necessary to u capabilities response and publish the WFS INSPIRE metadata according to an extension schema within an i nspire_dls:ExtendedCapabilities element. The INSPIRE extension schema and example instance documents can be found at: http://inspire.ec.europa.eu/schemas/inspire_dls/ The schema document it self is at http://inspire.ec.europa.eu/schemas/inspire_dls/1.0/inspire_dls.xsd te to There are two possible options that may be used and it is up to the implementing Member Sta decide which is more appropriate according to need. The first option is to use the ows:ExtendedCapabilities to publish a link to a Download Service metadata record. (e.g. in a discovery service). This should be done using a in the extended capabilities section. The second option is to publish all the metadata elements directly in the WFS capabilities (and using the mapping in the following table. ) ows:ExtendedCapabilities INSPIRE Metadata elements elements of 19142 ISO - onditional C ) andatory M ( ows:ServiceIdentification/ows:Title Resource Title (M) ows:ServiceIdentification/ows:Abstract Resource Abstract (M) inspire_common:ResourceType Resource Type (M) (ExtendedCapabilities) ins pire_common:ResourceLocator Resource Locator (C) (ExtendedCapabilities) w f s:M etadata URL (per feature type) Coupled Resource (C) inspire_common:SpatialDataServiceType Spatial Data Service Type (M) (ExtendedCapabilities) ows:Keywords/ows:Keyword; Keyword (M) inspire_common:Ke yword

67 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for - 08 - 2013 Page 67 of 89 09 INSPIRE Metadata elements elements of 19142 ISO ) C - andatory M ( onditional ows:WGS84BoundingBox (Layer property) Geographic Bounding Box (M) inspire_common:TemporalReference Temporal Reference (M) (ExtendedCapabilities) ows:ServiceIdentification/ows:Abstract Spatial Resolution (C) inspire_common:Conformity (M) Conformity * (ExtendedCapabilities) f to the Data *refers to conformity o Specificaitons Fees ows:ServiceIdentification/ ows: Conditions for Access and Use (M) ows:ServiceIdentification/ows :AccessConstraints Limitations on Public Access (M) /ows:ProviderName ows:ServiceProvider Responsible Organisation (M) and: ows:ServiceProvider/ ows:ServiceContact/ows:Cont actInfo inspire_common:MetadataPointOfContact Metadata Point of Contact (M) (ExtendedCapabilities) inspire_common:MetadataDate Metadata Date (M) (ExtendedCapabil ities) inspire_common:SupportedLanguages Metadata Language (M) (ExtendedCapabilities) inspire_dls:SpatialDataSetIdentifier/inspire_co Unique Resource Identifier (M) mmon:Code inspire_dls:SpatialDataSetIdentifier/inspire_co mmon:Namespace (ExtendedCapabilit ies) Table 19 : Mapping INSPIRE Metadata elements to ISO 19142 WFS INSPIRE Metadata for the Download Service shall EITHER be linked to via an TG Requirement 53 in an extended capabilities section, OR the extended capabi lities section shall contain all the INSPIRE Metadata for the Download Service in accordance with Table 4 and the inspire_dls:ExtendedCapabilities schema. The following example shows an inspire_d ls:ExtendedCapabilities section.

68 INSPIRE Technical Guidance for INSPIRE Download Services 3.1 of - 2013 Page 68 - 89 09 08 Extended capabilities Example 45: ex test service Please enter a ti tle 0000 - 01 - 01 notEvaluated [email protected] 0000 - 01 - 01 view infoFeat ureAccessService pol eng eng > mycodehttp://myuri.org mycode2 http://myuri.org

69 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 89 09 - 2013 Page 69 of 08 - Language R 6.7 for WFS /FE Implementation of Pre - equirements defined D ownload. anguage requirements for Net work Services were introduced in Section L and a re expanded upon 4.3 here as TG Requirements for the Pre - defined WFS Conformance Class : TG Requirement 54 A network service [Download Service] metadata response shall cont ain a list of the natural languages supported by the service. This list shall contain one or more languages that are supported. A client may specify a specific language in a request. If the requested TG Requirement 55 language is contained in the list of supported language s, the natural language fields of the service response shall be in the requested language. It the requested language is not supported by the service, then this parameter shall be ignored. To meet these requirements using 19142 WFS it is necessary to exten d som e operations of the WFS as follows: 6.7.1 GetCapabilities - Operation (language requirements) GetCapabilities Request: - The HTTP/GET binding of the GetCapabilities - Operation is extended by an additional parameter that indicates the client‘s preferred language. TG Requirement 56 The n ame of this parameter shall be ―LANGUAGE‖. The parameter values are based on ISO 639 - 2/B alpha 3 codes as used in [ INS MDTG ].

70 INSPIRE Technical Guidance for INSPIRE Download Services 3.1 of - 2013 Page 70 - 89 08 09 Parameter Value support andatory Parameter M andatory M Name for a Client by the Service? Request? LANGUAGE Codelist (See I SO/TS 19139) based on Yes, it is mandatory No, it is 3 codes of - 2. alpha to be supported and . optional - ISO 639 shall be processed if - Use only three - letter codes from in ISO 639 the parameter is 2/B (bibliographic codes), present in a client‘s request with a official EU 4 The list of codes for the 2 supported language the languages of the and languages EFTA code. If the is: Countries parameter is absent bul Italian – ita Bulgarian – in a client‘s request or it requested an lav Latvian Czech – – cz e unsupported language the service – ger dan – Liechenstein Danish shall respo nse in the dut Lithuanian – lit Dutch – service default language. – eng Maltese – English mlt Polish – Norwegian – nor pol Portuguese – por Estonian – est Romanian Finnish rum – fin – - roh fre – French Romansh – ger slo German Slovak – g re – Slovenian – slv Greek Hungarian – spa – Spanish hun Irish – Swedish gle – swe – - Croatian ice hrv Icelandic list of codes is defined at The complete http://www.loc.gov/standards/iso639 - 2/ also Regional languages are included in this list. 20 Table : Language parameter Schema: [OCG - GetCapabilities - Request]&LANGUAGE= Example: http://inspire.network.service.example/service?SERVICE=[...]&VERSION=[...]&LANG UAGE=eng

71 INSPIRE Technical Guidance for INSPIRE Download Services 3.1 of - 2013 Page 71 - 89 09 08 - Response: GetCapabilities - Response If a client request specifies a supported language the following fields of the GetCapabilties are affected: Titles Abstracts TG Requirement 57 If a client request specifies an unsupported language, or the parameter is absent in t he request, the above fields [Title, Abstract] shall be provided in the service default language. This behaviour ensures backward s compatibility so that any existing clients may interact with the service using the default andard. OGC st es Extended Capabiliti all respond to GetCapabilites requests with To advertise the supported languages the service sh e nded Capabilities as follows : Ext Example 46: Extended Capabilities structure ... ... ... http://www.csw.de eng eng ... ... ...

72 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - - 2013 Page 72 of 89 08 indicate the response language used for the TG Requirement 58 The Extended Capabilities shall Response: Depending on the requested language the value of GetCapabilities - corresponds to the current the If a supported used was requested, language. language shall correspond to that requested language. If an unsupported language was requested or if no language was requested specific correspond shall the service default language to DefaultLanguage> . indicated This of supported languages shall consist of list 1. exact ly one element indicating the service default language, and 2. zero or more elements to all additional ted languages. indicate suppor list of supported languages is Regardless of the response language, the Response. invariant for each GetCapabilities - TG Requirement 60 The Extended Capabilities shall use the XML Schema as defined in the INSPIRE online schema repository. Examples: e supports French and English and the service default language is French: A servic Response to [OGC - Example 47: - Request]&LANGUAGE=eng GetCapabilities fre eng eng

73 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - - 2013 Page 73 of 89 08 - GetCapabilities - Example 48: - GetCapabilities - Request] or [OGC Response to [OGC Request]&LANGUAGE=fre > fre eng fre ... A service supports only German: Response to any GetCapabilities Request (only German supported) Example 49: - ... ger ger ... dls:ExtendedCap abilities >

74 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - - 2013 Page 74 of 89 08 s it is recommended to TG Recommendation 14 For further language support for other operation online - resources in each language specific replace the operation - - Response by a specific operation online - resource for that - GetCapabilities online - resources the service - language. To support the additional operation - points to distinguish for shall listen at the language specific operation end the requested languages. e W FS.getCapabilities () An example of this behaviour is given below, showing how to extend th operation to support multilingual error messages. The client sends the initial Request for Capabilities: 1. GetCapabilities - - [OCG Request] 2. The service responses with extended Capabilities including the supported Languages: Service res ponse including supported languages Example 50: dls:ExtendedCapabilities ... fre eng dut eng ... > dls:ExtendedCapabilities [...] Get xlink:type="simple" 75 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - - 2013 Page 75 of 89 08 Example 52: - GetCapabilities - Request]&LANGUAGE=ger Response to [OCG [...] 76 INSPIRE Technical Guidance for INSPIRE Download Services 3.1 - 08 2013 Page 76 of 89 09 - IETF RFC 5646 short IETF RFC 5 646 long ISO639/B alpha 3 ul b g bg - BG b c c s cs - CZ ze an d a d da - DK d n l nl - NL ut e ng e n en - GB e st e t et - EE in - f i fi f FI - re f r fr f CH, fr - FR g er d e de - AT, d e - CH, de - DE, de - LI g e l el - GR re hrv hr hr - HR h un h u hu - HU g le g a ga - IE ce s Is - IS i i CH, t it - ta it - IT i i av l v lv - LV l l l t lt - LT it lt m t m mt - MT n n o no - NO or p ol p l pl - PL p or p t pt - PT oh rm rm r - CH r r o ro - RO um s lo s k sk - SK s s l sl - SI lv s pa e s es - ES SE s s v sv - we Table 21 : Mapping between ISO 639/B alpha 3 and the two forms of IETF RFC 4646 su pported by OWS 1.1.0

77 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - - 2013 Page 77 of 89 08 and Filter Encoding 7 Web Feature Service implementation of Direct Access Download S ervice. : Direct WFS: 3 Implement Direct Access Download Service (―Parts B & C‖) TG Conformance Class . using ISO 19142 Web Feature Service and ISO 19143 Filter Encoding is inclusive of : This conformance class TG Requirement 61 to TG Requirement 68 Direct Access download services (that satisfy Parts B and C of the IR) should be implemented where cable. This may be done using ISO 19142 WFS [ ISO 19142 practi ] and ISO 19143 Filter Encoding ] as described here. INS NS In order to be fully conformant with [ ISO 19143 ], it is necessary to also [ 5 ) or WFS enSearch (Chapter provide an implementation satisfying Part A, either based on Atom/Op 6 ). (Chapter 7.1 Necessary elements from WFS - based Pre - defined dataset download service Direct access Download Services provide additional fun ctionality beyond what is provided by Pre - defined Download Services. defined dataset and Direct Access Download services Because both Pre - are both based on [ ISO 19142 ] there is an overlap of requirements for both types of solutions ensuring exist independent of each other. the ability to Implementations shall meet TG Requirement 48 ( c onformance to [ ISO 19142 TG Requirement 61 ] ̳HTTP GET‘ ) and TG Requirement 52 ( o ne conformance class point for end each INSPIRE dataset) . 7.2 Conformance to ISO 19142 „Basic WFS‟ Conformance Class In order to implement direct access download services using ISO 19142 WFS and ISO 19143 FE it is necessary to conform to the ̳Basic WFS‘ conformance classes as describe d in the 19142 standard ISO 19142 ]. [ Implementations shall conform to ISO 19142 Conformance Class ̳Basic WFS‘ TG Requirement 62 7.3 Conformance to ISO 19143 „Ad hoc Query ‟ Conformance Class Ad hoc query support shall be implemented to enable user defined requests for spatial o bjects in a - WFS. TG Requirement 63 A Direct Access Download Service shall conform to ISO 19143 ̳Ad hoc Query‘ Conformance Class.

78 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 89 09 - 2013 Page 78 of 08 - 7.4 Conformance to ISO 19143 „Resource Identification ‟ Conformance Class The referencing of resources by identifier shall be supported as described in ISO 19143 ̳Resource TG Requirement 64 A Direct Access Download Service shall conform to ISO 19143 Identification‘ Conformance Class. 7.5 ‟ Conformance to ISO 19143 „Minimum Standard Filter Conformance Class Querying with Comparison and logical operators shall be supported by the Direct Access Download Services as described in ISO 19143. TG Requirement 65 A Direct Access Download Service shall conform to ISO 19143 ̳Minimum Standard Filter‘ Conformance Class. Conformance to ISO 19143 „Minimum Spatial Filter‟ 7.6 Conformance Class the Download Service shall be supported by the Direct Access Download Services Spatial querying of as described in ISO 19143. A Direct Access Download Service shall conform to ISO 19143 ̳Minimum TG Requirement 66 Spatial Filter‘ Conformance Class. 7.7 Conformance to ISO 19143 „Minimum Temporal Fil ter‟ Conformance Class Temporal querying of the Download Service shall be supported by the Direct Access Download Services as described in ISO 19143. TG Requirement 67 A Direct Access Download Service shall conform to ISO 19143 ̳Minimum Temporal Filter‘ Conformance Class. 7.8 C onformance to ISO 19143 „ Minimum XPath ‟ Conformance Class Querying of the Download Service using XPath shall be supported by the Direct Access Download Services as described in ISO 19143. TG Requirement 68 A Direct Access Download Service shall conform to ISO 19143 ̳Minimum XPath‘ Conformance Class.

79 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - 2013 Page 79 08 of 89 - L anguage requirements for Direct Access Download Service s 7.9 The language requirements defined in [INS NS] for Direct Access Download Services are addressed - by WFS instances as described in the following sub sections. D escribeFeatur eType Operation (language requirements) 7.9.1 Object Type operation of This operation as specified by ISO 19142 implements the Describe Spatial [ INS NS ]. In the implementing rule, a language parameter is specified, but as a DescribeFeatureType operation a description of the spatial object types in schema language, a parameter related to a natural returns language is not relevant. 7.9.2 GetFeature Operation (language requirements) Object operation of [INS NS]. This operation as specified by ISO 19142 implements the Get Spatial In the implementing rule, a language parameter is specified, but INSPIRE application schemas are modelled in a way so that in cases where multiple languages are possible for a feature property, the values in all languages may be provided simulta neously (e.g. for geographical names). i .e., if multilingual data is provided by a download service, all languages are provided by the download service. As a result, this parameter is not applicable in practice. 7.10 WFS metadata for “hybrid implementations” I n case of a ―hybrid implementation‖ based on Atom and WFS for Parts B and C, in addition to the it is possible to also document the WFS service through metadata in a discovery Atom service, . In this case, the link between the Atom and WFS implement ations can be established through service the ̳coupled resource‘ metadata element , which points to the same data set . TG Recommendation 16 In addition, a textual reference to the Atom service implementing part A should be included in the ̳abstract‘ metadata element of the WFS.

80 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - 2013 Page 80 08 of 89 - Quali ty of Service 8 TG Conformance Class 4 Quality of Service : Meet Quality of Service requirements. : Since quality of service (QoS) depends on the specific testing procedure for a given service, this section describes and normalizes the testing procedure that i s to be applied for the assessment of QoS for a given INSPIRE download service. The monitoring parameter NSi4 in the Commission decision for monitoring and reporting measures the conformity of all network services with the implementing rules. The conformit y of a network service requires the compliance with the Quality of Service as defined in Annex I of the NS regulation (in particular NSi4,1 and NSi4,2 for the current monitoring period). General requirements 8.1 Two options exist for the measurements of Qualit y of Services: 1. Quality of Services requirements are measured at the service side exposed to the Internet. 2. Quality of Services requirements are measured from a central network node within the infrastructure. above was includ ed for practical reasons. If a Member S tate uses a central network node in Option 2 the testing infrastructure, it shall take into account the network transport time. For a detailed overview of the testing procedure when using a central node, see Figure 6. Based on the evaluation o f experiences this option may be revisited in the future . For feasibility reasons the testing procedure is based on the following simplifications: For the transport of a small size of data over the network, the network latency can be considered as a cons tant value and is denoted x. So each network transport (request and response) is considered to consume the duration of x/2. o In case of option 1, x shall be set to 0. o In case of option 2, a member state should initiate a comparison between sample measures from the central node to sample measures at the service side, to find a realistic value of x for the specific national setting. It is assumed that the network transport rate is not slower than the rate of the service response output stream to avoid any dat a jam at the production stream.

81 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 08 - 2013 Page 81 of 89 - Figure 9 : Detailed Sequence Diagram Download Service 8.2 Perfo rmance 8.2.1 Implementation requirements mandated by the Implementing Rule “For the Get Download Service Metadata operation, the response time fo r sending the initial response shall be maximum 10 seconds in normal situation. For the Get Spatial Data Set operation and for the Get Spatial Object operation, and for a query consisting exclusively of a bounding box, the response time for sending the ini tial response shall be maximum 30 seconds in normal situation then, and still in normal situation, the download service shall maintain a sustained response greater than 0,5 Megabytes per second or greater than 500 Spatial Objects per second. For the Descri be Spatial Data Set operation and for the Describe Spatial Object Type operation, the response time for sending the initial response shall be maximum 10 seconds in normal situation then, and still in normal situation, the download service shall maintain a sustained response greater than 0,5 Megabytes per second or greater than 500 descriptions of Spatial Objects per second. [...] The normal situation represents periods out of peak load. It is set at 90 % of the time.”

82 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 89 09 - 2013 Page 82 of 08 - 8.2.2 Normalized testing procedure Performance shall be measured consistently based on sample reference TG Requirement 69 requests to a given service. Minimum 10 reference requests per hour shall be issued to the service continuously during its lifetime during the period of . testing To respect long running operations, the number of requests may be reduced. In such cases, a new request can be issued maximum 6 minutes after the previous request has finished. Example 53: Performance tests for long - running operations If a previous Get Spatial Data Set operation requesting a 1 GB data set was issued at 8:00 and lasts until 8:30, the next reference request shall be issued at the latest at 8:36. NOTE: The result of performance measurements in a production system may be ambiguous due to t the same time and therefore it is recommended the amount of user load that the service processes a capacity tests to be processed during maintenance time frames only. TG Recommendation 17 The frequency of the performance tests is recommended to be monthly, e.g., during systems maintenance. TG Requirement 70 the Get Download Service Metadata, Performance shall be measured using Get Spatial Data Set, Get Spatial Object, Describe Spatial Data Set and Describe Spatial Object Type operations. TG Recommendation 18 The structure of the sample reference request packages is recommended to be composed of: 10% Get Download S ervice Metadata requests, 10% Describe Spatial Data Set or Describe Spatial Object Type and 80% Get Spatial Data Set or Get Spatial Object. At least 2% of the requests should be Get Spatial Data Set. NOTE: This composition is assumed to represent a ―norma l situation‖. TG Requirement 71 For Get Spatial Object operations, the sample reference request shall Contain a BBOX parameter . TG Requirement 72 If a download service serves more than one feature type, only one feature type shall be requested by a Get Spatial Object operation.

83 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - - 2013 Page 83 of 89 08 ad service serves more than one (pre TG Requirement 73 defined) spatial data set, only - If a downlo one spatial data set shall be requested by a Get Spatial Data Set operation. NOTE 1 It is assumed that the feature type or data set requested in a reference request results in a : represe ntative measure for a specific download service. For both the Get Spatial Data Set and Get Spatial Object operations, the default language : NOTE 2 and CRS shall be used. For Get Spatial Object operations, the sample refe TG Recommendation 19 rence request is recommended to r rn at least 1 MB. etu For the Get Spatial Object operation, if the BBOX parameter is random it is recommended that the last 100 responses to a reference request have an average of at least 1 MB. According to Figure 6, the performance requirements are describe d by the following formulas: Initial byte: t ≤  x/2 + d + x/2 = x + d first x –  t ≤ d first Last byte:  t x/2 + d + max (y/0.5, z/500) + x/2 = x + d + max( y/0.5 , z/500) ≤ last  t – x – ≤ max( y/0.5 , z/500) d last  where, t uration of time between initiating the request and receiving the initial byte is the measured d first of the response in seconds, t is the measured duration of time between initiating the request and receiving the last byte of last the response in seconds, d is the time required t o send the initial response at service side and shall be set to 10 seconds (operations: Get Download Service Metadata, Describe Spatial Data Set, Describe Spatial O bject Type) or 30 seconds (operations: Get Spatial Data Set, Get Spatial Object), is the time estimated for the network latency (x=0s if measured at the service side). x is the size of data in MB, y is the size of data in count of objects or object descriptions, z TG Requirement 74 Evaluation and assessment criteria: The ―response time for sending the initial re sponse‖ is t – x and shall be maximum d (10 seconds or 30 seconds depending on operation). first The throughput of the ―maintained sustained response‖ is

84 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - - 2013 Page 84 of 89 08 and shall be greater than 0.5 MB/s or and shall be greater than 500 spatial objects / descripti ons per second. situation, which shall be identified by the 90% best performing sample reference All in normal requests. Get Spatial Data Set operation Example 54: = 5s, the duration x from issuing the request at client side till the first With a network latency set to t first t byte returned to the client side shall be ≤ 35 seconds and the duration t from issuing a request at last first the client side till the complete download (last byte returned) to the client side depends on the size of data set and shall be according to below : one of the tables size of data Maximum duration Maximum du ration size of data set set till complete download till complete download finished finished 100 KB 35 s 100 objects 35 s 37 s 1,000 objects 37 s 1 MB 10 MB 55 s 10,000 objects 55 s 4 min 100,000 objects 4 min 100 MB 000,000 objects 34 min 1, 1 GB 34 min Capacity 8.3 8.3.1 Implementation requirements mandated by the Implementing Rule “The minimum number of simultaneous requests to a download service to be served in accordance with the quality of service performance criteria shall be 10 reque sts per second. The number of requests processed in parallel may be limited to 50.”

85 INSPIRE Technical Guidance for INSPIRE Download Services 3.1 - - 2013 Page 85 09 89 08 of 8.3.2 Normalized testing procedure TG Requirement 75 Capacity shall be measured consistently based on sample reference request packages to a given service. at the rate of 10 new requests per Requests shall be made to the service second, using different types of requests according to the profile of the sample reference request packages. This rate shall be sustained throughout a measurement timeframe of 1 minute. In order to provide consistent and comparable measures, the capacity test shall restrict the number of requests being processed at any one time to a maximum of 50. A measurement shall take place at least once before launching the service in a production environment and monitored at regular intervals thereof to ensure that the compliance with the capacity requirement is still ensured. NOTE : The result of capacity measurements in a production system may be ambiguous due to the amount of user load that the service processes at the same time an d therefore it is recommended capacity tests to be processed durin g maintenance time frames only. The frequency of the capacity is recommended to be monthly, e.g., during TG Recommendation 20 systems maintenance. mended to TG Recommendation 21 The structure of the sample reference request packages is recom 10% Get Download Service Metadata requests, 10% be composed of Describe Spatial Data Set or Describe Spatial Object Type and 80% Get Spatial Data Set or Get Spatial Object. At least 2% of the requests should be Get Spatial Data Set. : This co mposition is assumed to represent a ―normal situation‖. NOTE The measured capacity shall fulfil the requirements of the regulation (both TG Requirement 76 capacity and performance) for all operations that are provided by the service. 8.4 Availability 8.4.1 dated by the Implementing Rule Implementation requirements man “The probability of a Network Service to be available shall be 99% of the time.” 8.4.2 Normalized testing procedure TG Requirement 77 Availability shall be measured consistently based on sample reference requests to a given service. Minimum 10 refe rence requests per hour shall be issued to the service continuously during its lifetime. To respect long running operations, the number of requests may be reduced. In such cases, a new request can be issued maximum 6 minutes after the previous request has finished.

86 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 - 08 - 2013 Page 86 of 89 Availability tests for long - running operations Example 55: If a previous Get Spatial Data Set operation requesting a 1 GB data set was issued at 8:00 and lasts until 8:30, the next reference request shall be issued at the latest at 8:36. TG Recommendation 22 The sample request issued to the service to measure performance can be used to measure availability as well, thus also fulfilling the same evaluation and assessment criteria. TG Requirement 78 The availability shall be based on a time frame of one year meaning a maximum unplanned downtime of 3.63 days per year. Periods of planned downtime e.g. because of system maintenance, shall not be included in the measure. Downtime is considered planned when notified to the community users or well in advance (minimum 1 week), e.g. via notifications to registered on portals. NOTE It is assumed that the availability is calculated in the following way: 100% ↔ 365 x 24 - (planned downtime) 99% ↔ [365 x 24 (planned downtime)] * 0.99 - etc. TG Recommendation 23 Planned downtime is recommended to be less than 10 hours per month (i.e ., less than 120 hours per year).

87 INSPIRE INSPIRE Download Services 3.1 Technical Guidance for 09 08 - 2013 Page 87 of 89 - Annex A script : Example OpenSearch The following code shows a sample server side script to implement the search engine needed for the OpenSearch implementation. This is a simple example implementation in a particular lang uage (PHP), however any programming language may be used for the OpenSearch implementation. This example is purely informative and does not constitute a normative part of this Technical Guidance. Sample PHP script for the search engine $value) { //echo("$name: $value \ n"); if ($name=="Accept" && $value==" application/x - filegdb "){ $returnFile = true; } } echo ("returnFile: $returnFile"); $q= $_GET['q']; $uriCod e = $_GET[' spatial_dataset_identifier_code ']; if (!$uriCode) { if (!$q) { header("Location: democcmdownloadservice.atom.en.xml"); exit; } $uriCode = $q; } $uriNamespace= $_GET[' spatial_dataset_identifier_nam espace ']; $crs= $_GET['crs']; $language= $_GET['language']; if (!$language || $language == "*"){ $language = "en"; } if ($language != 'en' && $language != 'it'){ die( "Only en and it languages are supported" ); } if ($ur iCode == "ccm2.1_2000"){ if ($returnFile){ header("Location: files/CCM21_WGS84_window2000.zip"); } else{

88 INSPIRE Technical Guidance for INSPIRE Download Services 3.1 - - 2013 Page 88 09 of 89 08 header("Location: subfeed2000.atom.en.xml"); } exit; } if ($uriCode == "ccm2.1_2001"){ if ($retur nFile){ header("Location: files/CCM21_WGS84_window2001.zip"); } else{ header("Location: subfeed2001.atom.en.xml"); } exit; } if ($uriCode == "ccm2.1_2002"){ if ($returnFile){ header("Location: files/ CCM21_WGS84_window2002.zip"); } else{ header("Location: subfeed2002.atom.en.xml"); } exit; } if ($uriCode == "ccm2.1_2003"){ if ($returnFile){ header("Location: files/CCM21_WGS84_window2003.zip"); } else{ header("Location: subfeed2003.atom.en.xml"); } exit; } echo 'Not found'; ?>

89 INSPIRE Technical Guidance for INSPIRE Download Services 3.1 09 - 08 - 2013 Page 89 of 89 Annex B: UML Atom/OpenSearch Deployment Diagram

Related documents

CityNT2019TentRoll 1

CityNT2019TentRoll 1

STATE OF NEW YORK 2 0 1 9 T E N T A T I V E A S S E S S M E N T R O L L PAGE 1 VALUATION DATE-JUL 01, 2018 COUNTY - Niagara T A X A B L E SECTION OF THE ROLL - 1 CITY - North Tonawanda TAX MAP NUMBER ...

More info »
G:\COMP\PHSA\PHSA.bel

G:\COMP\PHSA\PHSA.bel

G:\COMP\PHSA\PHSA-MERGED.XML PUBLIC HEALTH SERVICE ACT [As Amended Through P.L. 115–408, Enacted December 31, 2018] References in brackets ¿ ø¿ ø are to title 42, United States Code TITLE I—SHORT TITL...

More info »
RIE Tenant List By Docket Number

RIE Tenant List By Docket Number

SCRIE TENANTS LIST ~ By Docket Number ~ Borough of Bronx SCRIE in the last year; it includes tenants that have a lease expiration date equal or who have received • This report displays information on ...

More info »
Programming Guide for ZPL II, ZBI 2, Set Get Do, Mirror, WML (en)

Programming Guide for ZPL II, ZBI 2, Set Get Do, Mirror, WML (en)

Programming Guide ZPL II ZBI 2 Set-Get-Do Mirror WML

More info »
doj final opinion

doj final opinion

UNITED STAT ES DIS TRICT COURT IC F OR THE D ISTR T OF CO LU M BIA UNITED STAT F AMERICA, : ES O : : la in t if f, P 99 No. on cti l A vi Ci : 96 (GK) -24 : and : TOBACCO-F UND, : REE KIDS ACTION F : ...

More info »
MDS 3.0 RAI Manual v1.16 October 2018

MDS 3.0 RAI Manual v1.16 October 2018

Centers for Medicare & Medicaid Services Long-Term Care Facility Resident Assessment Instrument 3.0 User’s Manual Version 1.16 October 2018

More info »
Numerical Recipes

Numerical Recipes

Sample page from NUMERICAL RECIPES IN C: THE ART OF SCIENTIFIC COMPUTING (ISBN 0-521-43108-5) Permission is granted for internet users to make one paper copy for their own personal use. Further reprod...

More info »
HANDBOOK of METAL ETCHANTS

HANDBOOK of METAL ETCHANTS

HANDBOOK of METAL ETCHANTS Editors Perrin Walker William H. Tarn CRC Press Boca Raton Boston London New York Washington, D.C. © 1991 by CRC Press LLC

More info »
CalCOFI Atlas 33

CalCOFI Atlas 33

THE EARLY STAGES IN OF THE FISHES CALIFORNIA CURRENT REGION CALIFORNIA FISHERIES COOPERATIVE OCEANIC INVESTIGATIONS ATLAS NO. 33 BY THE SPONSORED STATES OF COMMERCE DEPARTMENT UNITED OCEANIC AND ATMOS...

More info »
Microsoft Word   A) Division 245.docx

Microsoft Word A) Division 245.docx

tables Attachment Division 245, including A: Nov. 15-16, 2018, EQC meeting 1 of 121 Page Division 245 CLEANER AIR OREGON 340-245-0005 Purpose and Overview (1) This statement of purpose and overview is...

More info »
Department of Defense   Law of War Manual (June 2015)

Department of Defense Law of War Manual (June 2015)

D E A R T M E N T O F D E F E N S E P N A L O F W A R M A W U A L J U N E 2 0 1 5 O F F I C E O F G E N ER A L C O U N S E L D P A R T M E N T E O F D E F E N S E

More info »
vol9 organic ligands

vol9 organic ligands

C HERMODYNAMICS HEMICAL T OMPOUNDS AND C OMPLEXES OF OF C U, Np, Pu, Am, Tc, Se, Ni and Zr O ELECTED WITH RGANIC L IGANDS S Wolfgang Hummel (Chairman) Laboratory for Waste Management Paul Scherrer Ins...

More info »
LawReferenceBook2018

LawReferenceBook2018

California Contractors License Law & Reference Book 2018 Edition With Rules and Regulations Contractors State License Board State of California Edmund G. Brown, Jr., Governor

More info »
NB18

NB18

Table of Contents National Board Pressure Relief Device Certificati ons NB-18 FOREWARD... 1 NATIONAL BOARD PRESSURE RELIEF DEVICE CERTIFICATION... 2 DETERMINATION OF CERTIFIED RELIEVING CAPACITIES... ...

More info »
June2018CUR

June2018CUR

CHANCELLOR'S UNIVERSITY REPORT JUNE 25 2018

More info »
oldnew 11.dvi

oldnew 11.dvi

C ́edric Villani O ptimal transport, old and new June 13, 2008 Springer Berlin Heidelberg NewYork Hong Kong London Milan Paris Tokyo

More info »
MCO 1200.17E MILITARY OCCUPATIONAL SPECIALTIES MANUAL (SHORT TITLE: MOS MANUAL)

MCO 1200.17E MILITARY OCCUPATIONAL SPECIALTIES MANUAL (SHORT TITLE: MOS MANUAL)

DEPAR T MENT THE NAVY OF ADQ UARTE UNI T ED ST ATE S MAR INE CORPS HE RS RINE COR N PS PENT 3000 MA AGO 20350-3000 NGTON, HI D.C. W AS 7E 00 .1 12 MCO 465 c AUG 0 8 013 2 ORDER 1200.17E MARINE CORPS C...

More info »
An Introduction to Computer Networks

An Introduction to Computer Networks

An Introduction to Computer Networks Release 1.9.18 Peter L Dordal Mar 31, 2019

More info »
CRPT 116hrpt9 u2

CRPT 116hrpt9 u2

U:\2019CONF\HJRes31Front.xml APPRO. SEN. [COMMITTEE PRINT] REPORT { } CONGRESS 116TH 1st HOUSE OF REPRESENTATIVES Session 116- FURTHER APPROPRIATIONS FOR MAKING CONTINUING OF HOMELAND SECURITY FOR THE...

More info »