EuroGeoSource. EU Information and Policy Support System for Sustainable Supply of Europe with Energy and Mineral Resources WP 5

Transcription

1 EuroGeoSource EU Information and Policy Support System for Sustainable Supply of Europe with Energy and Mineral Resources Grant Agreement no WP 5 Service implementation cookbook egs_wp5_cookbook-v2.1.doc Eurogeosource Cookbook 1

2 Version history Initial version 1.1 jan 2012 Deployment added 2.0 feb 2012 Updated to use version 2.0 of AM, ER & MR Deployment modified Content 1 INTRODUCTION SYSTEM REQUIREMENTS OPERATING SYSTEM SOFTWARE REQUIREMENTS REQUIRED COMPONENTS SOFTWARE CONFIGURATION FILES INSTALLING THE RELATIONAL DATABASE INSTALL POSTGRESQL INSTALL POSTGIS FOR POSTGRESQL INSTALLING WEB FEATURE SERVER CONFIGURING THE WEB FEATURE DATABASE CREATING THE INSPIRE USER CREATING THE INSPIRE DATABASE ENABLING THE UNIVERSALLY UNIQUE IDENTIFIER CREATING THE INSPIRE SCHEMA CONFIGURING THE WEB FEATURE SERVER CREATING THE INSPIRE WORKSPACE CREATING THE INSPIRE DATABASE CONNECTION CREATING THE INSPIRE FEATURE STORE CREATING THE INSPIRE WEB FEATURE SERVICE LOADING DATA AVAILABLE SOFTWARE DATABASE - LOADING STRATEGY DATABASE - KEYS DATABASE - INSPIRE ID DATABASE - VALIDATING DATA DATABASE - VALIDATING GEOMETRY WEB FEATURE SERVICE - REFRESH DEPLOYMENT egs_wp5_cookbook-v2.1.doc Eurogeosource Cookbook 2

3 9.1 DEPLOYING THE RELATIONAL DATABASE DEPLOYING THE INSPIRE WEB FEATURE SERVICE MAKING THE WEB FEATURE SERVICE INSPIRE COMPLIANT... ERROR! BOOKMARK NOT DEFINED. egs_wp5_cookbook-v2.1.doc Eurogeosource Cookbook 3

4 1 Introduction This document describes the steps to install an INSPIRE compliant Web Feature service. The concept behind this stack of software is to simplify the creation of INSPIRE compliant download services which implement the data models of the INSPIRE themes relevant to EGS. A complete list of all the software required to complete this cookbook is summarized in chapter 2 (System requirements) and chapter 3 (Software components). It includes all the version information and a short description of the contents. The installation and configuration is described in the chapters 4 (Installing the Relational Database) through 7 ( egs_wp5_cookbook-v2.1.doc Eurogeosource Cookbook 4

5 Configuring the Web Feature Server). cmp Transformation combined partner specific provided by WP5 Mapping rules EGS application schema «datasource» Local dataset ETL «database» Relational model «service» deegree WFS INSP IRE down load The software stack is primarily designed to encapsulate to process of creating the INSPIRE compliant XML which will be served by the Web Feature Service(WFS). This eases the knowledge required to serve INSPIRE datasets. The data which will be served is stored in a relational database. Database and ETL technology are the only prerequisites to be able to serve the required data. «datasource» Local dataset partner specific ET «database» Feature store provided by WP5 EGS application schema The most challenging aspect is to use the spatial capabilities of the database when loading data into the database. This aspect however is not covered in detail by this cookbook. Some hints and tips will be discussed in chapter 8 (Loading data) but we cannot go into to much detail because of the diversity and complexities found in the partner database models. L «service» deegree WFS INSP IRE down load egs_wp5_cookbook-v2.1.doc Eurogeosource Cookbook 5

