
vbandcomb(1)                 Khoros                  vbandcomb(1)

PROGRAM
     vbandcomb - Combine all bands from m images into one multi-
     band image

SYNTAX
     vbandcomb

     -o             output image filename

     [-base]        input basename

     [-i1]          input image filename

     [-i2]          input image filename

     [-i3]          input image filename

     [-i4]          input image filename

     [-i5]          input image filename

     [-i6]          input image filename

     [-i7]          input image filename

     [-i8]          input image filename

     [-i9]          input image filename

     [-i10]         input image filename

     [-m]           map option :
                    0 (ignore maps),
                    1 (map data through map),
                    or 2 (transfer maps)
                       [default = 0]

     [-c]           color space model:
                    0 (None),
                    1 (ntscRGB),
                    2 (ntscCMY),
                    3 (ntscYIQ),
                    4 (HSV),
                    5 (HLS),
                    6 (IHS),
                    7 (cieRGB),
                    8 (cieXYZ),
                    9 (cieUVW),
                    10 (cieucsUVW),
                    11 (cieucsSOW),
                    12 (cieucsLab),
                    13 (cieucsLuv),
                    14 (GENERIC),
                    or 15 (genericRGB)
                       [default = 0]

     [-V]           Gives the version for vbandcomb

     [-U]           Gives the usage for vbandcomb

     [-P]           Prompts for command line options

     [-A [file1]]   Creates the answer file called vbandcomb.ans
                    or file1

     [-a [file1]]   Uses vbandcomb.ans or file1 as the answer
                    file

DESCRIPTION
     vbandcomb combines all bands from m images (in separate
     files) into one image that contains all data bands.  An
     image may contain more than one band, or may be a single
     band image.  Note that ALL input images MUST be of the same
     dimensions.  However, the input images may be of different
     data storage types.

     Note that all input image arguments are optional.  This is
     to allow greater flexibility in terms of various combina-
     tions of input images.  That is, images may be specified
     explicitly by filename (ie. -i1 file1  -i2 file2 ...), or by
     using a basename (ie. -base images/feature ).  The input
     image arguments may be used together or separately to
     achieve the desired combination of input images.  Note that
     in any case, there MUST be at least TWO input images, for
     vbandcomb to work.

     The order that the files are combined in the resulting mul-
     tiband image follows the input entries on the form.  That
     is, the files found by "basename" are used prior to the
     files listed explicitly.  This is the order that the bands
     are in the resulting output image.

     If the -base (basename) option is used, then all images with
     the specified basename in the directory will be used as
     input to vbandcomb. If only a directory path is specified as
     the basename, then ALL files in that directory will be used
     as input to vbandcomb.  If all files in a directory are
     desired, then the restriction of having all files in that
     directory be of the same dimension, applies.  In addition,
     if any file in the specified directory is not a viff image,
     then an error message will indicate which file could not be
     read and the program will terminate.

     The input images may be of the same or different data types.
     If the input images are of different data types, then all
     input images will be upcast to the highest input image data
     type.  The output image data type will be the same as that
     of the highest data type of the input images.

     Each input image may be either a single band or multiband
     image with a map scheme of NONE, ONEPERBAND, or SHARED.  The
     options for this program include, map option, and color
     space model.

     The map options (-m) include,

     0  - ignore maps

     1  - map data through the maps

     2  - transfer map information

     If the -m option is set to 0, then the maps are ignored.
     That is, only the data from the input images are combined
     into a single multiband image.  The resulting map scheme
     will be NONE.

     If the -m option is set to 1, then the the data is mapped
     through the bands before combining the bands. If the map
     scheme for an input image is set to NONE, then that image is
     not mapped (ie. it has already been mapped).  The resulting
     map scheme will be NONE.

     If the -m option is set to 2, then the maps are transferred
     to the resulting multiband output image.  If the map scheme
     for an input image is set to NONE, then a linear map is gen-
     erated for that image.  Input images with map schemes of
     ONEPERBAND and SHARED will have their maps transferred to
     the new multiband image.  Note that if the maps are of dif-
     ferent sizes, then the smaller maps will be expanded to the
     size of the largest map from all the input images.  The
     resulting map scheme will be set to ONEPERBAND.

     The concatenation will be to tack the second image band to
     the bottom of the first image, and the third image band to
     the bottom of the second image band, etc.

     If the color space model -c option is set to something other
     than NONE and the resulting image does not contain 3 bands,
     the color space model passed in will be overridden and set
     to NONE.

     It is the users responsibility to ensure that all input
     images are of the same dimensions, and that the various com-
     binations of map options are valid for the particular appli-
     cation.

REQUIRED ARGUMENTS
     -o     type: outfile
            desc: output image filename

OPTIONAL ARGUMENTS
     -base  type: string
            desc: input basename
            default: null

     -i1    type: infile
            desc: input image filename

     -i2    type: infile
            desc: input image filename

     -i3    type: infile
            desc: input image filename

     -i4    type: infile
            desc: input image filename

     -i5    type: infile
            desc: input image filename

     -i6    type: infile
            desc: input image filename

     -i7    type: infile
            desc: input image filename

     -i8    type: infile
            desc: input image filename

     -i9    type: infile
            desc: input image filename

     -i10   type: infile
            desc: input image filename

     -m     type: integer
            desc: map option
            allowed values:
            0 (ignore maps),
            1 (map data through map),
            or 2 (transfer maps)

     -c     type: integer
            desc: color space model
            allowed values:
            0 (None),
            1 (ntscRGB),
            2 (ntscCMY),
            3 (ntscYIQ),
            4 (HSV),
            5 (HLS),
            6 (IHS),
            7 (cieRGB),
            8 (cieXYZ),
            9 (cieUVW),
            10 (cieucsUVW),
            11 (cieucsSOW),
            12 (cieucsLab),
            13 (cieucsLuv),
            14 (GENERIC),
            or 15 (genericRGB)

EXAMPLES
     vbandcomb -i1 red.xv -i2 green.xv -i3 blue.xv -o rgb.xv -c
     15

     combines 3 bands (red.xv  green.xv  blue.xv) into one image,
     resulting in a 3 band genericRGB image.

     vbandcomb -base feature -i1 red.xv -i2 green.xv -i3 blue.xv
     -o spectral.xv

     combines ALL images matching the basename "feature" in the
     current directory with the 3 images (red.xv  green.xv
     blue.xv) into one image, resulting in a multi-band image.

     vbandcomb -i1 image1.xv -i2 image2.xv -o newimage.xv -m 1

     combines the single band image "image1.xv" containing a 3
     column map with the single band image "image2.xv" containing
     no map into one image with 4 bands.  The single band image
     "image1.xv" was expanded to a 3 band image, corresponding to
     the 3 column map.  That is, "image1.xv" was mapped through
     the maps before being combined with the single band image
     "image2.xv".

SEE ALSO
     intro(1), verror(3), vgparms(3), vutils(3), lvbandcomb(3)
     intro(1), verror(3), vgparms(3), vutils(3), lvbandcomb(3),
     lvcast(3)

RESTRICTIONS
     vbandcomb will only map data if the input files have a data
     storage type of BYTE.

COPYRIGHT
     Copyright 1991, University of New Mexico.  All rights
     reserved.

Khoros                    Release: 1.0                          1

