deegree Web Catalogue Service

v.2.1

Change log

1 Introduction

deegree is a Java Framework offering the main building blocks for Spatial Data Infrastructures (SDIs). Its entire architecture is developed using standards of the Open Geospatial Consortium (OGC) and ISO Technical Committee 211 – Geographic information / Geoinformatics (ISO/TC 211). deegree encompasses OGC Web Services as well as clients. deegree is Free Software protected by the GNU Lesser General Public License (GNU LGPL) and is accessible at http://www.deegree.org.

deegree2 is the new release of deegree supporting a number of features that deegree1 was not able to handle. This documentation describes setup and configuration of the deegree Web Catalogue Service (CSW), an implementation of OGC's Catalogue Service Implementation Specification 2.0.0 and the ISO 19115 / 19119 Application Profile 0.9.3.

deegree's Web Catalogue Service implementation (Catalogue Service – Web profile, therefore CS-W) is able to serve different metadata formats in parallel based on the same physical datastore. This is possible because deegree CS-W uses XSLT processing to transform requests as well as responses into the desired format. deegree CS-W does not contain its a data access modul of its own. It uses an OGC WFS (at the moment limited to deegree WFS) as datasource. So in future it will be possible to use deegree CS-W on top of any other OGC compliant WFS to offer catalogue functionalities.

As deegree WFS is extremely flexible in regard to supporting different database schemas, it is possible to adjust deegree CS-W to almost any existing metadata base – without the need for replication.

Besides the CSW, deegree comprises a number of additional services and clients. A complete list of deegree components can be found at:

http://www.lat-lon.de → Products

Downloads of packaged deegree components can be found at:

http://www.deegree.org → Download

deegree's Web Catalogue Service offers great flexibility regarding it's configuration and output formats. It works with a wide range of physical data sources and server environments. The configuration of CSW is similar to the configuration of other deegree Web Services and requires the editing of XML files which control the functionality of the server.

deegree CS-W is an implementation of the OpenGIS® Catalogue Services Specification 2.0 - ISO19115/ISO19119 Application Profile for CSW 2.0 version 0.9.3 (in short: ISO APP; OGC project document 04-038r2). It supports the operations:

• GetCapabilities

• DescribeRecord

• GetRecords

• GetRecordByID

• Transaction and

• Harvest

It even extends the Harvest-operation by the possibility to harvest other Catalogue Serivces as a whole (a behaviour not specified by the ISO APP and the CS-W 2.0 specification).

The web services of deegree are realized as Java modules controlled by one central servlet (the “dispatcher”). This servlet has to be deployed to the respective web server/servlet engine. Most of the common web servers support servlet technology, thus making deegree a universal product. The Apache-Tomcat 5.5 Servlet-Engine is recommended due to its widespread use and its status as an open-source product.

2 Download / Installation

2.1Prerequisites

For deegree2 Web Catalogue Service to run you need:

• Java (JRE or JSDK) version 1.5.x

• Tomcat 5.5.x

• PostgreSQL 8.0 + PostGIS 1.0.x

For installation of these components refer to the corresponding documentation at java.sun.com tomcat.apache.org, http://www.postgresql.org/ and http://www.postgis.org/.

2.2deegree Web Catalogue Service release

deegree Web Catalogue Service can be downloaded from http://www.deegree.org. The release is packed as a WAR-archive. Simply put this file into your $TOMCAT_HOME$/webapps directory and (re-)start Tomcat. The installation of deegree WFS is already done with this.

Note: It is also possible to extract the WAR archive into another place of your computer and direct Tomcat to this place. Because of this possibility, in the remainder of this document, the directory you extracted the files to is referred to as $csw_home$ (=$TOMCAT_HOME$/webapps/deegree-csw in the standard case).

Your $csw_home$ will contain the following structure:

Table 1: Directory structure of the CSW release

2.3Setting up the example database

Create a database within PostgreSQL with UTF-8 Encoding (consult the according PostgreSQL and PostGIS documentation). After that execute the according SQL script create_database.sql located in $csw_home$/WEB-INF/conf/scripts.

Then you have to connect the catalogue against the PostgreSQL instance in the file WEB-INF/conf/csw/featuretypes/csw.xsd like this, where csw is the name of your database:

<xsd:appinfo>

<deegreewfs:Prefix>app</deegreewfs:Prefix>

<deegreewfs:Backend>POSTGIS</deegreewfs:Backend>

<deegreewfs:DefaultSRS>EPSG:4326</deegreewfs:DefaultSRS>

<JDBCConnection xmlns="http://www.deegree.org/jdbc">

<Driver>org.postgresql.Driver</Driver>

<Url>jdbc:postgresql://localhost:5432/csw</Url>

<User>USERNAME</User>

<Password>PASSWORD</Password>

<SecurityConstraints/>

<Encoding>iso-8859-1</Encoding>

</JDBCConnection>

<deegreewfs:SuppressXLinkOutput>true</deegreewfs:SuppressXLinkOutput>

</xsd:appinfo>

2.4Testing the installation

The deegree CS-W demo download comes pre-configured for accessing a Postgis database. The database can be filled with a few example metadataset to enable to perform a few example requests. Metadata datasets will find it's way into the database via a Transaction Insert request which can be sent via the generic client located under the url http://yourservername:port/deegree-csw/client/client.html. Go to the 'Request' dropdown menue, choose 'Transaction' -> 'inert_all.xml' and finally 'Send' the Transaction request. For further testing you have two options. Some example requests for demonstration of the principle behavior of the service will be explained in the following sections. You can also use the generic client to communicate with the CS-W. Just check out the example requests in the dropdown menue.

request 1:

http://my.server.domain/deegree-csw/services?SERVICE=CSW&ACCEPTVERSION=2.0.0&REQUEST=GetCapabilities

result:

<?xml version="1.0" encoding="UTF-8"?>

<csw:Capabilities xmlns:csw="http://www.opengis.net/cat/csw"

xmlns:deegree="http://www.deegree.org/csw" xmlns:ogc="http://www.opengis.net/ogc"

xmlns:ows="http://www.opengis.net/ows" xmlns:xlink="http://www.w3.org/1999/xlink"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" updateSequence="0" version="2.0.0">

<ows:ServiceIdentification>

<ows:ServiceType>CSW</ows:ServiceType>

<ows:ServiceTypeVersion>2.0.0</ows:ServiceTypeVersion>0

<ows:Title>deegree 2.1 CSW test</ows:Title>

<ows:Abstract>abstract</ows:Abstract>

<ows:Keywords>

<ows:Keyword>deegree</ows:Keyword>

</ows:Keywords>

<ows:Fees>NO FEES - IT'S FREE</ows:Fees>

<ows:AccessConstraints>NONE</ows:AccessConstraints>

</ows:ServiceIdentification>

<ows:ServiceProvider>

<ows:ProviderName>lat/lon GmbH</ows:ProviderName>

<ows:ProviderSite xlink:href="http://www.latlon.de" xlink:type="simple" />

<ows:ServiceContact>

<ows:IndividualName />

<ows:ContactInfo>

<ows:Phone>

<ows:Voice>++49 228 18496-0</ows:Voice>

<ows:Facsimile>++49 228 18496-29</ows:Facsimile>

</ows:Phone>

