Search the Community
Showing results for tags 'cat: georefeencing'.
I'll like to point I ve been processing some CRISM cubes, and have realized that the processing (particularly, projecting the cube) time is much longer in ENVI 5.6 in comparison to ENVI 5.0. For instance, an MSV took 10-12 mins to georeference in latest version, while it took 2-3 mins in the former. Can anyone from the developers team verify and tell why this is happening so?
Hi, I am getting a warning message after the georeferencing of CRISM data. It says that "MRO Custom datum D_Mars_2000_1AU_IAG_Custum_Sphere_lat00 not available. Projection may not match MTRDR. After georeferencing, when I check its details, it appears that DATAM is missing. Kindly help me to tackle this problem? Thanks,