Importing Level 2 M^3 Data into ISIS
I'd like to be able to look at the M3 Level 2 data. I downloaded an .IMG (M3G20090201T064933_V01_RFL.IMG) and .LBL (M3G20090201T064933_V01_L2.LBL) file. However, I have not been able to import them using either pds2isis or chan1m32isis (although the latter states that it's only applicable for Level 0 and Level 1B data).
When I try pds2isis, it states: I/O ERROR Unknown label type in [M3G20090201T064933_V01_L2.LBL]
When I try chan1m32isis, it states: USER ERROR Input file [M3G20090201T064933_V01_L2.LBL] does not appear to be a Chandrayaan 1 M3 detached PDS label. I/O ERROR Unknown label type in [M3G20090201T064933_V01_L2.LBL].
Is there any way to import this data into ISIS, or do I need to use ENVI?
#2 Updated by Catherine Neish 7 months ago
As an addendum, I should note that I'm not able to download the chan1 mission data. It points to another obsolete folder.
Thus, when I try to run the Level 1B data through chan1m32isis, it states: "I/O ERROR Unable to open [/Users/cneish/isis3/isis/../data/chandrayaan1/translations/m3Archive.trn]."
The folder is not even named chandrayaan1 anymore.
#3 Updated by Lynn Weller 7 months ago
- Assignee set to Lynn Weller
Unfortunately ISIS3 is not capable of handling the M3 L2B labels. I have even tried to run raw2isis on the data without success. As you already seem to know, ENVI can handle those files.
There is way a to do it, but it is not a streamlined process and involves editing/faking out labels and is not recommended. But if you are desperate to use this data in isis I will share. Keep in mind the spice currently available in isis is minimal (only JPL spacecraft position information is available, when asked for properly and there is no camera pointing information) therefore the geometry is not very good.
The person who is in a better position to help with your second issue (L1B data ingestion) is not available to help at the moment, but I'll take a stab at it. You may want to download the chandrayaan1 data area if you have not done so recently. According to what I see on our end, the latest public version of isis3 (isis3.5.1) houses the chandrayaan1 under $ISIS3DATA/chandrayaan1/, so the software is correct in looking in that location for translations files. If you have not updated your data area in the past year your data might reside under a directory called chan1/ or something similar and that could be the problem.
If you are up to date, something else is going on and it may take a day or two before the person who can help with this is available.
EDIT: I see our download documentation is incorrect in regard to the location of chandrayaan1 mission data. Sorry I missed this point in your second message.
Here is the correct data download information. You should probably remove the chan1/ data directory to avoid confusion.
rsync -azv --delete --partial isisdist.astrogeology.usgs.gov::isis3data/data/chandrayaan1 data/
#4 Updated by Catherine Neish 7 months ago
Thank you for providing the updated download information. It's downloading now, and I trust I will be able to import the Level 1B data into ISIS once that is complete. I'll let you know if I run into any other problems!
As for the Level 2 data, I am able to import them into ENVI, so I'll just stick with that software package.
Thanks for your help.
#5 Updated by Lynn Weller 7 months ago
- Status changed from Acknowledged to In Progress
Great! Thank you for letting us know how it went. I've created a new post to address the documentation problem.
Please let us know if you have problems or questions in regard to the L1B data once your data area is squared away and you move forward.
#8 Updated by Lynn Weller 7 months ago
I'm sorry, I did not mean for you to remove those kernels, but rather to have ISIS remove them from the system in general so as not to put out incorrect data to the public. But as my post indicated - they are not legitimate and should not be used in any case.
Currently, the only spice available for L1B data at this time are JPL spacecraft kernels that have to be called out specifically in your spiceinit command along with nadir camera pointing. The result may not be very useful depending on the image and when it was acquired during the mission. I don't have specifics for any particular image, but data acquired during optical period OP2B and OP2C are not likely to have good results because both star trackers were lost at this point and I think JPL had to do some magic to determine where the spacecraft was. Those optical periods run from May13 through Aug16, 2009.
Here is an example spiceinit run for accessing the JPL spacecraft kernels:
spiceinit from=M3G20090604T023806_V03_L1B_full.cub attach=true cksmithed=false ckrecon=false ckpredicted=false cknadir=true spksmithed=false spkrecon=true spkpredicted=false spk=/usgs/cpkgs/isis3/data/chandrayaan1/kernels/spk/CH-1-JPL-MERGED-23-MARCH-2010-1220.BSP
I am passing spiceinit the ingested cube containing all 85 bands (for the global files), after which individual bands may be extracted for further processing. I believe you should have the JPL spk in your chandrayaan1 data area, but if not, please let us know. If you run cam2map, I highly recommend pulling out only the bands you want to work with - projecting a cube with that many bands will produce a large output file and take a long time to process.
So to answer your question, yes, you can process L1B files in ISIS, but with less than optimal spice. Joe Boardman improved upon the JPL spk data, however I don't believe those data were released to the public by way of improved kernels. USGS (via a LASER proposal) started with Joe's improvements with the intent to globally control the L1B files and are in the process of working with collaborators to get L1B data (among other data products) released via a new pds archive that should be available sometime in 2018.