Uploading Global Cubes to OLAF
To start, make sure you've converted the cubes to BandSequential. Use the USGS ISIS program cubeatt (i.e. cube attributes). Search this page for "BandSequential" or "cubeatt" for instructions.
After that you'll need to make the "product_info.csv" for these cubes. You'll use productInfoOLAF-isis-global.sh along with a config.txt file. Note that all the values in this example are for a Q=512 ICQ, while the assessment products (albedo, best map, maxres, numimg, sigma) are all 1 degree bins. Config.txt looks something like this...
OBJECT="Saturn IX (Phoebe)" OUTNAME=Phoebe OUTID=_c AUTHLIST="Weirich, J.R." OBSSYSBOOK="ISIS-WAC; ISIS-NAC" TARGETNAME="Phoebe" TARGETTYPE=Satellite STARTTIME="N/A" STOPTIME="N/A" REFKEY="N/A" VER=v1 SAMPLES=2222 # This will stay the same for all Q=512 models LINES=1111 # This will stay the same for all Q=512 models VERTPXSCALE=300 # This will be different for each body, to calculate use SQRT(4*Pi*Radius^2/1579014) where Radius is in meters. HOZPXSCALE=300 # Same as for VERTPXSCALE
Choose "2D Array Image", and then follow the instructions.
Uploading Regional Cubes to OLAF
Similar to uploading global cubes, but the label creation follows a slightly different path. For regional photocubes the "product_info.csv" is generated using a shell script with a name something like productInfoOLAF-isis-unprojected-photocubes.sh along with a config.txt file. Same thing for the topocubes, but since the labels are different we use productInfoOLAF-isis-unprojected-topocubes.sh. For both shell scripts, config.txt looks something like this...
OBJECT=Mercury BIGMAP=NF2ED1 OUTNAME=nafn358706425 OUTID=_c AUTHLIST="Weirich, J.R.; Palmer, E.E." OBSSYSBOOK="MDIS-WAC; MDIS-NAC" TARGETNAME="Mercury" TARGETTYPE=Planet STARTTIME="N/A" STOPTIME="N/A" REFKEY="N/A" VER=v1 SAMPLES=1335 LINES=1335 VERTPXSCALE=60 HOZPXSCALE=60 WEST=63.07554 EAST=65.42407 SOUTH=34.92059 NORTH=36.80719 SPHNAME=Mercury AAXIS=2439700 BAXIS=2439700 CAXIS=2439700 LOCALDESC="This file is simple in a local reference frame and thus not in a map projection. Within cart:local_georeference_information we provide the needed vectors such that a transformation could be applied to this file." GEOINFO=""Vector" is the radius vector that extends from the center of the object to the middle vertex of the DTM. It is in Cartesian space with the first number being in the direction of x, the second number the direction of y, and the third number the direction of z. 0 West Longitude defines the positive x-axis, while north pole is the positive z-axis. 270 West Longitude defines the positive y-axis. The plane of the DTM is determined by the local slope. This plane of the DTM is defined by two horizontal unit vectors (i.e. Ux and Uy) and a vertical unit vector (i.e. Uz). Each of these unit vectors are defined in the same Cartesian space as the radius vector, where again the first number is in the direction of x, the second number the direction of y, and the third number the direction of z. # Vector 857.78729248046875 1778.3778076171875 1427.5522460937500 # Ux 0.24726431071758270 0.51332724094390869 -0.82180017232894897 # Uy -0.90092843770980835 0.43396770954132080 0.0000000000000000 # Uz 0.35663473606109619 0.74038314819335938 0.56977581977844238 "
Choose "2D Array Image", and then follow the instructions.
Uploading geoTiffs to OLAF
Add LIDs using "External Products" under "Add Data Products". Add a LID such as "urn:nasa:pds:lunar_lro_lroc_topography_domingue_2022:data:ings358416181_topo_noslope_masked" and then upload the the tif and xml files. I think you will still need to add the files to the bundle after Jesse sends you the zip/folder. You should also add the instrument info to the label since GDAL won't add that. This instrument info will have to be added to OLAF manually by the PDS, but if you are using OLAF they will have done this for the bundle, so you will be able to copy if from other labels generated by OLAF.
<Investigation_Area> // This should already be added by the current procedures, which utilize a python script.
<name>MESSENGER</name> // This should already be added by the current procedures, which utilize a python script.
<type>Mission</type> // This should already be added by the current procedures, which utilize a python script.
<Internal_Reference> // This should already be added by the current procedures, which utilize a python script.
<lid_reference>urn:nasa:pds:context:investigation:mission.messenger</lid_reference> // This should already be added by the current procedures, which utilize a python script.
<reference_type>data_to_investigation</reference_type> // This should already be added by the current procedures, which utilize a python script.
</Internal_Reference> // This should already be added by the current procedures, which utilize a python script.
</Investigation_Area> // This should already be added by the current procedures, which utilize a python script.
<Observing_System>
<Observing_System_Component>
<name>MESSENGER</name>
<type>Host</type>
<Internal_Reference>
<lid_reference>urn:nasa:pds:context:instrument_host:spacecraft.mess</lid_reference>
<reference_type>is_instrument_host</reference_type>
</Internal_Reference>
</Observing_System_Component>
<Observing_System_Component>
<name>MERCURY DUAL IMAGING SYSTEM NARROW ANGLE CAMERA</name>
<type>Instrument</type>
<Internal_Reference>
<lid_reference>urn:nasa:pds:context:instrument:mdis-nac.mess</lid_reference>
<reference_type>is_instrument</reference_type>
</Internal_Reference>
</Observing_System_Component>
</Observing_System>
<Observing_System>
<Observing_System_Component>
<name>MESSENGER</name>
<type>Host</type>
<Internal_Reference>
<lid_reference>urn:nasa:pds:context:instrument_host:spacecraft.mess</lid_reference>
<reference_type>is_instrument_host</reference_type>
</Internal_Reference>
</Observing_System_Component>
<Observing_System_Component>
<name>MERCURY DUAL IMAGING SYSTEM WIDE ANGLE CAMERA</name>
<type>Instrument</type>
<Internal_Reference>
<lid_reference>urn:nasa:pds:context:instrument:mdis-wac.mess</lid_reference>
<reference_type>is_instrument</reference_type>
</Internal_Reference>
</Observing_System_Component>
</Observing_System>
<Target_Identification> // This should already be added by the current procedures, which utilize a python script.
<name>Mercury</name> // This should already be added by the current procedures, which utilize a python script.
<type>Planet</type> // This should already be added by the current procedures, which utilize a python script.
<Internal_Reference> // This should already be added by the current procedures, which utilize a python script.