== **OSSIM Command Line Interface**

Provides access to many high-level functions available in OSSIM and associated plugins.

Usages: 
    ossim-cli <command> [command options and parameters]  \\
    ossim-cli --spec <command-spec-file>\\
    ossim-cli --version\\
    ossim-cli help <command> -- To get help on specific command.

Available commands:

  atp -- Provides automatic tiepoint generation functionality. This tool uses JSON format to communicate requests and results.\\
  bandmerge -- Merges multiple band files into a single RGB image.\\
  dem -- Provides DEM generation functionality. This tool uses JSON format to communicate requests and results.\\
  hillshade -- Computes shaded representation of input elevation surface with specified lighting parameters.\\
  hlz -- Computes bitmap of helicopter landing zones given ROI and DEM.\\
  info -- Dumps metadata information about input image and OSSIM in general.\\
  ortho -- Utility for orthorectifying and reprojecting image data.\\
  pointcloud -- Utility class for generating point-cloud-derived image products.\\
  potrace -- Computes vector representation of input raster image.\\
  remap -- Performs remap to 8-bit including optional histogram stretch and saves the corresponding external geometry file.\\
  shoreline -- Computes bitmap of water versus land areas in an input image.\\
  slope -- Utility for computing the slope at each elevation post and generating a corresponding slope image.\\
  subimage -- Tool for extracting a sub-image from a full image. No reprojection is done. Presently, the subimage geometry is represented by an RPC replacement model until generic models can support subimage chipping.\\
  vertices -- Utility for determining the active image corner vertices inside larger null-filled image rectangle.\\
  viewshed -- Computes bitmap image representing the viewshed from specified location using only DEM information.

ossim-cli provides a "tool" plugin design that enables high-level functionality to be included via plugin libraries. The plugin will need to register the tool (i.e., the class executing the functionality) with the tool registry.