I've noticed that RasterSymbolizers sometimes ignore env parameters passed in
the WMS request and use the default value instead. It appears that the env
function works fine when the coverage is rendered on the direct raster path.
I think that the env parameters from the request are not being used by
org.geotools.renderer.lite.StreamingRenderer because
org.geotools.filter.function.EnvFunction stores them in a ThreadLocal but
StreamingRenderer does the raster rendering on a separate thread.
Steve Ikeoka
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/RasterSymbolizer-Env-Function-Doesn-t-Always-Work-tp5314512.html
Sent from the GeoServer - User mailing list archive at Nabble.com.