ISIS3 cubes and PDS4 Cart

Fortunately, ISIS3+ is an application that maintains a map projection section for derived/orthorectified data. That just means a user can automate the translation from the ISIS map projection definition to a PDS4 label (with a CART section). But to be able to archive ISIS3+ cubes, there are still a couple of issues users should be aware of.

1. ISIS cubes are by default stored using tiles (not a raw stream). To force an ISIS cube to be PDS4 compliant (at any ISIS application run one can add this to the output file "+BandSequential"). For example:

> anyISISprog from=input_tiled.cub to=out_non-tiled_pds4.cub+BandSequential

more specifically, the generic cubeatt can be run as a last step also.

> cubeatt from=Ceres.DEM8ppd.cub to=Ceres_DEM8ppd_PDS4.cub+BandSequential

2. You could now use GDAL to create a label only (next to the archivable cube). This is a reminder that GDAL really wants a good input template (by default the very minimal built-in template will be used data/pds4_template.xml)

> gdal_translate -of PDS4 -co CREATE_LABEL_ONLY=YES Ceres_DEM8ppd_PDS4.cub Ceres_DEM8ppd_PDS4.xml

-- again a minimal output use case, the label will need edits or a template used during the run.

3. Lastly, ISIS3 does have some PDS4 support (using outdated 1.B.0.0, information model! which is no longer recommended), especially for CART but it could get someone started.

> isis2pds pdsversion=pds4 from=Ceres.DEM8ppd.cub to=Ceres_DEM8ppd_pds4.img

-- This will convert the cube to a raw "*.img" with an outdated 1.B.0.0 PDS4 XML label.

more: https://gdal.org/drivers/raster/pds4.html