Level 2 Help for MARSRESCALE

Input image.  Can be any format (except complex).
The image data and the bulk of the label is taken from the image.

Output rescaled image.

By default, the output will have the same number of bands as the 
input, and all bands will be processed. If BAND is specified, 
the output will have a single band.

The input file band number to use.  By default, the output will 
have the same number of bands as the input, and all bands will 
be processed. If BAND is specified, the output will have a single 
band. If a non-existent band (e.g. 4th band for a 3-band image) 
is specified, the first band is processed.

Number of lines in the rescaled image.  Values for NL and NS 
parameters should be specified at the same time.  If values for 
NL and NS parameters are specified, value for ZOOM parameter is
ignored.

Number of samples in the rescaled image.  Values for NL and NS 
parameters should be specified at the same time.  If values for 
NL and NS parameters are specified, value for ZOOM parameter is
ignored.

Zoom factor for the rescaled image.  Creates in image bigger or
smaller than the input image.  If values for  NL and NS 
parameters are specified, value for ZOOM parameter is ignored.

Interpolation method to use.  Currently three interpolation methods 
are supported: nearest neighboor, bilinear and bicubic spline.  Bicubic 
spline method is default.

Corrected navigation filename.
If marsnav was run on the input images it created a table of corrected
pointing parameters. If you refer to this table using NAVTABLE it
will override the pointing parameters (e.g. azimuth and elevation) in the
picture labels, giving you a better registered mosaic.

A colon-separated list of directories in which to look for configuration
and calibration files.  Environment variables are allowed in the list
(and may themselves contain colon-separated lists).  The directories are
searched in order for each config/cal file when it is loaded.  This allows
multiple projectes to be supported simultaneously, and allows the user to
override any given config/cal file.  Note that the directory structure below
the directories specified in this path must match what the project expects.
For example, Mars 98 expects flat fields to be in a subdirectory named
"flat_fields" while Mars Pathfinder expects them to be directly in the
directory specified by the path (i.e. no intermediate subdirectories).

Specifies a mission-specific pointing method to use.  Normally this
parameter is not used, in which case the "default" pointing methods
are used.  Some missions may have special, or alternate, pointing
methods available, which are indicated by this string (for example,
backlash models, using arm joint angles instead of x/y/z/az/el, etc).
A substring search is used, so multiple methods (where that makes sense)
can be specified by separating the keywords with commas.

Note that nav files created using one pointing method will most likely
not be compatible with a mosaic created using a different pointing method.

Also used for general but uncommonly used parameters in the PIG library.

Disables all label-derived parameters to the Site mechanism which underlies
coordinate systems.  This forces all sites to be identical, with all rotations
and offsets set the same.  In the case of MPF or Mars 98, this disables
the lander quaternion and offset (sets them to identity and 0, respectively).
This option should not be used with images taken from different vantage
points (e.g. the spacecraft moved, or mixing a lander and a rover) or
invalid results will be obtained.  The use of this option invalidates the
Fixed coordinate frame; any values reported in the Fixed frame will not
correctly reflect the orientation of the lander/rover.

Obviously, this option should be rarely used; it is intended for when the
image labels defining the site are invalid or inconsistent.