[Geoserver-users] Wrong CellType for Signed 8 bit GeoTiff

Hi all, When i submit a map using 8bit as a GeoTiff, the geoserver always interprets this map as unsigned. So the interval between -128 to -1 is interpreted as 128 to 255. The issue i guess that the geoserver doesn't care about the Gdal Byte special flag as described, a example of how fix the

Re: [Geoserver-users] SLD RasterSymbolizer: ColorMapEntry variable substitution doesn't work when there are multiple rules in the SLD

On Thu, Jun 16, 2016 at 6:29 PM, Mauro Bartolomeoli < maurobartolome...@gmail.com> wrote: > Hi, > I had a look at the issue, and it is related to EnvFunction not getting > correctly filled with environment variables when rendering involveves more > threads. > I tried a quick fix transforming the

Re: [Geoserver-users] SLD RasterSymbolizer: ColorMapEntry variable substitution doesn't work when there are multiple rules in the SLD

Hi, I had a look at the issue, and it is related to EnvFunction not getting correctly filled with environment variables when rendering involveves more threads. I tried a quick fix transforming the related ThreadLocal in EnvFunction in a InheritableThreadLocal, but that broke some geotools unit

Re: [Geoserver-users] SLD RasterSymbolizer: ColorMapEntry variable substitution doesn't work when there are multiple rules in the SLD

Hi Andrea, Yes, keeping 1 rule by SLD could be a possible workaround, but it would be difficult to manage at some level... Actually we often use different rules (filtered by ENV values) in a same SLD, for different reasons, e.g. to handle: - reversed values on legends (values growing

Re: [Geoserver-users] SLD RasterSymbolizer: ColorMapEntry variable substitution doesn't work when there are multiple rules in the SLD

On Thu, Jun 16, 2016 at 4:16 PM, Victor.Sinceac wrote: > I think many people uses multiple RasterSymbolyzer rules in one SLD: there > are many discussions on the forums about GetLegend results for such an SLD. > > > Thinking about it... this scenario basically

Re: [Geoserver-users] SLD RasterSymbolizer: ColorMapEntry variable substitution doesn't work when there are multiple rules in the SLD

Hi Victor, no, we're aware it does not work when there are two layers in the request... it's odd to have two raster symbolizes in one style though... Cheers Andrea On Thu, Jun 16, 2016 at 3:11 PM, Victor.Sinceac wrote: > Hi, > > Color variable substitution works

[Geoserver-users] SLD RasterSymbolizer: ColorMapEntry variable substitution doesn't work when there are multiple rules in the SLD

Hi, Color variable substitution works only when there is ONE SINGLE RULE in the SLD; when the SLD contains 2 or more rules, the variable substitution is broken and default color values are always used. It is reproducible on any raster layer in GeoServer 2.8.3/2.9.0. Did someone found a

[Geoserver-users] multi-tenant or farm hosting

Hi all, we're looking into reducing the number of geoserver instances in our network. We currently have a geoserver for each client/project in a virtual host, but for reasons of resource utilisation and maintenance we would like to concentrate multiple (smaller) clients/projects on one geoserver

Re: [Geoserver-users] GML QName issues with PostGIS feature store

On Wed, Jun 15, 2016 at 11:58 AM, Matthias Müller < matthias_muel...@tu-dresden.de> wrote: > Hi Andrea, > > thanks for the quick reply. > > Just for the record: Correct behaviour towards the client also matters in > option (2). Possibilities for handling wrong GML are: > > 2a) return an HTTP

Re: [Geoserver-users] GML QName issues with PostGIS feature store

Hi Jukka, UUIDs should be compliant with the general feature model for both feature identifiers and feature attributes. They just invalid with certain *encodings* such as GML (and WFS, which depends on GML encoding). With software, that supports multiple encodings, this raises questions

Re: [Geoserver-users] IDW Interpolation

Hi Rakesh, sorry, I'm not the author of that interpolator and have no experience using it, but I've seen examples of it working... it's probably a matter of adjusting the parameters, but if I had to guess, you might be referring to an attribute that does not exist. Is the value of each point