You need to log in before you can comment on or make changes to this bug.
I don't understand the behaviour of expressions with < and > If I use the following: "INWONERS > X" I get a map which is completely filled with the symbol I chose. Doesn't matter which value I choose for the X. The same applies to: "INWONERS < X" but then I get the normal map where nothing is the way I chose my symbol for the class. I have just one class defined. If I look in my SLD document I find the following: <Filter> <PropertyIsEqualTo> <PropertyName/> <Literal>INWONERS > 500000</Literal> </PropertyIsEqualTo> </Filter> So the expression is just filled in literally. According to Paul's email, it should work like this, which is what I assume I am doing right now :-) [attr] = "value" [attr] < "value" [attr] > "value" [attr] < "value" or [attr] > "value" Is this a bug, or am I doing something wrong?
Currently the only expression type that can be applied through sect is simple value equals expressions. In the classifier popup, the Expression text box, only the class value would be acceptable. example, Expression "1" Expression "Africa" , only unique values. logical or regular expression cannot be created by sect, but can be loaded and preview in sect.
*** Bug 269 has been marked as a duplicate of this bug. ***
Could not the ExpressionBuilder widget from Chameleon be (easily) integrated with SECT to allow for more complex expressions, i.e. Filters to be built?
