DATAMERGE

Name	Type	Caption	Length	Value range
MFILE *	String	Input file name, folder, or text file	1 - 192	See parameter description
DBIC	Integer	Input raster channel or channels	0 - 1024
FILO *	String	Output merged file name	1 - 192
FTYPE	String	Output file type	0 - 4	Default: PIX
FOPTIONS	String	Output file options	0 - 192
EXTENT	String	Output file extent	0 - 12	UNION\|INTERSECTION Default: UNION
NODATVAL	Float	NoData value of output file	0 - 1
RESAMPLE	String	Resampling method	0 - 5	See parameter description Default: NEAR

Parameter descriptions

MFILE

The name of a file, or a folder or text file that contains the data to process. If necessary, you can use a wildcard (*) in the string.

You can specify the value of the MFILE parameter by using any of the following:

A specific file name or folder path and file name. For example, "irvine.pix" or "C:\data\irvine.pix".
A specific file-name pattern or all of the files in a folder. For example, "C:\data\*.pix" or "C:\data".
An existing text file that contains references to multiple files with, optionally, different parameter settings per file. For example, "C:\list.txt".

If you specify a text file, the following general rules apply:

The file must have a .txt extension for the file containing multiple files and different parameter values.
List each set of parameters on its own line in the given order.
Specify string parameters in quotation marks.
Do not specify numeric parameters in quotation marks.
A quotation mark preceded by a backslash is used as part of the string. For example, ab\"c is used as: ab"c.
Precede comments in the file with an exclamation mark (!).
Use semicolons to delimit the parameters.
When you do not want to specify a value, leave the position between the semicolons empty (";;"). Alternatively, if there are no remaining parameters to specify at the end of a line, you can leave it blank.
Parameters in a text file may or may not be specified in the function:
- If a parameter is specified in the function and in the text file, the value in the text file is used.
- If a parameter is not specified in the text file, the parameter can be specified in the function.

The column structure of a text file you specify for DATAMERGE must be:

MFILE;DBIC

If the combination of parameters is invalid for an input file, a warning message displays, and no processing occurs. However, if the output file or its associated directory already exists, the processing is aborted.

DBIC

The channel or channels in the input file to process. If no value is specified for this parameter, DATAMERGE processes all channels in the source file.

This parameter may be overridden by an entry in a text file when one is specified for the MFILE parameter.

Ranges of channels or segments can be specified with negative values. For example, {1,-4,10} is internally expanded to {1,2,3,4,10}. When you are not specifying a range in this way, only 48 numbers can be specified explicitly.

FILO

The name of the output file to which to write the merged bands.

A file with the same name must not exist in the folder; otherwise, processing stops, and an error message is displayed.

FTYPE

The format of the output file. The format must be a GDB-recognized type.

Supported formats include, among others:

PIX: PCIDSK format (default)
TIF: Tagged Image File format
JP2: JPEG 2000 format

For a complete list of GDB-recognized file types, see GDB-supported file formats.

FOPTIONS

The file-creation options to apply on creating the output file. These are specific to the format of the file. In each case, the default of no options is allowed. You can specify the compression schemes, file-format subtypes, and other information.

Different options are available for each type, as described for the FTYPE parameter.

For a complete list of GDB-recognized file types, see GDB-supported file formats.

This parameter is optional.

EXTENT

The definition of the extents of the output file.

There are two options:

UNION: The extents of the output file are large enough to include all of the extents of the input file. No cropping of data occurs.
INTERSECTION: The extents of the output file are based on the region of overlap for all input files. Some cropping of data may occur.

NODATVAL

The pixel value to use as the NoData value in the output file.

All output pixels that do not have a value assigned by the merge process will be assigned a NoData value.

The NoData value must fall within the range of the output raster data type.

If no value is specified for this parameter, the NO_DATA_VALUE from the file or channel metadata is used, if it exists.

This parameter is optional.

The following table provides some use scenarios of how DATAMERGE processes the NODATVAL parameter.

When the value of NODATVAL is	And an input channel	Then
Specified	Has a NO_DATA_VALUE in either file or channel metadata	The value of the NODATVAL parameter, set at the file level, is used as the output NO_DATA_VALUE Pixels in the input channel that have the input NO_DATA_VALUE need to be changed to the new value from the NODATVAL parameter Pixels that are outside of the original image bounds in the output image should have their value set to the value of the NODATVAL parameter Pixels in the input image that have the same value as that of the NODATVAL parameter should have their value increased by `1` (or decreased by `1` if the value is at the high extent of the data range)
	Does not have a NO_DATA_VALUE in either file or channel metadata	The value of the NODATVAL parameter, set at the file level, is used as the output NO_DATA_VALUE Pixels that are outside of the original image bounds in the output image should have their value set to the value of the NODATVAL parameter Pixels in the input image that have the same value as that of the NODATVAL parameter should have their value increased by `1` (or decreased by `1` if the value is at the high extent of the data range)
	Has a NO_DATA_VALUE in both the file and channel metadata	The value of the NODATVAL parameter, set at the file level, is used as the output NO_DATA_VALUE Pixels in the input channel that have the input channel level NO_DATA_VALUE need to be changed to the new value of the NODATVAL parameter Pixels that are outside of the original image bounds in the output image should have their value set to the value of the NODATVAL parameter Pixels in the input image that have the same value as the NODATVAL parameter should have their value increased by `1` (or decreased by `1` if the value is at the high extent of the data range)