<ows:Address>

<ows:DeliveryPoint>Aennchenstr. 19</ows:DeliveryPoint>

<ows:DeliveryPoint>basement</ows:DeliveryPoint>

<ows:City>Bonn</ows:City>

<ows:AdministrativeArea>NRW</ows:AdministrativeArea>

<ows:PostalCode>53177</ows:PostalCode>

<ows:Country>Germany</ows:Country>

<ows:ElectronicMailAddress>info@lat-lon.de</ows:ElectronicMailAddress>

</ows:Address>

<ows:OnlineResource xlink:href="http://localhost:8080/deegree-csw/services"

xlink:type="simple" />

<ows:HoursOfService>9am-17pm</ows:HoursOfService>

<ows:ContactInstructions>personal</ows:ContactInstructions>

</ows:ContactInfo>

<ows:Role>PointOfContact</ows:Role>

</ows:ServiceContact>

</ows:ServiceProvider>

<ows:OperationsMetadata>

<ows:Operation name="GetCapabilities">

<ows:DCP>

<ows:HTTP>

<ows:Get xlink:href="http://localhost:8080/deegree-csw/services"

xlink:type="simple" />

</ows:HTTP>

</ows:DCP>

</ows:Operation>

<ows:Operation name="DescribeRecord">

<ows:DCP>

<ows:HTTP>

<ows:Get xlink:href="http://localhost:8080/deegree-csw/services"

xlink:type="simple" />

<ows:Post xlink:href="http://localhost:8080/deegree-csw/services"

xlink:type="simple" />

</ows:HTTP>

</ows:DCP>

<ows:Parameter name="typeName">

<ows:Value>csw:dataset</ows:Value>

<ows:Value>csw:datasetcollection</ows:Value>

<ows:Value>csw:application</ows:Value>

<ows:Value>csw:service</ows:Value>

</ows:Parameter>

<ows:Parameter name="outputFormat">

<ows:Value>text/xml</ows:Value>

</ows:Parameter>

<ows:Parameter name="schemaLanguage">

<ows:Value>XMLSCHEMA</ows:Value>

</ows:Parameter>

</ows:Operation>

<ows:Operation name="GetRecords">

<ows:DCP>

<ows:HTTP>

<ows:Post xlink:href="http://localhost:8080/deegree-csw/services"

xlink:type="simple" />

</ows:HTTP>

</ows:DCP>

<ows:Parameter name="typeName">

<ows:Value>csw:dataset</ows:Value>

<ows:Value>csw:datasetcollection</ows:Value>

<ows:Value>csw:application</ows:Value>

<ows:Value>csw:service</ows:Value>

</ows:Parameter>

<ows:Parameter name="outputFormat">

<ows:Value>text/xml</ows:Value>

</ows:Parameter>

<ows:Parameter name="outputSchema">

<ows:Value>DublinCore</ows:Value>

<ows:Value>csw:profile</ows:Value>

</ows:Parameter>

<ows:Parameter name="resultType">

<ows:Value>RESULTS</ows:Value>

</ows:Parameter>

<ows:Parameter name="elementSetName">

<ows:Value>brief</ows:Value>

<ows:Value>summary</ows:Value>

<ows:Value>full</ows:Value>

</ows:Parameter>

</ows:Operation>

<ows:Operation name="GetRecordById">

<ows:DCP>

<ows:HTTP>

<ows:Get xlink:href="http://localhost:8080/deegree-csw/services"

xlink:type="simple" />

<ows:Post xlink:href="http://localhost:8080/deegree-csw/services"

xlink:type="simple" />

</ows:HTTP>

</ows:DCP>

</ows:Operation>

<ows:Operation name="Transaction">

<ows:DCP>

<ows:HTTP>

<ows:Post xlink:href="http://localhost:8080/deegree-csw/services"

xlink:type="simple" />

</ows:HTTP>

</ows:DCP>

</ows:Operation>

</ows:OperationsMetadata>

<ogc:Filter_Capabilities>

<ogc:Spatial_Capabilities>

<ogc:Spatial_Operators>

<ogc:BBOX />

</ogc:Spatial_Operators>

</ogc:Spatial_Capabilities>

<ogc:Scalar_Capabilities>

<ogc:Logical_Operators />

<ogc:Comparison_Operators>

<ogc:Like />

</ogc:Comparison_Operators>

<ogc:Arithmetic_Operators>

<ogc:Simple_Arithmetic />

</ogc:Arithmetic_Operators>

</ogc:Scalar_Capabilities>

</ogc:Filter_Capabilities>

</csw:Capabilities>

request2:

http://my.server.domain/deegree-csw/services?SERVICE=CSW&ACCEPTVERSION=2.0.0&REQUEST=GetCapabilities&Sections=OperationsMetadata

result:

<?xml version="1.0" encoding="UTF-8"?>

<csw:Capabilities xmlns:csw="http://www.opengis.net/cat/csw"

xmlns:deegree="http://www.deegree.org/csw" xmlns:ogc="http://www.opengis.net/ogc"

xmlns:ows="http://www.opengis.net/ows" xmlns:xlink="http://www.w3.org/1999/xlink"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" updateSequence="0" version="2.0.0">

<ows:OperationsMetadata>

<ows:Operation name="GetCapabilities">

<ows:DCP>

<ows:HTTP>

<ows:Get xlink:href="http://localhost:8080/deegree-csw/services"

xlink:type="simple" />

</ows:HTTP>

</ows:DCP>

</ows:Operation>

<ows:Operation name="DescribeRecord">

<ows:DCP>

<ows:HTTP>

<ows:Get xlink:href="http://localhost:8080/deegree-csw/services"

xlink:type="simple" />

<ows:Post xlink:href="http://localhost:8080/deegree-csw/services"

xlink:type="simple" />

</ows:HTTP>

</ows:DCP>

<ows:Parameter name="typeName">

<ows:Value>csw:dataset</ows:Value>

<ows:Value>csw:datasetcollection</ows:Value>

<ows:Value>csw:application</ows:Value>

<ows:Value>csw:service</ows:Value>

</ows:Parameter>

<ows:Parameter name="outputFormat">

<ows:Value>text/xml</ows:Value>

</ows:Parameter>

<ows:Parameter name="schemaLanguage">

<ows:Value>XMLSCHEMA</ows:Value>

</ows:Parameter>

</ows:Operation>

<ows:Operation name="GetRecords">

<ows:DCP>

<ows:HTTP>

<ows:Post xlink:href="http://localhost:8080/deegree-csw/services"

xlink:type="simple" />

</ows:HTTP>

</ows:DCP>

<ows:Parameter name="typeName">

<ows:Value>csw:dataset</ows:Value>

<ows:Value>csw:datasetcollection</ows:Value>

<ows:Value>csw:application</ows:Value>

<ows:Value>csw:service</ows:Value>

</ows:Parameter>

<ows:Parameter name="outputFormat">

<ows:Value>text/xml</ows:Value>

</ows:Parameter>

<ows:Parameter name="outputSchema">

<ows:Value>DublinCore</ows:Value>

<ows:Value>csw:profile</ows:Value>

</ows:Parameter>

<ows:Parameter name="resultType">

<ows:Value>RESULTS</ows:Value>

</ows:Parameter>

