Data Integration System for Marine Pollution and Water Quality · 2006. 3. 6. · Data Integration System for Marine Pollution and Water Quality Deliverable D6.2 Final Report on DISPRO-1

Data Integration System forMarine Pollution and Water

Quality

Deliverable D6.2Final Report on DISPRO-1

DISMAR Report No. k2004-09-10

Version 0.3

Prepared by Éamonn Ó Tuama with input on thedemonstration nodes (section 4) and RSS news feed(section 3.3.1) supplied by the responsible partners.

Project funded by the European Community under the“Information Society Technology” Programme

(1998-2002) Contract Number: IST-2001-37657

Contract Start Date: 1 August 2002 – Duration: 3 years

DISMAR Report No. 6.2 Final Report on DISPRO-1 2

DELIVERABLES SUMMARY SHEET

Project Number: IST-2002-37657Project Acronym: DISMARTitle: Data Integration System for Marine Pollution and Water Quality

Deliverable No: D6.2Due date: June 2004Delivery Date: September 2004

Short Description:

This report provides an overview of the first DISMAR prototype system known as DISPRO-1.

DISPRO-1 is implemented as an OpenGIS compliant Web Map Service system. The technologyunderpinning the prototype is first described briefly (see also Report D6.1), emphasising thedistributed nature of the system. This is followed by descriptions of each node on the network and theirintegration through the portal.

Partners owning: all (all partners are listed in Appendix D)

Partners contributed: CMRC; Ifremer; JRC; Met.no; NERSC; NIVA; PML; Telespazio

Made available to: all partners, advisory group and IST

Contract No. Data Integration System for Marine Pollution and Water Quality 2004-09-10IST-2001-37657 version 0.3


Contents1 Introduction........................................................................................................................................................... 4

2 DISPRO Architecture............................................................................................................................................ 4

2.1 Dispro Portal.................................................................................................................................................. 4

2.2 Web GIS Client ............................................................................................................................................. 4

2.3 WMS Client.................................................................................................................................................... 5

2.4 WMS Server .................................................................................................................................................. 5

2.5 Geo-processing Service ................................................................................................................................5

2.6 Local Web Server.......................................................................................................................................... 5

2.7 Aggregator..................................................................................................................................................... 5

2.8 Catalogue....................................................................................................................................................... 5

2.9 Metadata........................................................................................................................................................ 5

3 DISPRO Implementation........................................................................................................................................ 6

3.1 The OGC WMS System................................................................................................................................ 6

3.1.1 The Web Interface ................................................................................................................................6

3.1.2 The Web GIS Client ............................................................................................................................. 7

3.1.3 The Java/XML Processor...................................................................................................................... 7

3.1.4 The OGC WMS Client .......................................................................................................................... 7

3.1.5 The OGC WMS Servers........................................................................................................................ 8

3.2 The Catalogue ...............................................................................................................................................9

3.3 The News System........................................................................................................................................ 11

3.3.1 RSS News Feed ................................................................................................................................. 11

3.3.2 Product Update List ............................................................................................................................ 12

4 WMS Nodes....................................................................................................................................................... 12

4.1 CMRC.......................................................................................................................................................... 12

4.2 EM................................................................................................................................................................ 12

4.3 GKSS........................................................................................................................................................... 12

4.4 Ifremer.......................................................................................................................................................... 12

4.5 Met.no.......................................................................................................................................................... 12

4.6 NERSC......................................................................................................................................................... 12

4.7 NIVA............................................................................................................................................................. 13

4.8 TPZ.............................................................................................................................................................. 13

4.9 PML.............................................................................................................................................................. 13

5 Technical Terms & Abbreviations....................................................................................................................... 14

6 References......................................................................................................................................................... 15

7 Appendix A: OGC WMS Operations ..................................................................................................................16

8 Appendix B: UMN MapServer Mapfile................................................................................................................ 18

9 Appendix C: OGC WMS Server Nodes.............................................................................................................. 19

10 Appendix D. Consortium and contact persons................................................................................................. 27



1 IntroductionThis document describes the implementation of the DISMAR prototype known as DISPRO I. For abackground on the requirements of this work package, the reader should consult the consortiumdocument “DISPRO I Progress Report” [1] where DISPRO is described in the context of the EUINSPIRE [2] initiative to develop a spatial data infrastructure (SDI) for Europe. The principles guidingthe design of DISPRO are to follow closely the INSPIRE, OpenGIS™ [3] and W3C [4] standards, andto use OpenSource software where available [5].

2 DISPRO ArchitectureThe architecture of the DISPRO system is described fully in the document “DISPRO I Progress Report”[1]. This architecture is consistent with the INSPIRE general model of an SDI. It consists of a multi-tiersystem (Illustration 1) featuring diverse end user applications communicating with various applicationservers which are in turn linked to the data repositories. The DISPRO I prototype implements an OGCWeb Map Service (WMS) system [9]. There are several components in each tier of the system. A briefdescription of the main components follows.

2.1 Dispro PortalThe portal is the front-end to the prototype and provides access to all features of the system through aweb browser. Authentication by password can be used to restrict access to the system. Several typesof client application are available within the portal.

• The map viewer client provides the interface for interacting with the web GIS client. It is restrictedto the basic functionality of the browser (i.e., a thin client).

• The catalogue browser provides an interface to the metadata catalogue.

• The news client displays the RSS news feed which provides news alerts on new and updated data,pollution events and service notices.

