NITF: Add support for writing multi-image nitf files

[yehiyam]

In the process of adding support for writing NITF files to our product, we noticed that the NITF driver was missing the functionality to correctly create sub images (NITF image segments).
Currently the driver only supports specifying the number of sub images (with the NUMI create option), but all of the properties of the sub-images (e.g. width, height, pixel format) are taken from the main image.
Following the design of the current NITF driver, where all NITF specific properties are set using create options, we have extended the set of create options to allow specifying the missing properties.
Unfortunately, we are still working with GDAL 1.8.1, so the attached patch is against the 1.8.1 version, and not the trunk version. I’m still creating this ticket in the hope that it will be useful for someone, and hopefully will be integrated into trunk in the future.
The new create options share the name of the NITF property with the suffix _XXX where XXX is the sub-image index (1 is the main image, 2 is the first sub-image, etc, with trailing zeros).
NROWS_XXX : the number of rows (height) of the sub-image.
NCOLS_XXX: the number of columns (width) of the sub-image.
ILOCROW_XXX: the vertical offset of the sub-image (in pixels)
ILOCCOL_XXX: the horizontal offset of the sub-image (in pixels)
IC_XXX: the compression of the sub image (must be NC for sub-images according to the NITF spec).
IREP_XXX: either RGB or RGB/LUT to reserve space for a color table if needed.
NBANDS_XXX: The number of bands for RGB images, or 1 for LUT.
APBB_XXX: The number of bits per band (or 8 for a 256 entries palette).
PVTYPE_XXX: string description of the pixel data type (INT, SI, R).
LUT_SIZE_XXX: the number of entries in the LUT.

[yehiyam]

Patch of nitffile.c

[Even Rouault]

This ticket has been automatically closed because Trac is no longer used for GDAL bug tracking, since the project has migrated to GitHub. If you believe this ticket is still valid, you may file it to ​https://github.com/OSGeo/gdal/issues if it is not already reported there.