Hi.
I made a workaround for this a while ago (I think we were using
Mapserver 4.10 at the time). It's possible there are better ways to
solve this now, but it still works :)
I can give more details tomorrow, but the gist of it is that I've made
an Apache handler (mod_perl) that modifies the
Yes, this is how the client is defined:
LAYER
CONNECTION "http://wms-server/dataset.wms?;
CONNECTIONTYPE WMS
DEBUG 4
METADATA
"wms_srs" "EPSG:3857"
"wms_exceptions_format" "XML"
"wms_cmap""Current_cms_WGYR_11colors_1.0"
"wms_transparent" "TRUE"
Hi Søren,
Just to clarify you are using MapServer as a WMS Client as outlined here
https://mapserver.org/ogc/wms_client.html
With "CONNECTIONTYPE WMS"?
Seth
--
web:http://geographika.co.uk
twitter: @geographika
On Wed, Aug 7, 2019, at 7:55 PM, Søren Laursen wrote:
> Hi,
>
> We have been
Hi,
We have been using mapserver to display static layers, and are now in progress
of using it to display dynamic (time bound) layers.
We have a wms server that serve forecast, and we use a shape file to mask out
areas, for example cut a forecast so it follow landmass.
This works perfect, but
