|National Imagery Transmission Format
This NITF implementation is very similar to GDB's previous implementation that was certified by the Joint Interoperability Test Command (JITC). The underlying NITFS features supported for registration have been maintained, but the Focus-level ELT-type behavior for NITF files has been modified to conform to regular GDB file support. The features of the certified NITF can be viewed in the JITC compliancy register. NITF Version 1.1 is also supported.
The following export options can be entered in the Focus Translate (Export) window.
NITF version options
You can choose from among several NITF versions when you create a new NITF file. The version of the NITF standard that is used is controlled by one of four values:
Two compression types can be applied to imagery in the NITF file:
The following types of tiling are available:
When an NITF file is created, some of the metadata has default values specific to each particular site. An example is the ONAME (Originator’s Name) field which contains a name for the operator. Each field that has a default is specified in the nitf.defaults file. This file should be placed in the etc subdirectory of the CATALYST Professional install directory.
Each line in the nitf.defaults file has the name of the field, colon, space, and the value. An example file is
ONAME: XYZ Company OPHONE: 1 (800) 555-0022 OSTAID: TorontoON FSCLAS: U
The following fields are valid entries in the nitf.defaults file:
ONAME, OPHONE, OSTAID, OID,
FSCLAS, FSCLSY, FSCODE, FSCTLH,
FSREL, FSDCTP, FSDCDT, FSDCXM,
FSDG, FSDGDT, FSCLTX, FSCATP,
FSCAUT, FSCRSN, FSSRDT, FSCTLN,
Values for the above-listed fields are not validated with the exception of FSCLAS, which can only have a value of T, S, C, R or U.
Further information on editing metadata values is given in the following section.
The metadata values shown in Focus in the File Properties window can be edited. However, the user must ensure that the format of the new values conforms to the standard. For example, in NITF 2.0 the IDATIM (Image Date and Time) field has the format of DDHHMMSSZMONYY, whereas in NITF 2.1 it has the format of CCYYMMDDhhmmss.
Some values are intrinsic to the file; therefore, the edited values will not be saved. For more details, please see the appropriate NITF standards document at http://www.gwg.nga.mil/ntb/baseline/documents.html.
© PCI Geomatics Enterprises, Inc.®, 2023. All rights reserved.