How big a change would depend on the implementation. The brute force approach where you simply loop through features once to compute ranges and then again to draw would be probably pretty straight forward and driver independent. Wouldn't be fast (but would be simple). Complexity would be added as you try and boost performance by:
- allowing drivers to compute stats in their own way (e.g. add to the layer API something like msLayerGetStats(...)) - caching geometries from a first pass through the shapes for the second Steve BTW The color ramp support needs to be cleaned up first. I think we scared the originator of that code away when an RFC was originally put together. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Bart van den Eijnden Sent: Wednesday, February 03, 2010 5:12 AM To: [email protected] Subject: [mapserver-users] colorramp and datarange on the fly? Hi list, is it possible to have a colorramp in Mapserver based on the min and max value in the current extent? So instead of predefining the min and max in DATARANGE, have Mapserver use the min and max value of the dataset in the current extent? If not, would it be an easy change or a very complex one? Best regards, Bart_______________________________________________ mapserver-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapserver-users _______________________________________________ mapserver-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapserver-users
