<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7654.12">
<TITLE> Spatial Filter with WFS</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<P DIR=LTR><SPAN LANG="de"></SPAN><SPAN LANG="en-us"><FONT FACE="Arial">Dear MapServer User,</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Arial">I want</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"> <FONT FACE="Arial">to let you know about the problem I</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"> <FONT FACE="Arial">had using filter encoding</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"><FONT FACE="Arial"> with a spatial filter requesting features via WFS:</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"></SPAN><SPAN LANG="en-us"></SPAN><SPAN LANG="en-us"><FONT FACE="Arial">1. </FONT></SPAN><SPAN LANG="en-us"></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"> <FONT FACE="Arial">Yewondwossen Assefa</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"><FONT FACE="Arial"> could confirm that</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"> <FONT FACE="Arial">this is an issue with OGR type layers.</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"> <FONT FACE="Arial">He</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"> <FONT FACE="Arial">was able to reproduce</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"> <FONT FACE="Arial">the problem</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"> <FONT FACE="Arial">and add</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"><FONT FACE="Arial">ed</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"><FONT FACE="Arial"> a bug on it [1]. Converting the ogr layer to shape and using</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"> <FONT FACE="Arial">the</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"> <FONT FACE="Arial">shape file directly i</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"><FONT FACE="Arial">n</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"><FONT FACE="Arial"> mapserver</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"><FONT FACE="Arial"></FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"> <FONT FACE="Arial">is</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"><FONT FACE="Arial"> working properly.</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"><FONT FACE="Arial"></FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"> <FONT FACE="Arial">As I experienced t</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"><FONT FACE="Arial">he problem with the OGR layer (MapInfo Tab) does only occur with MapServer version 5.6.5. I tested 5.4.2 and 5.2.3 and</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"> <FONT FACE="Arial">I</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"> <FONT FACE="Arial">did not</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"> <FONT FACE="Arial">run in</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"><FONT FACE="Arial"> the</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"> <FONT FACE="Arial">same</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"> <FONT FACE="Arial">problem with the same layer type. So it seems to be a matter of the MapServer version as well.</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"></SPAN></P>
<P DIR=LTR><SPAN LANG="de"></SPAN><SPAN LANG="en-us"></SPAN></P>
<UL DIR=LTR>
<P DIR=LTR><SPAN LANG="de"></SPAN><SPAN LANG="en-us"><FONT FACE="Arial">[1]:</FONT></SPAN><SPAN LANG="de"> </SPAN><A HREF="http://trac.osgeo.org/mapserver/ticket/3617"><SPAN LANG="de"><U></U></SPAN><U><SPAN LANG="en-us"><FONT COLOR="#0000FF" FACE="Arial">http://trac.osgeo.org/mapserver/ticket/3617</FONT></SPAN></U><SPAN LANG="de"></SPAN></A><SPAN LANG="de"></SPAN><SPAN LANG="en-us"></SPAN></P>
</UL>
<P DIR=LTR><SPAN LANG="en-us"></SPAN><SPAN LANG="en-us"></SPAN><SPAN LANG="en-us"><FONT FACE="Arial">2. </FONT></SPAN><SPAN LANG="en-us"></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"> <FONT FACE="Arial">A</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"><FONT FACE="Arial"> work around for postgis layer</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"><FONT FACE="Arial">s</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"><FONT FACE="Arial"> is to avoid using "USING UNIQUE</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"> <FONT FACE="Arial">[column name</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"><FONT FACE="Arial"> different than oid</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"><FONT FACE="Arial">]</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"><FONT FACE="Arial">"</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"><FONT FACE="Arial">.</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"> <FONT FACE="Arial">Yewondwossen described this bug as well.</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"></SPAN></P>
<UL DIR=LTR>
<P DIR=LTR ALIGN=JUSTIFY><SPAN LANG="de"></SPAN><SPAN LANG="en-us"></SPAN></P>
<P DIR=LTR ALIGN=JUSTIFY><SPAN LANG="de"></SPAN><SPAN LANG="en-us"><FONT FACE="Arial">[2]:</FONT></SPAN><SPAN LANG="de"></SPAN><A HREF="http://trac.osgeo.org/mapserver/ticket/3618"><SPAN LANG="de"><U></U></SPAN><U><SPAN LANG="en-us"><FONT COLOR="#0000FF" FACE="Arial">http://trac.osgeo.org/mapserver/ticket/3618</FONT></SPAN></U><SPAN LANG="de"></SPAN></A><SPAN LANG="de"></SPAN><SPAN LANG="en-us"></SPAN></P>
<P DIR=LTR ALIGN=JUSTIFY><SPAN LANG="de"></SPAN><SPAN LANG="en-us"><FONT FACE="Arial">Note that this work around</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"><FONT FACE="Arial"> will only work if the</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"> <FONT FACE="Arial">table</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"><FONT FACE="Arial"> in</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"> <FONT FACE="Arial">the</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"><FONT FACE="Arial"> DATA clause was created with OIDS.</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"><FONT FACE="Arial"> Otherwise a</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"><FONT FACE="Arial">n</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"><FONT FACE="Arial"> error will occur.</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"> <FONT FACE="Arial">The error message</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"> <FONT FACE="Arial">shows that some piece of a program is looking for the column oid.</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"></SPAN></P>
<P DIR=LTR ALIGN=JUSTIFY><SPAN LANG="de"></SPAN><SPAN LANG="en-us"></SPAN></P>
<UL DIR=LTR><UL DIR=LTR>
<P DIR=LTR ALIGN=JUSTIFY><SPAN LANG="de"></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"><FONT FACE="Courier New"><ows:Exception exceptionCode="mapserv" locator="NoApplicableCode"></FONT></SPAN></P>
<P DIR=LTR ALIGN=JUSTIFY><SPAN LANG="en-us"><FONT FACE="Courier New"><ows:ExceptionText></FONT></SPAN></P>
<P DIR=LTR ALIGN=JUSTIFY><SPAN LANG="en-us"><FONT FACE="Courier New">msWFSGetFeature(): WFS server error. FLTApplyFilterToLayer() failed msPostGISLayerWhichShapes(): Query error. Error (ERROR:</FONT></SPAN><SPAN LANG="de"><B></B></SPAN><SPAN LANG="de"><B></B></SPAN><B><SPAN LANG="en-us"> <FONT COLOR="#FF0000" FACE="Courier New">column "oid" does not exist</FONT></SPAN></B><SPAN LANG="de"></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"><FONT FACE="Courier New"> LINE 1: ...on(force_2d("the_geom")),'NDR'),'base64') as geom,"oid" from... ^ ) executing query: select encode(AsBinary(force_collection(force_2d("the_geom")),'NDR'),'base64') as geom,"oid" from ku_test_nooid where the_geom && GeomFromText('POLYGON((389965 5693582,389965 5732815,420177 5732815,420177 5693582,389965 5693582))',find_srid('','ku_test_nooid','the_geom'))</FONT></SPAN></P>
<P DIR=LTR ALIGN=JUSTIFY><SPAN LANG="en-us"><FONT FACE="Courier New"></ows:ExceptionText> </FONT></SPAN></P>
<P DIR=LTR ALIGN=JUSTIFY><SPAN LANG="en-us"><FONT FACE="Courier New"></ows:Exception></FONT></SPAN></P>
</UL>
<P DIR=LTR><SPAN LANG="de"></SPAN><SPAN LANG="en-us"></SPAN></P>
<P DIR=LTR><SPAN LANG="de"></SPAN><SPAN LANG="en-us"><FONT FACE="Arial">In</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"><FONT FACE="Arial"> case</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"> <FONT FACE="Arial">of a subquer</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"><FONT FACE="Arial">y where USING UNIQUE is</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"> <FONT FACE="Arial">required</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"><FONT FACE="Arial">,</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"> <FONT FACE="Arial">it is possible to use</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"> <FONT FACE="Arial">“USING UNIQUE OID”</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"><FONT FACE="Arial">.</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"><FONT FACE="Arial"> Otherwise an</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"><FONT FACE="Arial">other</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"><FONT FACE="Arial"> error occurs.</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"> <FONT FACE="Arial">So right now</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"> <FONT FACE="Arial">OIDS are needed</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"> <FONT FACE="Arial">in any case</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"> <FONT FACE="Arial">and in my opinion it would be worth thinking about to change this requirement to be able to use any other column with unique val</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"><FONT FACE="Arial">ues.</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"></SPAN></P>
</UL></UL>
<P DIR=LTR><SPAN LANG="de"></SPAN><SPAN LANG="en-us"><FONT FACE="Arial">Thanks to all</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"> <FONT FACE="Arial">who joined the discussion and helped solving this problem!</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Arial">Best regards</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-us"><FONT FACE="Arial">Andreas</FONT></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"></SPAN></P>
<P DIR=LTR><SPAN LANG="de"></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"></SPAN></P>
<P DIR=LTR><SPAN LANG="de"></SPAN><SPAN LANG="de"></SPAN><SPAN LANG="en-us"></SPAN></P>
<P DIR=LTR><SPAN LANG="de"></SPAN><SPAN LANG="de-de"></SPAN><SPAN LANG="de-de"><FONT FACE="Arial">Mit freundlichen Grüßen</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="de-de"><FONT FACE="Arial">Im Auftrag</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="de-de"><FONT FACE="Arial">Andreas Fischer</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="de-de"><FONT FACE="Arial">Kreis Unna - Der Landrat</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="de-de"><FONT FACE="Arial">Zentrale Datenverarbeit</FONT><FONT FACE="Arial">ung</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="de-de"><FONT FACE="Arial">Friedrich-Ebert-Straße 17</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="de-de"><FONT FACE="Arial">59425 Unna</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="de-de"><FONT FACE="Arial">Fon 02 3 03 27-44 16</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="de"></SPAN><SPAN LANG="de-de"></SPAN><SPAN LANG="de-de"><FONT FACE="Arial">Fax 0 23 03 27-28 96</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="de"></SPAN><A HREF="mailto:andreas.fischer@kreis-unna.de"><SPAN LANG="de"><U></U></SPAN><U><SPAN LANG="de-de"></SPAN></U><U><SPAN LANG="de-de"><FONT COLOR="#0000FF" FACE="Arial">andreas.fischer</FONT><FONT COLOR="#0000FF" FACE="Arial">@kreis-unna.de</FONT></SPAN></U><SPAN LANG="de"></SPAN></A><SPAN LANG="de"></SPAN><SPAN LANG="de-de"></SPAN></P>
<P DIR=LTR><SPAN LANG="de"></SPAN><A HREF="http://www.kreis-unna.de"><SPAN LANG="de"><U></U></SPAN><U><SPAN LANG="de-de"></SPAN></U><U><SPAN LANG="de-de"><FONT COLOR="#0000FF" FACE="Arial">www.kreis-unna.de</FONT></SPAN></U><SPAN LANG="de"></SPAN></A><SPAN LANG="de"></SPAN><SPAN LANG="de-de"></SPAN></P>
<P DIR=LTR><SPAN LANG="de"></SPAN></P>
<pre style="white-space:normal">Diese E-Mail wurde beim Ausgang auf Viren geprueft. Wegen der <br>potentiellen Gefahr auf den Uebertragungswegen wird zu einer <br>Vireneingangskontrolle geraten. Eine Haftung für Virenfreiheit<br>wird ausgeschlossen.<br><br><br></pre></BODY>
</HTML>