Hi John,
Can you try something like :
FilterIntersectsPropertyNameGeometry/PropertyNamegml:Polygongml:outerBoundaryIsgml:LinearRinggml:coordinates-61.63,45.04
-60.78,45.04 -60.78,46.08
-61.63,46.08/gml:coordinates/gml:LinearRing/gml:outerBoundaryIs/gml:Polygon/Intersects/Filter,
Hi,
On 16/06/2011 7:29 AM, Marco Bagni wrote:
Dear John,
let me take your request as the occasion to share a thought with this
community.
You are experiencing my same problem and your last deduction is correct:
BBOX works, for the rest the mismatch between the available documentation
and the
On 11-06-16 08:47 AM, Yewondwossen Assefa wrote:
On 16/06/2011 7:29 AM, Marco Bagni wrote:
You and I (and many more users with the same problem) are facing the
other side of the Open Source. Who writes the code and releases it for
public domain, sometimes arranges things in such a way that,
On 6/16/2011 5:29 AM, Marco Bagni wrote:
You and I (and many more users with the same problem) are facing the
other side of the Open Source. Who writes the code and releases it for
public domain, sometimes arranges things in such a way that, elegantly,
the users are suggested to turn to his
This WFS GetFeature request did work if I replaced ogc:Intersects with the
ogc:BBOX spatial filter.
- John
On Thu, Jun 9, 2011 at 12:47 PM, John Callahan john.calla...@udel.eduwrote:
Thanks. Yes, my server does support Intersect filter, according to the
WFS GetCaps file. I'm using the
Thanks. Yes, my server does support Intersect filter, according to the
WFS GetCaps file. I'm using the latest MS4W install with MS 6.
John
On Thursday, June 9, 2011, Alexandre Dube ad...@mapgears.com wrote:
Hello,
If you run a WFS GetCapabilities request on your server, it
