the dim file I changed was the coregistration pair’s to generate. According to the scripts, it will be generated in the tempcoreg folder.
Did you check the link above which explain how the coregistetion pairs were generate with example?(the process is a little difficult to explain without an example). Here the link is:
@ABraun@Linya-Peng@dongyusen
maybe the problem is because in the xml file there is no ESD operator, when I open it on snap nothing is written?
I ask to better understand the process
i using snap 8.0 and python 2.7 and i have the error mentioned above. i tried your advice but i have the same error, ihave the same coordinates in THE CLIP AOI and i change the AOI LONG E LAT MORE EXTENDED.
I don’t belive that is the problem of python version @ABraun
Simply a combination of both dates. Once these are added, I updated the baseline in the config file and ran both scripts again, sbas_topsar_coreg and sbas_topsar_ifg. Or is this too much to manually add connections?
But you should pay attention to time baselines in sbas_topsar_ifg, you may have to change them to longer according to the maximum time difference of the interferogram pairs you add. If you don’t change, it could be that the interferogram pair you added will not be processed in sbas_topsar_ifg.
Hi ABraun!
May I ask which SNAP version and python version did you use to run the script? I still couldn’t form ifg after successfully finishing coregistration, only coreg pairs of supermaster and slave could form ifg successfully. I don’t know whether it is a version problem or I did something wrong
the error during the interferogram computation is caused by the Land Sea Mask operator which tries to download SRTM 3Sec data as well. Updating SNAP and deleting incomplete zip files should help, otherwise you can remove the Land Sea Mask operator from the XML (sbas_topsar_1iw-seamask.xml, “Read” should directly feed into “Inteferogram”)