NITFS Technical Board (NTB) Documentation, Demonstration Software and JITC Test Tools
View NITFS Documentation - NTB Maintained Documents
Legacy Documents
The following Legacy Documentation available on request. If you would like a copy of one or more please contact the ntbchair@nga.mil.
| Bi-Level | MIL-STD-188-196 | Bi-Level Image Compression. |
| ARIDPCM | MIL-STD-188-197A | Adaptive Recursive Interpolated Differential Pulse Code Modulation (ARIDPCM) Compression Algorithm: Capability to read legacy MIL-STD-188-197A ARIDPCM compressed files is optional; specific USIGS segments, libraries, may be required to use this standard to ensure translation capabilities. (For NITF 1.1 only) |
| Downsampled JPEG | N-0106-97 | Bandwidth Compression Standards and Guidelines Document. |
| TACO2 | MIL-STD-2045-44500 | Tactical Communications Protocol 2. |
| IPON | STDI-0005 | Implementation Practices of The National Imagery Transmission Format Standard. |
| NITFS Handbook | MIL-HDBK-1300A | The National Imagery Transmission Format Standard (NITFS) Handbook. |
| CGM | MIL-STD-2301A | This standard establishes the requirements necessary to implement Computer Graphics Metafiles (CGMs) used for the representation of symbol graphics in the National Imagery Transmission Format Standard (NITFS). |
| NITF 2.1 | MIL-STD-2500B | National Imagery Transmission Format Version 2.1. Through NOTICE 2. |
| NITF 2.0 | MIL-STD-2500A | National Imagery Transmission Format (Version 2.0) through NOTICE 3. |
NITF Version 1.1, (1 January 1990)
The following NITF 1.1 files are available on request. For access to files, please download the NTB Sample Test File Request form, fill out and return to ntbchair@nga.mil.
| Number | Case | OBJECTIVE OF THIS FILE |
|---|---|---|
| 1 | U_0001A | Bitmapped, Labels and Text Data Types with Image: R1 is an NITF 1.1 file that displays 5 images, 100 symbols, 100 labels and 5 text files. |
| 2 | U_0001B | Multi-Image Data Type with 5-bit Image: R1_a is an NITF 1.1 file that displays 3 images, 1 image is less than 8 bits per pixel (5 bits). |
| 3 | U_0001C | Testing Display and Attachment Levels: R1_b is an NITF 1.1 file that checks the display & attachment levels for a 1.1 file. |
| 4 | U_0002A | Testing Header Only File: R2 is an NITF 1.1 file that is strictly a header only file. System should not lock and allow user to see contents of header. |
| 5 | U_0004A | Bitmapped Data Type: R4_2 is an NITF 1.1 file that is 16 128x128 bitmap symbols. |
| 6 | U_0005A | Label Data Type: R5_7 is an NITF 1.1 file that checks standard labels. |
| 7 | U_0006A | Text Data Type: R6_4 is an NITF 1.1 file that checks for the display of a large text file, no displayable segments, text only. |
MIL-STD-2500A, Version 2.0, (1 October 1998):
The following NITF 2.0 files are available on request. For access to files, please download the NTB Sample Test File Request form, fill out and return to ntbchair@nga.mil.
| Number | Case | OBJECTIVE OF THIS FILE |
|---|---|---|
| 1 | u_1005a | JPEG DCT Data Type: JPEG DCT Data Type: Checks a JPEG-compressed 64x64 8-bit mono image (LINCOLN), Q1 embedded tables, with image comments. |
| 2 | JPEG DCT Data Type: Checks a JPEG-compressed 256x256 8-bit mono image (TANK), using Q2 default tables, COMRAT 00.2. File also contains image comments. | |
| 3 | JPEG DCT Data Type: Checks a JPEG-compressed 1024x1024 8-bit mono image (AIRSTRIP), using Q3 default tables, COMRAT 00.3. File also contains image comments. | |
| 4 | JPEG DCT Data Type: Checks a JPEG-compressed 256x256 8-bit mono image (TANK), using Q4 default tables, COMRAT 00.4. File also contains image comments. | |
| 5 | JPEG DCT Data Type: Checks a JPEG-compressed 256x256 8-bit mono image (TANK), using Q5 default tables, COMRAT 00.5. File also contains image comments. | |
| 6 | CGM Data Type with Image: Checks a complex display and attachment level CGM files, contains 100 CGM files with multi displayable elements. | |
| 7 | Bitmapped Data Type with Image: Gray base image with one bitmapped 1024x1024 symbol having black border and tranparent center, max bit-map symbol bytes for CLEVEL1. | |
| 8 | Bitmapped, Labels and Text Data Type with Image: Can system handle 5 images, with 100 SYM, 100 LAB and 5 text segments in one NITF file. | |
| 9 | Testing Display and Attachment Levels: This NITF file contains 5 images, 4 symbols, 4 labels and 1 text with complex use of DL/AL (many parent child relationships). | |
| 10 | Testing Display and Attachment Levels: This file checks to see if an image is unpack in display level or branch level order. NITF systems must do display level order. | |
| 11 | Bitmapped, Labels and Text Data Type with Image: Checks max # of segments for CLEVEL2, 5 images, 100 symbols, 100 labels, 5 text. | |
| 12 | JPEG DCT Data Type: Checks JPEG 256x256 24-bit PI block color w/QFAC=custom, RSTI=4, IMODE=P. | |
| 13 | Testing Graphic with Lowest Display Level: Checks uncomp. base w/multiple CGM. CGM border has lowest DL not the first image. | |
| 14 | VQ Data Type: Checks to see if SUT can unpack and display a CIB VQ (C4) compressed image 1536x1536, file contains RPFHDR, RPFIMG and RPFDES TREs. | |
| 15 | Bitmapped Data Type with Image: Checks IMODE P 3072x3072 color image with max aggregate size for bitmaps symbols. | |
| 16 | JPEG DCT with IOMAPA Data Type with Image: 12-BIT JPEG with IOMAPA TRE mapping method 0 with S2 value of 1. The pixel presentation should be about the same for IOMAPA supported and non-supported applications with the acception of small adjustments as a result of Dynamic Range Adjustment that some application support. File also includes an NBLOCKA TRE. | |
| 17 | JPEG DCT with IOMAPA Data Type with Image: 12-BIT JPEG with IOMAPA TRE mapping method 0 with S2 value of 9. The pixel presentation for non-supported applications will look like u_4020a (Non-Supported). File also includes an NBLOCKA TRE. | |
| 18 | JPEG DCT with IOMAPA Data Type with Image: 12-BIT JPEG with IOMAPA TRE mapping method 1 with progressive block min values, block 1=300 thru block 12=3,600. The pixel presentation for non-supported applications will look like u_4020a (Non-Supported). File also includes an NBLOCKA TRE. |
Joint BIIF Profile, Version 2021-2, (20 April 2021):
The following JBP files are available on request. For access to files, please download the NTB Sample Test File Request form, fill out and return to ntbchair@nga.mil.
| Number | Case | OBJECTIVE OF THIS FILE |
|---|---|---|
| 1 | i_3000a | Non-Compressed Data Type: The application must be capable of decoding and displaying an NSIF 1.0 file with a single block, 8-bits, non-compressed, IREPBAND1 = M, PVTYPE = INT, monochrome image 1024x1024 with NROWS = NPPBV and NCOLS = NPPBH without block fill. |
| 2 | i_3408a | Non-Compressed Data Type: The application must be capable of decoding and displaying an NITF 2.1 file with a multi-block (512x512), 14-bits, non-compressed, IREPBAND1 = M, PVTYPE = INT, monochrome image 1024x1024 with NROWS = NPPBV and NCOLS = NPPBH without block fill. |
| 3 | i_3201ax | Non-Compressed Data Type: The application must be capable of decoding and displaying an NITF 2.1 file with multi-blocks (256x256), 8-bits, non-compressed, IREPBAND1 = LU, PVTYPE = INT, RGB/LUT image 512x512 with NROWS = NPPBV and NCOLS = NPPBH without block fill, three LUTs 256 entries. |
| 4 | i_3201c | Non-Compressed Data Type: The application must be capable of decoding and displaying an NITF 2.1 file with multi-blocks (256x256), 8-bits, non-compressed, IREPBAND1 = LU, PVTYPE = INT, RGB/LUT image 512x512 with NROWS = NPPBV and NCOLS = NPPBH without block fill, three LUTs 256 entries. |
| 5 | i_3301p | Non-Compressed Data Type: The application must be capable of decoding and displaying an NITF 2.1 file with a single block, 8-bits, non-compressed masked, IREPBANDn = R, G, B, PVTYPE = INT, RGB image 256x256 with NROWS = NPPBV and NCOLS = NPPBH without block fill, IMODE B. This is a single block masked file containing only Masked Blocks. Even with the Masked Header is in the file all blocks are present none are missing. Pad Output Pixel Code is present and set to "0" for transparent. Even thou the Pad Output Code is present does the application honor it for Block Mask and display as shown or does the background display in other than green. |
| 6 | i_3301c | Non-Compressed Data Type: The application must be capable of decoding and displaying an NITF 2.1 file with multi-blocks (256x256), 8-bits, non-compressed masked, IREPBANDn = R, G, B, PVTYPE = INT, RGB image 768x768 with NROWS = NPPBV and NCOLS = NPPBH without block fill, IMODE S This is a pad pixel file with TPXCD is set to "0", means pad pixels will be displayed as transparent showing the green background color. |
| 7 | i_3301k | Non-Compressed Data Type: The application must be capable of decoding and displaying an NITF 2.1 file with multi-blocks (256x256), 8-bits, non-compressed masked, IREPBANDn = R, G, B, PVTYPE = INT, RGB image 768x768 with NROWS = NPPBV and NCOLS = NPPBH without block fill, IMODE R. This is a pad pixel file with TPXCD is set to "0", means pad pixels will be displayed as transparent showing the green background color. |
| 8 | i_3231ax | Non-Compressed Data Type: The application must be capable of decoding and displaying an NITF 2.1 MULTI image 347x487 with NROWS = NPPBV and NCOLS = NPPBH without block fill, IMODE B with 4 bands, the image subheader has all bands marked as LU for display, the interpreter must display band 1 with associated LUT. |
| 9 | i_3228jx | Non-Compressed Data Type: The application must be capable of decoding and displaying an NITF 2.1 file with a single block, 16-bits, non-compressed MULTI, IREPBANDn = all BCS spaces, PVTYPE = INT, MULTI image 1280x1704 with NROWS = NPPBV and NCOLS = NPPBH without block fill, IMODE B with 9 bands, the image subheader as no bands are marked for display, the interpreter must display band 1 as red, band 2 as green, and band 3 as blue. |
| 10 | i_5110bx | Non-Compressed Data Type: The application must be capable of decoding and displaying an NITF 2.1 file with multi-blocks (256x256), 8-bits, non-compressed, PVTYPE = INT, MULTI image 1024x1024 with NROWS = NPPBV and NCOLS = NPPBH without block fill, IMODE B with 12 bands, the image subheader telling the interpreter to display as as RGB, IREPBAND4 = R, IREPBAND5 = G, and IREPBAND6 = B. Only displayable bands provided, open in viewer to see other bands for display. |
| 11 | i_3113c | JPEG DCT Data Type: The application must optionally be capable of decoding and displaying an NITF 2.1 file with a JPEG Downsampled 2048x2048 down sampling 744x744 8-bit mono image supporting embedded Quantization (Q1) and Huffman (H3) embedded NTB published Tables. |
| 12 | i_3113e | JPEG DCT Data Type: The application must optionally be capable of decoding and displaying an NITF 2.1 file with a JPEG Downsampled 2048x2048 down sampling 1692x1692 8-bit mono image supporting embedded Quantization (Q1) and Huffman (H5) embedded NTB published Tables. |
| 13 | i_3005b | JPEG DCT Data Type: The application must be capable of decoding and displaying an NSIF 01.01 file with a JPEG 64x64 8-bit mono image, supporting both embedded default Quantization (Q1) and Huffman tables, COMRAT 00.1, JPEG table associations. |
| 14 | i_3018a | JPEG DCT Data Type: The application must be capable of decoding and displaying an NITF 2.1 file with a JPEG 231x191 8-bit mono image supporting embedded custom Quantization (Q0) and Huffman tables custom, COMRAT 00.0, with corrupted restart marker occurring to early. |
| 15 | i_3032a | JPEG DCT Data Type The application must be capable of decoding and displaying an NITF 2.1 file with a JPEG 188x193 8-bit mono image supporting embedded custom Quantization (Q0) and Huffman tables custom, COMRAT 00.0, non-divide by 8, fill 7, 4 bits. |
| 16 | i_3306a | JPEG DCT Data Type: he application must be capable of decoding and displaying an NITF 2.1 600x600 JPEG DCT multi blocked at 256x256, 8-bit image image monochrome, with Restart Markers set to 16, image contains 168 pixels of block pad in each direction. |
| 17 | i_3420x | JPEG DCT Data Type: The application must be capable of decoding and displaying an NITF 2.1 3740x5120 JPEG DCT multi blocked at 512x256, 11-bit image image monochrome, with Restart Markers set to 32, supporting embedded custom Quantization and Huffman tables. |
| 18 | i_3228l | JPEG DCT Data Type: The application must be capable of decoding and displaying an NITF 2.1 1024x1024, 4 band MS JPEG DCT IMODE B single blocked image. Note: Optional, if not supported must show message of non-support. |
| 19 | i_3309c | JPEG DCT Data Type: The application must be capable of decoding and displaying an NITF 2.1 638x978, 3 band MS JPEG DCT IMODE B multi blocked at 489x319 image. Note: Optional, if not supported must show message of non-support. |
| 20 | c_3201p | JPEG DCT Data Type: The application must be capable of decoding and displaying an NITF 2.1 file with a JPEG 512x393 8-bit Color RGB image supporting embedded custom Quantization (Q0) and 2 Huffman tables custom, but all three Bands point only to first table, with fill. |
| 21 | i_3207bx | JPEG DCT Data Type: The application must be capable of decoding and displaying an NITF 2.1 file with a JPEG 512x512 8-bit Color RGB image supporting the standard Red, Green and Blue Quality Level 2 color tables COMRAT 00.2, with default Huffman Tables. |
| 22 | i_3311a | JPEG DCT Data Type: The application must be capable of decoding and displaying an NITF 2.1 2048x2048 JPEG DCT multi blocked at 512x512, 8-bit image, IMODE P, 3 band RGB image, with Restart Markers set to 32, with no block pad. |
| 23 | i_3213a | JPEG DCT Data Type: The application must be capable of decoding and displaying an NITF 2.1 file with a JPEG 521x521 8-bit YCbCr image supporting embedded custom Quantization (Q0) and 2 Huffman Tables custom, without subsampling, with RST Marker 32, image is non-divisible by 8, fill 7, 7 bits and data ordering. |
| 24 | i_3311ax | JPEG DCT Data Type: The application must be capable of decoding and displaying an NITF 2.1 2048x2048 JPEG DCT multi blocked at 1024x2048, 8-bit image, IMODE P, 3 band YCbCr, image, with Restart Markers set to 32, with no block pad. |
| 25 | 1001_512x512_s_1_1_mono | JPEG2000 Data Type: This is a basic 1-bit JPEG2000 CLEVEL 3 file. |
| 26 | 005_007_1024x1024_s_8_1_mono | JPEG2000 Data Type: Medium Size CLEVEL 3 NITF 2.1 file 1024x1024 file with precinct not specified. Bits per pixel 5.700401. |
| 27 | 027_2300x3000_s_8_1_mono | JPEG2000 Data Type: Medium Size CLEVEL 5 NITF 2.1 file lossless 8-bit single blocked mono 2300x3000 image file, last six layers have no visual intelligence created by software defaults. Bits per pixel 4.778911. |
| 28 | 026_1024x1024_s_8_3_rgb | JPEG2000 Data Type: 2049x2049 image single tile, Profile 1, Clevel 5 NITF 2.1 file test case using 9-7 filter, CPRL J2K codestream. |
| 29 | 043_6217x4766_s_8_3_rgb | JPEG2000 Data Type: Medium Size CLEVEL 5 NITF 2.1 file lossless single blocked color 6217x4766 image file. Bits per pixel 8.839957 or 2.946652 per band and numerically lossless. |
| 30 | 058_512x512_s_8_7_ms | JPEG2000 Data Type: Medium Size CLEVEL 3 NSIF 01.01 file lossless 7 Band single-blocked MS 512x512 image file with BIIF PROFILE BPJ2K01.00 recommended Layer bit-rates all layers have visual intelligence. Bits per pixel 30.656464 or 4.379495 per band and numerically lossless. |
| 31 | 074_614x512_s_8_9_ms | JPEG2000 Data Type: Small CLEVEL 3 NITF 2.1 lossless 614x512 file with BIIF PROFILE BPJ2K01.00. Bits per pixel 7.682351 and numerically lossless. |
| 32 | 105_128x128_s_8_255_ms | JPEG2000 Data Type: mall CLEVEL 5 NITF 2.1 file lossless 128x128 MS 255 band file. Bits per pixel 6.380371 and numerically lossless. |
| 33 | 016_1024x1024_s_11_1_mono | JPEG2000 Data Type: Medium Size CLEVEL 3 NITF 2.1 file 1024x1024 file with BIIF PROFILE BPJ2K01.00 recommended Layer bit-rates. Bits per pixel 8.746521 and numerically lossless. |
| 34 | i_3036a | Bi-Level Data Type: The application must be capable of decoding and displaying an NITF 2.1 file with a 1D BI-LEVEL image with fill. |
| 35 | C4RGB-LUT | VQ Data Type: The application must be capable of decoding and displaying an NITF 2.1 file with a RGB-LUT C4 VQ image with a 3 band LUT. |
| 36 | M4RGB-LUT | VQ Data Type: The application must be capable of decoding and displaying an NITF 2.1 file with a RGB-LUT M4 VQ image with a 3 band LUT. |
| 37 | i_3090e | CGM Data Type (with Image): The application must be capable of decoding and displaying an NITF 2.1 CGM CIRCLE1 checks for proper interpretation of VDCs and drawing of CGM circles across different quadrants. |
| 38 | i_3090k | CGM Data Type (with Image): The application must be capable of decoding and displaying an NITF 2.1 CGM CIRARCC3 checks for proper interpretation of VDCs and drawing of center-closed CGM circular arcs across different quadrants. |
| 39 | i_3090r | CGM Data Type (with Image): The application must be capable of decoding and displaying an NITF 2.1 CGM CIRARCCA checks for proper interpretation of VDCs and drawing of center-closed CGM circular arcs across different quadrants. |
| 40 | i_3114b | Text Data Type: The application must be capable of decoding and displaying an NITF 2.1 file with a Text Segment having a Text Format of "STA" with multi bytes of data, the product contains HTML data, but within the allowed character set of "STA". |
| 41 | i_3114d | Text Data Type: The application must be capable of decoding and displaying an NITF 2.1 file with a Text Segment having a Text Format of "UT1" with a basic "UT1" segment of 15 bytes. If displayed in brower, encoding should be set to "Western European (Windows)". |
| 42 | i_3114e | Text Data Type: The application must be capable of decoding and displaying an NITF 2.1 file with a Text Segment having a Text Format of "UT1" testing to see if application can display the extended UT1 values of 0xA0 to 0xFF per Table B-1 MIL-STD-2500C. If displayed in brower, encoding should be set to "Western European (Windows)". |
| 43 | i_3114f | Text Data Type: The application must be capable of decoding and displaying an NITF 2.1 file with a Text Segment having a Text Format of "U8S" with a basic "U8S" segment of 296 bytes. If displayed in brower, encoding should be set to "Unicode (UTF-8)". |
| 44 | 09-Image-IGEOLO | TRE Data Types (with Image): The application must be capable of decoding and displaying an NITF 2.1 product which contains ICORDS and IGEOLO data which is optional, but the IUT must as a minimum skip past ICORDS and IGEOLO in order to display a monochrome Non-Compressed Image segment. If supported the IUT when selecting pixel 256, 256 must display approximately 33:21:48N 044:21:10E based on IUT geographical digit display capability. |
| 45 | 15-Pixel-Space_IGEOLO | TRE Data Types (with Image): The application must be capable of decoding and displaying an NITF 2.1 product with two image segments in pixel space as required as part the NITFS CCS. Additionally, the data can optionally be displayed by the IUT in geographic space, but this is not required. If ICORDS/IGEOLO supported the IUT when selecting pixel 255.5, 255.5 of image with display level "001" should display approximately 33:21:48N 044:21:09E, if selecting pixel 0.5, 0.5 of the image with display level "002" should display approximately 33:21:29N 044:21:25E based on IUT geographical digit display capability. |
| 46 | 16-TRE-RPC | TRE Data Types (with Image): The application must be capable of decoding and displaying an NITF 2.1 product which contains RPC00B/ICHIPB TRE data which is optional, but the IUT must as a minimum skip past RPC00B/ICHIPB TRE in order to display a monochrome Non-Compressed Image segment. If supported the IUT when selecting pixel 256, 256 must display approximately 33:21:48N 044:21:10E based on IUT geographical digit display capability. |
| 47 | 17-TRE_GEOLOB | TRE Data Types (with Image): The application must be capable of decoding and displaying an NITF 2.1 product which contains GEOPSB/GEOLOB TRE data which is optional, but the IUT must as a minimum skip past GEOPSB/GEOLOB TRE in order to display a monochrome Non-Compressed Image segment. If supported the IUT when selecting pixel 256, 256 must display approximately 33:21:48N 044:21:10E based on IUT geographical digit display capability. |
| 48 | 18-TRE-BLOCKA | TRE Data Types (with Image): The application must be capable of decoding and displaying an NITF 2.1 product which contains BLOCKA TRE data which is optional, but the IUT must as a minimum skip past BLOCKA TRE in order to display a monochrome Non-Compressed Image segment. If supported the IUT when selecting pixel 256, 256 must display approximately 33:21:48N 044:21:10E based on IUT geographical digit display capability. |
NITFS Demonstration Software:
The following demonstration software is available on request. Please identify the software below you would like and contact the ntbchair@nga.mil.
|
|
|
|
|
|
|
|
|
|
BIIF Test Tool Information: JITC Test Tools: Compliant Image Validation Analyzer (CIVA)
The Joint Interoperability Test Command’s GEOINT TEST, EVALUATION, & CERTIFICATION (TEC) PROGRAM has developed the Compliant Image Validation Analyzer (CIVA) is a National Imagery Transmission Format (NITF) Standards (NITFS) analysis tool made available by NGA’s NITF Technical Board. Upon approved requests, JITC distributes CIVA to government programs to promote standards conformance during system development. CIVA does not provide a full conformance analyses given the contextual and dynamic nature of NITF products but provides users a suite of NITF analyses such as metadata parsing, field constraint analyses, field association analyses, and a variety of additional analysis tools.
REQUESTS:
If you are interested in receiving a copy of CIVA; please refer to the following link: JITC CIVA Tool Request
For questions on CIVA Contact: