[PATCH] MrSID with JPEG2K compressed NITFs don't use block size from JPEG2K data
The attached patch improves the block size specification in the GDAL MrSID driver. This modification causes the the tile size returned by the J2KImageReader to be used as the block size for the image in the case of JPEG2K data embedded in NITFs. Although JPEG2K compression supports efficient reads of arbitrary size, we've found it useful to have the tile sizes used in the underlying JPEG2K structure to be used as the block size for NITFs as opposed to the arbitrary 1024x128 that usually resulted before this patch.
Change History
(5)
| Summary: |
MrSID with JPEG2K compressed NITFs don't use block size from JPEG2K data → [PATCH] MrSID with JPEG2K compressed NITFs don't use block size from JPEG2K data
|
| Resolution: |
→ wontfix
|
| Status: |
new → closed
|
Note that many jpeg2000 data streams use only one jpeg2000 tile even for large files. So I don't think it would be appropriate to incorporate this patch in the default implementation. I believe it is only appropriate for particular (nonblocking) access patterns or cases where you know the jpeg2000 data streams will not have very large tiles.
The patch will remain available here in trac.
It might be appropriate to reference it from the MrSID developer page at:
http://trac.osgeo.org/gdal/wiki/MrSID