2.2 Web GIS Client The web GIS client provides the basic functionality of the GIS web interface, e.g., actions such asselecting/deselecting map layers to display, and panning, zooming, and querying. The CGI applicationUniversity of Minnesota (UMN) MapServer [6], running under the Apache [7] web server, is a widelyused Open Source example, and is used in DISPRO.


Illustration 1. The DISPRO architecture is consistent with the INSPIRE generalmodel of an SDI.


2.3 WMS ClientThe WMS client communicates with remote WMS servers to retrieve map layers. This functionality isoften an enhancement of the basic web GIS client, as in the case of UMN MapServer.

2.4 WMS Server A WMS server is one that runs on the DISMAR data provider’s site and serves maps for a givendemonstration region. These maps are available to the DISPRO WMS Client via OpenGIS protocols(GetCapabilities and GetMap). In response to GetMap requests from the WMS client, a WMS servergenerates and serves up maps in image (raster) format. The functions of an OGC WMS are describedin Appendix A.

2.5 Geo-processing Service Each geo-processing service application (e.g. oil drift model, HAB model, other algorithm) publishes itsavailability through the catalogue. When a user selects a service by browsing through the catalogue,an interface with the appropriate input form is presented. Most services will require some time to run(e.g., ca. 30 minutes for the oil drift model). The user will therefore need to be alerted when a modelrun is completed. This alert can be in the form of an RSS update (viewable through the RSS client) oran e-mail or SMS message. There are no geo-processing services available in DISPRO 1. Met.no areinvestigating how to provide oil drift model output as data layers available from their OGC WMS server.

2.6 Local Web ServerEach data provider will set up a web server to make files available via HTTP. They will implement anagreed directory structure on the server and upload their data there. The proposed structure is shownin ( Table 1).

Directory structure Contentsdismar/ top level directory

docs documents in PDFdata for data sets (shapefiles, GML, XML, PostgreSQL export files,

GeoTIFF)metadata for metadata describing the data sets in dismar/docs and

dismar/data directoriesmapserver a description of the OGC compliant WMS server at this site (in

XML, structure to be defined)services a description of the geo-processing services available from this

site (in XML, structure to be defined, possibly SoDa or WSDL)news one RSS file (XML) describing any new events, data sets, or

documents which have become available in one of the directoriesabove

Table 1. Proposed directory structure for DISPRO web servers.

2.7 AggregatorData providers use a special form to upload metadata to a dedicated directory on the portal. Theaggregator polls this directory at regular intervals checking for new items and adding them to thecatalogue database.

2.8 CatalogueThe catalogue is an inventory of all the geodata, services and other resources available in DISPRO.The catalogue entries consist of the metadata files that accompany each data product or service.

2.9 MetadataDISPRO uses a profile of ISO 19115 [8] for discovery metadata. Data producers are responsible forproviding metadata for each resource they provide.

3 DISPRO ImplementationThe implementation of DISPRO relies heavily on Java and XML technologies, with UMN MapServerproviding the core web GIS client and OpenGIS WMS functionality. The implementation of the maincomponents of DISPRO I are described below.



3.1 The OGC WMS SystemThe OGC WMS system consists of several sub-components (Figure 2) : the web interface to the GIS,the web GIS client application, the OGC WMS client, OGC WMS servers, and software to glue thesetogether into a co-ordinated whole.

3.1.1 The Web Interface The initial screen presents a map of Europe with hotspots linking to each of the demonstration regions(Illustration 3). Clicking on a hotspot loads the map viewer interface of the Web GIS client from theCMRC server and populates it with the map layers for that region (Illustration 4). These map layers canbe sourced from any OGC WMS compliant server, not just those located on the server node in thatparticular region. The interface is built to W3C standards and uses XHTML [14], CSS [15] andEcmaScript [13]. As such it should run in any modern browser and, because it does not rely on anyother plug-in technologies, it is known as a “thin” client.

In the North Sea/Skagerrak example (Illustration 4), the map layers are derived from the WMS servernodes at NERSC (SAR images, coastline), Met.no (wind, magniture wind), NIVA (HABs) and PML(HABs). Other nodes can be added by editing a configuration file. The interface illustrated providesbasic functions expected of a thin client such as selection/deselection of layers, drag-select zoom box,and panning, reference map and scalebar.


Illustration 2. DISPRO I implements an OGC compliant WMSsystem.

Illustration 3. The initial screen of the DISPROportal presents a map of Europe.


3.1.2 The Web GIS Client The web GIS client underlying the web interface is implemented using UMN MapServer. This runs as aCGI application of the Apache HTTP web server.

3.1.3 The Java/XML ProcessorJava and XML processing technologies are used to provide the dynamic aspects of the web mapserving (Illustration 5). The system relies on the Apache Cocoon [10] XML publishing framework (aJava application) which runs in the Apache Jakarta Tomcat [11] servlet container. The sequence ofevents is as follows (Illustration 6).

Each hotlink in the opening screen (Illustration 3) calls a configuration file for a particulardemonstration region. The configuration file lists one or more OGC WMS servers (nodes) to which aGetCapabilities request should be issued. There is also an XSLT stylesheet associated with eachconfiguration file. Cocoon applies this stylesheet to the files (capabilities files) returned by the nodes inresponse to the GetCapabilities request.

Applying the stylesheet to the Capabilities files results in three separate files which are required forUMN MapServer:

1. an 'index' file in HTML which sets up some initial parameters for the GIS client;

2. a 'template' file in HTML which defines the interface of the GIS client, including the list of map layersavailable;

