[Mapserver-users] question about legendurl_href in the history.txt file

[Daniel Morissette]

Pagurek, Debbie wrote:
> Could someone explain what the following note means? It is in the history.txt document that is released with mapserver 4.2.
> 
> I can't make sense of it or how to implement legendurl_href.
> 
> 
> "Replace wms_style_%s_legendurl, wms_logourl, wms_descriptionurl, wms_dataurl 
>   and wms_metadataurl metadata by four new metadata by metadata replaced. The 
>   new metadata are called legendurl_width, legendurl_height, legendurl_format, 
>   legendurl_href, logourl_width, etc...
>   Old dependancy to the metadata with four value in it , space separated, are 
>   not kept."
> 

Ouch!  That's a bad one... I had to re-read it almost 10 times to make 
sense of it...

First of all, you can't implement legendurl_href in WMS Capabilites yet, 
the comment above applies only to WMS context, the support of LegendURL 
in the WMS capabilities is still an open issue, see
http://mapserver.gis.umn.edu/bugs/show_bug.cgi?id=438

IIRC, what the comment above tries to say is that the following metadata 
were used before by the WMS context code, and that each of them used to 
expect a different number of parameters delimited by spaces:
    wms_style_%s_legendurl
    wms_logourl
    wms_descriptionurl
    wms_dataurl
    wms_metadataurl

This was a mess since some of the above included 4 space-delimited 
values (width, height, format, url) and some included only 2 (only 
format and url since width/height don't make sense for DataUrl for 
instance), so each of the above was replaced by a set of 4 metadata 
entries instead.
e.g.
wms_style_%s_legendurl has been replaced with:
    wms_style_%s_legendurl_width
    wms_style_%s_legendurl_height
    wms_style_%s_legendurl_format
    wms_style_%s_legendurl_href

wms_logourl has been replaced with:
    wms_logourl_width
    wms_logourl_height
    wms_logourl_format
    wms_logourl_href

... and so on for each of the 5 old metadata values above that were 
split into 4 values the same way.

I'll copy this explanation to the bug.

Daniel
-- 
------------------------------------------------------------
  Daniel Morissette               dmorissette at dmsolutions.ca
  DM Solutions Group              http://www.dmsolutions.ca/
------------------------------------------------------------