Question #5357

Mini-RF Bistatic

Added by Josh Cahill about 1 year ago. Updated about 1 year ago.

In Progress
Jean Backer
Target version:
Software Version:
Test Reviewer:
Tammy Becker


ISIS software folk,

The new LRO Mini-RF bistatic strips have lat/lon back planes in the DDRs that can be read into ENVI. I would like to use them to make maptemplates to apply to the data strips to mosaic it them in ISIS. I've initially attempted to do this manually from the label and the maptemplate function, but the projection seems to be off either by my fault or some other. Is there a method or function in ISIS to just load the lat/lon back planes which I've already made ISIS .cub files of and add there information to the mapping info of the data strip less tediously?

Thanks for your time,


#1 Updated by Josh Cahill about 1 year ago

  • Tracker changed from Bug to Question

Sorry, this should actually be listed as a question.

#2 Updated by Tammy Becker about 1 year ago

  • Status changed from New to Acknowledged

Hi Josh,

I'm hoping I understand the issue...

Are the bistatic strips already map projected? If so, there is the application called 'maplab'. This will require an accurate input map template that defines the target body, map projection and known center latitude, longitude, and map scale. The application 'maptemplate' should guide you through most of this. Along with the map template, maplab will need you to assign a sample, line coordinate with a lat, lon (you might be able to retrieve this by recording the values from the back planes)...I think most commonly you assign the center of the upper left corner pixel (0.5, 0.5) to the appropriate lat, lon (coordinates=latlon parameter), if you know the xy coordinate, this is an alternative option to LatLon. maplab should then compute the x,y translations from this information and update your input strip with a mapping group.

If your strips are not in a map projected format, you could try the application called 'nocam2map'. It takes as input, the image cube along with a latitude and longitude cube. It will need the same type of map template to define the output map projection.

You probably remember the mosaic requirements...the projection parameters and scale have to be exactly the same.

Let me know if this helps or not...

#3 Updated by Josh Cahill about 1 year ago

  • Test Reviewer set to Tammy Becker

Hey, So that helped quite a bit. But, it is still a little off. Could I send some data your way, you go through the process with one strip and then discuss with you?

Ran into Laz and Jean. So, Jean is cc'd or the code reviewer here now. These are just notes.

raw2isis from=$dd to=$dd.cub samples=$s lines=$l bands=6 bittype=real
raw2isis from=$s1 to=$s1.cub samples=$s lines=$l bittype=real

rotate from=$dd.cub to=$dd-90r.cub degrees=-90 interp=bilinear
rotate from=$s1.cub to=$s1-90r.cub degrees=-90 interp=bilinear


nocam2map fore each product. Or I suppose I could use map2map after the first nocam2map.

I'll send you an e-mail for the data...


#4 Updated by Tammy Becker about 1 year ago

  • Assignee set to Jean Backer

Follow-up note. Do not rotate the image before running nocam2map. With the lat/lon backplanes available, whether or not the input image is projected, nocam2map should map project ok (it would be similar to a map2map type function if the input is projected). Setting the nocam2map linc/sinc to 1 might also be helpful.

#5 Updated by Tammy Becker about 1 year ago

  • Status changed from Acknowledged to In Progress

Also available in: Atom PDF