2007.03.25 16:13 "[Tiff] libtiff cvs HEAD compile faliure (was: gdaladdo throwing errors)", by Seth Price

2007.03.25 16:13 "[Tiff] libtiff cvs HEAD compile faliure (was: gdaladdo throwing errors)", by Seth Price

I haven't tried your frameworks, but I may look into them. If I'm only using UNIXy utilities, are there any advantages?

libtiff CVS HEAD isn't compiling for me. This file is the output from ./configure && make: http://www.pricepages.org/temp/libtiff_cvs_err.txt

I'll copy the libtiff list because it is, in fact, a libtiff compile error.

~Seth

On Mar 25, 2007, at 1:24 AM, William Kyngesburye wrote:

> I have a very similar bug for this, which was fixed - the problem > is actually in libtiff (your errors are slightly different):

>
> http://bugzilla.remotesensing.org/show_bug.cgi?id=1204
>
> You need to build libtiff from CVS to get this fix.
>
> I see that you are on OSX (from your bug report) - have you tried
> my framework builds? I ran my gdal_translate, tiffcp and gdaladdo
> on your huge test tiff with no errors.
>
> On Mar 24, 2007, at 10:37 PM, Seth Price wrote:
>

>> I'm having a problem with gdaladdo, I'm afraid we don't seem to be >> getting along. It's very sensitive about the levels specified. For

>> example, if I specify "2 4 6 12 24 48 96" for a 21600x21600px >> image it works, but if I specify "2 4 8 16 32" it throws many errors.

>>

>> I can normally find a set of levels that works via guessing, but >> that isn't going to work any longer. Does anyone have any idea how

>> I can work around these errors? I haven't been able to find a >> pattern. Fixing the problem would be better.

>>
>> You can download the file that I've been using for a test here:
>> http://pricepages.org/temp/N048W123_x1_GLC.tif.gz (19MB)
>>

>> I think you can ignore the "StripByteCounts" warnings. I'm fairly >> sure that they are related to this bug. (It would be nice if

>> someone could have a look at that also, but it's not urgent.): >> http://bugzilla.remotesensing.org/show_bug.cgi?id=1483

>>
>> Here are some examples of the behavior that I'm talking about:
>>
>> $ /usr/local/bin/gdal_translate test.tif test.2.tif
>> Warning 1: TIFFReadDirectory:test.tif: Wrong "StripByteCounts"
>> field, ignoring and calculating from imagelength
>> Input file size is 21600, 21600
>> 0...10...20...30...40...50...60...70...80...90...100 - done.
>> Warning 1: TIFFReadDirectory:test.tif: Wrong "StripByteCounts"
>> field, ignoring and calculating from imagelength
>>
>> $ /usr/local/bin/gdaladdo -r nearest test.2.tif 2 4 8 16 32

>> 0.Warning 1: TIFFReadDirectory:test.2.tif: Wrong "StripByteCounts" >> field, ignoring and calculating from imagelength

>> Warning 1: TIFFReadDirectory:test.2.tif: Wrong "StripByteCounts" >> field, ignoring and calculating from imagelength

>> ERROR 1: test.2.tif:DumpModeDecode: Not enough data for scanline 0
>> ERROR 1: TIFFReadEncodedTile() failed.
>>
>> ERROR 1: IReadBlock failed at X offset 0, Y offset 2
>> ERROR 1: GetBlockRef failed at X block offset 0, Y block offset 2
>> ERROR 1: test.2.tif:DumpModeDecode: Not enough data for scanline 0
>> ERROR 1: TIFFReadEncodedTile() failed.
>>
>> ERROR 1: IReadBlock failed at X offset 0, Y offset 2
>> ERROR 1: GetBlockRef failed at X block offset 0, Y block offset 2
>> ERROR 1: test.2.tif:DumpModeDecode: Not enough data for scanline 0
>> ERROR 1: TIFFReadEncodedTile() failed.
>> [....]
>> $ ./gdaladdo -r nearest test.tif 2 4 6 12 24 48 96
>> Warning 1: TIFFReadDirectory:test.tif: Wrong "StripByteCounts"
>> field, ignoring and calculating from imagelength
>> 0...10...20...30...40...50...60...70...80...90...100 - done.
>>
>> Any ideas on where to proceed next with this?
>>
>> Thanks for any help,
>> Seth

>>
>
> -----
> William Kyngesburye <kyngchaos@kyngchaos.com>
> http://www.kyngchaos.com/
>

> "Those people who most want to rule people are, ipso-facto, those > least suited to do it."

>
> - A rule of the universe, from the HitchHiker's Guide to the Galaxy
>
>
>
>