Andreas, Thank you.
hmm, that's very interesting. Lets see if I understand correctly: I observe that in the CLASS EXPRESSIONs in a Postgis layer NULL is treated as zero for numeric fields. So NULL gets visualized in the class where zero is visualized. In my opinion that is not very desirable. I actually would expect a default behaviour where NULL values will not match any CLASS EXPRESSION. In Mapserver 6 we luckily had the FILTER option to filter out the NULL values to remedy this behaviour. Not very elegant but very doable. Now in Mapserver 7 we lost the FILTER option and have to write a subselect in the DATA statement to get rid of NULL values. That seems to be a rather complicated solution for something which seems to be a very common task. Or am I missing something and is there a way to avoid that NULL values end up as being treated as 0? MArco -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Filtering-NULL-values-from-Postgis-Layer-in-Mapserver-7-tp5280893p5281035.html Sent from the Mapserver - User mailing list archive at Nabble.com. _______________________________________________ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
