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 statistics from UInt16.
...
On the trunk, GDT_Int16 is used too, so how does gdalinfo detect that it
is actually UInt16?
Roger,
I believe the min/max is actually being read from the file header in trunk
and is handled without regard to the actual imagery or it's type.
I skimmed the changelog for this driver and I didn't notice any obvious
changes in metadata / statistics handling so I'm surprised at this result.
Best regards,
--
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up | Frank Warmerdam, warmer...@pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush | Geospatial Programmer for Rent
_______________________________________________
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev
