[mapserver-users] Mapserver as WMS client, legend pass-through . . .

Wed Jun 13 00:24:25 PDT 2012

Hi Bob b,

I have not used GeoMoose myself (not even sure what they mean with a
legend "chip"). So I am afraid I have no further clues...

Barend

On 12-06-12 20:33, "Basques, Bob (CI-StPaul)"
<bob.basques at ci.stpaul.mn.us> wrote:

>
>
>
>Barend,
>
>I can add this into the LAYER and get a label in a Mapserver Legend call:
>
>CLASS
>NAME "WS Distribution Mains"
>END
>
>But still no Legend Chip . . .
>
>bobb
>
>
>
>________________________________________
>From: mapserver-users-bounces at lists.osgeo.org
>[mapserver-users-bounces at lists.osgeo.org] on behalf of Barend Köbben
>[kobben at itc.nl]
>Sent: Tuesday, June 12, 2012 12:49 PM
>To: mapserver-users at osgeo.org
>Subject: Re: [mapserver-users] Mapserver as WMS client, legend
>pass-through . . .
>
>Hmm, I clearly didn't read your original post well enough, sorry... The
>easy solution would be to have the legend embedded in the WMS image (use
>STATUS EMBED in the LEGEND object). Won't be useful if you want the WMS in
>a tiled fashion, though...
>
>Barend
>
>
>
>
>
>On 12-06-12 17:44, "Basques, Bob (CI-StPaul)"
><bob.basques at ci.stpaul.mn.us> wrote:
>
>>you, I figured that out from the WMS request, but how to implement that
>>via the Mapserver WMS client we have in place.
>>
>>I can get a LEGEND graphic like this for example:
>>
>>http://wsgisserver.water.stpaul.city/ArcGIS/services/AUTOCAD/MapServer/WM
>>S
>>Server?request=GetLegendGraphic%26version=1.3.0%26format=image/png%26laye
>>r
>>=2&width=200
>>
>>but how to add this call into the MAPFILE for Our Mapserver client.
>>
>>bobb
>>
>>
>>________________________________________
>>From: Barend Köbben [kobben at itc.nl]
>>Sent: Tuesday, June 12, 2012 10:33 AM
>>To: Basques, Bob (CI-StPaul); mapserver-users at osgeo.org
>>Subject: Re: [mapserver-users] Mapserver as WMS client, legend
>>pass-through . . .
>>
>>Hi,
>>
>>In the "WMS world" you get a legend by requesting it with a
>>GetLegendGraphic request, something like:
>>
>>http://geoserver.itc.nl/cgi-bin/mapserv.exe?map=D:/Inetpub/mapserver/conf
>>i
>>g
>>OL.map&SERVICE=WMS&REQUEST=GetLegendGraphic&VERSION=1.1.1&FORMAT=image/pn
>>g
>>&
>>LAYER=forest
>>
>>And you can do this for any of let LAYERs you have in you MAP file...
>>
>>Barend
>>
>>--
>>Barend Köbben
>>Senior Lecturer, ITC - University of Twente,
>>Faculty of Geo-Information Science and Earth Observation
>>PO Box 217, 7500AE Enschede (The Netherlands)
>>+31-(0)53 4874 253
>>
>>
>>
>>On 12-06-12 17:12, "Basques, Bob (CI-StPaul)"
>><bob.basques at ci.stpaul.mn.us> wrote:
>>
>>>All,
>>>
>>>I have this MAPFILE which works fine for a Map image, but how do I get a
>>>WMS legend from the upstream WMS service? Do I need to set up a LAYER
>>>(like) definition inside of a LEGEND block for a mode=legend to work
>>>downstream. Right now I get a blank image.
>>>
>>>I don't see any information on the topic in this page:
>>>
>>>http://mapserver.org/ogc/wms_client.html#mapfile-configuration
>>>
>>>About WMS Legend pass-through . . .
>>>
>>>Thanks
>>>
>>>bobb
>>>
>>>
>>>------------
>>>
>>>MAP
>>> NAME 'WS_Distribution_Mains'
>>> SIZE 800 650
>>> EXTENT 593133.398829 170094.734526 593893.148973 170712.010326
>>>
>>> STATUS ON
>>> UNITS FEET
>>> IMAGETYPE PNG24
>>>
>>> PROJECTION
>>> "init=epsg:200068"
>>> END
>>>
>>> LAYER
>>> NAME "WS distribution Mains"
>>> TYPE RASTER
>>> STATUS DEFAULT
>>> CONNECTION
>>>"http://XXX.stpaul.city/ArcGIS/services/AUTOCAD/MapServer/WMSServer?"
>>> CONNECTIONTYPE WMS
>>>
>>> METADATA
>>> "wms_srs" "EPSG:4326"
>>> "wms_name" "2"
>>> "wms_server_version" "1.1.1"
>>> "wms_format" "image/png24"
>>>
>>> "ows_title" "0"
>>> "gml_include_items" "all"
>>> END
>>>
>>> PROJECTION
>>> "init=epsg:4326"
>>> END
>>> END #layer
>>>
>>> ##CONFIG "MS_ERRORFILE" "/tmp/trying2.txt"
>>> ##DEBUG 5
>>>
>>>END
>>>
>>
>>
>>Faculty of Geo-Information Science and Earth Observation (ITC)
>>University of Twente
>>Chamber of Commerce: 501305360000
>>
>>E-mail disclaimer
>>The information in this e-mail, including any attachments, is intended
>>for the addressee only. If you are not the intended recipient, you are
>>hereby notified that any disclosure, copying, distribution or action in
>>relation to the content of this information is strictly prohibited. If
>>you have received this e-mail by mistake, please delete the message and
>>any attachment and inform the sender by return e-mail. ITC accepts no
>>liability for any error or omission in the message content or for damage
>>of any kind that may arise as a result of e-mail transmission.
>>
>>
>
>
>Faculty of Geo-Information Science and Earth Observation (ITC)
>University of Twente
>Chamber of Commerce: 501305360000
>
>E-mail disclaimer
>The information in this e-mail, including any attachments, is intended
>for the addressee only. If you are not the intended recipient, you are
>hereby notified that any disclosure, copying, distribution or action in
>relation to the content of this information
> is strictly prohibited. If you have received this e-mail by mistake,
>please delete the message and any attachment and inform the sender by
>return e-mail. ITC accepts no liability for any error or omission in the
>message content or for damage of any kind that
> may arise as a result of e-mail transmission.
>_______________________________________________
>mapserver-users mailing list
>mapserver-users at lists.osgeo.org
>http://lists.osgeo.org/mailman/listinfo/mapserver-users
>

Faculty of Geo-Information Science and Earth Observation (ITC)
University of Twente
Chamber of Commerce: 501305360000

E-mail disclaimer
The information in this e-mail, including any attachments, is intended for the addressee only. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or action in relation to the content of this information is strictly prohibited. If you have received this e-mail by mistake, please delete the message and any attachment and inform the sender by return e-mail. ITC accepts no liability for any error or omission in the message content or for damage of any kind that may arise as a result of e-mail transmission.