<ows:Parameter name="elementSetName">

<ows:Value>brief</ows:Value>

<ows:Value>summary</ows:Value>

<ows:Value>full</ows:Value>

</ows:Parameter>

</ows:Operation>

<ows:Operation name="GetRecordById">

<ows:DCP>

<ows:HTTP>

<ows:Get xlink:href="http://localhost:8080/deegree-csw/services"

xlink:type="simple" />

<ows:Post xlink:href="http://localhost:8080/deegree-csw/services"

xlink:type="simple" />

</ows:HTTP>

</ows:DCP>

</ows:Operation>

<ows:Operation name="Transaction">

<ows:DCP>

<ows:HTTP>

<ows:Post xlink:href="http://localhost:8080/deegree-csw/services"

xlink:type="simple" />

</ows:HTTP>

</ows:DCP>

<ows:Parameter name="outputSchema">

<ows:Value>DublinCore</ows:Value>

<ows:Value>csw:profile</ows:Value>

</ows:Parameter>

</ows:Operation>

</ows:OperationsMetadata>

</csw:Capabilities>

request3:

http://my.server.domain/deegree-csw/services?request=DescribeRecord&version=2.0.0&outputFormat=text/xml&schemaLanguage=XMLSCHEMA&typeName=csw:Record&namespace=csw:http://www.opengis.org/csw

result:

<?xml version="1.0" encoding="UTF-8"?>

<csw:DescribeRecordResponse xmlns:csw="http://www.opengis.net/cat/csw"

xmlns:ogc="http://www.opengis.net/ogc" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xsi:schemaLocation="http://www.opengis.net/cat/csw http://schemas.opengis.net/csw/2.0.0/CSW-discovery.xsd">

<csw:SchemaComponent schemaLanguage="XMLSCHEMA" targetNamespace="http://www.deegree.org/csw">

<xs:schema xmlns:smXML="http://metadata.dgiwg.org/smXML"

xmlns:tns="http://schemas.opengis.net/iso19115full"

xmlns:xs="http://www.w3.org/2001/XMLSchema" attributeFormDefault="unqualified"

elementFormDefault="qualified"

targetNamespace="http://schemas.opengis.net/iso19115full">

<xs:import namespace="http://metadata.dgiwg.org/smXML"

schemaLocation="./smXML/metadataEntity.xsd" />

<xs:import namespace="http://www.opengis.net/cat/csw"

schemaLocation="./csw2.0/record.xsd" />

<xs:import namespace="http://schemas.opengis.net/iso19119"

schemaLocation="./iso19119.xsd" />

<xs:complexType name="MD_Metadata_Type">

<xs:complexContent>

<xs:extension base="csw:AbstractRecordType">

<xs:sequence>

<xs:element minOccurs="0" name="fileIdentifier"

type="smXML:CharacterString_PropertyType" />

<xs:element minOccurs="0" name="language"

type="smXML:CharacterString_PropertyType" />

<xs:element minOccurs="0" name="characterSet"

type="smXML:MD_CharacterSetCode_PropertyType" />

<xs:element minOccurs="0" name="parentIdentifier"

type="smXML:CharacterString_PropertyType" />

<xs:element maxOccurs="unbounded" minOccurs="0" name="hierarchyLevel"

type="smXML:MD_ScopeCode_PropertyType" />

<xs:element maxOccurs="unbounded" minOccurs="0"

name="hierarchyLevelName" type="smXML:CharacterString_PropertyType" />

<xs:element maxOccurs="unbounded" name="contact"

type="smXML:CI_ResponsibleParty_PropertyType" />

<xs:element name="dateStamp" type="smXML:Date_PropertyType" />

<xs:element minOccurs="0" name="metadataStandardName"

type="smXML:CharacterString_PropertyType" />

<xs:element minOccurs="0" name="metadataStandardVersion"

type="smXML:CharacterString_PropertyType" />

<xs:element maxOccurs="unbounded" name="identificationInfo"

type="smXML:_MD_Identification_PropertyType" />

<xs:element maxOccurs="unbounded" minOccurs="0" name="dataQualityInfo"

type="smXML:DQ_DataQuality_PropertyType" />

<xs:element maxOccurs="unbounded" minOccurs="0"

name="spatialRepresentationInfo"

type="smXML:_MD_SpatialRepresentation_PropertyType" />

<xs:element maxOccurs="unbounded" minOccurs="0"

name="referenceSystemInfo"

type="smXML:MD_ReferenceSystem_PropertyType" />

<xs:element maxOccurs="unbounded" minOccurs="0" name="contentInfo"

type="smXML:_MD_ContentInformation_PropertyType" />

<xs:element minOccurs="0" name="distributionInfo"

type="smXML:MD_Distribution_PropertyType" />

</xs:sequence>

</xs:extension>

</xs:complexContent>

</xs:complexType>

<xs:element name="MD_Metadata" substitutionGroup="csw:AbstractRecord"

type="tns:MD_Metadata_Type" />

<xs:complexType name="MD_Metadata_PropertyType">

<xs:choice>

<xs:element ref="tns:MD_Metadata" />

<xs:element ref="smXML:Reference" />

</xs:choice>

</xs:complexType>

</xs:schema>

</csw:SchemaComponent>

</csw:DescribeRecordResponse>

3 Architecture

As mentioned above deegree CS-W doesn't contain any direct data access modules. It uses deegree WFS through its API or – in future releases – any OGC WFS its their web interface. So deegree CS-W can be seen as a kind of facade on top a WFS offering components for transforming incoming catalogue requests into WFS requests and transforming WFS responses into CS-W responses.

Figure 1: deegree CS-W architecture

4 Basic configuration

4.1Structure of the configuration files

The following figure shows the relationships between the different configuration files that have to be adjusted:

Figure 2 File dependencies for deegree CSW configuration

4.2The deegree CS-W configuration document

The basic configuration allows usage of the full set of parameters that can be used for controlling the deegree CS-W. This includes the parameters mentioned in the OGC CS-W 2.0.0 specification for the Capabilities document, but also additional technical parameters.

In the following, the elements of the configuration file (an extended Capabilties document) will be described in detail. It is located at $csw_demo$/WEB-INF/conf/csw/csw_capabilities.xml. Appendix A includes an example of a complete configuration/capabilities document.

4.2.1deegree-Parameters

The <DefaultOnlineResource> is the URL by which the CS-W operations can be invoked. This parameter can be overwritten by the URLs defined in the request-definitions. Both parameters are mandatory. You have to adjust the <DefaultOnlineResource> to your system.

<deegree:deegreeParams>

<deegree:DefaultOnlineResource xlink:type="simple" xlink:href="http://localhost:8080/deegree-csw/services"/>

<deegree:CacheSize>100</deegree:CacheSize>

<deegree:RequestTimeLimit>60</deegree:RequestTimeLimit>

<deegree:Encoding>ISO-8859-1</deegree:Encoding>

<deegree:TransactionInputXSLT xlink:type="simple" xlink:href="transaction.xsl"/>

<deegree:TransactionOutputXSLT xlink:type="simple" xlink:href="transactionOut.xsl"/>

<!-- this parameter will be used to define the default schema used by the catalogue if OUTPUTSCHEMA parameter is missing. According to CS-W specification this must be OGCCORE which is not useful for GetRecordById requests -->

