Thank you so much. I would like to ignore these pairs but as you can see, these messages show just in the terminal and I cannot find which pairs faced with this warning. Could you please help me to find them?
I think to save the terminal using the following command and then try to find the pairs with that warning message:
python stamps_export.py project.conf > save.txt
Sorry, I just would like to check everything is OK in my running steps. I determined two commands with a red rectangle in the following in âExport to Stampsâ step of the package. I think it is nothing but really appreciate if anybody also confirmed me:
Not sure where the red rectangle is. Can you point exactly your issue?
So sorry for my mistake in uploading! 
I edited the picture in my post.
In addition, I tried again with those pairs with the warning message about the Bperp and still face that messages. So, I decided to ignore and remove them because they are just 6 pairs.
Sorry again. I run the package and faced the following warning about the DEM file for the coregistration and interferogram generation:
I checked those files and didnât find them in the SNAP server. I checked and found that they are located on the sea. So, officially, there is not any DEM file in these locations. I checked the âelevationâ band in ifg files and found it in the correct style.
Do you also think it is OK?
yes. if the DEM in the product looks alright, you can neglect this warning.
Additionally, I would say that normally you should not get PS on the sea, so there will not be a wrong estimation.
So if you are looking for points on land, I would say that you can go ahead with the processing.
Do you agree?
yes, there are always some few points which are accidently identified as stable over water, but with a low threshold allowing for random pixels in an area (density_rand) and a low standard deviation during the weeding (weed_standard_dev) only a sparse occurence over water should remain.
Hello, Andy and mdelgado. It is so convenient to use python scripts to do all data preparation for stamps. I am new to SNAP. I followed the manual and your guidance here to process my Sentinel data. I used snap7.0 but still met the proplem that operator âSpectralDiversityOpâ: unknown element âuseSuppliedShiftsâ when I did corregistration. Could you please tell me what I should do to provide âspectraldiversityopâ?
we had discussed this error earlier
It is related to the ESD operator which is not needed when working with only one burst.
Thanks for your quick reply. My test area covers 3 bursts and I got the problem exactly as what Duan met before and they suggested us using SNAP6.0 or new version. I tried but still failed. Is there any other hint?
The problem indeed is that you were using SNAP 7. This latest version updated the tags employed on the parameters of the ESD Operator.
You should update those and the issue will be solved. I am planning to update it in a new release, but in the meanwhile I suggest you to follow the solutions posted in the forum, as suggested by @ABraun.
Let us know if you need further help.
I got it. Thank you so much!
This problem happens when your splitted master image name contains âIW1â. I think it was the case for you ?
===========For less details, users can skip this part=========
For me, whene i splitted the master i named it : /home/abdel/INSAR/XXX/S1/master/S1A_IW_SLC__1SDV_20180416T145733_20180416T145800_021494_025070_1812_IW1.dim
This what will happen, i just figure the cause now :
On the project.conf file you will have something like this :
##################################
PROCESSING PARAMETERS
IW1=IW1
MASTER=/home/abdel/INSAR/XXX/S1/master/S1A_IW_SLC__1SDV_20180416T145733_20180416T145800_021494_025070_1812_IW1.dim
##################################
When you run splitting_slaves.py project.conf, this part of code :
Getting configuration variables from inputfile
try:
in_file = open(inputfile, ârâ)
for line in in_file.readlines():
if âPROJECTFOLDERâ in line:
PROJECT = line.split(â=â)[1].strip()
print PROJECT
if âIW1â in line:
IW = line.split(â=â)[1].strip()
print IW
Will read project.conf line by line and check if this line contain IW1 !!
But we have two lines that contain âIW1â
In the end the variable IW value will contain : â/home/abdel/INSAR/XXX/S1/master/S1A_IW_SLC__1SDV_20180416T145733_20180416T145800_021494_025070_1812_IW1.dimâ
instead of âIW1â
This value will be passed to the graph slave_split_applyorbit.xml here :
<subswath>IWs</subswath>
By this line in splitting_slaves.py
filedata = filedata.replace(âIWsâ,IW)
And the graph that will be run for spliting the slaves splitgraph2run.xml will contain this line :
<subswath>/home/abdel/INSAR/XXX/S1/master/S1A_IW_SLC__1SDV_20180416T145733_20180416T145800_021494_025070_1812_IW1.dim</subswath>
instead of
<subswath>IW1</subswath>
Which is not accepted by the GPT and give you Error: [NodeId: TOPSAR-Split] -1
===========Solution==================
To to sum up :
Try to not use IW1 in the name of your splitted master (for the image file and project.conf)
Or change the parameter IW1âs name in project.conf to smothing like IWs and specially not IW because all sentinel-1 images contain this. And then change this also in splitting_slaves.py :
if âIWsâ in line:
IW = line.split(â=â)[1].strip()
print IW
yes, exactly. Only the line IW1=IW2 (determining the sub-swath) can contain âIW1â, otherwise the script gets confused. 
I think in the project.conf, âIW1=âŚâ was used instead of âIW=âŚâ just to avoid this confusing situation with any Sentinel-1 image that contains âIWâ in the beginning : S1A_IW_SLC_1SDV_....
So we should notice this.
Indeed it should be enough if in the next release I will change it in small letters iw1 instead of IW1.
Then the parser will not get confused anymore.
Does the next release include this point as mentioned in the package future works :
Because in the context of a study, i had to adapte your scripts to include STRIPMAP mode and i am working also on other improvements : files managements, logfilesâŚ
I can give a hand on this point if is not done yet !
@Abdel Stripmap data is quite easy, because it doesnât require Split, Deburst, ectâŚ
You can prepare them with three steps:
You are right we can do that without scripting it is quite simple.
But for me, i avoid using a single Stack for all image because itâs very slow compared to multiple Stacks of images paires. This loads the RAM maybe ?
Anyway this still easy with or without scripting compared to TOPS mode.
