Dear Steve,
yes, I have read this. My layers do cascade. The only thing that doesn't work
is the GetFeatureInfo Request.
The original WMS supports GetFeatureInfo. But if I connect to this WMS and use
it as a layer for my new WMS GetFeatureInfo stops working.
Cora
Von: steve.tout...@inspq.qc.ca
i was able to cascade the featureinfo with a dummy template in the
layer section of the mapfile - without dummy template there was no
cascading featureinfo in my service
regards Holger
Zitat von steve.tout...@inspq.qc.ca:
Cora have you read this?
http://mapserver.org/ogc/wms_server.html#ca
Hi,
I have never tried to cascade GetFeatureInfo from Mapserver to other WMS
servers but I have tried to do that when Geoserver is used for cascading our
Mapserver. I would say that it is complicated. First issue is that the list of
supported info_formats is a per service feature, not per laye
Hmm, but it was only working with one layer in my 6.4.2 mapserver here.
If i was requesting more than one layer, mapserver crashed. I had to
made a patch for the mapwmslayer.c, so now it's working for all layers
in my cascading service. If it's not fixed in mapserver 7 (i can not
test at the mo
Would it help to have Mapserver 7 built as a public AMI (Amazon Machine
Image)?
I could help with that, but I would think that there are probably a number
of preferences in how Mapserver gets built.
For example I would typically build on Ubuntu and use NGINX, just because
that is more familiar to m
Hi thx for responses.
I dont use the fastcgi
My mapserver run on a tomcat environment.
My first goal is to be able to have two distinct cgi istance using the
same dataset resources (we work with tiffs and spatialites) and the
same mapfiles. his to reduce al minimum the manage overhead.
My need f
e I would typically build on Ubuntu and use NGINX, just because
>that is more familiar to me.
>-Mark Korver
>
>On Wed, Oct 28, 2015 at 2:31 AM, Rahkonen Jukka (MML) <
>jukka.rahko...@maanmittauslaitos.fi> wrote:
>
>> Hi,
>>
>>
>>
>> I wrote l