<deegree:DefaultOutputSchema>csw:profile</deegree:DefaultOutputSchema>

<deegree:WFSResource xlink:type="simple" xlink:href="wfs_capabilities.xml"/>

</deegree:deegreeParams>

The <CacheSize> parameter defines the size of the cache available to deegree-CS-W in megabyte. This parameter is optional, its default value is 100 MB. By <RequestTimeLimit> the maximum time span is defined in seconds after which a request has to be processed. If this value is exceeded the processing is cancelled and an exception will be thrown. Its default value is 30 seconds. The encoding element defines the default character encoding to be used within the catalogue if embedded sources doesn't provide encoding informations. This element is optional, default value is 'UTF-8'.

Because deegree CS-W uses a WFS as datasource one must define the WFS to be used. This is done by setting the WFSResource element. If it's missing it is assumed that a file named 'wfs_capabilities.xml' is available in the same directory as the catalogue capabilities file. deegree CS-W also uses this element to determine if a WFS is 'local' or 'remote'. A 'local' WFS will be connected through the deegree API; a 'remote' WFS uses HTTP connections defined by the OGC WFS 1.0.0 specification. A WFS will be handled as being 'local' if the capabilities document is referenced by a file URL or a relative path. Using a HTTP URL will force treating a WFS as 'remote'.

4.2.2ServiceIdentification

The ServiceIdentification section is required for giving basic informations about the a CS-W to the client/user. This information may be used to manage several catalogues within one client or to store a catalogue metadata in another catalogue. For details see OGC Catalogue Service 2.0.0 and the OWS Common specification.

<ows:ServiceIdentification>

<ows:ServiceType>CSW</ows:ServiceType>

<ows:ServiceTypeVersion>2.0.0</ows:ServiceTypeVersion>

<ows:Title>deegree v2.1 demo CSW</ows:Title>

<ows:Abstract>abstract</ows:Abstract>

<ows:Keywords>

<ows:Keyword>deegree</ows:Keyword>

</ows:Keywords>

<ows:Fees>NO FEES - IT'S FREE</ows:Fees>

<ows:AccessConstraints>NONE</ows:AccessConstraints>

</ows:ServiceIdentification>

4.2.3ServiceProvider

This section provides informations about the person(s) and organisation(s) making a catalogue available. For details see OGC Catalogue Service 2.0.0 and the OWS Common specification.

4.2.4OperationsMetadata

The OperationsMetadata sections provides information about each operation offered by a catalogue. Mainly these are the names of the operations and the parameters that have to be passed to them. Each parameter can be assigned to a list of possible values. At the moment deegree CS-W supports GetCapabilities, GetRecords, DescribeRecord, GetRecordById, Transaction and Harvest operations.

For the parameter 'outputSchema' of the GetRecords operation deegree introduces two additional attributes.

<ows:Parameter name="outputSchema">

<ows:Value deegree:input="inDC.xsl" deegree:output="outDC.xsl">DublinCore</ows:Value>

<ows:Value deegree:input="in_csw_profile.xsl" deegree:output="out_csw_profile.xsl">csw:profile</ows:Value>

</ows:Parameter>

The first additional attribute 'deegree:input' references a XSLT script that will be used to transform an incoming GetRecord request into a GetFeature request that will be understood by the underlying WFS. Vice versa the script referenced by 'deegree:output' transforms the feature collection returned from the WFS into a XML document that validates against the schema referenced by 'deegree:schema' attribute of the typeName parameter.

<ows:Parameter name="typeName">

<ows:Value deegree:schema="iso19115_be_bb_full.xsd">csw:dataset</ows:Value>

<ows:Value deegree:schema="iso19115_be_bb_full.xsd">csw:datasetcollection</ows:Value>

<ows:Value deegree:schema="iso19115_be_bb_full.xsd">csw:application</ows:Value>

<ows:Value deegree:schema="iso19119.xsd">csw:service</ows:Value>

</ows:Parameter>

This always should be referenced through an HTTP URL even if a relative path or a FILE URL is valid too. This schema will also be returned when performing a DescribeRecord request agaist a type. Details about how to construct the in- and out-scripts will be discussed below.

For general information on how to define service operations in a catalogues capabilities document see OGC Catalogue Service 2.0.0 and OWS Common specification.

4.2.5Filter_Capabilities

The last section of the capabilities document contains a description of the capabilities of the filter functions offered by a catalogue. You can leave this as it comes with the demo installation because this represents the current capabilities of the deegree Filter Encoding implementation. For details see OGC Catalogue Service 2.0.0, OWS Common and Filter Encoding specification.

5 Advanced configuration

5.1Manual Tomcat integration

The location of deegree's libraries and the central deegree configuration file csw_capabilities.xml should be registered with the Servlet Engine (in this case Apache Tomcat 5.5). Tomcat offers several possibilities to register and configure web contexts.

The easiest way to register deegree web services with Tomcat is to copy the deegree-csw.war file to the $TOMCAT_HOME$/webapps directory. You can do this either with running or stopped tomcat. If the tomcat is started afterwards, the application should be automatically deployed. Tomcat will unpack the deegree-wfs.war file (which is nothing more than a .zip file) to the webapps directory automatically. The name of the .war sets the name of the service address:

http://localhost:8080/deegree-csw

If you want to do the Tomcat installation process manually use the steps described in the following.

Unpack the deegree-csw.war to a directory (e.g. c:/deegree/webapps/deegree-csw) of your choice.

Afterwards Tomcat needs information about the root directory of the WFS. The easiest way is to create a XML-file in the directory $TOMCAT_HOME$/conf/Catalina/localhost, named the same as the service e.g. deegree-wfs.xml, and fill it with the following information

<Context docBase="c:/deegree/webapps/deegree-csw" path="/deegree-csw">

</Context>

where the docBase attribute reflects the physical location of the deegree service in the file system and the path attribute describes the virtual location of the main directory of the deegree web service. In the example, the root directory of the service is accessible at http://my.server.domain/deegree-csw/. For further information have a look at the Tomcat documentation included with the installation.

The name of the deegree-service directory is arbitrary whereas Tomcat definitely looks for a subdirectory WEB-INF (in capital letters – even on a Windows system) in the root directory. You will find this directory after tomcat automatically unpacked the war archive. Here the Deployment-Descriptor (web.xml) is located, which is analysed by Tomcat to identify the servlet(s) belonging to the application, their names, the parameters that are delivered to the servlet(s) and information about the existing access restrictions.

Before starting deegree WFS the following dataset entry in web.xml is essential:

<?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN"

"http://java.sun.com/j2ee/dtds/web-app_2.2.dtd">

<web-app>

<description>deegree v2.1 demo CSW</description>

<filter>

<filter-name>SOAPFilter</filter-name>

<filter-class>org.deegree.enterprise.servlet.SOAPFacadeServletFilter</filter-class>

</filter>

<servlet>

<servlet-name>services</servlet-name>

<servlet-class>org.deegree.enterprise.servlet.OGCServletController</servlet-class>

<init-param>

<param-name>services</param-name>

<param-value>csw</param-value>

<description>list of supported services, e.g.: wfs,wms (comma separated) allways use lowercase</description>

