A follow up on the previous problem with versions (see below):
I removed all old libgdal versions that were in /usr/local/lib and that has
solved the issue.
Best,
Tom
--
I thought LD_LIBRARY_PATH could be untouched since I'm doing a
system-install according to:
On 07/06/2018 07:14 AM, Even Rouault
wrote:
NoData Value=3.40282346638529011e+38
Metadata:
STATISTICS_MAXIMUM=3.4028234663853e+38
ok, the issue is that nodata value (stored as text in GeoTIFF) is slightly
above the maximum value of a
Got myself a build that has the correct proj version now (./configure
--with-proj) so it doesn't segfault.
I can confirm that the nodata values are correctly dealt with now :)
Still battling the linked gdal version though, will post when I dealt with
that.
Tom
On Fri, Jul 6, 2018 at 2:09 PM,
On vendredi 6 juillet 2018 14:00:16 CEST Tom van Tilburg wrote:
> I just did a fresh build of trunk (2.4.0) but noticed 2 issues:
>
> 1. The installed version in /usr/local/bin is still version 2.3.1:
You may have to defined LD_LIBRARY_PATH since it probably links against your
system libgdal
I just did a fresh build of trunk (2.4.0) but noticed 2 issues:
1. The installed version in /usr/local/bin is still version 2.3.1:
> ls /usr/local/bin/gdalinfo -lrth
-rwxr-xr-x 1 root root 40K Jul 6 13:51 /usr/local/bin/gdalinfo
> /usr/local/bin/gdalinfo --version
GDAL 2.3.1, released 2018/06/22
On jeudi 5 juillet 2018 14:22:16 CEST Tom van Tilburg wrote:
> I have a fresh gdal 2.3.1 build on a ubuntu 17.10 that tells me:
> > gdalinfo dem.tif -stats -mm
>
> [..snip...]
> Band 1 Block=2200x1 Type=Float32, ColorInterp=Gray
> Min=-2.233 Max=340282346638529993179660072199368212480.000
I have a fresh gdal 2.3.1 build on a ubuntu 17.10 that tells me:
> gdalinfo dem.tif -stats -mm
[..snip...]
Band 1 Block=2200x1 Type=Float32, ColorInterp=Gray
Min=-2.233 Max=340282346638529993179660072199368212480.000 Computed
Min/Max=-2.233,340282346638528859811704183484516925440.000
