Locked History Actions

WebClients

WebClients in deegree2

1. deegree portal

There are two deegree portal web clients to view data provided by OGC web services.

  • deegree portal standard edition
    1. is based on html, javascript, JSP, and is running with Java 1.5 and Apache Tomcat 5.5.*
    2. supports user login to check access rights for restricted service data
    3. is expandable in functionality by adding new modules
    4. available modules are: map view, map overview, toolbar (with pan, zoomin, zoomout, zoom2layer, map action history, feature info for selected layers, loading additional layers from WMS, printing), scale selection, switching between different contexts, switching between different contents, simple and dynamic legend generation, layer list view, , storing map contexts, loading stored map contexts, pdf-creation for printing, digitizing, gazetteer-client, csw-client
    5. can be combined with deegree security administration (drm-admin) to define start contexts for logged in users.
  • deegree portal portlet edition
    1. portlet edition based on Apache Jetspeed of deegree portal
    2. personalized GUI and functionality is supported
      • for each user a specific GUI/layout can be defined
      • depending on his rights a user is able to change layout and available modules
    3. a lot of modules/portlets are available for deegree portal
      • each portlet compliant to Jetspeed can be integrated
      • following deegree modules/portlets are available: map view, toolbar, overview, coordinate system selection, scale selection, digitizing, share contexts/projects, pdf-creation, deegree security administration (drm-admin), owsWatch - controlling state of OGC web sevices
    4. deegree portal portlet edition supports tabs/multi-pages

2. owsWatch

web-based application which can be used to monitor the availability of different OGC web services like deegree WMS, WFS, CSW.

owsWatch will notify the user per email (or through its interface) if any of the monitored services is experiencing any problems. These might be high traffic that caused response latency or the service suffered a failure altogether. Monitoring a service is done by sending standardised requests (like GetCapabilities form a WMS). These requests can be configured by the user of owsWatch with certain constraints on that test ( e.x. timeout, repeat times ) to test if the service is running.

  1. supports HTTP GET (with KVP requests) and HTTP POST (with XML requests)
  2. supports OGC web services in different versions: WMS 1.1.1, WFS 1.1.0, WCS 1.0.0, CSW 2.0.2, SOS 1.0.0
  3. supports GetCapabilities for all supported service types

  4. supports a service specific request for each service type (WMS:GetMap, WFS:GetFeature, WCS:GetCoverage, CSW:GetRecords, SOS:DescribeSensor)

  5. notifies the user per mail on case of response failure
  6. generates protocol files for each monitored service instance

3. drm-admin

web client for setting user/groups access rights on web service components as layers and featuretypes

The user can edit the following aspects of the U3R security system:

  • manage users
  • manage roles
  • manage groups
  • manage which users and groups belong to which groups
  • manage which groups have which roles
  • manage the rights of roles

Depending on the configuration, you can EITHER:

  • import layers/feature types from WMS/WFS into the database by requesting the services' capabilities
  • set which role can access which layers/feature types

OR:

  • add layers/feature types by typing them in
  • set which role can access which layers/feature types
  • set fine grained rights like:
    • feature types: insert/update/delete rights
    • layers: bbox, background color, width/height, exception formats, max. resolution, image formats, transparency

4. deegree coordinateCalculator

The deegree coordinateCalculator is a web based client to convert coordinates from one coordinate reference system (aka CRS, SRS) to another. The client is realised as Java webapp (Java Servlet, Java Server Pages).

There are two different modes for running the transformation:

  1. Single Mode:
    one pair of coordinates is transformed from source CRS to target CRS. The user may choose source and target CRS from a list of configurable sets of CRSs. The result of the transformation is presented on the web page.

  2. Batch Mode:
    an arbitrary number of coordinate pairs is transformed from source CRS to target CRS. The coordinate pairs need to be provided in one of the input formats and may be transformed to one of the corresponding output formats (see table below). The transformation result is stored in a file on the server and may be downloaded by the user. The download address is provided via email.

    input

    output

    *.csv / *.txt

    *.tab

    *.xls

    *.shp

    *.kml

    *.csv / *.txt

    (./)

    (./)

    (./)

    *.tab

    (./)

    (./)

    (./)

    *.xls

    (./)

    (./)

    (./)

The deegree coordinateCalculator uses the deegree CRS package as a backend for all transformations/projections (see description of the deegree CRS package). The deegree coordinateCalculator is preconfigured for a set of 12 different coordinate reference systems. It is possible to extend support to any of the coordinate reference system that are supported by deegree, by adding those to the configuration file.

5. deegree catalogueManager

The deegree catalogueManager is a web based tool for creating, editing and using standardised spatial metadata sets. Please see deegree catalogueManager


CategoryDeegree2