I understand the objective of rfc 91, but the most common use case would
be to pass the supplied geometry.
If mapserver doesn't use the supplied geometry, that means that it doesn't
support spatial filtering.
Our data covers the whole country, not using the supplied geometry means
we can't
Sorry my first post was with an inapprpriate title..
I'm using mapserver 6.4.1 and postgis 2.1
using OpenLayers 2.13.1 I draw a small polygon that I use for a within
spatial filter of a WFS getfeature request. The problem is that mapserver
is not sending this polygon to postgis, it is
sorry I'm confused, perhaps I misunderstand what you explained. I don't
understand what you mean by MapServer does use the supplied geometry,
it?s a matter of where the filter is applied ? the database or in
MapServer
In mapserver log I see
FLTLayerApplyPlainFilterToLayer(): ([shape]
Hello Steve,
maybe you can use a bounding box instead taking the
bbox=793732,6570204,793765,6570228 command in the WFS
request somehow (with your own coordinates naturally)? I do not
work with open layers so I do not know how to do it
MapServer does use the supplied geometry, it's a matter of where the filter is
applied - the database or in MapServer. This isn't a new limitation so others
may have more experience with workarounds. Maybe try also setting a bbox in the
filter based on the bbox of the geometry?
Steve
From:
It's a limitation in older versions of MapServer where specific backend
optimizations were scattered about the WMS/WFS code. Most of those
optimizations address the most common use cases - I guess this wasn't one of
them. It's surprising that at worst the extent of the supplied geometry isn't
Steve T.,
mapserver gets back all the geometries from postgis and then filters
them in mapserver against the geometry.
Mapserver passes the BBOX for the mapfile to postgis as you noticed
which is not very efficient, but you can override that to the BBOX of
the window using the BBOX
I'm using mapserver 6.4.1 and postgis 2.1
using OpenLayers 2.13.1 I draw a small polygon that I use for a within
spatial filter of a WFS getfeature request. The problem is that mapserver
is not sending this polygon to postgis, it is sending the extent of the
mapfile as filter...
The wfs POST
Thanks for your explanation Stephen.
I'm sure there were good reasons to do that, but it is a weird way of
filtering.
I Cannot use the bbox of the window but as you suggest, passing the bbox
of the geometry could be a workaround.
If someone as an idea on how we could pass the bbox of the
On 1/26/2015 2:12 PM, steve.tout...@inspq.qc.ca wrote:
Thanks for your explanation Stephen.
I'm sure there were good reasons to do that, but it is a weird way of
filtering.
It is a legacy issue the RFC 91 I think is trying to clean up. Mapserver
started with rasters and shapefiles, so
10 matches
Mail list logo
