just forgot to reply all
-------- Forwarded Message --------
From: Gabriel Roldán <groldan@anonymised.com>
To: Paolo Rizzi (JIRA) <jira@anonymised.com>
Subject: Re: [jira] Commented: (GEOS-341) Virtual WMS layers
Date: Fri, 13 May 2005 22:35:16 +0000
actually it is covered by the spec under the term "nested layers" if my
memory serves me right, and is something I'd never had the time to do
but always waiting the moment for.
Note this is inline with the need of better WMS configuration we talked
about a time ago, since not only we should be able of doing this, but
combining Layers from different sources beyond the featuretypes, like
gridcoverages, remote WFS's and cascaded WMS (like serving a MapServer
layer on a remote server)
So I keep thinking we should sit and think a bit on this as a whole, may
be taking Web Map Context documents as the configuration formats with a
needed extensions, if any.
Gabriel.
On Fri, 2005-05-13 at 10:39 -0500, Paolo Rizzi (JIRA) wrote:
[ http://jira.codehaus.org/browse/GEOS-341?page=comments#action_38998 ]
Paolo Rizzi commented on GEOS-341:
----------------------------------This would be a very much appreciated feature!!!
Bye
Paolo Rizzi> Virtual WMS layers
> ------------------
>
> Key: GEOS-341
> URL: http://jira.codehaus.org/browse/GEOS-341
> Project: GeoServer
> Type: New Feature
> Components: WMS
> Versions: 1.3.0-beta3
> Environment: all
> Reporter: dblasby
> Assignee: Gabriel Roldán
> Fix For: 1.4>
>
> Currently, the layers in the WMS are 1:1 with the FeatureTypes (and that FeatureType's default style).
> It would be great if you could create an (unqueryable) layer based on an SLD. This would be an SLD with a set of NamedStyles in it.
> For a more concrete example, I have a nice TIGER map. Its composed of a few 'base' layers (ie. roads, parks, and lakes) which I have a set of Styles for. I'd like to have Geoserver serve this up as an easy-to-grab single layer.
> Basically:
> 1. The user creates an SLD based on a set of NamedStyles (or, if you want to be even more tricky any SLD)
> 2. The user also provides a name for this layer
> 3. Geoserver WMS then advertises this layer, with these restrictions:
> a) its unqueriable (or you can have it try to query all the sublayers)
> b) you cannot re-style the layer. If you try to restyle the layer, it doesnt actually change the appearance. (it possible to remove this restriction, but I think it would be pretty complex for everyone involved. Basically, you'd have to make a big feature collection of ALL the sub-layer FeatureTypes. Yuck!)
> In the end you're converting a request like this:
> layers=layer1,layer2,layer3,layer4&styles=style1,style2,style3,style4
> into:
> layers=my_virtual_layer
> For my concrete TIGER example, lets say someone one to put a fireHydrant layer on the TIGER set. Currently, they have to do this:
> layers=giant_polygon,poly_landmarks,finalRoads,point_landmarks,fireHydrant
> styles=....
> With the virtual layer they could just request:
> layers=tiger_basemap,fireHydrant
> styles=default,myFireHydrantStyle