On 20/05/2010, at 4:57 PM, Andrea Aime wrote: > Eh, it might get tricky as we have two sources of uom specification, > the literal itself, but also the symbolizer one. I guess the local > one would win. > > Anyone interested in cooking up a patch?
Pick me pick me! After all I failed at applying the screenmap patch :-( I would actually like a bit of discussion first... We would still like to be fast at the default case of working with pixels, is there any way we can detect when we should check of a Measure.class? Or should we just try all the time. Ideas: - test if the literal is a Numeric prior to trying expr.evaulate( feature, Measure.class ) - test if the symbolizer already has a UOM setting; of so we should test for Measure.class Any other ways we can short cut? Or is this a case of make it work first and then make it fast. I am also a bit annoyed that we have to try for a Measure.class and not a Distance.class although I understand why (darn java generics being compile time only). Jody ------------------------------------------------------------------------------ _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
