ISIS Application Documentation
ringsautomos | Printer Friendly View | TOC | Home |
Create a mosaic using a list of map projected cubes
Overview | Parameters |
DescriptionThis program uses a text-based list of cubes, all in the same map projection and equivalent projection parameters (PixelResolution, CenterRingLongitude, etc), to generate a mosaic. By default, The program automatically determines the size of the mosaic by examining each cube. The user also has the option of entering their own ring radius and ring longitude range to use for the mosaic. There are four different ways/priorities (ONTOP, BENEATH, BAND and AVERAGE) for how the input image can be placed on the mosaic. In case of special pixels and the special pixel flags being enabled, the details for each priority is described in the tables below. The TRACK feature creates a separate tracking cube in addition to the mosaic cube, and contains information for the source files of every pixel within the output mosaic. The tracking cube will have the same base-name as the mosaic cube, but will end in "_tracking.cub", and must always reside in the same directory as the mosaic cube to be properly accessed. The tracking cube will always be of type unsigned integer. Depending on the bit-type of the mosaic cube and/or the number of bands it contains, the tracking cube may be as much as four times the size of the mosaic cube itself. The tracking cube can be used appropriately through the QVIEW-AdvancedTracking tool. As the user pans across the displayed mosaic, for every mosaic pixel location, QVIEW-AdvancedTracking will interactively report the index, the filename and the serial number of the input cube that was input to ringsautomos for that specific pixel location. Since the tracking cube is of bit-type unsigned integer, the DN values of 0, 1 and 2 are reserved for NULL, LRS and LIS, respectively, so valid pixel DN values will begin at an offset of 3. In other words, a pixel of DN value 3 in the tracking cube means that this same pixel within the mosaic was taken from the first input image. The tracking cube cannot be used outside of the QVIEW-AdvancedTracking tool except as a visual representation of the source cubes for the different pixels. The TRACK feature works differently depending on the Priority options and whether you are using single- or multi-band cubes:
Please Note: Prior to ISIS version 3.6.0, tracking for the various mosaicking apllications was being handled with an internal tracking band. Tracking is now being handled by an external tracking cube that contains the associated tracking information. This application can no longer add to mosaics of the old format. In order to continue to use these older mosaics with the updated mosaicking applications, you must first use the trackextract utility application to extract the tracking band and the associated tracking information into an external tracking cube. Tracking can be set at the time of Mosaic creation only and cannot be turned on after the mosaic is created. For multiband mosaics, if PRIORITY=ONTOP and all the Special Pixel flags are not set to true, or if PRIORITY=BENEATH, tracking will be turned off even if it was turned on while creating the mosaic. ONTOP priority places all the valid input pixels onto the mosaic unless the special pixel flags are turned on or if the mosaic has a NULL pixel. In a multi band scenario, a pixel origin within a particular line and sample will not be the same in all the different bands. WARNING: If Tracking is turned on in a mosaic, any subsequent applications that modify DN values will corrupt the Tracking cube. Priority BAND can track the origin for multiband input cubes. The input cube pixels will be placed in the output mosaic based on the "Lesser" or "Greater" criteria of a priority band defined by the user. Band can be implemented with the TYPE, BANDNUMBER or KEYWORD options.
Multiband input example with BAND priority and example parameters:
Expected Result:
Given this same example with CRITERIA=LESSER than:
MATCHBANDIN, if set, requires the specified input bands to match the mosaic bands and the bands can be anywhere in the mosaic but must be contiguous for multi-band. If MATCHBANDIN is not set then any input image can be placed on the mosaic within its boundaries. HIGHSATURATION, LOWSATURATION and NULL options, if set, will cause the the input pixels with these values to be copied to the mosaic for ONTOP and BAND priorities regardless of the CRITERIA for the BAND priority. These options are not supported for BENEATH priority. Currently Tracking can be viewed in the Advanced Tool Tracking option of the qview application. Following are the Tracking info: Index: Zero based and is in the order in which the image was placed on the mosaic. No origin is represented as -1. FileName: File name of input image Serial Number: Serial Number of the input image The following table describes how the program will determine the pixel value in the output mosaic for areas of image overlap.
Each of the following priority option tables indicates the resulting output pixel for a particular input pixel, given the selected special pixel options (parameters HIGHSATURATION for HRS, HIS; LOWSATURATION for LRS, LIS; and NULL) in each table row.
CategoriesHistory
|
Parameter GroupsFiles
Band Priority
Ground Range
Options
|
A list of map projected cubes to mosaic. The Mapping groups must match in order to mosaic the cubes.
Type | filename |
---|---|
File Mode | input |
Filter | *.txt *.lis *.lst |
The mosaic cube which will have the input cube placed into it.
Type | cube |
---|---|
File Mode | output |
Filter | *.cub |
This optional output list contains the names of all images that were added onto the mosaic.
Type | filename |
---|---|
File Mode | output |
Internal Default | None |
Filter | *.lis |
This parameter is used to select one of four ways to mosaic the pixels in areas of overlap.
Type | string | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Default | ONTOP | |||||||||||||||
Option List: |
|
The pixels in this band will be used for comparison between input image and the mosaic for a decision to be made in copying image into the mosaic.
Type | string | |||||||||
---|---|---|---|---|---|---|---|---|---|---|
Default | BANDNUMBER | |||||||||
Option List: |
|
The band number should match that in the "OriginalBand" of "BandBin" Group
Type | integer |
---|---|
Default | 1 |
The entered key name must match the key name in the "BandBin"
Type | string |
---|---|
Default | OriginalBand |
This value must match the value associated with the key name entered in the KEYNAME
Type | string |
---|---|
Default | 1 |
This parameter is used to select one of two ways to mosaic the pixels in areas of overlap when doing by band comparison.
Type | string | |||||||||
---|---|---|---|---|---|---|---|---|---|---|
Default | LESSER | |||||||||
Option List: |
|
The ground range can either be calculated automatically or entered by the user. If the USER option is selected, values must be entered for the MINRINGRAD, MAXRINGRAD, MINRINGLON, and MAXRINGLON parameters. AUTO is the default for this parameter.
Type | string | |||||||||
---|---|---|---|---|---|---|---|---|---|---|
Default | AUTO | |||||||||
Option List: |
|
The minimum ring radius value to use in the mosaic.
Type | double |
---|
The maximum ring radius value to use in the mosaic.
Type | double |
---|
The minimum ring longitude value to use in the mosaic.
Type | double |
---|
The maximum ring longitude value to use in the mosaic.
Type | double |
---|
The Track feature creates a separate tracking cube containing the index values for the source of every pixel in the output mosaic. The tracking cube can only be used appropriately through the QVIEW-AdvancedTracking tool. As the user pans across the displayed mosaic, for every mosaic pixel location QVIEW-AdvancedTracking will interactively report the filename, the serial number and the index of the input cube that was input to ringsautomos for that specific pixel location. The tracking cube cannot be used outside the QVIEW-AdvancedTracking tool except as a visual representation of the source cubes for the different pixels. TRACK must be set to TRUE at the time of mosaic creation only and cannot be turned on after the mosaic is created. When a mosaic is created with TRACK=TRUE, all subsequent runs will default to TRACK=TRUE. When a mosaic is created with TRACK=FALSE, an error will be encountered if subsequent runs have TRACK=TRUE. The tracking cube will always be of type unsigned integer. Depending on the bit-type of the mosaic cube and/or the number of bands it contains, the tracking cube may be as much as four times the size of the mosaic cube itself.
WARNING: If Tracking is turned on in a mosaic, any subsequent applications that modify DN values, such as the applicationreduce, will corrupt the DN values in the tracking cube.
Type | boolean |
---|---|
Default | FALSE |
This option causes the application to fail if the input bandbin group does not match the mosaic bandbin group.
Type | boolean |
---|---|
Default | TRUE |
This option causes the application to fail if the input DEM shapemodel does not match the mosaic's' shapemodel.
Type | boolean |
---|---|
Default | FALSE |
This option causes High Saturation values (both Instrument and Representation) in the input image to be automatically copied to the mosaic irrespective of the priority
Type | boolean |
---|---|
Default | FALSE |
This option causes Low Saturation values (both Instrument and Representation) in the input image to be automatically copied to the mosaic irrespective of the priority
Type | boolean |
---|---|
Default | FALSE |
This option causes NULL values in the input image to be automatically copied to the mosaic irrespective of the priority
Type | boolean |
---|---|
Default | FALSE |