When I use the raw data as SLC.xml for the Doppler range terrain correction (TC), it works good.
But when I calibrate first and filter it, then I use it as the input for TC in python, it says that the input is not a SAR product!
The output I get from either a calibrated SAR data filtered (e.g., Lee) is in SNAP standard format (.dim) and another folder containing also .hdr. I have tested both, but it didnt accept it as a SAR format in SNAP python. I wanna take care of calibration first, filter it, then apply TC.
I do appreciate if sb. could advise me about the input format required (after calibration or filtering) for TC.
I think this is not only python related. It is more S1TBX specific.
@lveci Is there something special necessary?
Most SAR specific operators are looking for values in the Abstracted Metadata to determine if the product is a SAR product. It might be that in your processing that metadata was lost.
Can you take the result of your calibration and speckle filtering from python and open it in the SNAP Desktop. Then try running the terrain correction from there and see if you get the same error. If you do, check the metadata of that product and see if it has an Abstracted Metadata.
Thanks a lot for your comments. You’re absolutely right. It doesnt work even by SNAP when I receive the “calibration obtained from the following code” as an input for the TC. The metadata is almost empty which I don’t know why it’s going that way! As you see below, my input to create the cal. is SLC.xml.
Another issue I have with the following code is that it saves the output automatically in a folder called “target” . How can I define it by myself in the code?
gpt Calibration -Ssource=‘target.dim’ -PsourceBands=‘Intensity_HH’
rem gpt Calibration -Ssource='20150720_134626_HH_SLC*product.xml’* -PsourceBands=‘Intensity_HH’
I really appreciate if you could help me out with it.
Add the -t option and specify the target file as you like.
gpt -h to get more help.