ISIS Application Documentation
mapmos | Printer Friendly View | TOC | Home |
Create a mosaic using map projected cubes
Overview | Parameters |
DescriptionThis program allows the user to create a mosaic using a map projected cube (Level2). A mosaic can be created from an initial cube or the input cube can be placed in a pre-existing mosaic. REQUIREMENT: The input cube must be map projected (Level2). The input cube is required to be projected to the EXACT SAME ProjectionName, PixelResolution (or MapScale), EquatorialRadius, PolarRadius, LatitudeType, LongitudeDirection, as well as specific map projection keywords (e.g., CenterLatitude, CenterLongitude). If these map projection requirements are not met, an error will be encountered. Note: The latitude and longitude range of the individual input cubes may vary.If a new mosaic is to be created, it must be initalized with an input cube and CREATE=YES. The default size of the output mosaic will be the SAME latitude and longitude extents of the input file. The size of the output mosaic can be entered by the user through any or all four boundary parameters: MINLAT, MAXLAT, MINLON, MAXLON. The input cube also establishes the number of bands and BandBin Group of the output mosaic. If there is a list of input cubes to mosaic together, refer to the similar application called automos. Integrity-check Parameters: MATCHBANDBIN = TRUE, the default is to require all the bandbin group and wavelength keywords of the input cube files exactly match the output mosaic. MATCHDEM = FALSE, the default does not check the SHAPEMODEL keyword of the input cube files and does not propagate what DEM Shapemodel was used when the input files were projected. The PRIORITY parameter will determine how each input cube is combined with the current output mosaic cube. The process involves replacing an output mosaic pixel (or not) with an input pixel at the same location. There are many user options and criteria that influence the pixel replacement. Use of the PRIORITY parameter with and without other options is explained in the tables and descriptions 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. This cube will have the same base-name as the mosaic cube, but will end in "_tracking.cub". The tracking cube must always reside in the same directory as the mosaic cube to be properly accessed; this means that if the mosaic cube is copied or moved, then its associated tracking cube must be copied or moved to the same location. 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 mapmos 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 with Priority options ONTOP and BENEATH for single band input cubes. It works for multiband cubes for PRIORITY=ONTOP only when the NULL, HIGHSATURATION and LOWSATURATION options are set to true. It also works for multiband cubes when PRIORITY=BAND. Furthermore, this feature is NOT supported when PRIORITY=AVERAGE. 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. 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.
Refer to automos for additional information and examples. CategoriesRelated Applications to Previous Versions of ISISThis program replaces the following application existing in previous versions of ISIS:
Related Objects and DocumentsApplicationsHistory
|
Parameter GroupsFiles
Band Priority
Initialization
Options
|
This cube will be placed in the mosaic. It must have the same ProjectionName, PixelResolution, EquatorialRadius, PolarRadius, LatitudeType, and LongitudeDirection as the mosaic. The projection specific keywords, such as CenterLatitude and CenterLongitude, must match as well.
Type | cube |
---|---|
File Mode | input |
Filter | *.cub |
The output mosaic cube which will have the input cube placed in it. If the selected cube does not already exist as a mosaic, the CREATE option must be selected and it will be created. In this case the latitude and longitude range parameters must be entered.
Type | cube |
---|---|
File Mode | output |
Filter | *.cub |
This parameter determines how the pixels from the input cube will be placed in the mosaic.
Type | string | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Default | ONTOP | |||||||||||||||
Option List: |
|
This option allows you to select the method to specify the band to use for the pixel comparison.
Type | string | |||||||||
---|---|---|---|---|---|---|---|---|---|---|
Default | BANDNUMBER | |||||||||
Option List: |
|
This is the number of the band to use for the pixel comparison.
Type | integer |
---|---|
Default | 1 |
This is the keyword string. The entered keyword name must match the name in the BandBin group in the image labels.
Type | string |
---|---|
Default | OriginalBand |
This value must match the value associated with the KEYNAME parameter.
Type | string |
---|---|
Default | 1 |
Select which type of comparison to do on the pixels. You can choose whether the lesser or greater of the two pixels will be placed on top of the mosaic.
Type | string | |||||||||
---|---|---|---|---|---|---|---|---|---|---|
Default | LESSER | |||||||||
Option List: |
|
Select this parameter if the mosaic does not already exist.
Type | boolean |
---|---|
Default | NO |
Inclusions |
|
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 mapmos 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 parameter specifies the minimum latitude of the mosaic.
Type | double |
---|---|
Internal Default | Use Map Value |
Minimum | -90.0 (inclusive) |
This parameter specifies the maximum latitude of the mosaic.
Type | double |
---|---|
Internal Default | Use Map Value |
Maximum | 90.0 (inclusive) |
Greater Than | MINLAT |
This parameter specifies the minimum longitude of the mosaic.
Type | double |
---|---|
Internal Default | Use Map Value |
This parameter specifies the maximum longitude of the mosaic.
Type | double |
---|---|
Internal Default | Use Map Value |
Greater Than | MINLON |
This option causes the application to fail if the input BandBin Group keywords do not match the mosaic BandBin Group.
Type | boolean |
---|---|
Default | TRUE |
This option causes the application to fail if the input DEM shapemodel file does not match the filename value in the output mosaic ShapeModel.
Type | boolean |
---|---|
Default | FALSE |
This option causes an input High Saturation special pixel value (both Instrument and Representation) to replace the output mosaic pixel regardless of the priority set or the original value of the mosaic pixel.
Type | boolean |
---|---|
Default | FALSE |
This option causes input NULL pixel values to replace the output mosaic pixel regardless of the priority set or the original value of the mosaic pixel.
Type | boolean |
---|---|
Default | FALSE |
This option causes NULL values in the input image to be automatically copied to the mosaic regardless of the priority.
Type | boolean |
---|---|
Default | FALSE |