Andrea Aime ha scritto: ... > Again, not very useful... it's telling you that at the 33% break there > is a 0, and by applying it, you'd get a class that ends with 0, and > another that starts with 0. Which is something the layman using > the application does not understand, it does not make sense to him. > > That's why I was suggesting to have the classes avoid breaks on > flat areas.... so I'm back at square one... current method is > mathematically sound, but does not make any sense to the normal > user. What now?
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. 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... Cheers Andrea ------------------------------------------------------------------------- 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
