[GRASS-dev] GRASS created geotiff do not properly load into PostGIS (raster2pgsql)

Blumentrath, Stefan Stefan.Blumentrath at nina.no
Fri May 16 02:40:18 PDT 2014


Hi,

And thanks for the swift response!
My GDAL version is:
GDAL 1.11.0, released 2014/04/16.

I recompiled GDAL recently (but not PostGIS). Can that be the source of error?
However, ASCII and Tiffs with assigned NoData work…

Cheers
Stefan



From: Rémi Cura [mailto:remi.cura at gmail.com]
Sent: 16. mai 2014 11:24
To: Blumentrath, Stefan
Cc: GRASS developers list (grass-dev at lists.osgeo.org); postgis-devel at lists.osgeo.org
Subject: Re: [GRASS-dev] GRASS created geotiff do not properly load into PostGIS (raster2pgsql)

Hey,
what is your version of gdal (type `gdalinfo --version`)
Cheers,
Rémi-C

2014-05-16 11:14 GMT+02:00 Blumentrath, Stefan <Stefan.Blumentrath at nina.no<mailto:Stefan.Blumentrath at nina.no>>:
Hi,

And sorry for posting on two lists. Just don`t know where the issue belongs to…

I tried to load a set of raster maps in Geotiff format, which I created in GRASS using r.external.out, into PostGIS 2.1.2dev.

In PostGIS the raster datasets only contain NoData values, while gdalinfo –stats produces reasonable statistics for the respective GeoTiffs.

I did some trouble shooting and found that the problem was that GRASS did not assign a numerical NoData value to the GeoTiff, but “nan”.

When I gdal_translate same GeoTiff with –a_nodata -9999, raster2pgsql loads the resulting file just fine.

Is raster2pgsql supposed to read rasters with nan as NoData values (using –N -9999 in raster2pgsql had no effect btw.) or should GRASS (r.external.out) assign a NoData value to the produced raster datasets?

Many thanks in advance,
Stefan



_______________________________________________
grass-dev mailing list
grass-dev at lists.osgeo.org<mailto:grass-dev at lists.osgeo.org>
http://lists.osgeo.org/mailman/listinfo/grass-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20140516/63d3bcef/attachment-0001.html>


More information about the grass-dev mailing list