[gdal-dev] Performance improvment for gdal_retile

christian.mueller at nvoe.at christian.mueller at nvoe.at
Sat Dec 18 08:31:21 EST 2010


Some last comment about the test case, the current source checks

test_gdal_retile_2()

ds.GetRasterBand(4).Checksum() != 35
ds.GetRasterBand(4).Checksum() != 35

If I run this on a Linux Intel 32 bit configuration, it has to be

ds.GetRasterBand(4).Checksum() != 283
ds.GetRasterBand(4).Checksum() != 122

Doing the same on a Linux AMD 64 Bit configuration, the values should be

ds.GetRasterBand(4).Checksum() != 283
ds.GetRasterBand(4).Checksum() != 126

It seems that the cecksum is dependent on the  platform. Is this  
desirable ? Could this cause some headaches later ?

Cheers
Christian




----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.




More information about the gdal-dev mailing list