Opened 18 years ago

Closed 18 years ago

#1525 closed defect (fixed)

WFS Intersects implementation not compliant

Reported by: doug@… Owned by: mapserverbugs
Priority: high Milestone:
Component: WFS Server Version: 4.6
Severity: critical Keywords:
Cc:

Description 

MapServer's implementation of the WFS Filter Encoding Specification for the
Intersects function is incorrect in 4.6.1. 

In the capabilities section, the operator is correctly described as "Intersect",
as described in the schema:

http://schemas.opengeospatial.net/filter/1.0.0/filterCapabilities.xsd

However, when creating a filter that uses the intersect method, the proper
operator is "Intersects", not "Intersect" as is required by MapServer. The
applicable schema is at:

http://schemas.opengeospatial.net/filter/1.0.0/filter.xsd

Here is a working example from the MapServer docs that shows the records
returned uxing the incorrect function "Intersect":

http://www2.dmsolutions.ca/cgi-bin/mswfs_filter?&VERSION=1.0.0&SERVICE=WFS&REQUEST=GetFeature&TYPENAME=popplace&Filter=%3CFilter%3E%3CIntersect%3E%3CPropertyName%3EGeometry%3C/PropertyName%3E%3Cgml:Polygon%3E%3Cgml:outerBoundaryIs%3E%3Cgml:LinearRing%3E%3Cgml:coordinates%3E2488789,289552%202588789,289552%202588789,389552%202488789,389552%202488789,289552%3C/gml:coordinates%3E%3C/gml:LinearRing%3E%3C/gml:outerBoundaryIs%3E%3C/gml:Polygon%3E%3C/Intersect%3E%3C/Filter%3E

Here is a non=working example that shows an exception whtn the proper
"Intersects" function is used:

http://www2.dmsolutions.ca/cgi-bin/mswfs_filter?&VERSION=1.0.0&SERVICE=WFS&REQUEST=GetFeature&TYPENAME=popplace&Filter=%3CFilter%3E%3CIntersects%3E%3CPropertyName%3EGeometry%3C/PropertyName%3E%3Cgml:Polygon%3E%3Cgml:outerBoundaryIs%3E%3Cgml:LinearRing%3E%3Cgml:coordinates%3E2488789,289552%202588789,289552%202588789,389552%202488789,389552%202488789,289552%3C/gml:coordinates%3E%3C/gml:LinearRing%3E%3C/gml:outerBoundaryIs%3E%3C/gml:Polygon%3E%3C/Intersects%3E%3C/Filter%3E

Also, note that when the POST method is used, the above exception is not valid
XML. There is a space missing after the start of the ServiceExceptionReport, for
example:

<ServiceExceptionReportxmlns="http://www.opengis.net/ogc"

Change History (1)

comment:1 by doug@…, 18 years ago

Resolution: → fixed
Status: new → closed 
Sorry, this bug has been fixed. There is something else wrong with my filter.
I'll check it out. Sorry.
Note: See TracTickets for help on using tickets.