6 2 System requirements 2.1 Operating system The software stack may be implemented in a Windows or Linux environment. The WP5 infrastructure survey showed that most partners are using the Windows platform for (spatial) data management. For that reason, we used Windows XP (32 bit) to create this cookbook. 2.2 Software requirements All components used to implement the stack require Java to be installed on your system. Product Version Requirements Java Development Kit jdk-6u24-windows-i586.exe 1.6.0_ MB disk space 128 mb memory Please note that on a 64 bit operating system a 64 bit version of the Java virtual machine must be installed. 3 Required components The software stack consists of a number of existing components and some files to configure those components. The following components are used to implement the EGS stack: Component Description PostgreSQL Postgres is an object relational database management system available for many platforms. Because it is free and open software, it is not controlled by any single company. PostGIS PostGIS adds support for spatial objects to PostgreSQL. In effect, it allows the database server to be used as a backend spatial database, much like ESRI SDE or Oracle SDO. Apache Tomcat Tomcat is an open source webserver and servlet container and provides a pure Java HTTP web server environment for Java code to run. Deegree deegree is a Java-based framework published under an open source licen se. It consists, among others, of a spatial server component for sharing spatial data through standardized interfaces like Web Feature Service (WFS). 3.1 Software All components have to be installed using the installation files that can be found on the software supplier s website. They can also be found on the TNO INSPIRE Services machine at this download location. Component Version Installation file PostgreSQL postgresql windows.exe (download no longer available) PostGIS postgis-pg84-setup exe (download) egs_wp5_cookbook-v2.1.doc Eurogeosource Cookbook 6

7 Apache Tomcat apache-tomcat exe (download) Deegree 3.1 Fahrenheit deegree-webservices zip (download) 3.2 Configuration files The following files are required to configure the components that make up the EGS stack: Configuration Version Description Configuration file Data model for Eurogeosource INSPIRE GML application schemas Eurogeosource GML application schemas 2.0 sql script that defines the EGS relational database model; this script contains PostGIS specific features the INSPIRE EnergyResource and MineralOccurence entitites are defined by those schemas 2.0 the entities that have been modified and/or added by EGS are defined in this schema scripts.zip, containing: AM_Datamodel_Postgres v2.0.sql ER_DataModel_PostGres v2.0.sql MR_DataModel_PostGres v2.0.sql AM_CodeListData v2.0.sql ER_CodeListData v2.0.sql MR_CodeListData v2.0.sql deegree-inspire-schemas.zip EuroGeoSource-AM-v2.0.xsd EuroGeoSource-ER-v2.0.xsd EuroGeoSource-MR-v2.0.xsd Deegree INSPIRE Mapping 2.0 mapping file which decribes how database tables are transformed to INSPIRE GML deegree_mapping-er-v2.0-mrv2.0.xml egs_wp5_cookbook-v2.1.doc Eurogeosource Cookbook 7

8 4 Installing the Relational Database 4.1 Install PostGreSQL Run the installer postgresql windows.exe and the following screen will appear: Click Next. Specify the directory where the database should be installed and click Next. Specify the directory where the data of the PostgreSQL database should be stored and click Next. egs_wp5_cookbook-v2.1.doc Eurogeosource Cookbook 8

9 Specify the super user username and password for the PostgreSQL. This account will be used to run the database service, which will start when Microsoft Windows starts. For example use "postgres" as username and password. Click Next. Enter the port number on which the database can be contacted. This defaults to This port will be used when administering the database with the PGAdmin tool. Click Next. Enter the locale English, United States as the locale for the database. Also select the option to install pl/pgsql in the database. Click Next. egs_wp5_cookbook-v2.1.doc Eurogeosource Cookbook 9

10 Click Next to start the installation. egs_wp5_cookbook-v2.1.doc Eurogeosource Cookbook 10

11 When the installation is completed successfully, the following screen will appear. Please uncheck the option to start the Stack Builder. Although the option can be used to install database add-ons like PostGIS, it will not be used in this cookbook. Click Finish. The PostgreSQL database is now installed. 4.2 Install PostGIS for PostGreSQL Run the installer postgis-pg844-setup exe and the following screen will appear: Click I Agree. egs_wp5_cookbook-v2.1.doc Eurogeosource Cookbook 11

12 Uncheck the option to create a spatial database and click Next. Enter the location where PostGIS is installed. The default location is inside the PostgreSQL directory. Click Next. Enter the super user username and password from the PostgreSQL installation (step 4.1) into this screen and click Next. The installation will now be performed. Close the installer after the installation has completed successfully. egs_wp5_cookbook-v2.1.doc Eurogeosource Cookbook 12

13 5 Installing Web Feature Server Start apache-tomcat exe to install Tomcat 6.0 to your computer. The following screen will appear. Click Next. Click I Agree. Use the default component settings to install Tomcat and click Next. egs_wp5_cookbook-v2.1.doc Eurogeosource Cookbook 13

14 Enter a location to install Tomcat and click Next. Enter a port number on which the web server can be contacted. Use the default of Click Next. Enter the location where the Java virtual machine is located. Click Install. Do not start the service when finishing the installation. egs_wp5_cookbook-v2.1.doc Eurogeosource Cookbook 14

