# writers.nitf

The NITF format is a US Department of Defense format for the transmission of imagery. It supports various formats inside a generic wrapper.

Note

LAS inside of NITF is widely supported by software that uses NITF for point cloud storage, and LAZ is supported by some softwares. No other content type beyond those two is widely supported as of January of 2016.

Default Embedded Stage

This stage is enabled by default

Streamable Stage

This stage supports streaming operations

## Example

Example One

    [
        {
            "type":"readers.las",
            "filename":"inputfile.las"
        },
        {
            "type":"writers.nitf",
            "compression":"laszip",
            "idatim":"20160102220000",
            "forward":"all",
            "acftb":"SENSOR_ID:LIDAR,SENSOR_ID_TYPE:LILN",
            "filename":"outputfile.ntf"
        }
    ]

Example Two

    [
        {
            "type":"readers.las",
            "filename":"inputfile.las"
        },
        {
            "type":"writers.nitf",
            "compression":"laszip",
            "idatim":"20160102220000",
            "forward":"all",
            "acftb":"SENSOR_ID:LIDAR,SENSOR_ID_TYPE:LILN",
            "aimidb":"ACQUISITION_DATE:20160102235900",
            "filename":"outputfile.ntf"
        }
    ]

## Options

filename

  NITF file to write. The writer will accept a filename containing a single placeholder character (‘#’). If input to the writer consists of multiple PointViews, each will be written to a separate file, where the placeholder will be replaced with an incrementing integer. If no placeholder is found, all PointViews provided to the writer are aggregated into a single file for output. Multiple PointViews are usually the result of using filters.splitter, filters.chipper or filters.divider.

clevel

  File complexity level (2 characters) [Default: 03]

stype

  Standard type (4 characters) [Default: BF01]

ostaid

  Originating station ID (10 characters) [Default: PDAL]

ftitle

  File title (80 characters) [Default: <spaces>]

fsclas

  File security classification (‘T’, ‘S’, ‘C’, ‘R’ or ‘U’) [Default: U]

oname

  Originator name (24 characters) [Default: <spaces>]

ophone

  Originator phone (18 characters) [Default: <spaces>]

fsctlh

  File control and handling (2 characters) [Default: <spaces>]

fsclsy

  File classification system (2 characters) [Default: <spaces>]

idatim

  Image date and time (format: ‘CCYYMMDDhhmmss’). Required. [Default: AIMIDB.ACQUISITION_DATE if set or <spaces>]

iid2

  Image identifier 2 (80 characters) [Default: <spaces>]

fscltx

  File classification text (43 characters) [Default: <spaces>]

aimidb

  Comma separated list of name/value pairs to complete the AIMIDB (Additional Image ID) TRE record (format name:value). Required: ACQUISITION_DATE, will default to IDATIM value. [Default: NITF defaults]

acftb

  Comma separated list of name/value pairs to complete the ACFTB (Aircraft Information) TRE record (format name:value). Required: SENSOR_ID, SENSOR_ID_TYPE [Default: NITF defaults]

where

  An expression that limits points passed to a writer. Points that don’t pass the expression skip the stage but are available to subsequent stages in a pipeline. [Default: no filtering]

where_merge

  A strategy for merging points skipped by a ‘where’ option when running in standard mode. If `true`, the skipped points are added to the first point view returned by the skipped filter. If `false`, skipped points are placed in their own point view. If `auto`, skipped points are merged into the returned point view provided that only one point view is returned and it has the same point count as it did when the writer was run. [Default: `auto`]