You can edit the following metadata for images with the NITF output format:
File header
File security fields
Image subheader
Image security fields
Image comments
For more information on NITF metadata, see the NITF 2.1 specification at http://www.gwg.nga.mil/ntb/baseline/docs/2500c/2500C.pdf.
In addition to the NITF metadata that you can edit, GeoExpress embeds metadata from NITF input files to preserve the source metadata. When reading a NITF file, GeoExpress stores many NITF fields as metadata, for example as tag/value pairs in MrSID imagery.
The following discussion assumes familiarity with the NITF specification.
In general, the tag name is of the form
NITF::xxnnn::field
where xx
is a two letter code representing the NITF segment (IM for image, FH for file header) and nnn
is the NITF segment number. TRE fields contain the prefix TRE_
. Specifically, GeoExpress stores input fields in metadata tags as described in the following tables.
GeoExpress stores file header fields in the following tags:
NITF Field | GeoExpress Tag |
---|---|
FHDR | NITF::FH000::FHDR |
FVER | NITF::FH000::FVER |
STYPE | NITF::FH000::STYPE |
OSTAID | NITF::FH000::OSTAID |
FDT | NITF::FH000::FDT |
FTITLE | NITF::FH000::FTITLE |
ONAME | nitf::fh000::oname |
OPHONE | nitf::fh000::ophone |
NUMI | nitf::fh000::numi |
NUMS | nitf::fh000::nums |
NUML | nitf::fh000::numl |
NUMT | nitf::fh000::numt |
numdes | nitf::fh000::numdes |
numres | nitf::fh000::numres |
Using GeoExpress, you can set the values for OSTAID, FDT, FTITLE, ONAME, and OPHONE when encoding NITF images.
GeoExpress stores security-related fields from the file header (unless they are blanks) in the following tags:
NITF Field | GeoExpress Tag |
---|---|
sclas | NITF::FH000::sclas |
sclsy | NITF::FH000::sclsy |
scode | NITF::FH000::scode |
sctlh | NITF::FH000::sctlh |
srel | NITF::FH000::srel |
sdctp | NITF::FH000::sdctp |
sdcdt | nitf::fh000::sdcdt |
sdcxm | nitf::fh000::sdcxm |
sdg | nitf::fh000::sdg |
sdgdt | nitf::fh000::sdgdt |
scltx | nitf::fh000::scltx |
scatp | nitf::fh000::scatp |
scaut | nitf::fh000::scaut |
scrsn | nitf::fh000::scrsn |
ssrdt | nitf::fh000::ssrdt |
sctln | nitf::fh000::sctln |
GeoExpress allows you to specify values for any of these fields.
GeoExpress stores image segment fields in the following tags:
NITF Field | GeoExpress Tag |
---|---|
iid1 | NITF::im001::iid1 |
idatim | nitf::im001::idatim |
tgtid | nitf::im001::tgtid |
iid2 | nitf::im001::iid2 |
isorce | nitf::im001::isorce |
icords | nitf::im001::icords |
igeolo | nitf::im001::igeolo |
nicom | nitf::im001::nicom |
icom1 | nitf::im001::icom1 |
icom2 | nitf::im001::icom2 |
icom3 | nitf::im001::icom3 |
icom4 | nitf::im001::icom4 |
icom5 | nitf::im001::icom5 |
icom6 | nitf::im001::icom6 |
icom7 | nitf::im001::icom7 |
icom8 | nitf::im001::icom8 |
icom9 | nitf::im001::icom9 |
With GeoExpress, you can enter custom data for these image segment fields: IID1
, IDATIM
, TGTID
, IID2
, ISORCE
, NICOM
, ICOM1 through ICOM9
.
In addition, GeoExpress does the following:
handles the security fields in the Image Segment as they are handled in the file header
stores all detected TREs in metadata as binary data. For example, USE00A data would be stored as an array of bytes using the following tag:
NITF::IM001::TRE_USE00A
explicitly recognizes the following TREs when reading in a NITF file:
J2KLRA
, USE00A
, STDIDC
, PIAIMC
, and RPC00A/B
For these TREs, additional metadata entries are created corresponding to each of their constituent fields. For example, PIAIMC data is represented as follows:
NITF::IM001::TRE_PIAIMC_CLOUDCVR
NITF::IM001::TRE_PIAIMC_SRP
NITF::IM001::TRE_PIAIMC_SENSMODE
NITF::IM001::TRE_PIAIMC_SENSNAME
…