15 Delete the contents of the TOMCAT_HOME\webapps\ROOT directory. Open the deegree-webservices zip and extract and merge the contents of the deegreewebservices directory of the zip archive into the directory where Tomcat was just installed, overwriting any existing files. To change to password which allows access to the Deegree Web Feature Service, change to contents of the password.txt in TOMCAT_HOME\webapps\ROOT\WEB-INF\workspace\manager. Open the Apache Tomcat 6 Properties via the task tray. Tomcat can now be started using the Start button. The Deegree Web Feature Server can be configured with a browser at egs_wp5_cookbook-v2.1.doc Eurogeosource Cookbook 15

16 6 Configuring the Web Feature Database 6.1 Creating the INSPIRE user Open the pgadmin III tool which can be found in the Start Menu. Connect to the installed database using the super user username and password. Right click on Login Roles and click on New Login Role. egs_wp5_cookbook-v2.1.doc Eurogeosource Cookbook 16

17 Type the username inspire and enter an appropriate password. In this cookbook we will use inspire. Click on the Role privileges tab. Check all the boxes to grant super user permissions to the new login role. Click Ok. egs_wp5_cookbook-v2.1.doc Eurogeosource Cookbook 17

18 The user is now created. Disconnect from the database and create a new Server Registration by clicking File -> Add Server Enter the details as described below. Click Ok when finished. egs_wp5_cookbook-v2.1.doc Eurogeosource Cookbook 18

19 6.2 Creating the INSPIRE database Connect to the database using the inspire credentials. Right click Databases and click on New Database egs_wp5_cookbook-v2.1.doc Eurogeosource Cookbook 19

20 Create a schema named inspire, with the owner inspire, encoding UTF-8 and use template_postgis as the template. This will create a schema with all the spatial functions needed by the Web Feature Service. 6.3 Enabling the Universally Unique Identifier While still connected as inspire, click on the Schemas and open the Query Tool from Tools -> Query Tool. egs_wp5_cookbook-v2.1.doc Eurogeosource Cookbook 20

21 Click File -> Open and navigate to POSTGRES_HOME\8.4\share\contrib. Open the uuid-ossp.sql file. Execute the opened file by clicking on Query -> Execute. Several UUID functions have now been added to the inspire database. They should become visible in the main pgadmin III window after a refresh. Click on View -> Refresh in the main pgadmin III window. egs_wp5_cookbook-v2.1.doc Eurogeosource Cookbook 21

22 6.4 Creating the INSPIRE schema While still connected as inspire, click on the Schemas and open the Query Tool from Tools -> Query Tool. Extract the scripts.zip to a temporary folder. Click File -> Open and navigate to AM_DataModel_PostGres v2.0.sql file. Execute the opened file by clicking on Query -> Execute. Click File -> Open and navigate to AM_CodeListData v2.0.sql file. Execute the opened file by clicking on Query -> Execute. Click File -> Open and navigate to ER_DataModel_PostGres v2.0.sql file. Execute the opened file by clicking on Query -> Execute. Click File -> Open and navigate to ER_CodeListData v2.0.sql file. Execute the opened file by clicking on Query -> Execute. egs_wp5_cookbook-v2.1.doc Eurogeosource Cookbook 22

23 Click File -> Open and navigate to MR_DataModel_PostGres v2.0.sql file. Execute the opened file by clicking on Query -> Execute. Click File -> Open and navigate to MR_CodeListData v2.0.sql file. Execute the opened file by clicking on Query -> Execute. To verify that the tables are present, refresh the public schema in the inspire database by rightclicking public in the pgadmin object browser. There should be 84 tables, 7 views, 790 functions and 43 sequences. egs_wp5_cookbook-v2.1.doc Eurogeosource Cookbook 23

