I have installed ISIS3 to my Mac lab computer and downloaded the LRO data sets, kernels excluded. I am trying to convert MRF S Band IMG and LBL data to an isis cube format but I always get this error I/O ERROR Unable to read [DATA_SET_ID] from input file [sband_12n333_cpr.img].
I am still new to using ISIS3 but I was wondering if there is anything I am missing?
Cheers,
[migrated from GIT issue at: https://github.com/USGS-Astrogeology/ISIS3/issues/3235]
These PDS files, as found at the GeoScience Node, linked here, are derived data products (map projected) which means they have already been processed and are ready for analysis. The ISIS3 program mrf2isis is geared toward Lunar Reconnaissance Orbiter Mini-RF LRO level 1 or level 2 data. Which I would think are “raw” or simply “calibrated” almost straight from the instrument (not map projected or ready for science). ISIS3’s main job is to help take “raw” data and make them science-ready. Since they are already processed, to read into ISIS3, simply try pds2isis
$ pds2isis from=sband_12n333_cpr.lbl to=sband_12n333_cpr.cub setnullrange=YES nullmin=0 nullmax=0
Also the *.lbl (with the *.img) should also simple open in most mapping applications like ArcMap, QGIS, etc. and they are ready for file format conversion using GDAL.
$gdal_translate -a_nodata 0 sband_12n333_cpr.lbl sband_12n333_cpr.tif
Why I am setting nodata/null definitions during conversion? That is because these label do not use the “standard” NoDATA PDS value for 32bit data (which is -3.4028226550889044521e+38). Instead they use 0.0, but the label doesn’t define it. This label should have a “MISSING_CONSTANT” parameter defined as 0.0.
If you are using ArcMap (or ArcGIS Pro), then you will want to use ArcCatalog to define NoData as 0.0 on the *.lbl file. Then it can also more easily stretch the file.
Lastly, in the datainfo text file (below), it states this data is “NASA Level 2” or “PDS Level 5”. So, I’m not 100% sure what “NASA Level 2” is…? But, I am more comfortable with calling this derived and map projected file, PDS Level 5. The whole “level” system means so many different things across applications we should drop it.
The data products in the DATA directory correspond to NASA Level 2, or PDS
Level 5 Derived Data. According to the PDS Standards Reference, these are
“derived results, as maps, reports, graphics, etc.” Each image has an
accompanying detached PDS label.The data set consists of 5 image files for each region mapped during a
typical 29-minute radar integration period. The images are named as follows:
XXXXXX_SCP.IMG (same-sense circular polarization map), XXXXXX_OCP.IMG
(opposite-sense circular polarization map), XXXXXX_ANG.IMG (map of beam
angle in radians), XXXXXX_INC.IMG (map of incidence angle in radians), and
XXXXXX_CPR.IMG (circular polarization ratio image), where XXXXXX is the
center latitude and longitude of the radar pointing target over the
observation period.
How can I get the Lunar Elevation BaseMap?
and what’s the map projection of Lunar Elevation BaseMap?
I want to know the map projection of this ArcGIS demo because I have some trouble about display LRO Mini-RF MAPCDR data on ArcGIS.
It looks to me like this error is coming from running:
mrf2isis from=sband_12n333_cpr.img to=sband_12n333_cpr.cub
rather than
mrf2isis from=sband_12n333_cpr.lbl to=sband_12n333_cpr.cub
Typically in ISIS, the label file is used for the from value.
Looking at the image name from the error message, sband_12n333_cpr.img, is this a LRO Mini-RF image, or an image taken at Arecibo?
[[Puts on PDS hat]]
I’m pretty sure that all MiniRF image products in the PDS start with “L” or “l” except for MOSDDRs, which start with “GLOBAL_”.
This is true even for the bistatic products (where Arecibo is the source).
Perhaps the user renamed the file or is working with data from a non PDS source? Hard to tell without being able to look at the file or know where they got it.
ISIS cannot process map projected Mini-RF data(such as MAPCDR).
You can try Mini-RF CDR data.