[gdal-dev] NITF TRE parsing - possible extensions for MIE4NITF

[Brad Hards]

MIE4NITF 1.1 can be downloaded from 
https://nsgreg.nga.mil/NSGDOC/files/doc/Document/MIE4NITF%20v%201_1.zip
(see https://nsgreg.nga.mil/doc/view?i=4205 for info).

> Is the UINT naming somewhat standardized ? Otherwise perhaps uint_be to
> reflect
> that it is binary encoded with big endianness (contrary to integer)

I can live with either.

The spec says:
5.9.2 MIE4NITF defined data types
MIE4NITF defines several data types that are used within its TREs. These data 
types are defined in this section. Table 8 introduces an unsigned integer type 
that is used in the MIE4NITF TREs. The UINTn nomenclature is somewhat 
standardized in the computing world but it is included here to unambiguously 
define its use. All bytes in the UINTn data type are stored in big endian 
order and all bits within those bytes are stored most significant bit first.

> Not sure to have understood the structure of those TREs and couldn't find 
> any
> public resource describing them.
Sorry, should have linked to those in the initial email. In the spec (above), 
see
5.9.3.6 Freespace TRE (FREESA)
5.9.4.8 Frame-Synchronous Metadata Wrapper TRE (FSYNWA)
5.9.4.9 Frame-Asynchronous Metadata Wrapper TRE (FASYWA)

I would caution that it's a bit confusing the first time.

Brad