24 7 Configuring the Web Feature Server 7.1 Creating the INSPIRE workspace The first when configuring the Web Feature Server is to alter the workspace to enable Deegree to use the INSPIRE data model and its extensions. Extract the deegree-inspire-schemas.zip to <TOMCAT_HOME>\webapps\ROOT\WEB- INF\workspace\appschemas. Create the appschemas directory if it does not exist Copy the EuroGeoSource-AM-v2.0.xsd to <TOMCAT_HOME>\webapps\ROOT\WEB- INF\workspace\appschemas. Copy the EuroGeoSource-ER-v2.0.xsd to <TOMCAT_HOME>\webapps\ROOT\WEB- INF\workspace\appschemas. Copy the EuroGeoSource-MR-v2.0.xsd to <TOMCAT_HOME>\webapps\ROOT\WEB- INF\workspace\appschemas. 7.2 Creating the INSPIRE database connection Open a browser and navigate to the Deegree Web Feature Service. Enter the username and password. Navigate to jdbc connections Create a new JDBC Connection, named inspire. egs_wp5_cookbook-v2.1.doc Eurogeosource Cookbook 24

25 Enter the details: Host DB type DB name Username Password localhost PostGIS inspire inspire inspire Click Test Connection to test the JDBC connection. Click Create to create the JDBC connection if the test was successful. 7.3 Creating the INSPIRE feature store Navigate to feature stores Enter a name for the feature store, e.g. inspire and select SQL from the drop down box. Click Create new. egs_wp5_cookbook-v2.1.doc Eurogeosource Cookbook 25

26 Select the option to Create config manually and select the JDBC Connection inspire (from step 7.2) Click Ok. egs_wp5_cookbook-v2.1.doc Eurogeosource Cookbook 26

27 In the editing window, clear the existing text and copy-paste the mapping information from the Deegree_mapping-ER-v2.0-MR-v2.0.xml file. Finally, click on Save. egs_wp5_cookbook-v2.1.doc Eurogeosource Cookbook 27

28 7.4 Creating the INSPIRE Web Feature Service Navigate to web services. Enter the name WFS and type of the service, e.g. WFS and click on Create new. In the dialog that appears the configuration of the WFS can be altered. In the dialog below an example configuration is shown. Please note there is no logical connection to the configured feature store or jdbc connection. All feature stores are included in the WFS by default. egs_wp5_cookbook-v2.1.doc Eurogeosource Cookbook 28

29 Please change the announced CRS to the European situation. To use ETRS89 specify EPSG:4258 <deegreewfs xmlns=" xmlns:xsi=" configversion="3.0.0" xsi:schemalocation=" <!-- [0...1] Activated OGC protocol versions, default: activate all implemented versions --> <SupportedVersions> <Version>1.0.0</Version> <Version>1.1.0</Version> </SupportedVersions> <!-- [0...1] Enable transactions (WFS-T operations), default: disabled --> <EnableTransactions>true</EnableTransactions> <!-- [0...1] Disable response buffering (allows rollback for generating clean exception reports, but hinders streaming), default: true --> <DisableResponseBuffering>true</DisableResponseBuffering> <!-- [0...n] Announced CRS, default: EPSG: > <QueryCRS>EPSG:4258</QueryCRS> <!-- [0...n] Output / input format configuration, default: GML 2.1, 3.0, 3.1, > <GMLFormat gmlversion="gml_32"> <!-- [1] Mime type handled by this format configuration --> <MimeType>text/xml; subtype=gml/3.2.1</mimetype> <!-- [0...1] Customization for GetFeature responses --> <GetFeatureResponse xmlns:gml=" <!-- [0...1] Qualified root element name for GetFeature response --> <ContainerElement>gml:FeatureCollection</ContainerElement> <!-- [0...1] Feature member element name for GetFeature response --> <FeatureMemberElement>gml:featureMember</FeatureMemberElement> <!-- [0...1] Value to add to xsi:schemalocation attribute (to define the container element) --> <AdditionalSchemaLocation>> <!-- [0...1] Disable output streaming (positive effect: numberoffeature attribute / gml:boundedby can be included in GetFeature responses) --> <DisableStreaming>false</DisableStreaming> </GetFeatureResponse> </GMLFormat> </deegreewfs> Example configuration file for a Deegree WFS Click Save when done. You have now completed the steps necessary to complete the creation of an INSPIRE compliant Web Feature Service. egs_wp5_cookbook-v2.1.doc Eurogeosource Cookbook 29