</init-param>

<init-param>

<param-name>wfs.handler</param-name>

<param-value>org.deegree.enterprise.servlet.WFSHandler</param-value>

</init-param>

<init-param>

<param-name>wfs.config</param-name>

<param-value>WEB-INF/conf/csw/wfs_capabilities.xml</param-value>

</init-param>

<init-param>

<param-name>csw.handler</param-name>

<param-value>org.deegree.enterprise.servlet.CSWHandler</param-value>

</init-param>

<init-param>

<param-name>csw.config</param-name>

<param-value>WEB-INF/conf/csw/csw_capabilities.xml</param-value>

</init-param>

<load-on-startup>1</load-on-startup>

</servlet>

<!--

<filter-mapping>

<filter-name>SOAPFilter</filter-name>

<url-pattern>/services</url-pattern>

</filter-mapping>

-->

<servlet-mapping>

<servlet-name>services</servlet-name>

<url-pattern>/services</url-pattern>

</servlet-mapping>

<welcome-file-list>

<welcome-file>welcome.html</welcome-file>

<welcome-file>index.jsp</welcome-file>

</welcome-file-list>

</web-app>

The name of the servlet and of the java-class representing the servlet should be indicated in the <servlet> tags. The servlet-name can be user defined, but care should be taken that the same name that is defined here is also used in the servlet-mapping. The servlet is located in the deegree2.jar library.

The tag <init-param> defines parameters that are analyzed by the servlet, while initializing. The transferred parameters are

• 'services': The value of this parameter contains a comma separated list of OWS that will be made available through the context. In the example only a 'csw' is defined to be available (other possible values at the moment are: wfs, wcs, sos, wpvs and csw).

• For each service listed in the 'service' init-param a handler class and a configuration file must be referenced.

• The name of the init-param for defining the handler starts with the service name ('wfs' in the example) followed by '.handler'. The value of this parameter is the name of the handler class to be used. It is possible to write a different class for this and reference it accordingly. As default ' org.deegree.enterprise.servlet.WFSHandler' should be used.

• The name of the init-param for defining the main configuration file of a service also starts with the service name followed by '.config'. Notice that you can use a relative path to the configuration file starting at the WEB-INF directory of the context.

If you want to make more than one service available through a servlet context, web.xml looks like this (the example defines a 'wms' as well as a 'wfs' and if you uncomment the WCS section even this one is accessible):

<?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN"

"http://java.sun.com/j2ee/dtds/web-app_2.2.dtd">

<web-app>

<description>deegree v2.1 demo CSW</description>

<filter>

<filter-name>SOAPFilter</filter-name>

<filter-class>org.deegree.enterprise.servlet.SOAPFacadeServletFilter</filter-class>

</filter>

<servlet>

<servlet-name>services</servlet-name>

<servlet-class>org.deegree.enterprise.servlet.OGCServletController</servlet-class>

<init-param>

<param-name>services</param-name>

<param-value>csw,wfs</param-value>

<description>

list of supported services, e.g.: wfs,wms (comma separated) allways use lowercase

</description>

</init-param>

<init-param>

<param-name>wfs.handler</param-name>

<param-value>org.deegree.enterprise.servlet.WFSHandler</param-value>

</init-param>

<init-param>

<param-name>wfs.config</param-name>

<param-value>WEB-INF/conf/csw/wfs_capabilities.xml</param-value>

</init-param>

<init-param>

<param-name>csw.handler</param-name>

<param-value>org.deegree.enterprise.servlet.CSWHandler</param-value>

</init-param>

<init-param>

<param-name>csw.config</param-name>

<param-value>WEB-INF/conf/csw/csw_capabilities.xml</param-value>

</init-param>

<load-on-startup>1</load-on-startup>

</servlet>

<!--

<filter-mapping>

<filter-name>SOAPFilter</filter-name>

<url-pattern>/services</url-pattern>

</filter-mapping>

-->

<servlet-mapping>

<servlet-name>services</servlet-name>

<url-pattern>/services</url-pattern>

</servlet-mapping>

<welcome-file-list>

<welcome-file>welcome.html</welcome-file>

<welcome-file>index.jsp</welcome-file>

</welcome-file-list>

</web-app>

In case you wish to run more than on deegree service, it es recommended to use the deegree-wms.war as this configuration already includes the services wfs,wcs and wms.

The tag <servlet-mapping> defines the alias name for the servlet. It is not necessary that the <servlet-name> and <url-pattern> are identical. <url-pattern> is the name for the parameter the servlet will be called through (part of the base-URL of the service that all requests have to use). Combined with the path settings in $TOMCAT_HOME$/conf/Catalina/localhost/deegree-csw.xml and respectively the name of the .war which you deployed in the $TOMCAT_HOME$/webapps (in our example deegree-csw) you should be able to point to your WFS (OWS) via the following URL: http://my.server.domain/deegree-csw/services?

5.2Setting up the Harvester

deegree CS-W supports harvesting capability as defined by the ISO APP extended by the possibility to harvest entire catalogues. The installation and configuration of this harvesting capability is described in the following.

5.2.1Setting up the database

Before the harvester can be activated, some additional tables have to be added to the CSW database. Execute the harvester.SQL file (located in $csw_home$/WEB-INF/conf/scripts/ on your CSW PostgreSQL/Postgis database. This will create 4 tables that can be used for managing the harvesting jobs, and to keep track of the metadata records belonging to the according CSW.

Afterwards you have to point the harvester to its database tables. Therefore, you have to adapt the properties file in the deegree2.jar in the following way:

1. Unzip the WEB-INF/lib/deegree2.jar in a temporary directory

2. Create a directory named $csw_home$/WEB-INF/classes/org/deegree/ogcwebservice/csw/manager

3. Copy the file org/deegree/ogcwebservice/csw/manager/harvestrepository.properties (from the unzipped jar) to $csw_home$/WEB-INF/classes/org/deegree/ogcwebservice/csw/manager and adapt the database connection there.

5.2.2Activating harvesting functionality

In order to activate the harvesting functionality for the CSW, you have to use the deployment descriptor WEB-INF/web_harvester.xml and rename it to web.xml (Be careful: make a backup copy of the original web.xml file).

The major difference to a deployment descriptor of a none harvesting CSW are following entries:

<web-app>

<context-param>

<param-name>CSW.config</param-name>

<param-value>

/WEB-INF/conf/csw/csw_capabilities.xml

</param-value>

</context-param>

<listener>

<listener-class>

org.deegree.enterprise.servlet.CSWHarvestingContextListener

</listener-class>

</listener>

...

These parameters force the assigned tomcat context to use a special listener that is called during initialization and shutdown of the catalogue service.

Because the harvester informs the “contractor” of the harvesting operations via eMail, you have to configure a SMTP connection for the catalogue service. Therefore, you have to set the following property for tomcat: “-DmailHost=SERVERNAME”. How this has to be done depends on the way how you have installed your Tomact and how you start it:

a) Tomcat is installed/started as service on a Windows OS: Open the Apache Tomcat configuration console and add the mailHost parameter to the Java Options:

Figure 3: Tomcat console on a Windows OS

b) Tomcat is installed/started as service on a Linux/Unix OS: Set JAVA_OPTS in $TOMCAT_HOME$/bin/catalina.sh

