-
|
Is it possible to run stackSentinel.py without the use of a -b flag? It is not listed as a Required Parameter in the topsStack readme file, however stackSentinel.py fails without it. I am looking to run a stack of SLC files where I process the whole extent, as opposed to a bounding box subset thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 8 replies
-
|
It should have been listed as required. In practice as you saw, it is required anyways. The reason for that is the fact that frames of Sentinel-1 are not fixed on ground. Therefore best practice is that user should know what area they want to process. The stack processor will still check all the SLCs and will provide some info on what common region exists. Keep in mind, because of the coverage issue, you may always download data for a bounding box larger than the bounding box you give to stackSentinel for processing (around 0.25 degrees larger to be safe), so that you will get the coverage that you want. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the reply - this makes sense. Even when choosing a bounding box that covers all of the SLC files (using the provided common region) I often get errors about there being a different number of bursts in images, this appears on any step that attempts to merge (merge_ref_sec, merge_burst_igram). Do you happen to know why I might be seeing this error?
|
Beta Was this translation helpful? Give feedback.
-
|
Hello @hfattahi , I would like to know if there is a way to subset SLCs generated by stackSentinel.py to a smaller size. I know that every SLC will eventually contain at least two bursts, but my study area is too small, and I hope to further narrow the area before the StaMPS processing. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your answer, I should say that I want to run mintpy after ISCE. Do It work for isce 2 mintpy process? |
Beta Was this translation helpful? Give feedback.
-
|
As far as I know mintpy only accepts unwrapped phase. So the -W parameter of stackSentinel needs to be set to "interferogram". This will take a long time in the phase unwrapping step of stackSentinel, and I haven't found an efficient way to handle it yet. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, it takes a long time. thanks a lot, dear Yuluenter. just one more question, Did you work with TSX before? |
Beta Was this translation helpful? Give feedback.
-
|
Perhaps a script could be written specifically for cropping interferograms. And run this script before the last step of phase unwrapping. Actually, "run_SLCcropStack.csh" just calls some tools of GDAL, which is not too complicated. |
Beta Was this translation helpful? Give feedback.
-
|
you're right thanks a lot. |
Beta Was this translation helpful? Give feedback.
It should have been listed as required. In practice as you saw, it is required anyways. The reason for that is the fact that frames of Sentinel-1 are not fixed on ground. Therefore best practice is that user should know what area they want to process. The stack processor will still check all the SLCs and will provide some info on what common region exists. Keep in mind, because of the coverage issue, you may always download data for a bounding box larger than the bounding box you give to stackSentinel for processing (around 0.25 degrees larger to be safe), so that you will get the coverage that you want.