3. a 'mapfile' which is the core configuration file of UMN MapServer, providing information andmetadata on the map layers available (see appendix B for sample file).

Once these three files are generated and stored in the appropriate locations on the portal server, theweb browser is automatically directed to the URL of the 'index' file. The index file is a simple pageproviding a forward link to the web GIS interface, i.e., the 'template' file (Illustration 4).

3.1.4 The OGC WMS Client An OGC WMS Client extends the functionality of a standalone web map serving application to allow itto retrieve maps using the OGC GetMap request. UMN MapServer can be compiled with thisfunctionality and can then retrieve maps using its native protocols or GetMap.


Illustration 4. The DISPRO I interface (map viewer) to the web GIS client.


3.1.5 The OGC WMS ServersThe WMS client communicates with one or more distributed OGC compliant WMS servers. DISPRO Iwill initially feature nine WMS servers. A particular demonstration region will feature data derived fromone or more of these servers (nodes). For example, the Skagerrak region will contain inputs fromnodes 5, 6, 7, 8. These are listed in Table 2.

Node Abbreviation1 Coastal & Marine Resources Centre CMRC2 Ecoles des Mines EM3 GKSS-Forschungszentrum Geesthacht GKSS4 Institut français de recherche pour l'exploitation de la mer IFREMER5 Norwegian Meteorological Institute Met.no6 Nansen Environmental and Remote Sensing Centre NERSC7 Norwegian Institute for Water Research NIVA8 Plymouth Marine Laboratory PML9 Telespazio TPZ

Table 2. OGC WMS server nodes in the DISPRO network.

In addition, other third party OGC WMS servers may be included. For example, the French AtlanticCoast demonstration region will include a JRC hosted OGC WMS node dedicated to the Prestige oilspill event.

All but two of the DISPRO nodes use UMN MapServer, the exceptions being Met.no and NIVA whichuse ArcIMS. Use of UMN MapServer requires compiling it with the WMS extension and providingadditional metadata in the mapfile (see Appendix B for example). For a description of each of thesenodes see section 4.


Illustration 5. Java and XML technologies areused to provide the dynamic functionality of

DISPRO


3.2 The Catalogue The DISPRO catalogue (Illustration 7) is implemented using the Open Source, native XML databaseeXist [12]. This runs as a Java application in the Apache Tomcat servlet container and uses ApacheCocoon as the web publishing framework. The items (records) in the catalogue are the discoverymetadata files provided by the DISMAR data providers. Metadata files are prepared locally eitherprogramatically or by hand and are validated against an XSD schema before being uploaded to a


Illustration 6. Cocoon XML publishing system used in Dispro.


dedicated directory on the portal using a special web form. An aggregator, scheduled to runperiodically, retrieves the files from the upload directory and stores them in the database.

The interface for querying the database (Illustration 8) allows searching by various combinations ofterms, e.g., location, date, title. The result of a search can be used in several ways. One is to presentthe full metadata files for each item in the result set (Illustration 9), with further links within themetadata description for viewing the data (via a GetMap request to the originating server), or to adownload site. Another is to configure a Web GIS client on-the-fly with data pertaining to a particularset of search terms, e.g., a geographic location, an event (e.g. Prestige), and/or a date; the end resultof a database query is the three files required for the UMN MapServer WMS client as described insection 3.1.3.


Illustration 7. The DISPRO catalogue system.

Illustration 8. The query interface to the DISPRO catalogue.


3.3 The News SystemThe news system provides timely information to DISPRO users regarding pollution incidents and theavailability of new data products. The two news sources are a real-time news feed from the EuropeMedia Monitor (EMM) [16] facility at the JRC and a product update list generated within DISPRO itself.

3.3.1 RSS News Feed DISPRO 1 is monitoring in real-time, incidents reported by the world's press concerning Oil Pollutionand Harmful Algal Blooms. This provides users with immediate updates in the event of an emergencyor during the evolution of an incident. This information complements the sensors from DISMARpartners.

The news feed consists of an RSS 2.0 (Really Simple Syndication) [17] file accessed over HTTP fromthe Europe Media Monitor (EMM). This feed has been created especially for DISMAR. The contentsare the result of a semantic scan of over 400 selected web sites by EMM's Alert system. Articles aredetected within minutes of publication.

The Alert system is a unique service run independently of a database and is a pure JAVA/XMLapplication. The text-processing algorithm uses a state machine to process in memory keyword listsagainst incoming text. It currently processes a single article of a few thousand words against 8000 pre-defined keyword patterns in 80 milliseconds.

By avoiding the use of a database and by exploiting the multi-threaded advantage of Java, the alertsystem is lightning fast and reliable. The results are held in RSS(XML) files that are continuouslyupdated. This allows fast access by many users over the Web, and gives the possibility to feedcontents directly to DISPRO. This is done by transforming the RSS feeds into JavaScript contentembedded in DISPRO.

The definition of the DISPRO feed consists of both boolean combinations of keywords and weighted


Illustration 9. Result set from searching the catalogue for itemswith location 'Skagerrak' and date 2004. The 'source' field

provides a hyperlink to the full metadata file.


lists of likely words. Fine tuning to improve quality will be performed during operations.

3.3.2 Product Update List The product update list is created from metadata entries in the catalogue. This is generated through asimple query interface to the catalogue (Illustration 10) which allows the end user to view data recordsrecently uploaded (today, 1 day ago, 2 days ago ...). The result set returned is displayed in a similarmanner to that in Illustration 8.

