Is there a way to include one <LegendURL> tag per FeatureType <Style> definition in the GetCapabilities document ? I try to handle some different config files but unsuccessfully.
Regards
Charles
No LegendURL support yet. If you give me an idea of how to do it I can
probably implement, or point you in the right direction. What would be
the easiest way for a user to configure this? I don't have a ton of
WMS experience, but am willing to learn to get things right. Gabriel
also might be able to help out, he's contemplating adding full WMS-SLD
support.
Chris
Quoting Charles Kolbowicz <Charles.Kolbowicz@anonymised.com>:
Is there a way to include one <LegendURL> tag per FeatureType <Style>
definition in the GetCapabilities document ? I try to handle some
different config files but unsuccessfully.Regards
Charles
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on
ITManagersJournal
Use IT products in your business? Tell us what you think of them.
Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find
out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
----------------------------------------------------------
This mail sent through IMP: https://webmail.limegroup.com/
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>
(I don't remember the syntaxis but that's the idea)
Need to check the spec to be more precise, but I think it could work.
gabriel.
On Tue, 2004-10-05 at 15:03, cholmes@anonymised.com wrote:
No LegendURL support yet. If you give me an idea of how to do it I can
probably implement, or point you in the right direction. What would be
the easiest way for a user to configure this? I don't have a ton of
WMS experience, but am willing to learn to get things right. Gabriel
also might be able to help out, he's contemplating adding full WMS-SLD
support.Chris
Quoting Charles Kolbowicz <Charles.Kolbowicz@anonymised.com>:
>
> Is there a way to include one <LegendURL> tag per FeatureType <Style>
> definition in the GetCapabilities document ? I try to handle some
> different config files but unsuccessfully.
>
> Regards
>
> Charles
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on
> ITManagersJournal
> Use IT products in your business? Tell us what you think of them.
> Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find
> out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>----------------------------------------------------------
This mail sent through IMP: https://webmail.limegroup.com/-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
Gabriel Roldán (gabriel.roldan@anonymised.com)
Director
Axios Engineering
te: (+34) 94 441 63 84
fax: (+34) 94 441 64 90
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
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 ellabo
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
--
Gabriel Roldán (gabriel.roldan@anonymised.com)
Director
Axios Engineering
te: (+34) 94 441 63 84
fax: (+34) 94 441 64 90