export JAVA_OPTS="-Xmx500m -Xms100m -DmailHost=SERVERNAME"

c) Tomcat ist started directly (e.g using a batch file): Set the option in the Java call:

java.exe -Xms100m -Xmx500m -jar -DmailHost=mymailhost.myhost.de -DCHARSET="UTF-8" -Duser.dir="C:\Programme\Apache\Tomcat 5.5" "C:\Programme\Apache\Tomcat 5.5\bin\bootstrap.jar" start

5.2.3Testing the harvester

Sending a harvester request – Adding a harvesting job

The following request shows a request that starts harvesting of a full catalog http://www.google.de/ue. This functionality is deegree-specific an not defined by the ISO APP (only harvesting of single metadata files is defined there).

http://my.server.domain/deegree-csw/services?request=Harvest&version=2.0.0&source=http://HOSTNAME:PORTNUMMBER/aCatalogue/services&resourcetype=catalogue&resourceformat=text/xml&responsehandler=mailto:info@myemail.de&harvestinterval=PT2M

Deleting a harvesting job

OGC CSW 2.0 specification does not specify an operation for deleting jobs for harvesting through its interface. In order to delete a harvesting job, you have to follow 2 steps:

1. Delete the job out of the related harvester tables harvestersource, metadatacache, jt_source_responsehandler, reponsehandler within one transaction
   
   The following SQL statements need to be executed step-by-step on the harvester DB:
   
   --execute everything in one transaction
   begin;
   
   -- find id of the desired harvestsource
   
   select id from harvestsource where source = 'http://HOSTNAME:PORTNUMMBER/aCatalogue/services';
   
   -- find all related id's in responsehandler belonging to the source's id
   
   select fk_responsehandler from jt_source_responsehandler where fk_harvestsource = ID OF DESIRED HARVESTSOURCE;
   delete from jt_source_responsehandler where fk_harvestsource = SOURCE-ID;
   delete from responsehandler where id = <LIST OF fk_harvestsource>;
   
   -- figure out all records with their fileidentifiers in the metadatacache belonging to the harvestsource
   
   select fileidentifier from metadatacache where id = ID of harvestsource;
   delete from metadatacache where id = ID of harvestsource;
   commit;
   
   
   

2. Using the list of fileidentifiers you have to delete all stored records in the CSW repository through the CSW Transaction Interface via HTTP POST. A request like this is shown in the following:
   
   
   

<?xml-stylesheet type="text/xsl"?>

<csw:Transaction service="CSW" version="2.0.0" xmlns:csw="http://www.opengis.net/cat/csw" xmlns:gml="http://www.opengis.net/gml" xmlns:iso19115="http://schemas.opengis.net/iso19115full" xmlns:iso19115brief="http://schemas.opengis.net/iso19115brief" xmlns:smXML="http://metadata.dgiwg.org/smXML" xmlns:ogc="http://www.opengis.net/ogc">

<csw:Delete>

<csw:Constraint version="1.0.0">

<ogc:Filter>

<ogc:PropertyIsLike wildCard="%" singleChar="_" escape="\">

<ogc:PropertyName>./iso19115:fileIdentifier/ smXML:CharacterString</ogc:PropertyName>

<ogc:Literal>FILEIDENTIFIERS</ogc:Literal>

</ogc:PropertyIsLike>

</ogc:Filter>

</csw:Constraint>

</csw:Delete>

Updating the harvestsource parameter

If you want to edit the harvestsource, you first have to delete all according metadata records for that harvestsource-id like described above . Then changing of the harvestsource works like this:

update harvestersource set source = 'NEW CATALOGUE URL' where id = 'ID OF THE SOURCE TO BE CHANGED';

Updating the email address to a harvestsource

SQL: execute step by step

-- find the accordind foreign keys for the harvestsource in the join table
select fk_responsehandler from jt_source_responsehandler where fk_harvestresource = ID;
update reponsehandler set address = 'NEW EMAILADDRESS' where id = fk_reponsehandler and isEmailAdress = 1;

Harvesting of one metadata record out of one file:

Send a harvestrequest with a file URL against the service:

http://my.server.domain/deegree/services?request=Harvest&version=2.0.0&source=http://HOSTNAME:PORTNUMMBER/aDirectory/aMetadataFile.xml&resourcetype=catalogue&resourceformat=text/xml&responsehandler=mailto:info@myemail.de&harvestinterval=PT2M

Be aware that this file gets harvested once and will remain in the metadata repository until it is deleted manually via the CSW transaction interface (using delete).

5.3Request and response formatting using XSLT

As mentioned above deegree CS-W needs to transform incoming GetRecords requests to WFS GetFeature requests and resulting WFS GML Feature Collections to the requested metadata outputSchema. For this behavior for each supported metadata format/schema two XSLT scripts must be defined, one for input/requests and on for output/responses. The following example explains what those scripts must do. Other than in the demo release where the ISO 19115 schema is configured the next section descibes the pricipally same DublinCore schema as supported metadata format and a deegree WFS serving a feature type named 'DublinCoreProduct' having the following GML application schema:

<?xml version="1.0" encoding="UTF-8"?>

<xs:schema targetNamespace="http://www.lat-lon.de"

xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:gml="http://www.opengis.net/gml"

xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:ll="http://www.lat-lon.de"

elementFormDefault="qualified">

<!-- import GML 2.1.2 schema definitions -->

<xs:import namespace="http://www.opengis.net/gml"

schemaLocation="./feature.xsd"/>

<xs:import namespace="http://www.opengis.net/gml"

schemaLocation="./geometry.xsd"/>

<!-- ========================================== -->

<!-- element definition -->

<!-- ========================================== -->

<xs:element name="FeatureCollection" type="ll:DCFeatureCollectionType"

substitutionGroup="gml:_FeatureCollection"/>

<xs:complexType name="csw:Record">

<xs:complexContent>

<xs:extension base="gml:AbstractFeatureType">

<xs:sequence>

<xs:element name="csw:DUBLINCORE.IDENTIFIER" type="xs:string"

minOccurs="0"/>

<xs:element name="csw:DUBLINCORE.CONTRIBUTOR" type="xs:string"

minOccurs="0"/>

<xs:element name="csw:DUBLINCORE.CREATOR" type="xs:string"

minOccurs="0"/>

<xs:element name="csw:DUBLINCORE.PUBLISHER" type="xs:string"

minOccurs="0"/>

<xs:element name="csw:DUBLINCORE.SUBJECT" type="xs:string"

minOccurs="0"/>

<xs:element name="csw:DUBLINCORE.DESCRIPTION" type="xs:string"

minOccurs="0"/>

<xs:element name="csw:DUBLINCORE.RELATION" type="xs:string"

minOccurs="0"/>

<xs:element name="csw:DUBLINCORE.SOURCE" type="xs:string"

minOccurs="0"/>

<xs:element name="csw:DUBLINCORE.RIGHTS" type="xs:string"

minOccurs="0"/>

<xs:element name="csw:DUBLINCORE.FORMAT" type="xs:string"

minOccurs="0"/>

<xs:element name="csw:DUBLINCORE.TYPE" type="xs:string"

minOccurs="0"/>

<xs:element name="csw:DUBLINCORE.TITLE" type="xs:string"/>

