Even
At the following url:
http://img529.imageshack.us/img529/5287/metadatatiff.jpg are the results
gdalinfo, I use raster GeoTIFF file.
If I open the tif with the ArcMap nodatavalue is equal to -128.
Greetings
Filippo Corò
___
gdal-dev mailing
Le vendredi 06 août 2010 23:41:37, Greg Coats a écrit :
> I agree that unsigned byte does not support -128. Signed byte does support
> -127.
Yes
> Signed byte does not could support -128.
No, the validty range of a signed byte is [-128,127].
> I note that
> http://www.gdal.org/gdal_translate.
I agree that unsigned byte does not support -128. Signed byte does support
-127. Signed byte does not could support -128. I note that
http://www.gdal.org/gdal_translate.html shows that gdal_translate supports 11
data types
Byte/Int16/UInt16/UInt32/Int32/Float32/Float64/CInt16/CInt32/CFloat32/CF
Filippo,
What is the format of that raster file ? Can you share a link to the dataset ?
or the output of gdalinfo at the very least
I'd note that -128 can only be considered a valid value for a 8bit raster if
the metadata item PIXELTYPE at band level is set to SIGNEDBYTE
(IMAGE_STRUCTURE metad
Hi List,
I have a problem with the function GetNoDataValue () of GDAL 1.6.2 ver. I
use some raster where the nodatavalue is equal to -128 and the pixel depth
is 8bit. Opening the raster with the following code (with pydev end
python 2.6):
# Get the bands and block sizes
primoBand primoD
