importing MOC into GMT with grdraster

Hi. Has anyone successfully imported MOC images into GMT using grdraster? I have been working on this for over a week, and I (as well as several others helping me) have had no luck. Some issues:

1. Should the MOC images, processed with ISIS, be map projected or not? Altered with mocaspect?

2. What files are acceptable as input to grdraster? I found online that .bmp, .gif, .jpeg, .jpg, .tif, and .wbmp are raster images. I am only able to get my files into .tif, .raw, or .bmp files (ISIS2 dform and ISIS3 isis2std aren't working properly on the machines I use). I have not managed to get any of these data types into GMT (problems with -I (increment) and/or data type definitions in grdraster.info file).

3. Has anyone used the output of isis2ascii (ISIS3) --> xyz2grd (GMT) to do this? From the output I have generated, I think that the isis2ascii output is a grid of pixel values which need to have latitude and longitude values appended.

If anyone has any advice or ideas, I'd really appreciate the help- thanks!
~Kelly

some answers....

I've been working on this for awhile now, and I have some answers in case anybody else ever needs to do this.

1. YES the MOC images should be map projected. Don't worry about mocaspect; ISIS3 doesn't use this.

2. For GMT grdraster, I found that .raw files produced by ISIS3's isis2raw (16 bit signed/unsigned, MSB/LSB depending on OS) work as input for grdraster. ISIS3 programs such as camrange, catlab, and getkey can be used to determine latitude and longitude coverage and pixel resolution.

3. I did not end up using isis2ascii, but I was told how. Step 1: Run ISIS3 phocube to get latitude vs. pixel and longitude vs. pixel bands. Step 2: Run ISIS3 isis2ascii on the output cubs. Step 3: GMT xyztogrd (presumably after some manipulation/copy-paste of isis2ascii output files).

Other note:
Be sure to process MOC images with ISIS3. ISIS3 products are not compatible with ISIS2 programs/products and vice versa.

~Kelly