<xs:element name="csw:DUBLINCORE.DATE" type="xs:date" minOccurs="0"/>

<xs:element name="csw:DUBLINCORE.LANGUAGE" type="xs:string"

minOccurs="0"/>

<xs:element name="csw:DUBLINCORE.COVERAGE"

type="gml:GeometryPropertyType" minOccurs="0"/>

</xs:sequence>

</xs:extension>

</xs:complexContent>

</xs:complexType>

<xs:complexType name="DCFeatureCollectionType">

<xs:complexContent>

<xs:extension base="gml:AbstractFeatureCollectionType">

<xs:sequence/>

</xs:extension>

</xs:complexContent>

</xs:complexType>

</xs:schema>

For details about how to configure a deegree WFS please have a look to deegree WFS demo and documentation.

5.3.1Input/request

According to OGC CS-W specification and the DublinCore schema a valid GetRecord request asking for all metadata objects describing a product having a subject that contains the literal 'pollution' looks like this:

<?xml version="1.0" encoding="UTF-8"?>

<csw:GetRecords xmlns:ogc="http://www.opengis.net/ogc"

xmlns:csw="http://www.opengis.net/cat/csw" version="2.0.0" service="CSW"

outputFormat="text/xml" outputSchema="OGCCORE">

<csw:Query typeNames="csw:Record">

<csw:ElementName>subject</csw:ElementName>

<csw:ElementName>title</csw:ElementName>

<csw:ElementName>date</csw:ElementName>

<csw:Constraint>

<ogc:Filter>

<ogc:PropertyIsLike wildCard="%" singleChar="_" escape="\">

<ogc:PropertyName>subject</ogc:PropertyName>

<ogc:Literal>%structure%</ogc:Literal>

</ogc:PropertyIsLike>

</ogc:Filter>

</csw:Constraint>

</csw:Query>

</csw:GetRecords>

The respective GetFeature request to be performed against the underlying WFS (see schema above) must look like:

<?xml version="1.0" encoding="UTF-8"?>

<wfs:GetFeature outputFormat="text/xml; subtype=gml/3.1.1"

xmlns:csw="http://www.opengis.net/cat/csw" xmlns:fo="http://www.w3.org/1999/XSL/Format" xmlns:gml="http://www.opengis.net/gml"

xmlns:ogc="http://www.opengis.net/ogc" xmlns:wfs="http://www.opengis.net/wfs"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<wfs:Query typeName="csw:Record">

<wfs:PropertyName>csw:DUBLINCORE.IDENTIFIER</wfs:PropertyName>

<wfs:PropertyName>csw:DUBLINCORE.TITLE</wfs:PropertyName>

<wfs:PropertyName>csw:DUBLINCORE.SUBJECT</wfs:PropertyName>

<ogc:Filter>

<ogc:PropertyIsLike escape="!" singleChar="#" wildCard="*">

<ogc:PropertyName>csw:DUBLINCORE.SUBJECT</ogc:PropertyName>

<ogc:Literal>*structure*</ogc:Literal>

</ogc:PropertyIsLike>

</ogc:Filter>

</wfs:Query>

</wfs:GetFeature>

If you have a close look to the the GetRecords and the GetFeature request above you see that their structure is more or less identical. Only the name of the request differs; the typeName of the GetFeature Query must be determined from the GetRecords outputSchema and the typeName of the GetRecords request; ElementName must be mapped to PropertyName and its values must be mapped to the propertynames known by the WFS. The transformation of the filter expression is a bit tricky. In principle it should be no problem to substitue the value of PropertyName with the name known by the WFS. The problem is that a filter expression is a recursive datastructure with a possible unlimited depth of nested elements (see Filter Encoding specification for details).

The XSLT that enables the required transformation is given below:

<?xml version="1.0" encoding="UTF-8"?>

<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"

xmlns:fo="http://www.w3.org/1999/XSL/Format" xmlns:gml="http://www.opengis.net/gml"

xmlns:ogc="http://www.opengis.net/ogc" xmlns:csw="http://www.opengis.net/cat/csw"

xmlns:wfs="http://www.opengis.net/wfs"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<xsl:include href="inDC_WFSMapping.xsl"/>

<xsl:template match="csw:GetRecords">

<wfs:GetFeature outputFormat="text/xml; subtype=gml/3.1.1"

xmlns:gml="http://www.opengis.net/gml">

<xsl:if test="/@maxRecords != '' ">

<xsl:attribute name="maxFeature">

<xsl:value-of select="/@maxRecords"/>

</xsl:attribute>

</xsl:if>

<xsl:if test="/@startPosition != '' ">

<xsl:attribute name="startPosition">

<xsl:value-of select="/@startPosition"/>

</xsl:attribute>

</xsl:if>

<xsl:for-each select="./csw:Query">

<xsl:variable name="TYPENAME">

<xsl:value-of select="../@outputSchema"/>:<xsl:value-of select="./@typeName"/>

</xsl:variable>

<wfs:Query>

<xsl:attribute name="typeName">csw:Record</xsl:attribute>

<xsl:apply-templates select="."/>

</wfs:Query>

</xsl:for-each>

</wfs:GetFeature>

<xsl:apply-templates select="csw:ResponseHandler"/>

</xsl:template>

<xsl:template match="csw:ResponseHandler"/>

<xsl:template match="csw:Query">

<xsl:if test="./csw:ElementSetName = 'brief' ">

<wfs:PropertyName>

<xsl:value-of select="$WFS_identifier"/>

</wfs:PropertyName>

<wfs:PropertyName>

<xsl:value-of select="$WFS_title"/>

</wfs:PropertyName>

<wfs:PropertyName>

<xsl:value-of select="$WFS_subject"/>

</wfs:PropertyName>

</xsl:if>

<xsl:if test="./csw:ElementSetName = 'summary' ">

<wfs:PropertyName>

<xsl:value-of select="$WFS_identifier"/>

</wfs:PropertyName>

<wfs:PropertyName>

<xsl:value-of select="$WFS_title"/>

</wfs:PropertyName>

<wfs:PropertyName>

<xsl:value-of select="$WFS_subject"/>

</wfs:PropertyName>

<wfs:PropertyName>

<xsl:value-of select="$WFS_description"/>

</wfs:PropertyName>

</xsl:if>

<xsl:if test="./csw:ElementSetName = 'full' "/>

<xsl:if test="./csw:ElementSetName = 'hits' ">

<wfs:PropertyName>_COUNT_</wfs:PropertyName>

</xsl:if>

<!--xsl:apply-templates select="csw:ElementName"/-->

<xsl:for-each select="./child::*">

<xsl:if test="local-name(.) = 'ElementName' ">

<wfs:PropertyName>

<xsl:apply-templates select="."/>

</wfs:PropertyName>

</xsl:if>

</xsl:for-each>

<xsl:apply-templates select="csw:Constraint"/>

</xsl:template>

<xsl:template match="csw:Constraint">

<ogc:Filter>

<xsl:apply-templates select="ogc:Filter"/>

</ogc:Filter>

</xsl:template>

<xsl:template match="ogc:Filter">

<xsl:apply-templates select="ogc:And"/>

<xsl:apply-templates select="ogc:Or"/>