4 WMS NodesAs mentioned in section 3.1.5, the DISPRO network consists of nine WMS nodes: CMRC, EM, GKSS,Ifremer, Met.no, NERSC, NIVA, PML, and TPZ. A summary description of each node follows and anassociated table with more details is available in Appendix C.

4.1 CMRCThe CMRC is a supplementary DISPRO node not directly involved in a demonstration case. It isprimarily used to prototype and test the set up of OGC web map services, and also to demonstratehow a rich set of GIS layers can enhance and provide context for the kinds of data generated by thespecialist DISMAR data providers. This is especially important as many of the DISPRO nodes, forvarious reasons, are having difficulties obtaining base data layers for their area.

4.2 EMThe node being provided by Ecole des Mines will not be implemented in DISPRO-1.

4.3 GKSSGKSS, in collaboration with two other data providing partners (OPTIMARE, RUB) is responsible for theDISPRO node covering the German Bight. This node will demonstrate the integration and display of avariety of data sources including remote sensing (aircraft, satellites, ground based radar). All dataproviders deliver their products (maps, pictures, metadata, etc) via FTP to the German WMS. RUBdelivers and receives radar maps for data fusion via FTP.

4.4 IfremerThe Ifremer node is concentrating on the Prestige oil spill case. It will make available a range of geo-referenced images covering the Prestige area derived from browsing hindcast model outputs andimagery, together with base maps for context. The data are provided by Cedre, Météo-France,Mercator, and Met-no. Work flow is manual. The node uses a static map file.

4.5 Met.noThe Met.no node specialises in oil spill monitoring and forecasting, and numerical weather predictions(NWP). Within the DISPRO context, the aim is to test the feasibility of NWP and oil drift prognosis onrequest. The area of interest for the demo is the North Sea and Skagerrak, but NWP are availablewithin Met.no’s area of calculation (North West Europe). NWP are now available as OGC WMS layers,with prognosis of oil drift planned to be available for testing in DISPRO 2. Oil drift will, once inoperational mode, be updated on request. NWP are updated four times a day, the sea model twice aday. NWP will be uploaded to the OGC WMS server as part of Met.no’s post processing routines.GetCapabilities are static map files.

4.6 NERSCThe NERSC DISPRO-1 Node serves satellite data and derived products generated by NERSC duringthe first demonstration phase of DISMAR, i.e. during spring and summer of 2004. The purpose of thenode is to demonstrate delivery of various types of satellite data (SAR, optical) and derived products(oil spill analysis, chl-a concentrations, algal bloom interpretations), as well as sample base layers(coastline, bathymetry, gridlines). Each data set or product is accompanied by metadata in XML format(conforming to the DISPRO profile of ISO 19115), which is also served by the same web server butcurrently not through the DISPRO-1 node.

For data preparation and upload, satellite images are pre-processed and analysed in NERSC legacysystems. Resulting images and analyses are prepared as files that can be handled by the UMNMapServer, typically TIFF for raster data and Shapefiles for vector data. Interpretations will be provided


Illustration 10. Simple query interface forchecking for new data products in the

catalogue.


as ASCII text or XML files depending on what can be most easily handled by the MapServer andDISPRO web portal.

4.7 NIVAThe main function of the NIVA node is to present FerryBox data from the Skagerrak with parameters toshow algal blooms and water quality. FerryBox data consists of a number of parameters collected fromsensors onboard the ferry and transferred in real time to NIVA over the internet. Realtime functionalityis not implemented in DISPRO 1. During the demo period in the spring 2004, further demo data will beadded if a HAB situation should occur. Data from water samples collected on fixed intervals or duringHAB situations are analysed in the laboratory. These results can be shown together with the onboardmeasurements. For the demo, NIVA node will also provide a layer for aquaculture sites operated bythe Norwegian Directorate of Fisheries.

For the demonstration, in spring 2004, representative data for algal blooms will be selected from theFerryBox database and converted to shapefiles for serving by the NIVA OGC WMS server. Metadatais prepared manually.

4.8 TPZThe Italian Node of DISPRO I will be verified by means of an oil spill application. The algal bloomapplication is currently under development. The eventual use of the first results of this application isstill under investigation. Data types used for the demonstration are mainly Shapefile andGIF/JPEG/Tiff raster files.

The oil spill application used for DISPRO I will concatenate a model for oil spill detection and for oildrift (for following position of the spill). The process starts in ASI with the identification of a probable oilspill on an ERS1 Quicklook image. Then a ERS1 Precise Resolution Image (PRI) is generated to feedthe OSAD model. OSAD is then run by the ASI operator with the ERS1 PRI image as input and itsoutput is uploaded to the Telespazio (TPZ) local repository. The OSAD products uploaded are:

• OSAD report html file

• Oil spill Quicklooks jpeg images

• Oil spill contours text files

The contours are then downloaded from the TPZ repository and converted to shapefile format usingArcInfo software. The resulting shapefiles are then uploaded to the TPZ repository. The drift of the spillis the detected using the Università del Piemonte (UNIPM) Oil Drift Model and the output (shapefiles)uploaded to the TPZ repository.

