|
FME Format Type Identifier |
NITF |
|
Reader/Writer |
Both |
|
Typical File Extensions |
.ntf, .nsf |
The National Imagery Transmission Format (NITF) standard is composed of an image accompanied by subimages, symbols, labels, text, and other information that relates to the image. One of the main features of the NITF is that it allows several items of each data type to be included in one file, yet any data types may be omitted.
NITF Product and System Requirements
|
Format |
Product |
Operating System |
||||
|---|---|---|---|---|---|---|
|
Reader/Writer |
FME Desktop License |
FME Server |
FME Cloud |
Windows |
Linux |
Mac |
|
Reader |
Available in all FME editions |
Yes |
Yes |
64-bit: Yes |
Yes |
Yes |
|
Writer |
Available in all FME editions |
Yes |
Yes |
64-bit: Yes |
Yes |
Yes |
- More about FME Licenses and Subscriptions.
- More about FME Desktop Editions and Licenses.
Reader Overview
The NITF Reader supports reading of several subtypes of NITF image files, including NITF 1.1, NITF 2.0 and NITF 2.1/NSIF 1.0 files with uncompressed or VQ compressed images.
Color tables for pseudocolored images are read. In some cases, Nodata values may be identified. Lat/Long extents are read from the IGEOLO information in the image header if available. Other coordinate systems (such as MGRS) are ignored at this time.
FME considers a single NITF file to be a dataset. The NITF file contains pixel data, and each pixel in the file is a point in a single FME raster feature.
Writer Overview
The NITF Writer supports writing georeferenced and non-georeferenced files with classified or continuous data. Files are always written in the uncompressed NITF 2.1 format.
GCPs (ground control points) present along with a projection in an NITF file being read can either be applied to the data as an affine transformation, or stored as properties on the raster geometry. GCPs cannot be written to NITF.
FME considers a dataset to be a folder name. The names of the NITF output files written to the output dataset folder are determined from the fme_raster_filename attribute or from the FME feature type. The destination folder does not have to exist before the translation occurs. Any existing files in the folder which have the same name are overwritten with the new feature data.
The NITF writer distinguishes duplicate output files by appending numbers to the filenames.
Note: At this time, writing georeferenced NITF files can be done only using Latitude/Longitude and Universal Transverse Mercator (UTM) projections with the WGS-1984 datum. If the source data does not contain information satisfying these criteria, FME will automatically try to reproject the data before writing the file. If this reprojection fails or if the source data is not georeferenced, the destination file will not be georeferenced.
FME Raster Features
FME raster features represent raster data and use several concepts that are unlike those used in the handling of vector data. The topics below describe how FME processes raster data.
NITF supports rasters with up to nine bands, provided all bands are the same data type. When this data type is UInt8, any number of bands may have a palette.