Opened 15 years ago
Closed 15 years ago
#3110 closed defect (fixed)
NITF driver: improve handling of NITF IREP=RGB/LUT with JPEG2000 data
Reported by: | Even Rouault | Owned by: | Even Rouault |
---|---|---|---|
Priority: | normal | Milestone: | 1.7.0 |
Component: | default | Version: | unspecified |
Severity: | normal | Keywords: | |
Cc: |
Description
Currently, NITF datasets with a color table (IREP=RGB/LUT) and JPEG2000 data content are not correctly handled. GDAL only returns a single band without any color table associated. Depending whether the color table is only in the NITF image header (http://www.gwg.nga.mil/ntb/baseline/software/testfile/Jpeg2000/jp2_09/file9_j2c.ntf) or in it and the JPEG2000 data (http://www.gwg.nga.mil/ntb/baseline/software/testfile/Jpeg2000/jp2_09/file9_jp2_2places.ntf) , GDAL should return either the expanded RGB data returned by the JPEG2000 driver or a single band with the color table.
r17575 /trunk/gdal/frmts/nitf/nitfdataset.cpp: NITF driver : some infrastructure work to use a NITFWrapperRasterBand to wrap JPEG/JPEG2000 bands in a proxy band instead of setting them directly in the NITF dataset which lead to dirty hacks in the JPEG/JPEG2000 drivers themselves; used to solve the cases of NITF file with a color table and JPEG2000 data content
r17576 /trunk/autotest/gdrivers/nitf.py: Add tests for the NITF driver for files with IREP=RGB/LUT and JPEG2000 content