These actions are followed by metadata generation, validation and uploading to the dismar/metadatadirectory, and data uploading to dismar/data dir. The static map file is than updated using a text editoror an automatic mapfile production tool such as Mapedit of MapLab suite(http://www.maptools.org/maplab/index.phtml). The final data available on MapServer then will be:

• OSAD Report

• Oil spill contours

• Oil drift contours

The georeferencing and publication of ERS1 and oil spill Quicklooks is under study.

4.9 PMLThe PML node mainly serves gridded (raster) datasets, modelled parameters, and remotely senseddata from SeaWiFS and AVHRR. Data preparation consists mostly of converting current datasets intoGeoTIFF or other formats useful for this project, then storing them on the webserver and registeringinformation about the data in a database. The database provides data for the metadata creation, whichwill be generated dynamically (either written as a large batch, or more likely, generated on request).Map files will be dynamically generated based on the client request on our WMS, and using data in adatabase.



5 Technical Terms & Abbreviations

Architecture The models, standards, technologies, specifications, and procedures used torepresent, transform and generally accomodate the integration, maintenance anduse of information in digital format. [from INSPIRE]

AVHRR Advanced Very High Resolution Radiometer

CGI Common Gateway Interface, a standard for how external programs interface withHTTP servers

Component A group of technically similar functionalities within the architecture. [from INSPIRE]

CSS Cascading Style Sheets

ECMAScript JavaScript standard produced by European Computer Manufacturers Association

GeoTIFF Tagged Image File Format for geocoded raster images

GIS Geographic Information System

GML Geography Markup Language

HAB Harmful Algal Bloom

HTTP Hypertext transfer protocol, the network protocol as used by the world-wide web.

JPEG Joint Photographic Experts Group; raster image file format

OGC Open GIS Consortium

PNG Portable Network Graphics; raster image file format

RSS Really Simple Syndication; Rich Site Summary

SAR Synthetic Aperture Radar

SDI Spatial Data Infrastructure

SeaWiFS Sea-viewing Wide Field-of-view Sensor

SMS Short Message System

SVG Scalable Vector Graphics

TCP/IP Transmission Control Protocol / Internet Protocol

Web Services A specialised varient and refer to the programmatic interfaces exposed forapplication to application communication via the web.

XHTML HTML 4 reformulated as an XML application

XML eXtensible Markup language

XSD XML Schema Definition

WMS Web Map Service

XSLT XSL (Extensible Stylesheet Language) Transformations



6 References

[1] DISPRO 1 Progress Report; http://www.nersc.no/Projects/dismar/internal/Reports/D61-DISMAR-final.pdf

[2] INSPIRE Architecture and Standards Position Paper, Architecture and Standards WorkingGroup, Editor Paul Smits, 2002-10-03; http://inspire.jrc.it/reports/position_papers/inspire_ast_pp_v4_3_en.pdf

[3] OpenGIS Consortium; http://www.opengis.org[4] W3C; http://www.w3c.org/[5] OpenSource; http://www.cospa-project.org/ [6] MapServer; http://mapserver.gis.umn.edu/[7] Apache HTTPD; http://httpd.apache.org/ [8] ISO 19115; http://www.isotc211.org/scope.htm#19115[9] OpenGIS WMS; http://www.opengis.org/techno/specs/01-068r3.pdf[10] Apache Cocoon; http://cocoon.apache.org/[11] Apache Jakarta Tomcat; http://jakarta.apache.org/tomcat/index.html[12] eXist; http://exist.sourceforge.net/[13] EcmaScript Standard; http://www.ecma-international.org/publications/standards/ECMA-

262.HTM[14] XHTML; http://www.w3.org/MarkUp/[15] CSS; http://www.w3.org/Style/CSS/[16] Europe Media Monitor; http://emm.jrc.org/NewsBrief/worldedition/en/en.html[17] RSS; http://blogs.law.harvard.edu/tech/rss



7 Appendix A: OGC WMS Operations

An OGC conformant Web Map Service returns map images (i.e., visual representations rather than thegeodata itself) in response to requests delivered over HTTP (the standard protocol of the web). Thereare three WMS operations – GetCapabilities, GetMap, and GetFeatureInfo. The first one -GetCapabilities - is a request for information about the WMS. The GetCapabilities request takes theform of a standard HTTP request with a series of name-value pairs appended to a base URL:

http://143.239.249.70/cgi-bin/mapserv?map=/home/dismar/dispro-wms.map&SERVICE=WMS &VERSION=1.1.0&REQUEST=GetCapabilities

In this example, the base URL, http://143.239.249.70/cgi-bin/mapserv? map=/home/dismar/dispro-wms.map points to the configuration file dispro-wms.map of the UMN MapServer application runningon the server with IP address 143.239.249.70. The service required is WMS, version 1.1.0, and therequest is GetCapabilities. On receiving the GetCapabilities request, the server returns a Capabilitiesfile encoded in XML (Fig. 1), describing the service, including the content available and which requestparameters to use.

Based on the information provided in the returned Capabilities file, GetMap requests can now beissued to the server. The GetMap request has a similar format to GetCapabilities but many morename-value pairs. For example, the following request returns a 1024x768 pixel raster image in PNG


Illustration 11. Part of a Capabilities file returned in response to a GetCapabilitiesrequest. Note the “OnlineResource” element with the attribute “xlink:href” pointing to

the base URL, and several “Layer” elements.


format of the nature reserves layer overlaid on the bathymetry layer (Fig. 2).http://143.239.249.70/cgi-bin/mapserv?map=/home/dispro-wms/dispro-wms.map&REQUEST=GetMap&VERSION=1.1.0&FORMAT=image/png&WIDTH=1024&HEIGHT=768&LAYERS=bathymetry_low_res,nat_reserves

Other attributes of the layer that can be specified include style (STYLES), bounding box (BBOX),spatial reference system (SRS), image background colour (BGCOLOR), transparency(TRANSPARENT), time (TIME) and elevation (ELEVATION). The raster formats (e.g., png, jpeg) thatare requestable are listed under the GetMap element in the Capabilities file (Fig. 1).

Unlike the previous two operations, the GetFeatureInfo request is optional for an OGC compliantWMS. It returns information about a map feature at a particular point on the map.


Illustration 12. A GetMap request returns a raster image of the map layers (e.g.nature reserves and bathymetry) in the image format and dimensions requested.


8 Appendix B: UMN MapServer Mapfile

Part of a mapfile of University of Minnesota MapServer is shown below. The additional metadatarequired for OGC WMS compliance is indicated in red.



9 Appendix C: OGC WMS Server Nodes

Title NERSC Dispro-1

Bounding Box 51ºN - 64ºN, 4ºW - 14ºE

Data Types:ASAR (Envisat), MERIS (Envisat) or MODIS (the NASA Earth Observing System (EOS)Aqua and Terra satellites), feature interpretation (from SAR and optical data), chl-a profilesVolume:Approx. 500 k – 1 MB for raster image products, 50-100 k for interpretation (text) products.

Metadata Production and Validation: The first metadata generation and validation is done manually,by means of XMLSPY. Later, during the first demonstration phase, it is foreseen that themetadata will be generated automatically from either the original data format’s headerinformation or from a database. An XML parser, probably Xerces from Apache.org, will thenbe used for validation.Full metadata: This will not be available in phase 1 demonstration.

Web Map Server Application:University of Minnesota MapServer, version 4.0.1URL: http://www.nersc.no/cgi-bin/mapserv?map=../doc/Projects/dismar/dispro/nersc_demo1.map (simple client,password protected)

Base layers • Coastline (public domain, from GMT (Generic Mapping Tools))

• Bathymetry (not available yet)

• Gridlines (for every degree latitude and longitude within the Norwegian demo area)

Configuration forOGC WMS

Under WEB Object: METADATA "wms_title" "The NERSC OGC WMS for DISPRO-1" "wms_onlineresource" http://www.nersc.no/cgi-bin/mapserv?map=../doc/Projects/dismar/dispro/nersc_demo1.map "wms_srs" "epsg:4326" "wms_contactperson" "Torill Hamre" "wms_contactorganization" "NERSC" ENDUnder LAYER Object: METADATA "wms_title" "asar20030509" "wms_group_title" "oil" "wms_srs" "epsg:9810" END

WMS Base URL http://www.nersc.no/cgi-bin/mapserv?map=../doc/Projects/dismar/dispro/nersc_demo1.map

HTTP server http://www.nersc.no/Application: Apache web serverDirectory structure: /Projects/dismar/dispro/ is the root directory. Subdirectories include:data, metadata, multimedia, docs, news, services, mapserver, featureserver. (The site ispassword protected.)



Title GKSS Dispro-1

Bounding Box SYLT: 8.29225 E, 55.05370 N, 8.40445 E, 55.08484 N

BUESUM: 8.78245 E, 54.10196 N, 8.86412 E, 54.13982 N

Data Types:

png, gif, tiff ( all 8-bit); shapefile

Volume:

600-1200 kb each product

Metadata Production and Validation:

Metadata production is automated (included in data processing).

Validation: XMLSPY

Full metadata:

Web Map Server Application:

University of Minnesota MapServer, version 4.2

URL: http://dismar.gkss.de/ (simple client, password protected)

Base layers • BASE MAP (topo map): islands, natural reserves, mainland, coastline, nationalboundaries

• SEAMAP: depth -12, depth -10, depth -6, depth -5


Under WEB Object: METADATA "wms_title" "" "wms_onlineresource" "http://dismar.gkss.de/cgi-bin/mapserv? map=/srv/www/htdocs/dispro/cmrc-dispro.map" "wms_srs" "" "wms_contactperson" "" "wms_contactorganization" "GKSS" ENDUnder LAYER Object: METADATA "wms_title" "" "wms_srs" "epsg:" END

WMS Base URL http://dismar.gkss.de/cgi-bin/mapserv?map=/srv/www/htdocs/dispro/cmrc-dispro.map

HTTP server URL: http://dismar.gkss.de/

Application: Apache web server

Directory Structure:

/srv/www/htdocs/dispro/ data + docs + mapserver + metadata + news + services



Title PML Dispro-1

Bounding Box Approx: 7W – 5 E 47 – 53 N (subject to revision)

Data Format – mostly GeoTIFF for raster-gridded data. Shapefiles for any vector layers.

Remotely sensed and modelled parameters of ocean regions.

Unknown volume.


Automated production (database-driven is the current plan).

Full metadata:

Discovery metadata only, full in future (hopefully)


University of Minnesota MapServer, MapScript, and specially written Perl code for WMSsupport (currently very much work-in progress).

URL: http://eddy.nerc-pml.ac.uk/cgi-bin/map-wrapper.cgi ?

Base layers Base layers – unknown at the moment, but hopefully Western Europe/North Sea coastlineat least.


No mapfile as configuration for the final WMS server. A “virtual mapfile” is generated on-the-fly using perl/mapscript based on request parameters and will be database driven(again, work-in- progress).

WMS Base URL http://eddy.nerc-pml.ac.uk/cgi-bin/map-wrapper.cgi?request=getCapabilities

HTTP server URL: http://eddy.nerc-pml.ac.uk/



/dismar is the root directory.



Title TPZ Dispro-1

Bounding Box Demo area considered for Oil Spill Demonstration I: a portion of Adriatic Sea in front ofVieste Town in the southern Italy.

Lat. NW: 42.37 Long. NW: 16.02

Lat. NE: 42.18 Long. NE: 17.19

Lat. SE: 41.30 Long. SE: 16.93

Lat. SW: 41.48 Long. SW: 15.77

Data Data Type Volume

Administrative boundaries shape file 65 Mbytes

Main localities shape file 130 Mbytes

Geographic grid shape file 20 Kbytes

Oil Spill Contour shape file 90 Kbytes

Oil Spill Drift shape file

OSAD Reports html 850 Kbytes

Oil Spill Quicklooks jpeg 50 Kbytes/each


Discovery metadata on available datasets have been produced and validated by handusing XMLSPY tool. Schema used is dispro-core-19115-v5b.

Full metadata:

Production of full metadata is still under investigation.


University of Minnesota MapServer, version xx

URL: http://map.cs.telespazio.it/cgi-bin/mapserv.exe?

Layers Base:

Other:


Under WEB Object: METADATA "wms_title" "" "wms_onlineresource" "http://143.239.249.70/cgi-bin/mapserv? map=/home/dismar/dispro-wms.map" "wms_srs" "" "wms_contactperson" "" "wms_contactorganization" "" ENDUnder LAYER Object: METADATA "wms_title" "" "wms_srs" "" END

WMS Base URL http://map.cs.telespazio.it/cgi-bin/mapserv.exe ? map=D:/inetpub/wwwroot/dismar/data/test.map

HTTP server URL: http://map.cs.telespazio.it/dismar/

Application: Apache?

Directory structure: subdirectories off 'dismar' for docs, data, metadata, mapserver,featureserver, services, multimedia, news



Title CMRC Dispro-1

Bounding Box

minx="-10.7022" miny="51.3362" maxx="-8.1008" maxy="52.0305"

Data Types:

N/A

Volume:

N/A

Metadata

Production and Validation:

The first metadata generation and validation is done manually, by means of XMLSPY.

Full metadata:

Available for some layers.

WebMapServer

Application:

University of Minnesota MapServer, version 4.0.1

URL: http://143.239.249.70/cgi-bin/mapserv?

(local client, password protected)

Layers Base:

Coastline; Ordnance Survey; Bathymetry; Admiralty Charts; Colour Ortho

Other:

Aquaculture; Emergency; Habitats; Navigation Aids; Obstruction Points; PipelineCables; Pipeline Regions; Nature Reserves; National heritage Areas (NHA);Special Areas of Conservation (SAC); Services; Shore Access; Soundings;Special protected Areas (SPA).


Under WEB Object: METADATA "wms_title" "CMRC DISPRO-1 Server" "wms_onlineresource" "http://143.239.249.70/cgi-bin/mapserv? map=/home/dismar/dispro-wms.map" "wms_srs" "epsg:29900" "wms_contactperson" "Éamonn Ó Tuama" "wms_contactorganization" "CMRC" ENDUnder LAYER Object: METADATA "wms_title" "Habitats" "wms_srs" "epsg:29900" END

WMSBaseURL

http://143.239.249.70/cgi-bin/mapserv?map=/home/dismar/dispro-wms.map&

HTTPserver

N/A



Title IFREMER Dispro-1

Bounding Box

minx="-14.0" miny="40.0" maxx="0.0" maxy="47.0"

Data Types : geotiff , shape files, netcdf, grib

volume : N/A


The first metadata generation and validation is done manually, using the XMLSPY editor.

Full metadata:

N/A.


University of Minnesota MapServer, version 4.0.1

URL: http://www.ifremer.fr/delao/cgi-bin/mapserv ?

Layers Base:

Coastline; Bathymetry; EEZ

Other:

Oil Spill contours , Airborne surveillance Flights, Ship positions


Under WEB Object: METADATA WMS_TITLE "Ifremer Dispro-1" WMS_ABSTRACT "DISMAR DISPRO 1 pplication for Prestige Area." WMS_ACCESSCONSTRAINTS none

WMS_ONLINERESOURCE "http://www.ifremer.fr/delao/cgibin/mapserv.cgi?map=/home1/iletudy/www/htdocs/delao/dispro/dispro.map"

WMS_SRS "EPSG:4326" WMS_CONTACTORGANIZATION" "IFREMER" END METADATAUnder LAYER Object: METADATA WMS_TITLE "GEBCO SHORELINE" WMS_SRS "EPSG:4326" END

WMS Base URL http://www.ifremer.fr/delao/cgi-bin/mapserv.cgi?

map=/home1/iletudy/www/htdocs/delao/dispro/dispro.map&

HTTP server URL: http://www.ifremer.fr/



/delao/dispro/ is the root directory. Subdirectories include: data, metadata, multimedia,

docs, news, services, mapserver, featureserver.



Title NIVA Dispro-1

Bounding Box

4E/60N, 14E/60N, 15E/55N, 4E/55N

Data Current Ferrybox parameters collected in real time from Skagerrak are:

• Date and Time (UTC)

• Georeference (coordinates lat/lon in WGS 84)

• Chlorophyll fluorescence (µg/l)

• Turbidity (FTU)

• Temperature ( °C)

• Salinity

• Light (µE/m2/s)

Data from water samples collected on fixed intervals or during HAB situations anddetermined in laboratory.

• Algal composition (cellnumber and cellvolume).

• Chlorophyll-a concentrations (µg/l)

• Turbidity (FTU).

• Gelbstoff (m-1)

• Suspended material (mg/l)

Metadata

Manually produced by using the editor XML-Spy. Planned to be made automatic whenrealtime data is implemented in DISPRO 2. Metadata is according to schema v. 0.6.


ESRI ArcIMS 4.01

URL:

Layers Base:

Coastline

Other:

Aquaculture

ConfigurationforOGCWMS

WMSBaseURL

http://143.239.249.70/cgi-bin/mapserv?map=/home/dismar/dispro-wms.map&

HTTP server URL: www.niva.no/Dismar

directory structure:

www.niva.no/Dismar/Metadata for metadata

www.niva.no/Dismar/Dispro for Dispro node with Ferrybox data from Skagerrak

www.niva.no/Dismar/Multimedia for storing multimedia files for time sequence views.



Title Met.no

Bounding Box Area of interest for the demo is North Sea and Skagerrak, but numerical weatherpredictions (NWP) are available within met.no’s area of calculation (North West Europe)

Data Weather data

Metadata N/A. Information originates from met.no’s suite of numerical weather prediction models,which are mainly updated four times a day.

Web Map Server Application: ESRI ArcIMS

URL: http://metoc.met.no:8080/metoc/menu.jsp

Layers N/A


N/A

WMS Base URL http://metoc.met.no:8080/metoc/metocwms?

HTTP server FTP: ftp://metoc.met.no/data/data/grib/ *



10 Appendix D. Consortium and contact persons

Nansen Environmental and RemoteSensing Center (NERSC), Edv.Griegsvei 3A N-5059 Bergen,NORWAYTel: +47 55297288 Fax: +47 55200050http://www.nersc.noE-mail: [email protected],[email protected]

Norwegian Meteorological Institute(met.no), PO Box 43 Blindern0313 Oslo, NorwayTel: +47 22963000 Fax: +47 22963050http://www.met.noE-mail [email protected]@met.no

Norsk Institutt for Vannforskning(NIVA), PO Box 173 Kjelsaas0411 Oslo, NorwayTel: +47 22185275 Fax: +47 22185200http://www.niva.noE-mail: [email protected] [email protected]

Optimare GmbH Am Luneort 15 a27572 Bremerhaven, GermanyTel. +49 (0) 471 / 48361-0Fax +49 (0) 471 / 48361-11http://www.optimare.deE-mail: [email protected]@optimare.de

GKSS GmbH, Institute for CoastalResearchMax-Planck-Strasse 121502 Geesthacht, GermanyTel: +49 4152 87 2827Fax: +49 4152 87 2818http://www.gkss.deE-mail: [email protected]

Ruhr-Universitat Bochum, Institut fuerNeuroinformatik Universitaet-strasse150, 44780 Bochum, GermanyTel. +49 234 322 7965Fax. +49 234 321 4209http://www.ruhr-uni-bochum.deE-mail:[email protected]

Telespazio spa - Osservazioni dellaTerra - Centro spaziale di MatteraContrada Terlecchia, 75100 Matera,ItalyTel. +39 0835 377437Fax +39 0835 330022http://www.telespazio.itE-mail: [email protected]

Agencia Spaziale Italiana (ASI), Centrodi Geodesia SpazialeLoc. Terlecchia, 75100 Matera, ItalyTel. +39 0835 377220Fax +39 0835 339005http://www.asi.itE-mail: [email protected]

Universita degli studi del PiemonteOrientale Dipartimento di Scienze eTechnologie AvanzateC.so Borsalino 5415100 Alessandria, Italy,Tel. +39 0131 283857Fax. +39 0131 254410http://www.unipmn.it E-mail: [email protected]

Coastal & Marine Resources Centre(Ionad Acmhainní Cósta is Mara)ERI, University College Cork,Naval Base, Haulbowline,Cobh, County Cork,IrelandTel: +353 21 4703100Fax: +353 21 4703132http://cmrc.ucc.ieE-mail: [email protected],[email protected]

Plymouth Marine Laboratory (PML)Prospect Place, West HoePL1 3DH Plymouth, UKTel. +44 1752 633150Fax. +44 1752 633101http://www.pml.ac.ukE-mail: [email protected]

Joint Research Centre (JRC)Institute for the Protection andSecurity of the Citizen (IPSC)TP 270, Via E. Fermi21020 Ispra, ItalyTel. +39 0332 785044Fax. +39 0332 785032http://www.jrc.itE-mail: [email protected]

Ecoles des Mines, CentreTeledetection & ModelisationPO Box 207Rue Claude Daunesse Les Lucioles,06904 Sophia Antipolis, FranceTel. +33 4 93 95 74 60Fax. +33 4 93 95 75 35http://www.ensmp.frE-mail: [email protected]

CEDREPO Box: BP 20413Rue Alain Colas29604 Brest, FranceTel. +33 4 94304887Fax. +33 4 94301372http://www.cedre.frE-mail: [email protected]

IFREMERPO Box 7029280 Plouzane, FranceTel. +33 298 224310Fax. +33 298 224555http://www.ifremer.frE-mail: [email protected]

EU Project OfficerMario Verdese: European CommissionDirectorate General InformationSocietyMail: BU31 5/50, B-1049 BrusselsOffice: Av. de Beaulieu 31, B-1160BrusselsTel: +32 2 2963518 Fax: +32 2 2991749E-mail: [email protected]


Documents

Data Integration System for Marine Pollution and Water Quality · 2006. 3. 6. · Data Integration System for Marine Pollution and Water Quality Deliverable D6.2 Final Report on DISPRO-1