Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Processing Multiple Slices of Sentinel-1 TOPS using ISCE #448

Open
hariiirs opened this issue Feb 23, 2022 · 19 comments
Open

Processing Multiple Slices of Sentinel-1 TOPS using ISCE #448

hariiirs opened this issue Feb 23, 2022 · 19 comments
Labels
question Further information is requested

Comments

@hariiirs
Copy link

hariiirs commented Feb 23, 2022

Hello Everyone,

My study area is lying over multiple sub-swaths and bursts, and multiple slices (stand-alone product) of Sentinel-1 (IW acquisiton mode) data.

Concern 1: I am able to process single slice of Sentinel-1 TOPS using ISCE processor, but dont know how to perform the Slice Assembly and Merging of sub-swath of Sentinel-1 products using ISCE processor.

Concern 2: Slice assembly and merging tools are available in SNAP. If I am performing these operations in SNAP, I dont know how to read the SNAP outputs in ISCE for further processing. This I am asking because my area is large and SNAP is slow compared to ISCE.

Can anybody help me for any one concern described above?

Many thanks
Hari Shankar

@bjmarfito
Copy link
Contributor

bjmarfito commented Feb 28, 2022

Hi @hariiirs,

  • Regarding your first concern, ISCE automatically implements slice assembly and merging of subswaths in Sentinel-1 using the topsApp.py and stackSentinel.py workflows. You just need to edit the topsApp.xml file for topsApp.py or just specify the needed parameter and argument for stackSentinel.py

  • Regarding your second concern, what is your purpose of further processing Snap outputs in ISCE? As far as I know, Snap and ISCE read specific file formats so ISCE cannot possibly read Snap output files. They are also end-to-end SAR data processors so for me there is no point as of now ingesting Snap outputs in ISCE for further processing.

@hariiirs
Copy link
Author

hariiirs commented Feb 28, 2022 via email

@bjmarfito
Copy link
Contributor

Hi @hariiirs,

Regarding the multiple scenes with the same dates, as far as I know, ISCE can resolve those multiple scenes with the same dates which covers the study area as long as the images have the same IPF numbers. You may need also to check if the images are on the same path/track (ascending or descending) as you may not be able to process them if they are on different path/track. I experienced this before where multiple scenes were imaged on the same day but they have different paths/tracks.

@hariiirs
Copy link
Author

hariiirs commented Mar 1, 2022 via email

@hariiirs
Copy link
Author

hariiirs commented Mar 8, 2022 via email

@bjmarfito
Copy link
Contributor

You're welcome @hariiirs. Pls close this issue. Thanks!

@hariiirs
Copy link
Author

hariiirs commented Mar 14, 2022 via email

@bjmarfito
Copy link
Contributor

Hi @hariiirs, kindly check if you miss running any previous steps before running run_5.

@hariiirs
Copy link
Author

hariiirs commented Mar 17, 2022 via email

@bjmarfito
Copy link
Contributor

Hi @hariiirs, could you post the stackSentinel.py command and arguments that you used here?

@hariiirs
Copy link
Author

hariiirs commented Mar 22, 2022 via email

@hardreddata
Copy link
Contributor

hardreddata commented Mar 22, 2022

Hi @hariiirs

It could be a bug in the --num-proc 4 which hasn't been merged.

See #271

The feedback from @yunjunz slipped past me. I will look to resolve this in the coming days. I would be happy to see anyone else take ownership of it.

You could fix this manually by ensuring the last lines of any of your run scripts contain wait, and the earlier lines end in &.

Or just run the one process.

Cheers.

@hariiirs
Copy link
Author

hariiirs commented Mar 22, 2022 via email

@hariiirs
Copy link
Author

hariiirs commented Apr 13, 2022 via email

@OliviaDdy
Copy link

my qq number is 790672784.Can we make a friend and chat with each other?

@hariiirs
Copy link
Author

hariiirs commented Apr 26, 2022 via email

@hardreddata
Copy link
Contributor

hardreddata commented Apr 26, 2022

@hariirs the multilook of 3 and 9 are associated with the different azimuth and range resolutions for Sentinel-1. The outcome of ISCE2 with these parameters is a roughly regular grid. Your choice of parameters will depend on your applications. If you choose 1 and 1 you will have more range than azimuth pixels.

See for example https://sentinel.esa.int/web/sentinel/technical-guides/sentinel-1-sar/products-algorithms/level-1/single-look-complex/interferometric-wide-swath for details.

@zff168
Copy link

zff168 commented Sep 28, 2022

@hariiirs How to use isce to merge data from two adjacent Sentinel-1s?

@rtburns-jpl rtburns-jpl added the question Further information is requested label Nov 1, 2022
@ZGHHGZ
Copy link

ZGHHGZ commented Aug 13, 2023

@bjmarfito
Hello, what should I do to handle a single burst for stackSentinel.py ?
#756

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

7 participants