ASTER 1A data in HDF format comes with sensor information that allows ENVI to open the dataset with RPCs (rational polynomial coefficients) that can be used to orthorectify the data. I would say that typically a radiometric calibration is performed first and then orthorectification. To process 1A data, I would do the following:
- open the 1A dataset as EOS->ASTER. The 4 separate datasets (VNIR + 3b, SWIR, TIR) should open and the map coordinates should show "RPC Geographic Lat/Lon'
- first run Radiometric Calibration since you need to extract information from the HDF to perform the calibration. You can calibrate all datasets here. The TIR bands can be calibrated to TOA radiance. VNIR and SWIR can be calibrated to TOA radiance or reflectance. The processed datasets will retain the RPCs.
- use RPC Orthorectification workflow to orthorectify the datasets to a standard map projection. You can include GCPs here to improve the RPC model. If some of the datasets do not align after orthorectification, you can use the Image registration workflow to perform an image-to-image registration.
- Atmospheric correction for VNIR and SWIR can be accomplished through our ACM Module (FLAASH and Quac), or by included methods such as empirical line calibration, flat field, IARR, dark subtraction, log residuals. ENVI has the Thermal Atmospheric Correction tool for thermal datasets. Then the emissivity tools can be used to convert to temperature. These are all located under the Radiometric Calibration tools in ENVI 5.2.
There are no tools specific to removing striping from ASTER data. If you are referring to the stagger issue in ASTER TIR bands, it looks to be compensated for with preprocessing performed as ERSDAC:
http://www.science.aster.ersdac.jspac...
This description states there is a correction applied and that it is good to +/-4 pixels, so you may still see offsets.