Andrea Aime wrote: > Well, since I have a customer that needs this, and there seems to be > no agreement (or lack of interest) on what to do, I'll roll a custom > variant of the quantile algorithm inside GeoServer that does what I > suggested, set apart the flat areas of the histogram in their own > classes when they are big enough (say, half of a standard sized > class?), and try to build classes with the expected size for the rest > of the values. That sounds fine; why not just update the geotools implementation? ie we found something that is a mistake (two categories with the same (0,0) range) can we fix it? > I'd like to avoid that, but I see no way to do so without introducing > extra parameters that would break all existing callers of the current > quantile function... So far you have some style generation code; and it probably would die on the case you describe anyways... if I cared to have specific functionality I would have provided test cases. Lets rock and roll...
Cheers, Jody ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
