Hi again, Just to leave a note in case others encounter the same problem and read this thread:
1) It seems the problem occurs only with rasters in double or floating point precision (a test with integer (Int16) rasters worked fine). However, other integer types may cause problems too: see http://trac.osgeo.org/gdal/browser/trunk/gdal/gcore/gdalrasterband.cpp, where the CPLIsNan function handles NaN explicitly for some data types (see also: http://osgeo-org.1560.x6.nabble.com/gdal-dev-GDALSetRasterNoDataValue-and-NaN-td4996633.html). 2) GDAL handles NaN without problems, at least on Linux and Windows (I have no Mac for testing). In any case, I reopened a relevant ticket on this issue which I found in PostGIS trac: http://trac.osgeo.org/postgis/ticket/828 Cheers Stefan
_______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
