LibTiff Mailing List
TIFF and LibTiff Mailing List Archive
July 2007
Previous Thread
Next Thread
Previous by Thread
Next by Thread
Previous by Date
Next by Date
Contact
The TIFF Mailing List Homepage
This list is run by Frank Warmerdam
Archive maintained by AWare Systems
Thread
2007.07.02 18:49 "Re: Old corrupted TIFF data - "Can not read directory count"", by Steve Bougerolle
2007.07.02 19:06 "Re: Old corrupted TIFF data - "Can not read directory count"", by Steve Bougerolle
2007.07.03 17:06 "Re: Old corrupted TIFF data - "Can not read directory count"", by Steve Bougerolle
2007.07.03 18:11 "Re: Old corrupted TIFF data - "Can not read directory count"", by Steve Bougerolle2007.07.03 17:06 "Re: Old corrupted TIFF data - "Can not read directory count"", by Steve Bougerolle
I think I've cracked this. It looks like these were read improperly off CD originally. I re-read the original CDs using Windows rather than Linux (a tremendous moral defeat, that) and got back readable TIFFs that were longer than the originals and for which the directory offsets made sense. Can TIFF files be sparse? That is, could the directory have been written at a specific location set by block size, even though the data didn't actually reach that far? That's my best theory so far: that the files were dumped out with file system offsets then read back in sequentially, losing a few hundred (meaningless) bytes in the process. Thanks for your help, all! John Aldridge wrote: > Steve Bougerolle wrote: >> This file is 16822272 bytes in size. The field points to 16823130, just >> past it (858 bytes). > > I take it there's no chance that these files have been ftp'ed in ascii > mode, maybe converting cr/lf into lf? > _______________________________________________ > Tiff mailing list: Tiff@lists.maptools.org > http://lists.maptools.org/mailman/listinfo/tiff > http://www.remotesensing.org/libtiff/ > -- Steve Bougerolle <steveb@sebgitech.com> http://www.sebgitech.com http://www.bougerolle.net