30 8 Loading data 8.1 Available software Data can be loaded into the PostgreSQL database using the SQL interface. The difficulty of loading data depends on the ability of the selected tool to insert or update spatial objects. Luckily there are several software products available on the market for this purpose. The following list contains a few of the available tools which support the processing of spatial data into a PostgreSQL / PostGIS database. PostgreSQL pgadmin III Pentaho Data Integration (GeoKettle) Talend Open Studio Safe software FME ESRI ArcGIS Desktop 8.2 Database - Loading strategy The ManagementZone table is central to both EnergyResource and MineralResource models. If possible, these zones should be inserted first when loading data into the model. The Energy Resource data model is in essence a simple one. There are a couple of central tables, EnergyResouce, ResourceRegion and EnergyProducingCountry, on which nearly all other tables depend with a foreign key relationship. The other tables ReportingInformation, ResourceAmount, EnergyProducingCountry can be filled as soon as the central table is populated. The Mineral Resource datamodel is bigger than the Energy Resource datamodel, but the same principles apply. The central tables are: MineralOccurrence, Mine and MineralProducingCountry. 8.3 Database - Keys Primary keys of all feature and data tables will be generated automatically if no value is specified when a record is inserted. The Postgres implementation uses a separate sequence for each table while the Oracle implementation uses a sequence for each module (ER, MR and AM). To make it easier to delete features, foreign keys to parent tables are defined such that child records will be deleted when the parent record is deleted. Foreign keys to codelist tables are defined such that codes can be added to codelists or that existing codes can be modified (Postgres only). 8.4 Database - INSPIRE ID The INSPIRE identifiers are an important part when exchanging data with other parties. The combination should result in a unique identifier and will be used by external applications to reference the spatial object. The Inspire identifier should not change in time. An INSPIRE ID consists of two required fields: a namespace and a local identifier. The optional version field is not used within EGS. To ensure the INSPIRE ID s uniqueness and reproducibility over time, we egs_wp5_cookbook-v2.1.doc Eurogeosource Cookbook 30

31 advise the partners to use their own (national) unique identifiers as the local identifier. Not introducing a totally new identifier will also help the partners to recognize the data once it is transformed. The namespace, which includes the country code, will ensure all partners will use a unique identifier. The namespace is used to identify the datasource and should start with a 2-digit country code. For use within EGS it is recommended to encode the namespace according to: <countrycode><tablename> (NLEnergyResource for instance). Namespaces will eventually be registered in the Inspire Namespaces Register to guarantee uniqueness. The local identifier should be unique within the datasource and may be a UUID (universally unique identifier) Database - Validating data Flat data relationships are preserved using foreign key constraint. Unfortunately, using this construct, there is no guaranteeing that in a one-to-many relationship that a parent can have at least one child. This problem can be solved by running a query which will identify missing child relations and removing their parents from the database. Another strategy is to add children with dummy values. 8.6 Database - Validating geometry Geometries can be validated by using the PostGIS function ST_IsValid(Geometry). ST_IsValidReason(geometry) can be used to determine the reason why a geometry is invalid. Geometries which are invalid cannot be repaired. They should be fixed externally before moving them into the data model. 8.7 Web Feature Service - Refresh After loading new data into the database, make sure to reload the Web Feature Service. Deegree keeps a cache as soon as it is has queried the database. To make sure this cache is cleared, you should use the reload function. This can be done by clicking on the Reload link in the top left corner of the Deegree console. 1 The Postgres uuid-ossp function uuid_generate_v5(uuid_ns_url(),<text>) may be used to generate reproducible UUID s that depend on <text> only. egs_wp5_cookbook-v2.1.doc Eurogeosource Cookbook 31

32 9 Deployment The deployment of the database and the Web Feature Service onto a server will be different from what is described in this cookbook. For instance, the database and service can be deployed onto different machines. The configuration steps described in the previous chapters of this cookbook can be easily translated to your specific server setup. Other issues which might arise are described in this chapter. 9.1 Deploying the relational database Data can be pushed directly from a source database into the Web Feature database or the data can be prepared on a local computer. When using a local computer to prepare all the data pgadmin III can be used to generate an SQL insert script which can then be executed on the server. To create such a file: Open pgadmin III, and navigate to the inspire schema. Then right click the public schema and select Backup. Next, enter the file options and specify where the file should be saved. Also specify PLAIN as the format. In the second tab, Dump Options #1, check the option to use insert commands. Also check the option tho use Only data. On the Objects tab specify the tables you wish to export. When done click on OK to create the sql file. Once the file has been created, it can be executed as an SQL script on the server using the pgadmin III tool. Please make sure to truncate all the data before restoring the backup you have made on your local machine. Cascading delete constraints, which are already present in the database, will help to reduce the number of tables which have to be truncated. In the ER model these are: EnergyResouce, ResourceRegion and EnergyProducingCountry. In the MR model, these are: MineralOccurrence, Mine and MineralProducingCountry. In the AM model, this is: ManagementZone. egs_wp5_cookbook-v2.1.doc Eurogeosource Cookbook 32

