Locked History Actions


deegree 3 terrainService

NOTE: This deegree 3 component is currently unmaintained and the documentation may be out-of-date. If you're interested to become the maintainer of this module, please contact the deegree-devel list.

The deegree terrainService is part of the deegree3D suite. It is an implementation based on OpenGISĀ® Web Perspective View Service (WPVS) Implementation Specification, Draft proposed version 1.0 which evolved from the WTS (Web Terrain Service). A WPVS is a web service which is able to generate perspective terrain views, e.g. images of a certain terrain/area (possibly containing three dimensional objects, e.g. building or trees) rendered from a requested viewpoint.

In deegree 2 there is a WPVS implementation as well, it is described at WebServices#WebPerspectiveViewService. Due to implementation improvements, usage of deegree 3 terrainService is recommended.

1. Features of the implementation

  • TBD

2. See a demo installation


3. Get it up and running in 5 minutes

  1. Make sure that you have installed the system requirements on your machine.

  2. Make sure that your machine matches the additional 3D requirements for using deegree's 3D components.

  3. Currently, no binary builds are available to run the deegree 3 terrainService. One needs to retrieve the code from the SVN repository and build it. The needed modules are deegree-core, deegree-services and deegree-tools. Maven- and Eclipse- based building processes are documented on this wiki. Furthermore, one usually needs texture files (whose location is specified in the d3_services/resources/example/conf/wpvs/wpvs_configuration.xml file) that will be accessed to render the datasets.

  4. Running any WPVS client needs a larger amount of memory than is allocated by default. Therefore the JAVA_OPTS variable should be exported with the options '-Xmx????M' and '-XX:DirectMaxMemorySize=????M', where the questions marks need to be replaced by values (in Megabytes) that suit one's system. Some experimenting is recommended before a good compromise between speed and memory is achieved.

  5. Running the InteractiveWPVS can be done once the d3_tools module is built. In the d3_tools/build/ directory, the d3toolbox.sh script runs all the available tools. We will run the InteractiveWPVS:

    ./d3toolbox.sh InteractiveWPVS -wpvsconfig file:/../d3_services/resources/example/conf/wpvs/wpvs-configuration.xml
  6. Deploying the web application into Tomcat is done in the terminal as follows (one needs to be in the d3_services directory):

    ant create-wpvs-template
    ant register-webapp-dir

4. Configuration basics

Like every other deegree 3 application, the configuration of the deegree terrainService is based on the common deegree3/WorkspaceConfiguration concept.

The terrainService is based on an OGC (Open Geospatial Consortium) defined protocol. For an introduction to OGC based deegree 3 service please read the OGCWebservices page. The page you are currently reading describes the terrainService specific part of the installation/configuration.

For the purposes of the terrainService needs to process and render different kinds of geospatial data which is retrieved from different pre-configured datasets. These datasets can be remote OGC web services or locally installed deegree 2 web services.

With the deegree terrainService it is easy to display vector based- as well as raster data from different storage formats and deliver it to any client that is able to perform a HTTP GET or POST request (at the moment, only GET requests are supported). The currently supported storage formats are:

  • PostgreSQL / PostGIS Oracle (Spatial / Locator) databases allowing JDBC-connections ESRI Shapefiles

(all provided by the deegree featureService)

  • GML2 and GML3 provided by a OGC WFS 1.1.0 JPEG, GIF, PNG, BMP, TIFF and GeoTIFF images (provided by the deegree coverageService) OGC WMS 1.1.0/1.1.1/1.3.0

5. Preparing elevation-model and raster data

5.1. DEM

Please see DigitalElevationModel page.

5.2. Raster data


6. Library dependencies