I am new using the PolSARpro, I am trying to import an image ALOS PALSAR lvl 1.1 downloaded from https://vertex.daac.asf.alaska.edu/, and I get a notice “DON’T FORGET TO EXTRACT DATA BEFORE RUNNING ANY DATA PROCESS”, and the import is canceled. The same thing happened to someone, does anyone know how to solve this problem?
This is not an error… just a reminder. You have imported now, so please proceed extracting the data before running any data process
when I imported the ALOS,the T3 matrix’s range is very low ,is it correct?
It would be easier to answer if you gave some example what you mean by low.
Did you apply complex calibration before matrix generation?
Sorry to interrupt again,when I imported the ALOS data,it is impossible to do complex calibration unless the S2 matrix was generated.However,the S2 matrix’s calibration does not have outputs.So how to apply complex calibration before matrix generation?which tool should I use ?Thank you for your help.
I did not use SNAP ,I used the polsarpro as the tool
sorry, I always get confused in these sub topics.
I’ll try with PolSARpro as well. But for now it works:
Have you already extracted your data correctly after import?
I think I have extracted the S2 matrix successfully
I choose the third calibration method after that ,but the output directory does not have S2 matrix after calibration.
can you make an RGB of the S2 matrix (menu > display > create RGB file > sinclair) to test if it conains data?
Do you get an error message during calibration?
I did not get error messages during calibration. I think it might not be possible to calibrate.
Here’s my solution,and I am not sure it is correct.I did not apply calibration ,and apply the polarimetric decomposition directly,and generate the db format at the same time.
After the procedures,the range becomes from 0 to 255,then I covered it to the tiff format,the false color composition is more clearly .But I am not sure whether the calibration can have a big effect on the decomposition result.
unless you want to do follow multi-temporal approach, complex calibration might not be necessary
okay,thank you for your help.
Would like to report an issue while importing PALSAR CEOS L1.1, where PolSARPro says each time: ‘There is not confing file’ in attempts to convert S2 to T3, or C3! I found, that Num-Rows and Num-Cols must be below the initial size…AND must be reduced in each consequential import… strange???
have you successfully extracted the data before conversion from S2 to T3?
After extraction, there should be a folder with bin data generated from the L1.1 product
An example is given here: Calibration in PolSARpro problem