Hi,
You I do remember but someone really had a WMS 1.3.0 question.
I have had no time for testing cascading WFS 1.1.0 yet. I should make Mapserver
to send WFS requests through a logging proxy first for getting some reasonable
results. From previous experience I am a bit sceptical but I cannot say much
before having a try. Typical things which can go wrong are
- All WFS servers do not necassarily support correctly filters which are sent
url-encoded inside http GET requests even they can support them with http POST.
I do not know which method Mapserver is using.
- Some WFS servers would rather see PropertyNames given with namespaces
- With WFS 1.1.0 geometries used in spatial filters should follow the official
axis order of the corresponding srsName.
- It would be best to give always all the gml geometries explicitly the
srsName. Otherwise nobody can really guarantee what srsName the WFS 1.1.0
server is using as default. As far as I remember Mapserver builds filters
without srsName.
There are better possibilities for success with cascading WFS 1.0.0 servers but
I won't say that it is impossible with WFS 1.1.0. What is essential is to make
as simple trial as possible and capture the requests Mapserver is sending. If
you play a week or two with different filters and different WFS servers the
result to expect is a bunch of bug reports.
-Jukka Rahkonen-
Michal Šrédl wrote:
Hi Jukka, all,
I was asking about applying WFS 1.1.0 FES filter (while cascading, but
this is not the issue). I don't get any error message, rather the
filter seems not to be applied. Documentation
(http://mapserver.org/ogc/filter_encoding.html#use-of-filter-e
ncoding-in-mapserver)
mentions FES 1.0.0, so the question is whether WFS 1.1.0 filtering is
supported.
The original email can be found here:
http://lists.osgeo.org/pipermail/mapserver-users/2011-November
/070726.html
Thanks a lot,
Michal
2011/11/17 Rahkonen Jukka jukka.rahko...@mmmtike.fi:
Hi,
Somebody was asking about cascading an external WMS 1.3.0
server. I remember that the one who asked the questiod had
captured a rather self-explaining error message like this one
from our Mapserver 6.0
msBuildWMSLayerURL(): WMS connection error. MapServer
supports only WMS 1.0.0 to 1.1.1 (please verify the VERSION
parameter in the connection string).
Perhaps it would be still worth adding a line about
supported versions into the Limitations/TODO in document
http://mapserver.org/ogc/wms_client.html
-Jukka Rahkonen-
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users
