[Geoserver-devel] Re: <LegendURL> tag in GetCapabilities document (continued)

My email client decided to send the message before I finish writing, so I continue here:

I completelly understand what you say.
Anyway, I think that for classification maps there still makes sense to
create the legend graphic dynamically. Indeed I guess it would be
better.
Don't know how fast you need this functionality, but it could be a good
idea to work together on it.

I think it does not exists, so may be we can ellaborate a simple protocol for
a GetLegend request and if it works, send it to OGC for inclussion in the WMS spec.

Wich features it should address?

- It should be able to recieve a request for a legend, containing the feature type(s) it
ferers to.
- that request should contain the SLD, named or inline, for the given feturetype(s)
- and, the request should contain additional information for the legend's output properties,
such as font color, size and name (in the case the legend for a classification map can hold both
the graphic representation, say a mini polygon, and the text for each class, say a feature attribute,
a range of values it applyies to, etc)

well, we can keep talking about it if makes sense for you.

cheers,

Gabriel.

On Tue, 2004-10-05 at 23:58, Charles Kolbowicz wrote:

Gabriel Roldán a écrit :

>the way I think we should go for legendurl support is:
>
>The URL for the LegendURL element should reference a dynamic resource
>(say, a servlet) wich builds the legend based on the CGI parameters
>passed in.
>
>for example:
><LegendUrl>
>localhost:8080/geoserver/wms/GetLegend?style=<namedStyle>
></LegendUrl>
>
>
Indeed that's a good way to automaticly produce a legend from a SLD
file. However in some complex cases we need to reference a static image,
as for classification maps (clustering maps ? don't know the exact
translation) where differents rules are applied according to attribute
values.
I am far from having a global view of your WMS but a fast solution is
perhaps to include a <LegendURL> tag in info.xml files for each feature
types configured, and to manage it in the GetCapabilities document
generated.

Charles