[mapserver-users] mapserver 0-values problem

[Raivo Alla]

Hi again,

I have to add that this expression:
EXPRESSION ([way] >= 1000000 OR [way]<=0) worked fine when I
substituted those 0-values with -1.

As I mentioned before, expression like that
EXPRESSION ([way] >= 1000000 OR [way]<=0 OR [way] eq 0)
does'nt filter out rows that had 0 value on "way" field.


Raivo

On Fri, Jan 16, 2009 at 11:23 PM, Raivo Alla <snaperski at gmail.com> wrote:
> Thank you for answering!
>
> Sorry about absent parentheses, manuallly typing mistake:( In mapfile
> it's with parentheses..
> In ArcGIS i can select those rows with "[way]=0" filter, successfully.
> The origin of the data table is oracle table, where those fields were
> originally with <null> values. After generating shapefiles on that
> table, these <null> values were substituted by 0-s.
>
>
> Raivo
>
> On Fri, Jan 16, 2009 at 9:40 PM, Steve Lime <Steve.Lime at dnr.state.mn.us> wrote:
>> I'll start with the obvious question, do you really mean:
>>
>>  EXPRESSION "[way] eq 0"
>>
>> That should be:
>>
>>   EXPRESSION ([way] eq 0)
>>
>> Steve
>>
>>>>> On 1/16/2009 at 2:50 AM, in message
>> <49dc012b0901160050h1473a696qbad0cc15a6dc534 at mail.gmail.com>, Raivo Alla
>> <snaperski at gmail.com> wrote:
>>> Hi!
>>>
>>> I have strange situation where my mapfile EXPRESSION "[way] eq 0" does
>>> not find rows in a table where there is value 0.
>>> The type of the shapefile [way] attribute is double.
>>> I heard that mapserver 5 handles <null> values as "0" for numbers, so
>>> maybe the problem is that my filter is searching for null-values?
>>> Maybe someone can fix my incompetence?
>>>
>>>
>>> Sincerely,
>>> Raivo
>>> _______________________________________________
>>> mapserver-users mailing list
>>> mapserver-users at lists.osgeo.org
>>> http://lists.osgeo.org/mailman/listinfo/mapserver-users
>>
>>
>