ISIS Application Documentation
isisexport | Standard View | TOC | Home |
Convert from ISIS cube to another format
Description
Categories
Groups
History
NOTE: This program and the associated template files are incomplete. The documentation describes what the eventual intended capabilities are. Many capabiliteis are not implemented at this time.
Exports an ISIS cube file to an external, non-ISIS, format. The intended output formats include PDS4, PDS3, and FITS compatible label and image files. The contents of the label file are generated using a template file. The template file name is generated automatically from the ISIS cube label information. If the template can not be found, the user must specify its name using the TEMPLATE parameter.
The image file is generated from the input ISIS cube specified by the FROM parameter. The output image file will be a copy of the input ISIS cube with the image data stored in Band Sequential format.
This application uses the Inja templating engine to render the template file. The input data from the cube and extra data sources is converted to JSON and then it is accessed via the Inja templating syntax. See the Inja documentation for the full template syntax. The data from the label of the input cube is accessible under "MainLabel", the data from the originally ingested PVL or XML label stored on the input cube is accessible under "OriginalLabel", and the extra data is accessible under "ExtraPvl", "ExtraXml", and "ExtraJson".
Name | Description |
---|---|
FROM | Input cube |
TEMPLATE | Input template |
TO | Output label file name |
Name | Description |
---|---|
DATA | Output JSON data |
EXTRAPVL | Extra PVL data |
EXTRAXML | Extra XML data |
EXTRAJSON | Extra JSON data |
This is the input cube that will be exported.
Type | cube |
---|---|
File Mode | input |
Filter | *.cub |
The file name of the input template. This file contains "inja" compatible template syntax. The data used to replace the template elements comes from the ISIS cube label, the original label (PDS3, FITS, PDS4), and user specified input PVL, XML, or JSON files.
Type | filename |
---|---|
File Mode | input |
Internal Default | None |
The output file name of the exported label. The output image name will be derived from this parameter by removing the last extension and adding an appropriate file extension.
Type | filename |
---|---|
File Mode | output |
The output file name to store the template data source. This is a dump of the JSON data used by the template engine to fill in the template elements. It is a combination of the ISIS main cube lable, the original lable, and any other data sources supplied. The purpose of this parameter is for debugging the templates.
Type | filename |
---|---|
File Mode | output |
Internal Default | None |
The PVL data contained in the file(s) specified by this parameter will be added to the template data source under ExtraPvl. If multiple PVL files are specified, then they will be merged together.
Type | filename |
---|---|
File Mode | input |
Internal Default | None |
The XML data contained in the file(s) specified by this parameter will be added to the template data source under ExtraXml. If multiple XML files are specified, then they will be merged together.
The elements inside this file must be surrounded by a single XML element.
Type | filename |
---|---|
File Mode | input |
Internal Default | None |
The JSON data contained in the file(s) specified by this parameter will be added to the template data source under ExtraJson. If multiple JSON files are specified, then they will be merged together.
Type | filename |
---|---|
File Mode | input |
Internal Default | None |
Stuart Sides | 2021-01-03 | Original version |