Not specified	Has a NO_DATA_VALUE in either the file or channel metadata	The input NO_DATA_VALUE, set at the channel level, is used as the output NO_DATA_VALUE No pixel value needs to be changed, they can be copied as is Pixels that are outside of the original image bounds in the output image should have their value set to the NO_DATA_VALUE
	Does not have a NO_DATA_VALUE in either the file or channel metadata	Do not set any NO_DATA_VALUE metadata No pixel values need to be changed, they can be copied as is Pixels that are outside of the original image bounds in the output image should have their value set to the lowest possible value in the data types range
	Has a NO_DATA_VALUE in both the file and channel metadata	The input channel level NO_DATA_VALUE, set at the channel level, is used as the output NO_DATA_VALUE No pixel value needs to be changed, they can be copied as is Pixels that are outside of the original image bounds in the output image should have their value set to the NO_DATA_VALUE

RESAMPLE

The resampling method to use to determine the output pixel values.

Supported values are:

NEAR: nearest neighbor. This is the default value.
BILIN: bilinear interpolation
CUBIC: cubic convolution

Examples

Merge image band files in DataMerge.txt into one PCIDSK file, called Merged.pix, the extents of which will be a union (UNION specified for EXTENT) of the extents of all of the input files.

DataMerge.txt contains four lines of band file names:

"C:\DEMO\po_123456_red.pix"
"C:\DEMO\po_123456_grn.pix"
"C:\DEMO\po_123456_blu.pix"
"C:\DEMO\po_123456_nir.pix"

EASI>MFILE="Demo/DataMerge.txt"
EASI>DBIC=
EASI>FILO="Demo/Merged.pix"
EASI>FTYPE=
EASI>FOPTIONS= 
EASI>EXTENT="UNION"
EASI>NODATVAL=
EASI>RESAMPLE=
EASI>r DATAMERGE

The output file channel listing look like following:

C:\Demo\Merged.pix
[S 4PIC 512P 512L]Day-Month-Year
1 [16U] ADS red(0.610-0.660 um)[po_123456_red.pix]
2 [16U] ADS green(0.535-0.585 um)[po_123456_grn.pix]
3 [16U] ADS blue(0.430-0.490 um)[po_123456_blue.pix]
4 [16U] ADS nir(0.835-0.885 um)[po_123456_nir.pix]

Merge image band files in DataMerge.txt into one PCIDSK file, called Merged2.pix, the extents of which will be an intersection (INTERSECTION specified for EXTENT) of the extents of all of the input files.

DataMerge.txt contains four lines of band file names:

"C:\DEMO\po_123456_red.pix;1"
"C:\DEMO\po_123456_grn.pix;2"
"C:\DEMO\po_123456_blu.pix;3"
"C:\DEMO\po_123456_nir.pix;1,2,3"

EASI>MFILE="DataMerge.txt"
EASI>DBIC=
EASI>FILO="Merged2.pix"
EASI>FTYPE=
EASI>FOPTIONS= 
EASI>EXTENT="INTESECTION"
EASI>NODATVAL=
EASI>RESAMPLE=
EASI>r DATAMERGE

The output file channel listing look like following:

C:\Demo\Merged2.pix
[S 6PIC 512P 512L]Day-Month-Year
1 [16U] ADS red(0.610-0.660 um)[po_123456_red.pix]
2 [16U] ADS green(0.535-0.585 um)[po_123456_grn.pix]
3 [16U] ADS blue(0.430-0.490 um)[po_123456_blue.pix]
4 [16U] ADS nir(0.835-0.885 um)[po_123456_nir.pix]
5 [16U] Filtered ADS nir(0.835-0.885 um)[po_123456_nir.pix]
6 [16U] Resample ADS nir(0.835-0.885 um)[po_123456_nir.pix]

Environments	PYTHON :: EASI
Quick links	Description :: Parameters :: Parameter descriptions :: Details :: Examples :: Related

DATAMERGE

Merge and recombine multiple bands into a single file

Description

Parameters

Parameter descriptions

Details

Examples