Automatic WMS views.

[pacesm]

Synopsis:

Currently the WMS views for Referenceable Datasets are created on-the-fly by warping and range-stretching of the original data which is very slow for fairly big real satellites products making this functionality unusable. The issue is typically solved by registering additional pre-rendered (full-resolution) browse images. When these browse images are registered in the same instance of the EOxServer, WMS cannot be blocked for the referenceable datasets (needed by the browses) leaving a severe DoS risk (a couple of WMS requests for Referenceable Datasets kills the server). Another option is to create two instances of EOxServer, one serving the data (blocked WMS) and second serving the pre-rendered browses only.

Although this issue primarily applies for Referenceable Datasets it may be relevant for other coverage types as well.

Proposed Solution:

1. Allow blocking of the default WMS views for individual coverages. Preferably blocked by default unless explicitly requested during registration due to the inherent DoS vulnerability.

2. Allow registration of one or more pre-rendered, performance optimised browse views (warped to one or more projections, RGB/Greyscale range-stretched, with overviews) as additional coverage data items. The WMS service shall than preferably use the pre-rendered browses instead matching the requested projection.

[constantinius]

This issue is fixed using Products and Browses. When a browse image (a pre-rendered, rectified RGB image) is registered with a product the render performance is increased.

There is, however, no way yet to disable the rendering of referenceable coverages in WMS requests when no browses are available.

TODO:

• [ ] add documentation/examples for registering such product + browse