Re: [Geoserver-users] geotiff compression with predictor

2017-05-25 Thread Andrea Aime
The GDAL GeoTIFF reader has been explicitly removed from the GDAL extension package as it kept on causing problems (but I don't remember the details of what was happening, sorry!). Cheers Andrea On Thu, May 25, 2017 at 5:53 PM, Rahkonen Jukka (MML) < jukka.rahko...@maanmittauslaitos.fi> wrote:

Re: [Geoserver-users] geotiff compression with predictor

2017-05-25 Thread Keith Jenkins
There is also this GDAL extension for GeoServer: http://docs.geoserver.org/latest/en/user/data/raster/gdal.html I haven't tried it, but from that page, it looks like GeoTIFF would still be handled by the built-in GeoServer GeoTIFF support (and not via the GDAL extension). Keith On Thu, May

Re: [Geoserver-users] geotiff compression with predictor

2017-05-25 Thread Rahkonen Jukka (MML)
Hi, I wonder if it woud work with the imageio-ext GDAL plugin http://docs.geotools.org/stable/userguide/library/coverage/imageio.html which seems to contain GDAL GeoTIFF driver -Jukka Rahkonen- Keith Jenkins wrote: Re: [Geoserver-users] geotiff

Re: [Geoserver-users] geotiff compression with predictor

2017-05-25 Thread Keith Jenkins
Thanks, Andrea. For now, I'm just planning to avoid using compression predictors in any GeoTiFFs. When we get data from other sources, we don't always know how the files were generated. As far as I can tell, gdalinfo will indicate if compression is used in a GeoTIFF, but it doesn't say what

[Geoserver-users] rest/seed/workspace:layername Problem communicating with GeoServer

2017-05-25 Thread Alberto CD
Hi list, I am spent a couple of days try to find a solution for this so If only I could find help here that would be great. Problem specification: I am using GeoServer rest to truncate and seed layers after upload process (done using the rest too). Weird thing is /rest/truncate/masstruncate

Re: [Geoserver-users] geotiff compression with predictor

2017-05-25 Thread Andrea Aime
Hi Keith, as far as I know predictor=3 is completely unknown to the TIFF reader, and the type=2 does not support 32 bit data. There is a ticket open in imageio-ext (the library we use to read TIFF) about this, although it may be a bit too specific (only talks about type 3):