Opened 3 years ago

Closed 2 years ago

#740 closed defect (fixed)

More gdal-dev, qgis-dev gremlins reading tiffs

Reported by: houska1 Owned by: osgeo4w-dev@…
Priority: major Component: Package
Version: Keywords: gdal qgis dev tiff
Cc: houska1

Description (last modified by jef)

Thanks for fixing LERC (#739) Unfortunately, there's some additional tiff reading issues in qgis-dev relying on gdal-dev 3.6.0

tiffs with the following structure (gdalinfo) that load fine in qgis 3.24.2 using gdal 3.4.3 now fail to load in dev:

Image Structure Metadata:
  COMPRESSION=YCbCr JPEG
  INTERLEAVE=PIXEL
  JPEGTABLESMODE=1
  JPEG_QUALITY=75
  SOURCE_COLOR_SPACE=YCbCr

The qgis error message is:

2022-05-09T06:20:48     WARNING    201404 DRAPE IR fc (RVCA) : C:/...path.../DRAPE 2014 IR compressed.tif, band 3: IReadBlock failed at X offset 23, Y offset 30: TIFFReadEncodedTile() failed.
2022-05-09T06:20:48     WARNING    201404 DRAPE IR fc (RVCA) : C:/...path.../DRAPE 2014 IR compressed.tif, band 2: IReadBlock failed at X offset 23, Y offset 30: TIFFReadEncodedTile() failed.
2022-05-09T06:20:48     WARNING    201404 DRAPE IR fc (RVCA) : C:/Users/...path.../DRAPE 2014 IR compressed.tif, band 1: IReadBlock failed at X offset 23, Y offset 30: TIFFReadEncodedTile() failed.

I've made the above referenced tiff available at https://www.dropbox.com/s/jnu5iwg5ehlll34/DRAPE%202014%20IR%20compressed.tif?dl=0 until closure of this ticket. Warning 50Mb. Similar failures on other similarly encoded tiffs.

Thanks!

Change History (6)

comment:1 by jef, 3 years ago

Description: modified (diff)

comment:2 by andreaerdna, 3 years ago

in reply to:  2 comment:4 by jef, 3 years ago

Replying to andreaerdna:

Maybe this is related to https://github.com/OSGeo/gdal/issues/5489

"completely unrelated."

comment:5 by houska1, 2 years ago

Gentle ping on this. A solution seems to be proposed at https://github.com/OSGeo/gdal/issues/5736 (though it went over my head).

No problem for this to sit here if it's just a bleeding-edge dev branch issue. But commenting to make sure that -- if unaddressed -- it doesn't break non-dev QGIS 3.26.0 in 2 weeks. I *think* the trigger point will be whether that non-dev build will continue to use GDAL 3.4.X or move to 3.6, but I'm not sure.

Note: See TracTickets for help on using tickets.