<xsl:apply-templates select="ogc:Not"/>

<xsl:if test="local-name(./child::*[1]) != 'And' and

local-name(./child::*[1])!='Or' and local-name(./child::*[1])!='Not'">

<xsl:for-each select="./child::*">

<xsl:call-template name="copyProperty"/>

</xsl:for-each>

</xsl:if>

</xsl:template>

<xsl:template match="ogc:And | ogc:Or | ogc:Not">

<xsl:copy>

<xsl:apply-templates select="ogc:And"/>

<xsl:apply-templates select="ogc:Or"/>

<xsl:apply-templates select="ogc:Not"/>

<xsl:for-each select="./child::*">

<xsl:if test="local-name(.) != 'And' and local-name(.)!='Or'

and local-name(.)!='Not'">

<xsl:call-template name="copyProperty"/>

</xsl:if>

</xsl:for-each>

</xsl:copy>

</xsl:template>

<xsl:template name="copyProperty">

<xsl:copy>

<xsl:if test="local-name(.) = 'PropertyIsLike'">

<xsl:attribute name="wildCard">

<xsl:value-of select="./@wildCard"/></xsl:attribute>

<xsl:attribute name="singleChar">

<xsl:value-of select="./@singleChar"/></xsl:attribute>

<xsl:attribute name="escape">

<xsl:value-of select="./@escape"/></xsl:attribute>

</xsl:if>

<ogc:PropertyName>

<xsl:apply-templates select="ogc:PropertyName"/>

</ogc:PropertyName>

<xsl:for-each select="./child::*">

<xsl:if test="local-name(.) != 'PropertyName' ">

<xsl:copy-of select="."/>

</xsl:if>

</xsl:for-each>

</xsl:copy>

</xsl:template>

<xsl:template match="ogc:PropertyName | csw:ElementName">

<!-- mapping property name value -->

<xsl:variable name="VAL">

<xsl:value-of select="."/>

</xsl:variable>

<xsl:if test="$VAL = 'title'">

<xsl:value-of select="$WFS_title"/>

</xsl:if>

<xsl:if test="$VAL = 'creator'">

<xsl:value-of select="$WFS_creator"/>

</xsl:if>

<xsl:if test="$VAL = 'subject'">

<xsl:value-of select="$WFS_subject"/>

</xsl:if>

<xsl:if test="$VAL = 'description'">

<xsl:value-of select="$WFS_description"/>

</xsl:if>

<xsl:if test="$VAL = 'publisher'">

<xsl:value-of select="$WFS_publisher"/>

</xsl:if>

<xsl:if test="$VAL = 'contributor'">

<xsl:value-of select="$WFS_contributor"/>

</xsl:if>

<xsl:if test="$VAL = 'date'">

<xsl:value-of select="$WFS_date"/>

</xsl:if>

<xsl:if test="$VAL = 'type'">

<xsl:value-of select="$WFS_type"/>

</xsl:if>

<xsl:if test="$VAL = 'format'">

<xsl:value-of select="$WFS_format"/>

</xsl:if>

<xsl:if test="$VAL = 'identifier'">

<xsl:value-of select="$WFS_identifier"/>

</xsl:if>

<xsl:if test="$VAL = 'source'">

<xsl:value-of select="$WFS_source"/>

</xsl:if>

<xsl:if test="$VAL = 'language'">

<xsl:value-of select="$WFS_language"/>

</xsl:if>

<xsl:if test="$VAL = 'relation'">

<xsl:value-of select="$WFS_relation"/>

</xsl:if>

<xsl:if test="$VAL = 'coverage'">

<xsl:value-of select="$WFS_coverage"/>

</xsl:if>

<xsl:if test="$VAL = 'rights'">

<xsl:value-of select="$WFS_rights"/>

</xsl:if>

<xsl:value-of select="VErdamgtmtwse"/>

</xsl:template>

</xsl:stylesheet>

As you can see at line 2 the XSLT script includes another script defining the mapping between DublinCore property names and property names used by the WFS. This enables you to adjust the input mapping script to another WFS schema just by adjusting/substitution of inDC_WFSMapping.xsl.

<?xml version="1.0" encoding="UTF-8"?>

<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format" xmlns:gml="http://www.opengis.net/gml" xmlns:ogc="http://www.opengis.net/ogc" xmlns:csw="http://www.opengis.net/cat/csw" xmlns:wfs="http://www.opengis.net/wfs" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<!-- Mappings used for DublinCore fields in the generated WFS-GetFeature-requests.-->

<xsl:variable name="WFS_title">csw:DUBLINCORE.TITLE</xsl:variable>

<xsl:variable name="WFS_creator">csw:DUBLINCORE.CREATOR</xsl:variable>

<xsl:variable name="WFS_subject">csw:DUBLINCORE.SUBJECT</xsl:variable>

<xsl:variable name="WFS_description">csw:DUBLINCORE.DESCRIPTION</xsl:variable>

<xsl:variable name="WFS_publisher">csw:DUBLINCORE.PUBLISHER</xsl:variable>

<xsl:variable name="WFS_contributor">csw:DUBLINCORE.CONTRIBUTOR</xsl:variable>

<xsl:variable name="WFS_date">csw:DUBLINCORE.DATE</xsl:variable>

<xsl:variable name="WFS_type">csw:DUBLINCORE.TYPE</xsl:variable>

<xsl:variable name="WFS_format">csw:DUBLINCORE.FORMAT</xsl:variable>

<xsl:variable name="WFS_identifier">csw:DUBLINCORE.IDENTIFIER</xsl:variable>

<xsl:variable name="WFS_source">csw:DUBLINCORE.SOURCE</xsl:variable>

<xsl:variable name="WFS_language">csw:DUBLINCORE.LANGUAGE</xsl:variable>

<xsl:variable name="WFS_relation">csw:DUBLINCORE.RELATION</xsl:variable>

<xsl:variable name="WFS_coverage">csw:DUBLINCORE.COVERAGE</xsl:variable>

<xsl:variable name="WFS_rights">csw:DUBLINCORE.RIGHTS</xsl:variable>

</xsl:stylesheet>

As a matter of course other metadata format/schema like ISO 19115 (which is currently configured with this demo) or FGDC need special input transformation script. But notice this may map GetRecord requests to the same WFS feature type!

In principle it is possible to use more extensive mappings and to put these mappings into a Java class invoked by the XSLT processor.

Example:

<xsl:stylesheet version="1.0" ...

xmlns:java="java" xmlns:mapping="de.latlon.catalog.Mapping">

<xsl:variable name="HIERARCHY">

...

</xsl:variable>

...

<xsl:template match="ogc:PropertyName | csw:ElementName">

<!-- mapping property name value -->

<xsl:value-of select="mapping:mapPropertyValue( ., $HIERARCHY )"/>

</xsl:template>

...

5.3.2output/response

Like the incoming request the response returned from the WFS must be transformed. The request described above will lead to a WFS response that looks like this:

<ResultCollection xmlns:gml="http://www.opengis.net/gml"

xmlns:xlink="http://www.w3.org/1999/xlink"

xmlns:csw="http://www.opengis.net/cat/csw"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<gml:boundedBy>

<gml:Box>

<gml:coord>

<gml:X>-9.0E9</gml:X>