NTBNITFS Technical Board TitleHomeNGA Seal - HomepageWhat's NewCalendarNTB AnnouncementsNTB AgendasNTB MinutesAction Item DatabaseBriefing Charts
What is NITFS?

The evolution of computer microprocessor technology in the early 1980s made it feasible to build numbers of systems that could interchange annotated digital imagery. By 1984, the need for a common data format became apparent, and a project to develop such a format was initiated. The original goal was to develop a co-standard that could be added to all of the existing systems and incorporated into new systems during the acquisition process. Version 1.0 of the NITF, which included only the image format, was approved in 1987 for use as a demonstration capability but not as a general implementation baseline. A formal structure was created to continue the development of NITF. The NITF Technical Board (NTB) was created to manage development, validation, certification, and integration. A Defense Support Project Office (DSPO) representative was appointed to manage development and co-chair the NTB. An Intelligence Communications Architecture (INCA) Project Office representative was appointed to manage validation, certification, and testing, and to co-chair the NTB.

NITF 1.1:

Version 1.1, an improved format, was developed, validated, and proposed as the implementation baseline. The NITF Configuration Control Board (NCCB), chaired by a representative from the Office of the Assistant Secretary of Defense for Command, Control, Communications, and Intelligence, OASD(C3I) approved Version 1.1 for general implementation in March 1989. A certification test facility was established in 1990 under INCA sponsorship. In 1991, the Defense Intelligence Agency (DIA) assumed INCA's responsibilities, and the certification test facility was moved to the Joint Interoperability Test Command (JITC), Ft. Huachuca, AZ. By March 1992, over thirty different system configurations had been certified as compliant with NITF Version 1.1, some with waivers.


Development of an improved version of NITF began in 1988. Initially, the new version was called NITF 2.0. The key improvement over the earlier version of NITF was the inclusion of a communications support capability, to enable NITF to be transmitted over tactical circuits. The primary communications support capability was the communications protocol TACO2. Additionally, improved image compression, forward error correction, and enhanced graphics algorithms began development. In 1991, NITF began conversion to a DOD standard. To mark this, the name was changed to the National Imagery Transmission Format Standard (NITFS). NITFS now encompasses not only the NITF 2.0 file format, but also includes supporting standards for image compression, transmission protocols, and graphics. The Handbook is the top level document in the document structure. There are supporting format and data representation standards as well as the embraced protocol standards and Technical Interface Specifications (TIS), the latter providing detailed implementation guidance. In 1992, the Image Handling Standards and Guidelines document for Commercial Analyst Workstation (CAWS) adopted the NITF 2.0 file format (only) as the format for full frame National imagery to be distributed from IDEX II, System III, and Low Cost Media. Also in 1992, development responsibility moved to the National Imagery and Mapping Agency (NGA), formerly the National Imagery and Mapping Agency (NIMA) and was incorporated into the Defense Standardization Program under the auspices of the Defense Information Systems Agency (DISA).

NITF 2.1

The imagery community is planning the transition from NITF2.0 (Mil Std 2500A) to NITF2.1 (Mil Std 2500B). The new military standard is being coordinated and reviewed with an anticipated date for CM baseline of September 1997. NITF2.1 will provide increased capability and flexibility. NITF2.1 will include JPEG compression, CGM for graphics, new decompression algorithms, changes to address the Y2K issue, and implementation of USMTF structured text.

As implementations transition from NITF2.0 to NITF2.1, there will be a need to maintain backward compatibility with NITF2.0. This will allow continued interoperability with legacy 2.0 systems that have not yet transitioned and provide access to the vast number of archived 2.0 formatted files.

All currently fielded imagery systems must be NITF 2.1 compliant or replaced by NITF 2.1 compliant systems within two years of the start date for the NITFS Certifcation, Test, and Evaluation (CTE) Program. To support interoperability during the transition period, all NITF 2.1 compliant systems must have a mode of operation that allows for proper interpretation and use of NITF Version 1.1 formatted files and that limits the creation of an NITF file content to the constraints of NITF version 1.1. Developmental imagery systems must be tested for and achieve NITF 2.0 compliance prior to fielding.


Currently, by Office of Secretary of Defense for Command, Control, Communications and Intelligence (OSDC3I) directive, NITFS is mandated for all DoD SIDS. In May 1989, the Chairman of the Committee on Imagery Requirements and Exploitation (COMIREX) directed the adoption of the NITF as the Intelligence Community standard for the transmission of secondary images.


The purpose of the NITFS is to transmit a file composed of an image accompanied by subimages, symbols, labels, text, and other information that relate to the image. One of the main features of the NITFS is that it allows several items of each data type to be included in one file, yet any data types may be omitted. Figure 3 [not currently available via this server] illustrates the functional relationship of the components of the NITFS. The figure illustrates imagery, graphics, and text (documents and labels) as input to the formation of a NITF file, which incorporates the CGM standard for graphics and accommodates user-selectable compression for images. Then the file is submitted to the Message transfer Facility (MXF), which allows it to be transferred using any of a set of user-selectable protocols and media. The output is a message which, by conforming to the standards and their use as illustrated, is compliant with the NITFS.

Certification Test and Evaluation (CTE) Program

Assistant Secretary of Defense for Command, Control, Communications and Intelligence (ASD(C3I)) has mandated compliance with the NITFS for all DOD SIDS. In 1989, on behalf of the Intelligence Community, COMIREX established the NITFS as the standard for imagery transmission. The National Imagery and Mapping Agency (NGA) oversees the NITFS Certification Test and Evaluation (CTE) Program that determines compliance with the NITFS.

The Defense Information System Agency's (DISA) Joint Interoperability Test Command (JITC), located at Fort Huachuca, Arizona, serves as NGA's Executive Agent for execution of NITFS test-related activities. The JITC has established a NITFS CTE Facility that supports certification testing of NITFS capable systems, validation testing of proposed additions to NITFS, and other test activities related to NITFS. A register of NITFS certified systems is also maintained at the CTE Facility. Detailed information concerning the NITFS Certification Test and Evaluation Program, including the established certification test criteria, is contained in DISA/JIEO Circular 9008.

Configuration Management of NITFS

As mandated by ASD(C3I) memo dated September 1991, subject: "Executive Agent for DoD Information Standards," NITFS configuration management is managed by the Defense Information Systems Agency (DISA), Joint Interoperability and Engineering Organization (JIEO), center for Standards (CFS), in accordance with DoD Instruction 5000.2, Defense Acquisition Management Policies and Procedures, 23 February 1991.

Point of Contact: ntbchair@nga.mil
                             NTB Members | MISB Members | NCGIS | NGA Home | GWG Home