Opened 19 years ago
Last modified 15 years ago
#1019 assigned defect
support legend graphic generation for WMS layers — at Version 7
Reported by: | Owned by: | mapserverbugs | |
---|---|---|---|
Priority: | normal | Milestone: | 6.0 release |
Component: | WMS Client | Version: | 4.3 |
Severity: | trivial | Keywords: | |
Cc: | debbie.pagurek@…, tomkralidis, sholl, nhermann |
Description (last modified by )
When mapserver acts as a WMS client, it does not use the legendurl metadata to generate legend icons. It would be very nice if mapserver would be able to generate legend icons for remote WMS layers from the legendurl metadata. An acceptable limitation would be to require all the metadata that is created when loading a context file. The intention would be to have legend icons show up in both the mapserver legend and the legend template processor output.
Change History (7)
comment:2 by , 19 years ago
For wms layers, we should alaways have 2 metadatas at the layer level for the legend icnon to be generated : - "wms_style" "sytle_name" - "wms_style_<style_name>_legendurl_href " "http..." We should not think about automatically using a GetLegendGraphic request becase we do not know at that point if the server supports such a request. Applications could setup the legendurl_href metadata to a GetlegendGraphic if that is possible. Thinking about it the current GetlegendGraphic in Mapserver supports the RULE paramater (to select the class) and returns an icon, anf if no RULE is specified it returns all the classes with the labels. I think we should have the possiblity to return an icon for the first class without spcifying a RULE if there is someting like ONLY_FISRT_ICON (or something) specified in the request. I think Cubewerx uses this kind of solution. This will make it easier for applications to generate the GetLgenedGraphic url (since they do not have to do a GetStyles request and parse it to extract the rule name)
comment:3 by , 19 years ago
Is there a way that this url to get a single icon when no rule is specified can be advertized in capabilities? Keep in mind that you cannot just craft this url in the WMS client (unless you go back to capabilities, etc.): the legend graphic url has to come from capabilities.
comment:4 by , 19 years ago
Cc: | added |
---|
I don't see how this can be advertized in the capabilities We can still support the wms_style ans wms_style_<name>_legnedurl_href and leave the application the task of setting the value properly after doing a getStyles on the layer. Paul is this acceptable ? I have added Tom in cc since his opinion on this can be valuable.
comment:5 by , 19 years ago
I agree w/ Assefa. We should stay away from WMS Client automatically generating the GetLegenGraphic, and use whatever is in "wms_legendurl_href", which may or may not be a GetLegendGraphic request URL.
comment:6 by , 19 years ago
Cc: | added |
---|
comment:7 by , 16 years ago
Description: | modified (diff) |
---|---|
Milestone: | 5.0 release → 5.2 release |
Note:
See TracTickets
for help on using tickets.