deegree3 mapService Requirements

ID

Feature

Minispec

Status

Priority (M-S-C-W)^(*)

Discussion

wms-g01

support automatic crs transformations for cascaded WMS layers (GetMap, GetFeatureInfo)

This requires transforming envelopes upon requests and transformation of resulting coordinates for the responses.

testing (GetMap)

M

-

wms-g02

support automatic calculation of scales in different formats

Should be specified in configuration as "real scales" as stated in WMS 1.3.0 spec. and transformed to WMS 1.1.1 ScaleHint as specified in WMS 1.1.1 spec if GetCapabilities is requested with version=1.1.1

testing

M

-

wms-g03

support requestable layers with any number of data sources, separated by scale

This can be implemented by supporting at most one data source per layer, and by supporting 'invisible' layers (previously called data sources). That way, one can avoid duplication of concepts on layer and data source level.

testing

M

AP: datasources also should be seperable by filters (especially spatial); I don't agree to implementation hints; we already discussed this in context of WPVS

wms-g04

add a vendor-specific parameter: PROPERTYNAME/PROPERTYVALUE

With the propertyname/-value one can filter by eg. an ID value to quickly select feature(s) to be rendered (without the need to resort to SLD).

not started

M

-

wms-g05

add a vendor-specific parameter: WKT

Request GetFeatureInfo/GetMap(?) for all features intersecting the given WKT geometry. See also deegree 2 implementation using a specialized datasource configuration (for each layer).

not started

M

-

wms-g06

add a vendor-specific parameter: MARK

Mark (=render in a different style) one or more features in a map (layer) identified by the WKT or PROPERTYNAME/-VALUE VSP. To be cross-checked with deegree 2 implementation (who is the author?)

not started

M

-

wms-g07

improve logging

Improve logging to make debugging more comfortable: (just an example: log, if a layer is requested outside scale range or bbox.)

testing

S

-

wms-g08

improve GetLegendGraphic configuration

Possibly by defining/choosing from templates for generated legends.

not started

S

AP: automatic legend generation from style-definition should also be improved

wms-g09

improve performance

?

in progress

M

some enhancements already done

wms-g10

support TIME/ELEVATION and other dimensions

?

testing

M

-

wms-g11

support protocol version 1.3.0

?

testing

M

-

wms-g12

support other protocol versions

Only OGC WMS version 1.1.1. will be supported additionally to 1.3.0. 1.1.0 won't be supported

testing

M

-

wms-g13

prevent application restart after configuration change

Three implementation options: 1.) dynamic layers: specify directory of shape files or specify PostGIS database (and use all geometry tables), 2.) use a java class for manipulating the layer tree, 3.) automatic reloading of main configuration file

in progress

M

Make option 2 a plugin?

wms-g14

support caching/an optimized data model

Like WPVS?

?

C

shall be moved to data access requirements

wms-g15

support KML, HTML image maps and PDF as output format

Needs spec.

not started

C

-

wms-g16

support WMTS protocol

Besides the protocol support, tool support is needed to generate tile images.

not started

C

after WMTS adoption

wms-g17

add vendor-specific parameters for authentication and authorisation: USER/PASSWORD/SESSIONID

To be used with deegree security.

?

M

JF: Other security concepts to be supported as well? AP: Don't understand that; why should WMS understand these parameters? And if it must be understood there should be support for all authentication mechnism supported by deegree

wms-g18

improve tolerance for request and configuration errors

WMS should be more tolerant according to configuration errors and invalid requests; level of tolerance should be configurable (e.g. loose, strict, very strict). Levels need to be specified more detailed.

in progress

S

to be clarified

wms-g20

add a vendor-specific parameter: SQL

a SQL statement may be assigned to each layer (if supported) that overrides server-side configuration

?

C

see also da-g08

wms-g19

support complex feature types

applies to configuration and GetMap/GetFeatureInfo handling

?

?

already included in other requirements

wms-s01

support GetStyles/PutStyles, style repositories

Needs concept of persistent style storage.

postponed

W

needs better spec – open discussion if the WMS-based concept is more or less useful than an alternative implementation using Registry technology

wms-s02

support other SLD requests (POST GetMap, DescribeLayer)

?

not started

M

was supported in deegree 2

wms-s03

define style catalogue

Spec needed: internal styles? Collection of SE documents?

?

S

-

wms-s04

support scale dependent styling

This is supported by SE/SLD, and can easily be implemented.

testing

M

-

wms-f01

improve flexibility for GFI on cascading layers

GFI for layer set up on a cascaded WMS should be improved. E.g. there may be a lookup function that enables selecting correct transformation script (XSLT) by setting the vendor and version of the cascaded WMS.

not started

S

-

wms-f02

support for raster data

GFI on raster data should be possible.

testing

M

-

wms-f03

improve flexibility/ease of use for GFI output formats

Simplify configuration for layouting GFI responses; beside registering XSLT scripts (for each layer/datasource) it should be possible to register HTML fragment templates for each layer/datasource.

not started

M

-

wms-f04

support complex feature types

Support for complex schemas for GetFeatureInfo (GFI)

not started

M

-

wms-f05

support VSP QUERYGEOMETRY

A WKT-encoded geometry can be used for feature retrieval

not started

C

-

wms-f05

support of multiple concatable db fields for Text Symbolizer

Additional Text/Symbols not include in DB should be addable

not started

M

-