On Thu, 27 Aug 2009, Roger Bivand wrote:
On Mon, 24 Aug 2009, Frank Warmerdam wrote:
Roger Bivand wrote:
(reverting to list)
Correction, the user reported that:
Apparently, gdalinfo retrieves the correct min, max, and statistics,
despite the use of GDT_Int16.
on his Windows platform. Th
On Mon, 24 Aug 2009, Frank Warmerdam wrote:
Roger Bivand wrote:
(reverting to list)
Correction, the user reported that:
Apparently, gdalinfo retrieves the correct min, max, and statistics,
despite the use of GDT_Int16.
on his Windows platform. The different GDAL versions ought to explain
Roger Bivand wrote:
(reverting to list)
Correction, the user reported that:
Apparently, gdalinfo retrieves the correct min, max, and statistics,
despite the use of GDT_Int16.
on his Windows platform. The different GDAL versions ought to explain
why his gdalinfo says Int16 but gives statist
On Fri, 21 Aug 2009, Roger Bivand wrote:
On Fri, 21 Aug 2009, Frank Warmerdam wrote:
Roger Bivand wrote:
Hi,
The code for the LAN/GIS driver uses GDT_Int16 for Pixel type 2, rather
than GDT_UInt16. Is this justified? A user of rgdal has a case of unsigned
16-bit data stored by "a forest la
Roger Bivand wrote:
Hi,
The code for the LAN/GIS driver uses GDT_Int16 for Pixel type 2, rather
than GDT_UInt16. Is this justified? A user of rgdal has a case of
unsigned 16-bit data stored by "a forest landscape model", being treated
by the driver as signed. The header does not seem to have
Hi,
The code for the LAN/GIS driver uses GDT_Int16 for Pixel type 2, rather
than GDT_UInt16. Is this justified? A user of rgdal has a case of unsigned
16-bit data stored by "a forest landscape model", being treated by the
driver as signed. The header does not seem to have a signed/unsigned fla