33 9.2 Deploying the Web Feature Service The URL which exposes the service must be available to the internet. Using a reverse proxy such as Apache Web Server for security reasons is possible, but there is a small problem: By default Deegree is deployed as a ROOT webapp, which is an issue when deploying multiple webapps in the same instance of tomcat. If Deegree is deployed on a separate dedicated (virtual) machine, this is not a problem. Renaming the Deegree webapp from ROOT to a different name, e.g. deegree would solve the problem of deploying multiple webapps within the same Tomcat. The url will change from to Deploying the Web Feature Service behind a reverse proxy It is possible to deploy the Web Feature Service behind a reverse proxy. Apache Web Server can be used to this end. When deployment is done this way there are some configuration steps to keep in mind. In the example below Apache is configured as a reverse proxy (and forwards traffic) to Tomcat. Apache needs to be listening on a different port than Tomcat, e.g. Apache on 80 and Tomcat on Both applications need to be configured to achieve this. 1. Install Apache Web Server 2. Install mod_jk for Apache 3. Configure the <APACHE_HOME>/conf/httpd.conf Insert this section after the load modules section. The paths in the example below need to be modified for your situation. <IfModule!mod_jk.c> LoadModule jk_module "C:/Apache/Apache22/modules/mod_jk.so" </IfModule> JkWorkersFile "C:/Apache/Apache22/conf/workers.properties" JkLogFile "C:/Apache/Apache22/logs/mod_jk.log" JkLogLevel emerg 4. Add workers.properties file in <APACHE_HOME>/conf Insert the following configuration details worker.list=tomcat #tomcat worker definition: worker.tomcat.type=ajp13 worker.tomcat.host=localhost worker.tomcat.port=8009 worker.tomcat.socket_keepalive=1 5. Configure Tomcat s server.xml file (located in <TOMCAT_HOME>/conf) so it listens on AJP port Although it is setup to do so by default, please make sure the following line is enabled <!-- Define an AJP 1.3 Connector on port > <Connector port="8009" protocol="ajp/1.3" redirectport="8443" /> egs_wp5_cookbook-v2.1.doc Eurogeosource Cookbook 33

34 6. Configure Tomcat server.xml file (located in <TOMCAT_HOME>/conf) so it knows it is running behind a reverse proxy. This allows Tomcat to translate any relative URL s correctly and use Apache s hostname or address instead of the machine where Tomcat is deployed. Find the connector configuration and add the proxyname and proxyport attributes <Connector port="8009" protocol="ajp/1.3" connectiontimeout="20000" redirectport="8443" proxyname="dinolab52.dinonet.nl" proxyport="80" /> As a side note: These attributes can also be applied to the HTTP connector when using mod_proxy instead of mod_jk. 7. Configure the <APACHE_HOME>/conf/httpd.conf and add or modify the virtual host section to forward all traffic destined for your WFS from Apache to Tomcat <VirtualHost dinolab52.dinonet.nl:80> DocumentRoot "C:/Apache/Apache22/htdocs" ServerName dinolab52.dinonet.nl <Location /> #Options +Indexes +FollowSymLinks AllowOverride None Order deny,allow Allow from all Satisfy all </Location> JkMount /* tomcat </VirtualHost> Restart Apache and Tomcat. 9.4 Testing the Web Feature Service with a browser Rudimentary testing can be performed in a web browser. The following URL s can be used to check if all data is properly returned from the Web Feature Service. GS_ManagementRestrictionOrRegulationZone egs_wp5_cookbook-v2.1.doc Eurogeosource Cookbook 34

35 Testing the Web Feature Service with Gaia 1. Download Gaia from: 2. In Gaia add the URL of the service to the services list. Then select a feature type from the feature list. As you can see, no preview is shown. 3. Uncheck maximum features and use bounding-box filter. Then select GML3_2 as the GML version. Then a preview is shown. In version you also have to check the option reverse x/y to get a presentable result. In previous versions of Gaia 3 this was not necessary to do this reversal. egs_wp5_cookbook-v2.1.doc Eurogeosource Cookbook 35

36 4. Click Add Layer. Below is an example of the EGS_NonRenewableEnergyResources layer. 5. Done. egs_wp5_cookbook-v2.1.doc Eurogeosource Cookbook 36