On Thu, Aug 5, 2010 at 11:38 AM, Andreas Hocevar <[email protected]> wrote: > Hi, > > Eric's patch won't solve the problem, because the input to the filter will > then be "0.2" instead of ".2". > > Arnd, can you please create a ticket? This behavior was introduced by > http://trac.openlayers.org/changeset/8927, and I think it would be better to > cast in filter.evaluate rather than in format readers. >
Isn't the fix to simply put ".2" in the literal instead of .2 which is treated as a number? I know we had this problem in GeoServer (GeoTools) with interpreting literal values that are ambiguous. Ian -- Ian Turton _______________________________________________ Users mailing list [email protected] http://openlayers.org/mailman/listinfo/users
