Opened 11 years ago
Closed 11 years ago
#5034 closed defect (fixed)
Large images via JP2KAK result in "too many tile-parts" error
Reported by: | warmerdam | Owned by: | warmerdam |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | GDAL_Raster | Version: | unspecified |
Severity: | normal | Keywords: | jp2kak |
Cc: |
Description
It seems writing an image via the JP2KAK driver with more than about 260000 lines results in the following Kakadu error:
Too many tile-parts for tile 0. No tile may have more than 255 parts.
The problem seems to be that by default the selected tile size for the JP2KAK driver is the full height of the image, and it is written out with a flush every CHUNK_SIZE (1024) lines which generally ends up being a tile part in the output tile.
Note:
See TracTickets
for help on using tickets.
Fix applies to restrict the default tile height to avoid too many tile parts in trunk (r25764) and 1.9 (r25765).
As a workaround the BLOCKYSIZE creation option can be set to 250000 for very long images.