Habitats d4.3.2 networking services and service toolkit final

2,023 views

Published on

This deliverable presents the final status of the HABITATS Networking Services and service toolkits. Networking services are series of specific networking service applets deployed and tested for data sharing within the project. This deliverable also presents the background of invoking services and their relevance to the HABITATS project and examines the basic networking architecture and specific tools that are considered. The focus of this final report is not only on the application of these aspects within the Reference Laboratory but also includes the invoking of services at the level of the different pilots. The rich prototype set as implemented on the HABITATS Reference Laboratory geoportal platform and its relationship to the pilot architecture are also described.

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,023
On SlideShare
0
From Embeds
0
Number of Embeds
441
Actions
Shares
0
Downloads
20
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Habitats d4.3.2 networking services and service toolkit final

  1. 1. European Commission Information Society and Media DELIVERABLE Project Acronym: HABITATS Grant Agreement number: 3-250455 Project Title: Social Validation of INSPIRE Annex III Data Structures in EU HABITATS D4.3.2 HABITATS networking services and service toolkitDocument identifier: D4.3.2Date: 07 March 2013Nature: PDissemination level: PuWP Lead Partner: HSRSRevision V1 Project co-funded by the European Commission within the ICT Policy Support Programme Dissemination Level PU Public X RE Restricted to a group specified by the consortium (including the Commission Services) CO Confidential, only for members of the consortium (including the Commission Services) This project is partially funded under the ICT Policy Support Programme as part of the Competitiveness and Innovation Framework Programme by the European Commission http://ec.europa.eu/ict_psp This document reflects only the authors views and the European Community is not liable for any use that might be made of the information contained herein. © HABITATS Consortium, 2012
  2. 2. European CommissionInformation Society and MediaAbstract: This deliverable presents the final status of the HABITATS Networking Servicesand service toolkits. Networking services are series of specific networking service appletsdeployed and tested for data sharing within the project. This deliverable also presents thebackground of invoking services and their relevance to the HABITATS project and examinesthe basic networking architecture and specific tools that are considered. The focus of thisfinal report is not only on the application of these aspects within the Reference Laboratorybut also includes the invoking of services at the level of the different pilots. The richprototype set as implemented on the HABITATS Reference Laboratory geoportal platformand its relationship to the pilot architecture are also described.Key Words: HABITATS, networking services, service toolkits, invoking prototype applet,data sharing, Reference Laboratory, social media, social networkingAuthors:Karel Charvat (HSRS)Jachym Cepicky (HSRS)Premysl Vohnout (HSRS)Stepan Kafka (HSRS)Michal Sredl (HSRS)Tomas Mildorf (HSRS)John J O’Flaherty (MAC)Joe Cantwell (MAC)Raitis Berzins (IMCS)Peteris Bruns (IMCS)G. .Osorio (Tragsa)Jan Bojko (FMI)A. Sciana (Madonia) Statement of originality: This deliverable contains original unpublished work except where clearly indicated otherwise. Acknowledgement of previously published material and of the work of others has been made through appropriate citation, quotation or both.This project is partially funded under the ICT Policy Support Programme as part of the Competitiveness andInnovation Framework Programme by the European Commission http://ec.europa.eu/ict_pspThis document reflects only the authors views and the European Community is not liable for any use that mightbe made of the information contained herein. © HABITATS Consortium, 2012
  3. 3. Revision HistoryRevision Date Author Organization DescriptionV1.0 08/10/2012 K. Charvat HSRS First draftV0.3 06/01/2013 K. Charvat HSRS Integration of contributionsV0.2 07/01/2013 J. O`Flaherty MAC Update of documentV0.1 01/03/2013 G. .Osorio Tragsa Update of documentV2 03/03/2012 K.Charvat HSRS Finalisation of documentDocument Change RecordIssue Date Author Item Reason for Change
  4. 4. Project Officer: Krister Olson European Commission DG Information Society and Media Project Officer Address: DG INFSO – E06 Office: EUFO – 01/177 L – 2920 LUXEMBOURG Phone: +(352) 43 0134332 Fax: +(352) E-mail: Krister.olson@ec.europa.euProject Manager: Mariano Navarro de la Cruz Address: C/ Julian Camarillo, 6b, 28037, Madrid, Spain Phone: +34 91 322 65 21 Fax: +34 91 322 63 23 E-mail: mnc@tragsa.es
  5. 5. Date: 7-Mar-13 HABITATS Networking Services and Service ToolkitsDoc. Identifier: D4.3.2Project: Social Validation of INSPIRE Annex III Data Structures in EU Habituas TABLE OF CONTENTS1 FIGURES........................................................................................................................72 TABLES ........................................................................................................................103 INTRODUCTION .......................................................................................................... 11 Terms ................................................................................................................................ 11 Abbreviations ....................................................................................................................124 INSPIRE, NETWORKING ARCHITECTURE AND HABITATS.......................................145 INVOKING SERVICES .................................................................................................15 INVOKING service requirements and recommendations...................................................166 PROBLEMS OF POLICY DRIVEN SDI .........................................................................18 Neogeography ..................................................................................................................197 HABITATS NETWORKING SERVICES ........................................................................20 Reference Lab ..................................................................................................................20 Uniform Resource Management (URM) Concept ..............................................................23 Use of the URM in the HABITATS RL ........................................................................... 268 RL NETWORKING SERVICES AND INVOKING TOOLS..............................................28 Authorization and Authentication tools ..............................................................................30 Liferay based geoportal solution .......................................................................................31 Customisation of the portal content.................................................................................. 33 WordPress based GeoSocial Network ..............................................................................36 Uniform Resource Management (URM) ............................................................................39 MICKA ............................................................................................................................. 39 Geoserver.......................................................................................................................... 43 Data management ......................................................................................................... 43 Data visualisation ......................................................................................................... 44 Map compositions ........................................................................................................ 45 Data publication ........................................................................................................... 45 Styler............................................................................................................................. 46 Vector data editing ........................................................................................................ 47 Layer hierarchy and thematic maps.............................................................................. 49 Metadata Extractor ........................................................................................................... 51 Networking Services and Invoking ....................................................................................52 Catalogue Services ........................................................................................................... 52 Invoking of discovery services ..................................................................................... 55 Experiences with sharing of metadata in INSPIRE and GEOSS and Super Catalogue implementation ............................................................................................................. 56 Catalogues interoperabity problems ................................................................................................................. 56 Central catalogue implementation .................................................................................................................... 57 Testing Results ................................................................................................................................................. 61 Practical Results ............................................................................................................................................... 61 Plans for future ................................................................................................................................................. 63 View Services ...................................................................................................................63 Map ............................................................................................................................... 65 Layer Switcher ............................................................................................................. 66 Logical structure............................................................................................................................................... 6707 March 2013 1 of 44
  6. 6. Date: 7-Mar-13 HABITATS Networking Services and Service ToolkitsDoc. Identifier: D4.3.2Project: Social Validation of INSPIRE Annex III Data Structures in EU Habituas OWS ............................................................................................................................. 67 Printing with HSLayers ................................................................................................ 68 Web Map Context ........................................................................................................ 70 Permanent link .............................................................................................................. 73 Embedded ..................................................................................................................... 73 Querying displayed layers ............................................................................................ 74 User graphics and measuring ....................................................................................... 75 OGC Web Processing Service client ............................................................................ 76 Server-side scripts ........................................................................................................ 77 HSProxy ........................................................................................................................................................... 78 StatusManager server script ......................................................................................... 78 Proxy4OWS ..................................................................................................................................................... 78 Invoking with HSlayers ................................................................................................ 79 Invoking of view (WMS) services.................................................................................................................... 79 WMS coordinate transformation ...................................................................................................................... 80 Invoking of Map Compositions – Web Map Context ....................................................................................... 82 Invoking of WFS and WCS.............................................................................................................................. 83 Invocation ..................................................................................................................... 86 Filter Encoding Filtering WFS Layers ............................................................................................................. 86 FE Examples: ............................................................................................................... 86 Filter Encoding and WFS ................................................................................................................................. 87 WPS invoking .................................................................................................................................................. 92 HSLayers SOS client ........................................................................................................................................ 94 HSLayers Embed component ........................................................................................................................... 95 Mobile solutions for RL ................................................................................................... 97 Using KML as common format .................................................................................. 101 Field editing ................................................................................................................ 1029 PROCESSING WORKFLOW MANAGEMENT ........................................................... 104 Orchestration environment .............................................................................................. 104 Workflow Management System ....................................................................................... 104 Business Process Execution Language .......................................................................... 104 Engines and work-flow managers .................................................................................. 105 Apache ODE............................................................................................................... 105 Orchestra .................................................................................................................... 105 Taverna Server ............................................................................................................ 106 Workflow designers .................................................................................................... 107 52°North WPS Workflow Modeller and Orchestration API ...................................... 107 ECLIPSE BPEL ......................................................................................................... 108 HUMBOLDT Workflow Design and Construction Service....................................... 110 Taverna Workbench .....................................................................................................11110 HABITATS PILOTS’ NETWORK SERVICES............................................................... 113 PILOTS DESCRIPTIONS ............................................................................................... 115 Wild Salmon Monitoring ................................................................................................ 115 La Palma Protected Marine Reserve .............................................................................. 119 MadoniE Hiking Trip Planner ........................................................................................ 122 Madonia Sheep and Goat Herding Management ........................................................... 123 Augmented Reality Natural Reserve .............................................................................. 125 Economical activity at marine coastal benthic habitats.................................................. 130 National Forest Programme............................................................................................ 13311 INTEROPERABILITY AND INVOCATION TESTS ...................................................... 13607 March 2013 2 of 44
  7. 7. Date: 7-Mar-13 HABITATS Networking Services and Service ToolkitsDoc. Identifier: D4.3.2Project: Social Validation of INSPIRE Annex III Data Structures in EU Habituas Interoperability and Enabling Services ............................................................................ 136 3.2 HABITATS “Quick Prototyping” Service Applets .................................................... 137 The interoperability tests IMCS RL .................................................................................. 138 IRISH test with RL ......................................................................................................... 138 La Palma Reserve Marine Pilot test with RL ................................................................. 139 Augmented Reality Nature Reserve Pilot test with RL.................................................. 140 FMI Liberec region test of Reference Laboratory......................................................... 141 Experimentation with Open Linked Data ....................................................................... 14312 CONCLUSIONS AND RECOMMENDATIONS ............................................................ 14513 REFERENCES ........................................................................................................... 147Figure 1 INSPIRE Networking Architecture............................................................................ 16Figure 2 Reverse “pyramid” effect (Bregt 2012). .................................................................... 18Figure 3 Spider Web Paradigm ................................................................................................. 19Figure 4 The changing sources of spatial data (Harris & Lafone). .......................................... 19Figure 5 Habitats Networking Architecture ............................................................................. 21Figure 6 Habitats RL and pilots................................................................................................ 21Figure 7 Habitats RL ................................................................................................................ 22Figure 8 URM concept ............................................................................................................. 24Figure 9 URM principles .......................................................................................................... 25Figure 10 URM Spidernet ........................................................................................................ 26Figure 11 Portal login ............................................................................................................... 30Figure 12 Portal registration ..................................................................................................... 31Figure 13 Liferay Interface....................................................................................................... 32Figure 14 Customisation of RL I .............................................................................................. 33Figure 15 Customisation of RL II ............................................................................................ 34Figure 16 Customisation of RL III ........................................................................................... 35Figure 17 Customisation of RL IV ........................................................................................... 36Figure 18 WordPress Based RL................................................................................................ 37Figure 19 WordPress Article Editing ........................................................................................ 38Figure 20 Micka Metadata Editing ........................................................................................... 40Figure 21 Micka Metadata Validation ...................................................................................... 40Figure 22 Micka Metadata importing ....................................................................................... 41Figure 23 Micka Metadata importing XML ............................................................................. 41Figure 24 Micka metadata importing WMC ............................................................................ 42Figure 25 Editing of Imported metadata .................................................................................. 42Figure 26 Validation result ....................................................................................................... 43Figure 27 Metadata records management ................................................................................ 43Figure 28 Slyling ...................................................................................................................... 47Figure 29 Editing of vector data ............................................................................................... 48Figure 30 Data flow between HS Layers and Geoserver. ........................................................ 49Figure 31 User (or administrator) can create thematic maps (map compositions) usingstandard OGC OWS client, part of the mapping application. .................................................. 50Figure 32 Ordering layers into groups, without touching the physical structure of displayedmaps.......................................................................................................................................... 50Figure 33 Changing the physical structure of displayed layers. In the "Physical view" tab,layers cannot be structured into groups, but their position in the layer tree (using drag&drop)can be changed. ........................................................................................................................ 51Figure 34 Metadata extractor ................................................................................................... 5207 March 2013 3 of 44
  8. 8. Date: 7-Mar-13 HABITATS Networking Services and Service ToolkitsDoc. Identifier: D4.3.2Project: Social Validation of INSPIRE Annex III Data Structures in EU HabituasFigure 35 Catalogue Search ..................................................................................................... 53Figure 36 Advanced search ...................................................................................................... 53Figure 37 Metadata Detail ........................................................................................................ 54Figure 38 Metadata Spatial Exten ............................................................................................ 54Figure 39 Catalogue Client architecture ................................................................................... 55Figure 40 Catalogue Import ..................................................................................................... 56Figure 41 Catalogue import ...................................................................................................... 56Figure 42 SuperCat harvesting ................................................................................................. 58Figure 43 Micka harvesting configuration ............................................................................... 59Figure 44 RSS channel – harvesting results ............................................................................. 60Figure 45 Heartbeat protocol .................................................................................................... 60Figure 46 Portal – metadata catalogue client ........................................................................... 62Figure 47 Mobile catalogue client ............................................................................................ 62Figure 48 Mobile catalogue client connected to central catalogue and map viewer showingfound WMS .............................................................................................................................. 63Figure 49 Illustration of relation between ExtJS and OpenLayers libraries inside of HSLayers................................................................................................................................................... 63Figure 50 HSlayers Map Portal ................................................................................................ 64Figure 51 Map Window ............................................................................................................ 65Figure 52 Physical and Logical Structure ................................................................................ 66Figure 53 HSLayers.OWS - Open Web Services client ........................................................... 68Figure 54 Printing with HSLayers............................................................................................ 69Figure 55 Printing Result ......................................................................................................... 70Figure 56 Web Map Content Editing........................................................................................ 72Figure 57 Permanent Link ........................................................................................................ 73Figure 58 Embedded ............................................................................................................... 74Figure 59 Result of the point query on one vector layer. ......................................................... 75Figure 60 User graphic ............................................................................................................. 75Figure 61 OGC WPS client ...................................................................................................... 76Figure 62 Image classifcation................................................................................................... 77Figure 63 Buffering .................................................................................................................. 77Figure 64 Sequence diagram of proxy4ows shows the negotiation between the client,proxy4ows middleware and the target server. .......................................................................... 79Figure 65 Invoking from catalogue .......................................................................................... 79Figure 66 WMS invoking ......................................................................................................... 80Figure 67 WMS Sequence diagram. ......................................................................................... 81Figure 68 WMS transformation result - left map coordinate system, right - transformed resultfrom EPSG:4326 source. .......................................................................................................... 81Figure 69 Composition Saving ................................................................................................. 82Figure 70 Open Composition from local disk .......................................................................... 83Figure 71 WFS invoking scheme ............................................................................................. 84Figure 72 Get Map Scheme ...................................................................................................... 85Figure 73 OWS Dispatch ......................................................................................................... 86Figure 74 Geoportal, Filter Encoding....................................................................................... 90Figure 75 Filter Encoding......................................................................................................... 91Figure 76 Filtering of WFS ...................................................................................................... 91Figure 77 WPS Invoking .......................................................................................................... 92Figure 78 Proxy ........................................................................................................................ 93Figure 79 HSLayers SOS client ............................................................................................... 9507 March 2013 4 of 44
  9. 9. Date: 7-Mar-13 HABITATS Networking Services and Service ToolkitsDoc. Identifier: D4.3.2Project: Social Validation of INSPIRE Annex III Data Structures in EU HabituasFigure 80 HSLayers Embeded ................................................................................................. 96Figure 81 Rendering Map......................................................................................................... 97Figure 82 Locus map app, Catalogue client ............................................................................. 99Figure 83 WMS displayed in Locus app, map legend............................................................ 100Figure 84 Parcel Info app ....................................................................................................... 100Figure 85 KML metadata in the catalogue client ................................................................... 101Figure 86 Displaying KML in Google Maps and Locus ........................................................ 102Figure 87 Simple mobile editing application ......................................................................... 103Figure 88 Filed editing results displayed online in Google Earth as KML ............................ 103Figure 89 Apache ODE .......................................................................................................... 105Figure 90 Orchestra ................................................................................................................ 106Figure 91 Taverna ................................................................................................................... 107Figure 92 Workflow modeller ................................................................................................ 108Figure 93 Eclipse BPEL ......................................................................................................... 109Figure 94 Humboldt Workflow Design ...................................................................................111Figure 95 Taverna Workbench................................................................................................ 112Figure 96 Aquatic Invasive Species ....................................................................................... 116Figure 97 Aquatic Invasive Species App ............................................................................... 116Figure 98 AIS classification ................................................................................................... 117Figure 99 Integration with RL ................................................................................................ 117Figure 100 AIS sighting ......................................................................................................... 118Figure 101 Ireland Pilot architecture ...................................................................................... 118Figure 102 Publishing ............................................................................................................ 119Figure 103 Sea Monitoring..................................................................................................... 120Figure 104 La Palma Pilot Scheme ........................................................................................ 120Figure 105 La Palma portal .................................................................................................... 121Figure 106 La Palma metadata ............................................................................................... 122Figure 107 Madonia Architecture........................................................................................... 123Figure 108 Madonia implementation ..................................................................................... 124Figure 109 Augment Reality Technology............................................................................... 125Figure 110 Android App ......................................................................................................... 126Figure 111 Augment Reality Scheme ..................................................................................... 126Figure 112 Augment Reality Implementation ........................................................................ 127Figure 113 Pilot portal ............................................................................................................ 128Figure 114 Pilot Metadata ...................................................................................................... 128Figure 115 Coastal HABITATS pilot is design ...................................................................... 130Figure 116 Latvian Pilot Implementation............................................................................... 131Figure 117 Latvian portal ....................................................................................................... 132Figure 118 Processing services .............................................................................................. 132Figure 119 FMI pilot scheme ................................................................................................. 134Figure 120 OPRL Data ........................................................................................................... 135Figure 121 Harmonised data publishing on RL ..................................................................... 138Figure 122 Invasive species on RL ........................................................................................ 139Figure 123 Invasive species on RL ........................................................................................ 139Figure 124 The screen capture shows the data as it appears on the HABITATS RL Geoportal:http://www.habitats.cz/view?permalink=44b2ad495fd262b365f8fdb5310a1458 ................. 140Figure 125 The screen capture shows the data as it appears on the HABITATS RL Geoportal:http://www.habitats.cz/view?permalink=8555142bd2d6f5462d4f766015bc4776 ................ 141Figure 126 Liberec Basic portal functionality ........................................................................ 14207 March 2013 5 of 44
  10. 10. Date: 7-Mar-13 HABITATS Networking Services and Service ToolkitsDoc. Identifier: D4.3.2Project: Social Validation of INSPIRE Annex III Data Structures in EU HabituasFigure 127 Liberec Thematic Maps using standardised data from FMI ................................ 142Figure 128 Flood portal as part of Geoportal ......................................................................... 143Figure 129 Education and awareness ..................................................................................... 143Figure 130 Integration of Open Linked data from skiing resorts ........................................... 144107 March 2013 6 of 44
  11. 11. Date: 7-Mar-13 HABITATS Networking Services and Service ToolkitsDoc. Identifier: D4.3.2Project: Social Validation of INSPIRE Annex III Data Structures in EU Habituas FiguresFigure 1 INSPIRE Networking Architecture............................................................................ 16Figure 2 Reverse “pyramid” effect (Bregt 2012). .................................................................... 18Figure 3 Spider Web Paradigm ................................................................................................. 19Figure 4 The changing sources of spatial data (Harris & Lafone). .......................................... 19Figure 5 Habitats Networking Architecture ............................................................................. 21Figure 6 Habitats RL and pilots................................................................................................ 21Figure 7 Habitats RL ................................................................................................................ 22Figure 8 URM concept ............................................................................................................. 24Figure 9 URM principles .......................................................................................................... 25Figure 10 URM Spidernet ........................................................................................................ 26Figure 11 Portal login ............................................................................................................... 30Figure 12 Portal registration ..................................................................................................... 31Figure 13 Liferay Interface....................................................................................................... 32Figure 14 Customisation of RL I .............................................................................................. 33Figure 15 Customisation of RL II ............................................................................................ 34Figure 16 Customisation of RL III ........................................................................................... 35Figure 17 Customisation of RL IV ........................................................................................... 36Figure 18 WordPress Based RL................................................................................................ 37Figure 19 WordPress Article Editing ........................................................................................ 38Figure 20 Micka Metadata Editing ........................................................................................... 40Figure 21 Micka Metadata Validation ...................................................................................... 40Figure 22 Micka Metadata importing ....................................................................................... 41Figure 23 Micka Metadata importing XML ............................................................................. 41Figure 24 Micka metadata importing WMC ............................................................................ 42Figure 25 Editing of Imported metadata .................................................................................. 42Figure 26 Validation result ....................................................................................................... 43Figure 27 Metadata records management ................................................................................ 43Figure 28 Slyling ...................................................................................................................... 47Figure 29 Editing of vector data ............................................................................................... 48Figure 30 Data flow between HS Layers and Geoserver. ........................................................ 49Figure 31 User (or administrator) can create thematic maps (map compositions) usingstandard OGC OWS client, part of the mapping application. .................................................. 50Figure 32 Ordering layers into groups, without touching the physical structure of displayedmaps.......................................................................................................................................... 50Figure 33 Changing the physical structure of displayed layers. In the "Physical view" tab,layers cannot be structured into groups, but their position in the layer tree (using drag&drop)can be changed. ........................................................................................................................ 51Figure 34 Metadata extractor ................................................................................................... 52Figure 35 Catalogue Search ..................................................................................................... 53Figure 36 Advanced search ...................................................................................................... 53Figure 37 Metadata Detail ........................................................................................................ 54Figure 38 Metadata Spatial Exten ............................................................................................ 54Figure 39 Catalogue Client architecture ................................................................................... 55Figure 40 Catalogue Import ..................................................................................................... 56Figure 41 Catalogue import ...................................................................................................... 56Figure 42 SuperCat harvesting ................................................................................................. 5807 March 2013 7 of 44
  12. 12. Date: 7-Mar-13 HABITATS Networking Services and Service ToolkitsDoc. Identifier: D4.3.2Project: Social Validation of INSPIRE Annex III Data Structures in EU HabituasFigure 43 Micka harvesting configuration ............................................................................... 59Figure 44 RSS channel – harvesting results ............................................................................. 60Figure 45 Heartbeat protocol .................................................................................................... 60Figure 46 Portal – metadata catalogue client ........................................................................... 62Figure 47 Mobile catalogue client ............................................................................................ 62Figure 48 Mobile catalogue client connected to central catalogue and map viewer showingfound WMS .............................................................................................................................. 63Figure 49 Illustration of relation between ExtJS and OpenLayers libraries inside of HSLayers................................................................................................................................................... 63Figure 50 HSlayers Map Portal ................................................................................................ 64Figure 51 Map Window ............................................................................................................ 65Figure 52 Physical and Logical Structure ................................................................................ 66Figure 53 HSLayers.OWS - Open Web Services client ........................................................... 68Figure 54 Printing with HSLayers............................................................................................ 69Figure 55 Printing Result ......................................................................................................... 70Figure 56 Web Map Content Editing........................................................................................ 72Figure 57 Permanent Link ........................................................................................................ 73Figure 58 Embedded ............................................................................................................... 74Figure 59 Result of the point query on one vector layer. ......................................................... 75Figure 60 User graphic ............................................................................................................. 75Figure 61 OGC WPS client ...................................................................................................... 76Figure 62 Image classifcation................................................................................................... 77Figure 63 Buffering .................................................................................................................. 77Figure 64 Sequence diagram of proxy4ows shows the negotiation between the client,proxy4ows middleware and the target server. .......................................................................... 79Figure 65 Invoking from catalogue .......................................................................................... 79Figure 66 WMS invoking ......................................................................................................... 80Figure 67 WMS Sequence diagram. ......................................................................................... 81Figure 68 WMS transformation result - left map coordinate system, right - transformed resultfrom EPSG:4326 source. .......................................................................................................... 81Figure 69 Composition Saving ................................................................................................. 82Figure 70 Open Composition from local disk .......................................................................... 83Figure 71 WFS invoking scheme ............................................................................................. 84Figure 72 Get Map Scheme ...................................................................................................... 85Figure 73 OWS Dispatch ......................................................................................................... 86Figure 74 Geoportal, Filter Encoding....................................................................................... 90Figure 75 Filter Encoding......................................................................................................... 91Figure 76 Filtering of WFS ...................................................................................................... 91Figure 77 WPS Invoking .......................................................................................................... 92Figure 78 Proxy ........................................................................................................................ 93Figure 79 HSLayers SOS client ............................................................................................... 95Figure 80 HSLayers Embeded ................................................................................................. 96Figure 81 Rendering Map......................................................................................................... 97Figure 82 Locus map app, Catalogue client ............................................................................. 99Figure 83 WMS displayed in Locus app, map legend............................................................ 100Figure 84 Parcel Info app ....................................................................................................... 100Figure 85 KML metadata in the catalogue client ................................................................... 101Figure 86 Displaying KML in Google Maps and Locus ........................................................ 102Figure 87 Simple mobile editing application ......................................................................... 10307 March 2013 8 of 44
  13. 13. Date: 7-Mar-13 HABITATS Networking Services and Service ToolkitsDoc. Identifier: D4.3.2Project: Social Validation of INSPIRE Annex III Data Structures in EU HabituasFigure 88 Filed editing results displayed online in Google Earth as KML ............................ 103Figure 89 Apache ODE .......................................................................................................... 105Figure 90 Orchestra ................................................................................................................ 106Figure 91 Taverna ................................................................................................................... 107Figure 92 Workflow modeller ................................................................................................ 108Figure 93 Eclipse BPEL ......................................................................................................... 109Figure 94 Humboldt Workflow Design ...................................................................................111Figure 95 Taverna Workbench................................................................................................ 112Figure 96 Aquatic Invasive Species ....................................................................................... 116Figure 97 Aquatic Invasive Species App ............................................................................... 116Figure 98 AIS classification ................................................................................................... 117Figure 99 Integration with RL ................................................................................................ 117Figure 100 AIS sighting ......................................................................................................... 118Figure 101 Ireland Pilot architecture ...................................................................................... 118Figure 102 Publishing ............................................................................................................ 119Figure 103 Sea Monitoring..................................................................................................... 120Figure 104 La Palma Pilot Scheme ........................................................................................ 120Figure 105 La Palma portal .................................................................................................... 121Figure 106 La Palma metadata ............................................................................................... 122Figure 107 Madonia Architecture........................................................................................... 123Figure 108 Madonia implementation ..................................................................................... 124Figure 109 Augment Reality Technology............................................................................... 125Figure 110 Android App ......................................................................................................... 126Figure 111 Augment Reality Scheme ..................................................................................... 126Figure 112 Augment Reality Implementation ........................................................................ 127Figure 113 Pilot portal ............................................................................................................ 128Figure 114 Pilot Metadata ...................................................................................................... 128Figure 115 Coastal HABITATS pilot is design ...................................................................... 130Figure 116 Latvian Pilot Implementation............................................................................... 131Figure 117 Latvian portal ....................................................................................................... 132Figure 118 Processing services .............................................................................................. 132Figure 119 FMI pilot scheme ................................................................................................. 134Figure 120 OPRL Data ........................................................................................................... 135Figure 121 Harmonised data publishing on RL ..................................................................... 138Figure 122 Invasive species on RL ........................................................................................ 139Figure 123 Invasive species on RL ........................................................................................ 139Figure 124 The screen capture shows the data as it appears on the HABITATS RL Geoportal:http://www.habitats.cz/view?permalink=44b2ad495fd262b365f8fdb5310a1458 ................. 140Figure 125 The screen capture shows the data as it appears on the HABITATS RL Geoportal:http://www.habitats.cz/view?permalink=8555142bd2d6f5462d4f766015bc4776 ................ 141Figure 126 Liberec Basic portal functionality ........................................................................ 142Figure 127 Liberec Thematic Maps using standardised data from FMI ................................ 142Figure 128 Flood portal as part of Geoportal ......................................................................... 143Figure 129 Education and awareness ..................................................................................... 143Figure 130 Integration of Open Linked data from skiing resorts ........................................... 144207 March 2013 9 of 44
  14. 14. Date: 7-Mar-13 HABITATS Networking Services and Service ToolkitsDoc. Identifier: D4.3.2Project: Social Validation of INSPIRE Annex III Data Structures in EU Habituas TablesTable 1 Testing WMS services results ...................................................................................... 61Table 2 Comparison of INSPIRE solutions and current mobile solutions ............................... 98307 March 2013 10 of 44
  15. 15. Date: 7-Mar-13 HABITATS Networking Services and Service ToolkitsDoc. Identifier: D4.3.2Project: Social Validation of INSPIRE Annex III Data Structures in EU Habituas IntroductionThe INSPIRE Directive considers that spatial information is needed for the implementation ofCommunity policies which must integrate environmental protection in accordance withArticle 6 of the Treaty, and establishes the basis for an infrastructure for spatial informationin Europe in order to support EU environmental policies and those activities which may havean impact on the environment. It defines 34 spatial data themes related to environmentalapplications and requires, in order to ensure that infrastructures of the Member States arecompatible and usable in a trans-boundary context, that common Implementing Rules areadopted for all Member States, in specific areas: Metadata, Data Specifications, NetworkServices, Data and Service Sharing and Monitoring and Reporting.The HABITATS project (Social Validation of INSPIRE Annex III Data Structures in EUHABITATS) focuses on the adoption of INSPIRE standards through a participatory process todesign and validate data, metadata and services specifications with real citizens andbusinesses.This deliverable presents the current status, the ongoing work, and the plans for theHABITATS Networking Services, which are series of specific networking service appletsdeployed and tested for data sharing within the project. The HABITATS networking serviceswill be ultimately deployed at two levels: • On the HABITATS Reference Laboratory as a central portal with the support of global data, but also supporting cross scenarios implementations; • HABITATS pilot applications, as implementations of single HABITATS pilot cases, which will also be used for testing the sharing of local data and metadata.The prototype set of services as implemented on the HABITATS Reference Laboratorygeoportal platform are described in the context of future pilot implementations.These follow from the HABITATS generic networking and data sharing architecture1, and itspossible logical components, based on user needs that were found in the pilots2 and will bevalidated by users on the basis of concrete implementations in second phase of the project3.Terms• discovery services – search for spatial data sets and services on the basis of the content of the corresponding metadata and to display the content of the metadata [INSPIRE Directive]• download services – services to copy of spatial data sets, or parts of such sets, to be downloaded and, where practicable, accessed directly [INSPIRE Directive]• feature – abstraction of real world phenomena [ISO 19101]• feature catalogue – catalogue(s) containing definitions and descriptions of the spatial object types, their attributes and associated components occurring in one or more spatial data sets, together with any operations that may be applied [ISO 19110 – modified]• infrastructure for spatial information – metadata, spatial data sets and spatial data services;1 Developed in D4.2.1 and D4.2.22 As reported in D5.2.1.3 To be reported in D2.4.3 and D5.4.207 March 2013 11 of 44
  16. 16. Date: 7-Mar-13 HABITATS Networking Services and Service ToolkitsDoc. Identifier: D4.3.2Project: Social Validation of INSPIRE Annex III Data Structures in EU Habituas network services and technologies; agreements on sharing, access and use; and coordination and monitoring mechanisms, processes and procedures, established, operated or made available in accordance with this Directive; [INSPIRE Directive]• INSPIRE application schema – application schema specified in an INSPIRE data specification• INSPIRE data specification – harmonised data product specification for a theme adopted as an Implementing Rule• metadata – information describing spatial data sets and spatial data services and making it possible to discover, inventory and use them [INSPIRE Directive]• services allowing – spatial data services to be invoked [INSPIRE Directive]• spatial data – data with a direct or indirect reference to a specific location or geographic area [INSPIRE Directive]• spatial data set – identifiable collection of spatial data [INSPIRE Directive]• spatial object – abstract representation of a real-world phenomenon related to a specific location or geographical area [INSPIRE Directive]• transformation services – services enabling spatial data sets to be transformed with a view to achieving interoperability [INSPIRE Directive]• view services – services to display, navigate, zoom in/out, pan, or overlay viewable spatial data sets and to display legend information and any relevant content of metadata [INSPIRE Directive]Abbreviations • API – Application Programming Interface • CMS – content management systems • CSW - Catalogue Service Web • EC – European Commission • EN - European Norm • ESA – European Space Agency • EU – European Union • GEOSS - Global Earth Observation System of Systems • GMES – Global Monitoring for Environment and Security • GML – Geography Markup Language • HTML – HyperText Markup Language • INSPIRE – INfrastructure for SPatial InfoRmation in Europe • ISO – International Organisation for Standardisation • KML – Keyhole Markup Language • OGC – Open Geospatial Consortium • RL – Reference Laboratory • SDI – Spatial Data Infrastructure • SEIS – Shared Environmental Information System • SOA – Service Oriented Architecture • UML – Unified Modelling Language • URI – Uniform Resource Identifier • URM – Uniform Resource Management • WCS – Web Coverage Map • WFS – Web Feature Map Service07 March 2013 12 of 44
  17. 17. Date: 7-Mar-13 HABITATS Networking Services and Service ToolkitsDoc. Identifier: D4.3.2Project: Social Validation of INSPIRE Annex III Data Structures in EU Habituas • WMC – Web Map Context • WMS – Web Service Map • WPS – Web Processing Services07 March 2013 13 of 44
  18. 18. Date: 7-Mar-13 HABITATS Networking Services and Service ToolkitsDoc. Identifier: D4.3.2Project: Social Validation of INSPIRE Annex III Data Structures in EU Habituas4 INSPIRE, Networking Architecture and HABITATSIn order to validate the HABITATS networking services architecture defined in Task 4.2, aseries of specific service applets were deployed and tested for data sharing using theHABITATS Reference Laboratory (RL) geoportal platform.Comparing network services and spatial data services, the INSPIRE Forum4 definitions are: • Spatial data services are all services (Discovery, View, Download, Transformation, Invoke, Other) regarding spatial data. • Network services (Discovery, View, Download, Transformation, Invoke): • non-compliant network services are INSPIRE compliant services with respect to functionality; • compliant network services are compliant services with respect to functionality and quality of service.The HABITATS networking architecture supports INSPIRE Network services, but needs to gobehind this concept. INSPIRE networking services are in principle limited only to themanagement of existing data and metadata. The HABITATS Networking Services alsosupport such functionality with data and metadata management, data and metadata collection,working with non-spatial data, etc.The HABITATS service applets re-use existing applications where possible and arethemselves designed for re-use. The selection of the specific services to deploy is primarily auser-driven process, as defined in the user scenarios and requirements of task T2.3 and asrequired by the pilot validation platform of task T5.2. Task T4.3 has defined the prototype setof Network Service Applets to be installed in validation pilot platforms, as: • A series of specific networking service applets deployed and tested for data sharing within the project using the Network Service Architecture (of D4.2.1) • Interoperability Services • Enabling Services • Visualisation of information layers • Overlay of information from different sources • Spatial and Temporal Analysis • “quick” and “light” on-demand applets to meet validation pilot expectations and user needs • Usability, simplicity and openness to rapid prototyping mash-ups. • A set of specific service applets that allow users to identify, access, use and reuse habitats-related data, designed and deployed on-demand to meet user needs, • Users selected in the T2.3 user scenarios and T5.2 pilot validation platform. • Mobile Apps allowing use advantage of HABITATS RL • “Quick Prototyping” service applets respecting the HABITATS service architecture and developed on-demand.These are based on the outcomes from the earlier tasks and work with the HABITATS RL,and will now lead into the interface tools and toolkit.4 http://inspire-forum.jrc.ec.europa.eu/mod/groups/topicposts.php?topic=11135&group_guid=865107 March 2013 14 of 44
  19. 19. Date: 7-Mar-13 HABITATS Networking Services and Service ToolkitsDoc. Identifier: D4.3.2Project: Social Validation of INSPIRE Annex III Data Structures in EU HabituasThe HABITATS Networking Architecture aims to extend the principles of the INSPIREnetworking architecture, because INSPIRE doesn’t cover important aspects such as datamanagement and data collection. So all components of the INSPIRE networking architecturewill be included in the HABITATS architecture, but this concept will be extended by otherfunctionalities. From this point of view principles of GEOSS and GMES and also principlesof Shared Environmental Information System (SEIS) and Single Information Space in Europefor the Environment (SISE) have influenced the HABITATS architecture and its networkedservices.The development of the network service architecture process of WP4 was initiated through astate of the art analysis of existing SDI, to find out more about already existing infrastructuresand to examine how data should be shared and what services are required to enable sharing.When designing the networking architecture, a set of specific networking service applets wasdeployed and tested for data sharing within the project. Also the potential for re-use ofexisting application was taken into account.This Report deals also with the tools for invoking of Geospatial Services that arose within theHABITATS network architecture, interlinking different data sources and also interlinking datasources from different INSPIRE thematic areas.5 Invoking servicesThe definition of spatial data services included in the INSPIRE directive is the following:‘spatial data services’ means the operations which may be performed, by invoking a computerapplication, on the spatial data contained in spatial data sets or on the related metadata(INSPIRE 2007). ISO 19119 defines also taxonomy for Geospatial services (INSPIRE InvokeServices 2009): • Geographic human interaction services • Geographic model/information management services • Geographic workflow/task management services • Geographic processing services o Geographic processing services – spatial o Geographic processing services – thematic o Geographic processing services – temporal o Geographic processing services – metadata • Geographic communication services • Geographic system management services (HABITATS 2009)From INSPIRE Networking architecture, there are basic Networking services 1. Discovery Service (discovery): Is a services that makes it possible to search for spatial data sets and services on the basis of the content of the corresponding metadata and to display the content of the metadata. 2. View Service (view): Is a service that makes it possible, as a minimum, to display, navigate, zoom in and out, pan or overlay viewable spatial data sets and to display legend information and any relevant content of metadata. 3. Download Service (download): Is a service that enables copies of spatial data sets, or parts of such sets, to be downloaded and, where practicable, accessed directly.07 March 2013 15 of 44
  20. 20. Date: 7-Mar-13 HABITATS Networking Services and Service ToolkitsDoc. Identifier: D4.3.2Project: Social Validation of INSPIRE Annex III Data Structures in EU Habituas 4. Transformation Service (transformation): Is a service that enables spatial data sets to be transformed with a view to achieving interoperability. 5. Invoke Spatial Data Service (invoke): Is a service that allows defining both the data inputs and data outputs expected by the spatial service and a workflow point of view 5The INSPIRE Spatial Data Service and Invoke Service – Draft, implements rules defining thatInvoke service has to be accessible via Internet and offers a mean to invoke the linked spatialdata services. Invoke shall support in order to allow clients invoking spatial data services.Taking into account the potentially wide diversity of interfaces and protocols, invoke servicesare services that allow access to sufficient service metadata to enable the activation orexecution of the spatial data service. The document updated the basic INSPIRE architecturescheme and defined sets of requirements for INSPIRE Invoking services.Figure 1 INSPIRE Networking ArchitectureThe requirements are divided into two groups of requirements: • IR Requirement - Are requirements that are reflected in the Implementing Rule on interoperability of spatial data sets and services are shown using this style. • SDS Requirement - Requirements that are not reflected in the Implementing Rule on interoperability of spatial data sets and services are shown using this style.Document INSPIRE Spatial Data Services and Invoke Service define also set ofrecommendation.INVOKING service requirements and recommendations • IR Requirement 1 The implementing rules are restricted to spatial data services that relate to spatial data sets in themes in Annex I-III, or to their related metadata. • Recommendation 1 There shall be no other requirements applicable to ALL spatial data services than the establishment of discovery metadata. • Recommendation 2 A spatial data service in this context shall have clearly defined interfaces for machine-to-machine communication. A Geographic Information System or other systems, understood as a set of tools for collecting, processing and storing5 INSPIRE Spatial Data Services and Invoke Service – Draft, implementing rules,Draft_IR_SDS_and_Invoke_1.0.doc07 March 2013 16 of 44
  21. 21. Date: 7-Mar-13 HABITATS Networking Services and Service ToolkitsDoc. Identifier: D4.3.2Project: Social Validation of INSPIRE Annex III Data Structures in EU Habituas spatial data, should not be considered an invokable spatial data service from the perspective of the relevant Implementing Rules. But any specific functionality included in it, and with a well-defined and exposed interface, could be an invokable spatial data service. • IR Requirement 2 Interoperability arrangements in the INSPIRE context shall be related to invokable spatial data services. • IR Requirement 3 Requirements for interoperability arrangements are only mandatory for spatial data services operating upon harmonised data (i.e. spatial data sets conformant to the regulation for IDSS). • IR Requirement 4 A spatial data service conformant to interoperability arrangement shall support coordinate reference systems according to Annex II.1 of the Commission Regulation (EC) No 1089/2010 . • IR Requirement 5 The default temporal reference system referred to in point 5 of part B of the Annex to Commission Regulation (EC) No 1205/2008 shall be used, unless other temporal reference systems are specified for a specific spatial data theme in Annex I-III. • IR Requirement 6 A spatial data service conformant to the interoperability arrangement shall be available 99% of time. • IR Requirement 7 A spatial data service conforming to interoperability arrangement returning spatial objects as part of the output, shall encode those spatial objects according to Article 7 of Commission Regulation (EU) No 1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services. • IR Requirement 8 All spatial data services conformant to the interoperability arrangements shall include a Get Service Metadata operation. • IR Requirement 9 Newly developed spatial data services operating upon harmonised data or their metadata shall be conformant with interoperability arrangements. • IR Requirement 10 Any harmonised spatial data service shall follow the interoperability arrangements. • IR Requirement 11 Any harmonised spatial data service shall have minimal performance criteria defined in the same way as network services, i.e. performance, capacity, and availability. The values will depend upon the character of the type of service. • Recommendation 5 The gazetteer service should be related to harmonised datasets conforming to Addresses, Geographical names and Administrative boundaries. i.e. Location instances should be fetched from these three themes, and correspondingly the Location type should be either an address, a geographical name, or an administrative polygon. • IR Requirement 12 A registry service shall be compliant with ISO 19135:2005, Geographic information -- Procedures for item registration.07 March 2013 17 of 44
  22. 22. Date: 7-Mar-13 HABITATS Networking Services and Service ToolkitsDoc. Identifier: D4.3.2Project: Social Validation of INSPIRE Annex III Data Structures in EU Habituas6 Problems of Policy Driven SDIINSPIRE is politically driven top down approach. It is important to see how INSPIREreflects local, regional and national needs. Currently, there is low awareness on regional leveland the benefits for the local level are no clearly defined. During the JRC Cost benefitworkshop in 2012 the schema depicted in next figure was presented.Figure 2 Reverse “pyramid” effect (Bregt 2012).The schema shows the relation between the level of governance and the amount of benefits.The HABITATS idea is to find a solution how to turn the green triangle upside down. It is alsovital for successful implementation of INSPIRE.The authors identified three areas where special attention needs to be given for successfulimplementation of the INSPIRE Directive: • metadata; • networking architecture;The INSPIRE architecture doesn’t reflect the needs of regions regarding data collection andupdating. Usually, for different pilots’ needs, the generic INSPIRE architecture has to bemodified, extended or reduced. (Charvát 2011)Global SDI building is usually described in a form of a pyramid. Current practices prove that“spider web infrastructure building”, where different local or global levels are able to directlyshare data, is more efficient. The HABITATS intention is to shift SDI from the pyramid to thespider web paradigm.07 March 2013 18 of 44
  23. 23. Date: 7-Mar-13 HABITATS Networking Services and Service ToolkitsDoc. Identifier: D4.3.2Project: Social Validation of INSPIRE Annex III Data Structures in EU HabituasFigure 3 Spider Web ParadigmNeogeographyThere exist a large number of different voluntary or bottom-up initiatives supporting buildingof different parts of SDI. The SDI world is changing with development of new GPS devices,smartphones, mobile cameras and tablets. More and more localised information is collectedby citizens. For such type of data collection “people as sensors” or “human sensors” terms areoften used. This means that “human observations” can be part of future real-time SDIs andserve as an input for spatial decision-making processes. Current use and collection of data bycitizens is higher than collection of data by public bodies. Such process is depicted in nextFigure.Figure 4 The changing sources of spatial data (Harris & Lafone).Local and community activities capture local knowledge in multiple media forms including07 March 2013 19 of 44
  24. 24. Date: 7-Mar-13 HABITATS Networking Services and Service ToolkitsDoc. Identifier: D4.3.2Project: Social Validation of INSPIRE Annex III Data Structures in EU Habituasvideos, photos or oral histories. The collected information can contribute to up-to-date data.The term neogeography is used for these methods. It is related to new ApplicationProgramming Interfaces (APIs), Web 2.0 and the mapping capabilities of the Geospatial Web.People can create “geotagged” information from mobile devices. This new technology opensnew possibilities. Neogeography represents a new way of collection and geographicknowledge production using interactive technologies, interfaces and technical expertise. Thesemethodologies bring serious challenges to SDIs and traditional forms of data acquisition,analysis, and publication. (Harris & Lafone forthcoming)7 HABITATS Networking ServicesThe intention of the HABITATS Networking Services is to provide shift from classicalINSPIRE (GEOSS, GMESS architecture) towards solution, which will support local andregional SDI building and their interaction with INSPIRE and also, which will movestandards SDI model towards Neography and SpiderWeb paradigm. The way to test andprovide it is Reference Laboratory as key tool of HABITATS Networking architecture.The HABITATS architecture defines a platform-neutral SDI with a basic set of networkingservices in compliance with the INSPIRE Directive for sharing environmental data, especiallythat related to the 4 INSPIRE themes of 16.Sea-Regions (SR), 17. Bio-geographical Regions(BR), 18. HABITATS and Biotopes (HB) and 19. Species Distribution (SD). This will resultin a European Metadata profile for these four data themes, which will be an extension of theINSPIRE profile. Our intention is not only to follow the INSPIRE profile for discoveryservices, but to also reflect on the extension the profiles for using data; a link to datamodelling activities is therefore necessary. This profile is further open to extension by singlecountries or user groups, but the aim is that it be respected as a minimum set.The set of HABITATS Networking Services have been implemented on the HABITATSReference Laboratory (RL) geoportal platform6. This acts as a client of the 7 HABITATSpilots that provides a very rich set of cross-pilots, inter-regional and enabling services.Reference LabThe reference laboratory is the central hub of the HABITATS Networking Architecture. Itconsists of several layers, which are (HABITATS D4.2.2 2011): • Data layers – management data and files on storage, eventually guarantee access to external sensors Server (engine layer) – defines tools, which guarantee basic services on the server side – supplying service Client layer – is client side of web services, which guarantee access of users to services • Application layer is some form of wrapping elementary client services into application or into such form, which could be used by other web tools and social media.Presentation layer contain such web tools, which allow to combine and publish single objectsfrom the application level as part of Web presentationThe illustration below (taken from HABITATS D4.2.2 2011) shows the different layers of theHABITATS Networking Architecture.6 www.habitats.cz07 March 2013 20 of 44
  25. 25. Date: 7-Mar-13 HABITATS Networking Services and Service ToolkitsDoc. Identifier: D4.3.2Project: Social Validation of INSPIRE Annex III Data Structures in EU HabituasFigure 5 Habitats Networking ArchitectureThe final implementation of the HABITATS Services anticipates that selected concreteservices will be deployed for every pilot, and that there will be one central platform (i.e. theReference Laboratory).Figure 6 Habitats RL and pilots07 March 2013 21 of 44
  26. 26. Date: 7-Mar-13 HABITATS Networking Services and Service ToolkitsDoc. Identifier: D4.3.2Project: Social Validation of INSPIRE Annex III Data Structures in EU HabituasThe HABITATS RL provides the Networking Architecture supporting both NetworkingServices and Spatial Data services, that support the SDI network services to enable trans-European sharing of habitats-related spatial data between public authorities and otherstakeholders in the Community, enabling the creation of value added services. The RL isfocused on implementation of: • Cross pilot scenarios based on sharing of data among more pilots • Validation platform for testing of conformity of implemented pilot services • Services supporting global discovery, view and downloading • Repository for common metadata • Repository for pan European datasets such as Natura 2000, CLC, Urban Atlas and Open Street Maps • Interlink with social networksThe RL provides the Networking Architecture, that supports the SDI network services toenable trans-European sharing of habitats-related spatial data between public authorities andother stakeholders in the Community enabling the creation of value added services.The RL enables deployment of specific service applets, including interoperability andenabling services, on-demand from user communities and the pilots for initial implementationand validation. It is being developed further to include an invoking service toolkit integratingthe service applets with the goal of facilitating the development of end-user services accessinghabitats-related spatial data over timeHowever applications are the key objectives and final goal of using the HABITATS RL. Asthe RL is just a geoportal tool to help to build applications that address the Pilots’ typical usecases.The HABITATS RL is• an interface that enables interactive search, portrayal, evaluation, sharing, analyse and reuse of spatial and non-spatial data.• a solution based on interoperable standards (OGC, W3C, OASIS, ISO). It is interconnected to other resources through the Internet. It helps to create a distributed structure of information and knowledge with spatial position.Figure 7 Habitats RLHowever the RL is not a central data storage or a closed web application with maps. It is ageoportal with07 March 2013 22 of 44
  27. 27. Date: 7-Mar-13 HABITATS Networking Services and Service ToolkitsDoc. Identifier: D4.3.2Project: Social Validation of INSPIRE Annex III Data Structures in EU Habituas • Independent components • Composition according to user requirements • Based on SOA • Possibility to integrate with other resources • Maximum openness • Open Source • Open Standards • Extension to non-GIS community • Open Search • Administration of other (non-spatial) data sourcesThe HABITATS RL allows deployment of the current state of the art of technologicalsolutions, which will be tested and adopted by the HABITATS partners and user stakeholders.It allows testing of current existing technology and generation of further research tasks drivenby users. The RL also collects information coming from other projects, which is an importantinput for the HABITATS analysis and public discussion. The methods of social assessmentwill be an increasingly important part of the RL.Thus the RL’s networking services aim to help HABITATS to extend user-centric, co-designapproaches into the arena of standards design and adoption processes, considering standardsinitiatives such as INSPIRE, OGC, UNSDI to be significant social, economic and institutionalinnovations. The elements of the approach are maintained, applying the model at all levelsfrom the global scale to the local and regional policies that frame many HABITATS validationpilots. Community building activities follow a Web 2.0 approach to capture the knowledge inactive user communities with a strong interest in contributing to the standards developmentprocess. By inviting a broad multi-sectoral and inter-disciplinary range of concernedstakeholders to participate into the HABITATS network, a viral motivation spiral is set off. Apeer-to-peer approach to opening up information sources and providing access to contentensures a rapid extension of the critical mass of environmental data established by projectpartners.Uniform Resource Management (URM) ConceptUniform Resource Management (URM) provides a framework in which communities canshare information and knowledge through description, which is easily understandable insideof the community. It is based on a standardised schema supporting a uniform description ofinformation and knowledge including common vocabularies. The schema defines themeaning, characteristics and relationships of a set of properties, and includes constraints onpotential values and the inheritance of properties from other schemas. The URM concept hasbeen defined and developed through the NaturNet-Redime project and extended by c@r tosupport knowledge sharing inside a community (Charvát et al. 2008).07 March 2013 23 of 44
  28. 28. Date: 7-Mar-13 HABITATS Networking Services and Service ToolkitsDoc. Identifier: D4.3.2Project: Social Validation of INSPIRE Annex III Data Structures in EU HabituasFigure 8 URM conceptUniform Resource Management supports validation, discovery and access to heterogeneousinformation and knowledge. It is based on utilisation of metadata schemas. The URM modelscurrently integrate different tools, which support sharing of knowledge. Geoportal containscommon visualisation, data sharing, metadata and catalogue functionalities. It includes alsotools for sensor observation management and spatial data transformation and processing.The principle of the URM allows to build a "spider web" infrastructure supportinginterconnection of portals and effective exchange of information. This concept is also morerelated to GEOSS and Single Information Space for Environment (SISE) principles.Many context attributes characterize the environmental information or knowledge. From thepoint of view of context, the information or knowledge can involve different parties: • Information or knowledge provider i.e. a party supplying the resource; • Custodian accepts accountability and responsibility for the resources and ensures appropriate care and maintenance of the resource; • Owner of the resource; • User, who uses the resource; • Distributor who distributes the resource; • Originator who created the resource; • Point of Contact to be contacted for acquiring knowledge about or acquisition of the resource; • Principal investigator responsible for gathering information and conducting research; • Processor who has processed the data in a manner such that the original resource has been modified; • Publisher, i.e. party who published the resource; • Author, i.e. party who authored the resource.The HABITATS RL is a new integrated solution designed as a combination of previoustechnologies - Uniform Resource Management, Geohosting and new technologicaldevelopment of a visualization client based on HSLayers. The URM Geoportal is not oneintegrated solution, but a set of modules and services, which can communicate throughinteroperable services (OGC, W3C). The solution is modular and can be readily modified for07 March 2013 24 of 44
  29. 29. Date: 7-Mar-13 HABITATS Networking Services and Service ToolkitsDoc. Identifier: D4.3.2Project: Social Validation of INSPIRE Annex III Data Structures in EU Habituasdifferent purposes. The URM Geoportal is based on Open Source technologies, but it can beintegrated with different technologies such as MS SQL or ArcSDE. The Uniform ResourceManagement (URM) supports validation, discovery and access to heterogeneous informationand knowledge. It is based on utilization of metadata schemas. The URM models currentlyalso integrate different tools, which support sharing of knowledge.The URM Geoportal contains: Metadata Catalogue client Visualization client Metadata Editor Geoserver Styler Metadata Extractor Enterprise management tools Content management Social Networks toolsFigure 9 URM principlesThe HABITATS RL geoportal contains common visualization, data sharing, metadata andcatalogue functionalities. Additional parts of the solution can also be tools for management ofsensor observation and spatial data transformation and processing.The core part of the RL is the metadata system, which guarantees access to all informationstored in the portal07 March 2013 25 of 44
  30. 30. Date: 7-Mar-13 HABITATS Networking Services and Service ToolkitsDoc. Identifier: D4.3.2Project: Social Validation of INSPIRE Annex III Data Structures in EU HabituasThe URM concept also allows access to any information stored on one portal with otherportals that use the URM principles.Figure 10 URM SpidernetSo the URM allows a "spidernet" SISE (Single Information Space for the Environment inEurope) infrastructure supporting interconnection of portals to be built with the effectiveexchange of informationUSE OF THE URM IN THE HABITATS RLThe HABITATS RL portal is based on the Uniform Resource Management (URM) conceptand was designed to aid awareness raising, training, presentation and sharing of knowledgeand tools within Living Labs (LL). Its first design was made in the Naturnet Redime researchproject7, it is also used by EnviroGrids BlackSee project for implementation of GEOSSinfrastructure8 and its design and development continues into the current HABITATS project.It is built as an interoperable network for an effective exchange of the information,knowledge, and services relating to its multi- and interdisciplinary subject matters inside ofLL or among LLs. The portal is implemented using AJAX technology (WEB 2) supporting aneasy management of information within the portal and enabling an easy context awareness forknowledge discovery using the URM. This URM concept supports a sharing of knowledgewithin the community using metadata and catalogue standards for information description anddiscovery. The system for authorization and support for a unique login for all components is7 See www.naturnet.org8 See www.envirogrids.net07 March 2013 26 of 44
  31. 31. Date: 7-Mar-13 HABITATS Networking Services and Service ToolkitsDoc. Identifier: D4.3.2Project: Social Validation of INSPIRE Annex III Data Structures in EU Habituasalso an important part of the portal.The portal supports those users searching for information dealing with the subjects ofsustainability, environmental protection and management and is also a place for others topublish related information and resources.It is possible to search by terms within several categories (this list of categories is not limitedand can be changed or increased). Firstly, the user can choose from one of several possiblefolders (‘all’, ‘documents only’, ‘projects’, ‘maps’, etc.) by selecting the tabs at the top of thepage, which enable the user to search using their SEARCH TERM either more generally orwithin a restricted range. The (main panel) window then displays the results of a search withinthe catalogued information. The user can check the metadata for any of the listed items or canrun the application or view the document in those cases where the listed items are directlylinked to a document or an application.An extended search allows searching for information in a variety of ways. Users can choosefrom any of the parameters listed in the left window or use the map window. The map windowoffers a way to select the geographic area in which the user is particularly interested. Userscan select by country or a smaller detailed area from the whole of Europe using the selectionrectangle for zooming.A combination of both windows provides a better opportunity to precisely specify the requiredinformation. • Publishing user documents on the URM portal. o Users can use the Metadata Extractor, to find their file on their computer; using the Metadata Extractor (file searching), ask for extraction of the available metadata, then complete the missing metadata and publish their file and its metadata on the URM portal. • Publishing of user Web pages on the URM portal. o Users can publish any Web content through the URM portal. They put their web address (URL) into the metadata extractor and extract the metadata. Edit the missing records in the metadata (including a selection for the type of their content) and then save the metadata. • Registration of user metadata system on the URM portal. o If a user has a catalogue system supporting the following profiles (ISO 19115, ISO 19119 and Dublin Core ISO 15836-2003 and supporting the Catalogue Service for the Web (for instance using MICKA or GeoNetwork) they can ask for registration of their catalogue on the URM portal. • Registration of data or services directly from a user application. o An applications developer who directly publishes interactive Web data or services, can ask for the CSW client, which will support direct registration of their results in the catalogue. • Publishing using URM tools. o Users may use the independent URM tools for working with their data, or for their integration into new systems and presentation in e-learning or web services forms.URM Tools that are available on the HABITATS RL are described in the followingsubsections.07 March 2013 27 of 44

×