On Wed, 5 Aug, 2015 at 5:27 PM, Jody Garnett <[email protected]>
wrote:
There is a really different track here on how to modify the style
interfaces in a safe manner (between this proposals and anime's. I
made the suggestion for FeatureTypeStyle.getSortBy() ... and the
answer was to consistently use the vendor options parameter map. Down
a few levels here to RasterSymbolizer and we have this proposal that
is far more invasive.
Can we try for a middle ground ... can RasterSymbolizer make use of
vendor options for this functionality? At least the getParameters()
is acting like RasterSymbolizer.getOptions().
OK after a quick chat with Jody (which must have been really early for
him, so thanks for getting up now). I'm going to go with a plan to use
Vendor Options for this which is almost certainly a better way of doing
it for interoperability.
This will change the proposal a bit and I'll hack on it later to
reflect the changes I actually make.
The plan is to use the existing (but deprecated) getType() in
ContrastEnhancement to store a string or a code list ContrastMethod
which will alert users of the class to go check for options like
algorithm and parameters when they come to do some enhancement work.
Ian
------------------------------------------------------------------------------
_______________________________________________
GeoTools-Devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
