Correct. Filters specified in this manner are passed directly to the underlying 
driver. My goal was to remove ambiguity with the FILTER keyword itself since it 
could take both MapServer syntax and native driver syntax - depending on 
context. --Steve

-----Original Message-----
From: Michael Smith [mailto:[email protected]] 
Sent: Wednesday, June 10, 2015 5:28 AM
To: Andrea Peri; Lime, Steve D (MNIT)
Cc: [email protected]
Subject: Re: [mapserver-users] Incompatibility at Filter - level between 
mapserver 6.x and the last mapserver-dev ?

Andrea,

You can always use your existing filters with

PROCESSING "NATIVE_FILTER=WHERE (ANNO = 2006) and (CODICE_UNIVOCO like
'%idtpn%' )"

Or you can use a MapServer expression which are documented here:
http://mapserver.org/mapfile/expressions.html#mapserver-expressions

Mike

----
Michael Smith

US Army Corps
Remote Sensing GIS/Center
[email protected]




-----Original Message-----
From: Andrea Peri <[email protected]>
Date: Wednesday, June 10, 2015 at 5:41 AM
To: "Lime, Steve D (MNIT)" <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [mapserver-users] Incompatibility at Filter - level between
mapserver 6.x and the last mapserver-dev ?

>Hi steve,
>this new sintax will allow the AND operator ?
>
>I have a filter like this:
>
>FILTER "WHERE (ANNO = 2006) and (CODICE_UNIVOCO like '%idtpn%' )"
>
>and don't know how to transform it with the new sintax.
>
>Is this kind of filter supported ?
>
>Thx,
>
>A.
>
>
>2015-06-09 19:05 GMT+02:00 Lime, Steve D (MNIT) <[email protected]>:
>> As of MapServer 7.0 FILTERS must be given using MapServer syntax - this
>>is a regression noted in the Migration Guide, see
>>http://mapserver.org/MIGRATION_GUIDE.html#migration. There's an OGR
>>example right towards the top of that document. Basically:
>>
>>   FILTER "WHERE ([CODICE] = 107)"
>>   FILTERITEM "CODICE"
>>
>> Becomes:
>>
>>   PROCESSING 'NATIVE_FILTER=CODICE=107'
>>
>> Steve
>>
>> -----Original Message-----
>> From: [email protected]
>>[mailto:[email protected]] On Behalf Of Andrea Peri
>> Sent: Tuesday, June 09, 2015 3:45 AM
>> To: [email protected]
>> Subject: [mapserver-users] Incompatibility at Filter - level between
>>mapserver 6.x and the last mapserver-dev ?
>>
>> Hi,
>> I have just update my mapserver to the last mapserver-dev .
>>
>> After this update, I see an error on the filtering.
>>
>> In my mapfile the data configuration was originally this:
>>
>>     CONNECTION "/path-to-spatialite-db/zz_db_tematici.sqlite"
>>     CONNECTIONTYPE OGR
>>     DATA "IFT2009"
>>     EXTENT 1554650.74 4678225.52 1771822.76 4924891.9
>>     FILTER "WHERE ([CODICE] = 107)"
>>     FILTERITEM "CODICE"
>>       ....
>>
>>
>> The log report this error:
>>
>> [Tue Jun  9 10:39:46 2015].153296 msDrawMap(): rendering using
>> outputformat named AGGA (AGG/PNG).
>> [Tue Jun  9 10:39:46 2015].154698 msDrawMap(): WMS/WFS set-up and
>>query, 0.001s
>> [Tue Jun  9 10:39:46 2015].262330 LayerDefaultTranslateFilter():
>> General error message. This data driver does not implement filter
>> translation support
>> [Tue Jun  9 10:39:46 2015].282402 msDrawMap(): Layer 239
>> (rt_ucs.idift.rt.107), 0.128s
>> [Tue Jun  9 10:39:46 2015].282550 msDrawMap(): Drawing Label Cache,
>>0.000s
>>
>> I'm using spatialite as db.
>>
>> After this error, I read this RFC:
>> http://www.mapserver.org/ru/development/rfc/ms-rfc-91.html
>>
>> And try the new settings,
>>
>>     FILTER (([FILTERITEM[ = "string") AND (CODICE = 107))
>>
>> but it seem don't work.
>>
>> I don't understand if this is an issue of the new settings with
>> spatialite or I'm wrong something.
>>
>> Thx,
>>
>>
>> --
>> -----------------
>> Andrea Peri
>> . . . . . . . . .
>> qwerty àèìòù
>> -----------------
>> _______________________________________________
>> mapserver-users mailing list
>> [email protected]
>> http://lists.osgeo.org/mailman/listinfo/mapserver-users
>
>
>
>-- 
>-----------------
>Andrea Peri
>. . . . . . . . .
>qwerty àèìòù
>-----------------
>_______________________________________________
>mapserver-users mailing list
>[email protected]
>http://lists.osgeo.org/mailman/listinfo/mapserver-users


_______________________________________________
mapserver-users mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Reply via email to