Jump to content
PDS Geosciences Node Community

Dealing with CRISM band bands dataset


Sehaj
 Share

Recommended Posts

Hello CRISM Team!

I have been using CRISM data for around 2 years and I appreciate the team for providing useful workshops and TRR-V3 data. I am wondering no new workshops have came up for using CRISM data.

Recently, I have processed MSP and HSP images (TRDR) of Hellas Planitia region. In HSP dataset, I am getting a lot of bad bands. Though ATP and PHT corrections ignore some bad bands, but after applying these corrections, hsp0002d9a3 is getting worse (Display 2 in screenshot) as there might be more bad bands. Projecting the cube and applying destriping (Display 3 in screenshot) gives unusual results.

Similar issues are being faced while processing some other files.

Do, I need to spectrally subset good bands individually from each of the files? I am afraid there are lot of bands and many files, so this would be a a bit difficult job.

Or else, can I safely ignore this data and try with different observations.

Thanks in anticipation!

- Sehajpal Singh (Doctoral candidate at IIT Bombay)

bad_band_data.jpg

Link to comment
Share on other sites

Sehajpal: Destriping must be done on the sensor space data. That way each column is from one spectral detector set and destriping takes advantage of this simple arrangement. Did you try destriping after projection? You state: "Projecting the cube and applying destriping (Display 3 in screenshot) gives unusual results." If so, that is likely your problem.

Ray Arvidson

Link to comment
Share on other sites

Thanks for your quick response. No, I destriped before going for projecting.

Please let me correct that after atmospheric and photometric correction, am applying destriping, followed by projection (As the processed filename suggests: hsp..._corr_destripe_p.img) . I am afraid if HSP data has some problem, because I did not face any issues while processing MSP dataset.

However, I keep on getting the following error while projecting with respective ddr files. Although, the final image is projected and shows coordinates when we move cursor across it.

Can you tell what is the problem?

projection_error.png

Link to comment
Share on other sites

Hi Sehaj,

The header error is because the customized map projection engine data for CAT is not set up correctly in your computer. You can following the instruction document (custom_pedata_instructions.docx) in CAT_ENVI\aux_files\pe_user_defined folder to set up correctly. Please let me know if you still have a problem. BTW what ENVI version are you using? I saw you use ENVI classic. Is it possible for you to upgrade ENVI to 5+ version and use the standard interface?

 

Thanks,

 

Feng

 

Link to comment
Share on other sites

Thanks Feng. I am using ENVI 5.6 (IDL 8.8).  I have been using ENVI classic for processing via CAT toolkit and performing other geoprocessing operations in standard version. 

Link to comment
Share on other sites

Hey Feng,

I did follow your instructions but couldn't solve it. I uninstalled and reinstalled envi and CAT toolkit.

Now, I have messed up some other things and am not able to georeference the cube, which earlier was working great.

Please help in solving the following error.

err1.png

err2.png

Link to comment
Share on other sites

Hi Sehaj,

 

Thanks for you update. I will help you to fix these problems. To better assist you, can we go to a zoom meeting to fix these problems? You can send me (feng.zhou@wustl.edu) an email with your available time slots so that I can send you a zoom link.

 

BTW, would you please try the standard interface of ENVI 5.6? It has a lots of new features than classic.

 

Thanks,

 

Feng

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...