I have encountered an error for one pair (as of the moment) during the coregistration and interferogram formation using snap2stamps. Please see images below. This is the first time I encounter such error and I want to ask what could be the problem and how to resolve it.
The good thing is the other pairs (60 in total) are still in progress. I thought the processing will terminate after this error but it didn’t. I just want to ask also if it’s ok to delete this pair from the folders (coreg and ifg) if the error can’t be solved.
Please check if you can load the zip file of this product into SNAP. Maybe the download was incomplete.
The next script will take all products which are inside the split folder, so if you delete this one in there (as it was probably created but not finished) it will be skipped.
I was able to load the zip file of that specific product into SNAP. I was able to open all the bands (i, q, intensity) specifically. I got the same error for another pair as of writing.
You mean it is better to delete these products that got error in the split folder?
I have downloaded again the S1B images which got the same error during the coreg and ifg formation process. As of writing, I am redoing everything again using snap2stamps. I got 4 pairs with the same error after completing the first run, and I am afraid that excluding these pairs in the analysis would result to bad output. These are consecutive scenes paired with a common master and removing them would leave a 36-day gap.
Fortunately, the first pair I had the error and reported here has been solved. So I believe @ABraun is correct about the cause of the error. I will report what happens to the other pairs after completing the second attempt.
No. I am only using a single master I have selected using the InSAR Stack Tool in SNAP. What I mean is like this: the single master (20171011) paired with consecutive scenes (20161203, 20161215, 20161227, 20170108). These were the 4 pairs I got the same input/output error.
Removing these products would leave a 36-day gap which is I think not good for slow-moving landslide analysis.
Regards.
Testing the program I have got the following error:
WARNING: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: RangeShiftOp: Cross-correlation failed for all bursts, set range shift to 0
Since my AOI is in 1 subswath only, I used the ‘python splitting_slaves.py project.conf’ command to split all downloaded images (slaves and master). This is to make sure that split images are well matched. After this, I usually remove the master image from the ‘slaves’ and ‘split’ folders and move it to the ‘master’ folder.
I tried to interchange LON MIN and LON MAX but I did get the same error.
