[mapserver-users] Re: WFS Filter Encoding for strings

Jeff Konnen jaykayone at gmail.com
Mon Jan 2 13:00:11 EST 2012



On 2 janv. 2012, at 18:57, Jeff Konnen <jaykayone at gmail.com> wrote:

hi all, is there anyone who knows how to handle this problem?

PropertyIsLike works now but i still have not found a solution for the described PropertyIsEqual Problem ..

All the best for 2012 and kind regards
Jeff
> 
> 
> On 19 déc. 2011, at 21:36, Jeff Konnen <jaykayone at gmail.com> wrote:
> 
>> 
>> Hi
>> 
>> We are using Mapserver 6.0.1 on linux with a postgis database.
>> We have some wfs services that used to work correctly in earlier versions of mapserver.
>> 
>> In version 6, we observed the following: when people use a wfs filter on a string field with a numeric value <PropertyIsEqualTo><PropertyName>code_commu</PropertyName><Literal>105</Literal></PropertyIsEqualTo>, mapserver will generate a sql statement without quotes assuming that the Literal is an Integer.
>> 
>> To fix this i have to use the "gml_types" "auto" directive.
>> 
>> now the filter works but it alters the describefeature xml document by setting the attribute types to 'Character'. This however does not seem to be valid xml, at least my client (FME) does not to seem to like this type declarations, telling me that they are not valid...
>> 
>> Is there another way to fix the filter issue?
>> 
>> There is a similar problem with the PropertyIsLike operator but I could not make it work at allin version 6.0.1
>> 
>> Thanks in advance for your help
>> Best regards
>> Jeff
>> 
>> PS: sorry if this post appears twice, there has been a formatting problem in the earlier version of the mail
>> 



More information about the mapserver-users mailing list