Processing Multiple Slices of Sentinel-1 TOPS using ISCE

[hariiirs]

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]

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]

Thank you very much @ Baryan Marfito

Concern 1: Actually I am confused because part of multiple scenes of same dates are covering the study area. The downloaded data is in .zip file (Sentinel-1), so will it take all scenes in account for assembly and merging? If it is, then its good for me. I will process it day after tomorrow and will come back to you if any further concern is there.

Concern 2: This I wan thinking if assembly and merging is not possible in ISCE then these steps can be first performed in SNAp and then output can be process in ISCE which will serve my purpose. Not more than that.

Thank you once again.

With regards

Hari Shankar

On Mon, 28 Feb 2022 at 17:13, Bryan Marfito @.***> wrote:

Hi @hariiirs https://github.com/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.

— Reply to this email directly, view it on GitHub https://github.com/isce-framework/isce2/issues/448#issuecomment-1054171964, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKDZGJIIOS7CZ27NVUUFUK3U5NNU3ANCNFSM5PDP2UBA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you were mentioned.Message ID: @.***>

-- HS

[bjmarfito]

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]

Ok, i will check it tomorrow. Thank you very much for help.

With regards Hari Shankar

On Tue, 1 Mar 2022, 07:29 Bryan Marfito, @.***> wrote:

Hi @hariiirs https://github.com/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.

— Reply to this email directly, view it on GitHub https://github.com/isce-framework/isce2/issues/448#issuecomment-1054900745, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKDZGJJVLIL5I3J4S2GKLBTU5V2WVANCNFSM5PDP2UBA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you were mentioned.Message ID: @.***>

[hariiirs]

Thank you Mr. Bryan Marfito

This is to inform you that I am successful in processing multi-slice, multi-subswath and multi-burst SAR dataset in ISCE using stackSentinel.py. Thank you very much once again. I will come back to you in future for any other problem related to ISCE and InSAR processing.

With regards Hari Shankar

On Tue, 1 Mar 2022 at 09:19, Hari Shankar @.***> wrote:

Ok, i will check it tomorrow. Thank you very much for help.

With regards Hari Shankar

On Tue, 1 Mar 2022, 07:29 Bryan Marfito, @.***> wrote:

Hi @hariiirs https://github.com/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.

— Reply to this email directly, view it on GitHub https://github.com/isce-framework/isce2/issues/448#issuecomment-1054900745, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKDZGJJVLIL5I3J4S2GKLBTU5V2WVANCNFSM5PDP2UBA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you were mentioned.Message ID: @.***>

-- HS

[bjmarfito]

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

[hariiirs]

Dear Bryan

I am stucked in the processing when running sh run_05_fullBurst_resample. It gives a message of non-availability W1.xml.data.dat file under each coreg_secondarys folder. Though these files are created under the same folder but nothing is there inside them. The screen shots are attached here for your reference. I repeated this processing (till this step0 three times. Can you please help me in this regard?

With regards Hari Shankar

On Wed, 9 Mar 2022 at 11:29, Bryan Marfito @.***> wrote:

You're welcome @hariiirs https://github.com/hariiirs. Pls close this issue. Thanks!

— Reply to this email directly, view it on GitHub https://github.com/isce-framework/isce2/issues/448#issuecomment-1062581158, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKDZGJLZLYBEMSSY5WOYE3TU7A42ZANCNFSM5PDP2UBA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you were mentioned.Message ID: @.***>

-- HS

[bjmarfito]

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

[hariiirs]

Dear Bryan

I repeated three times. But similar msg is received.

With regards HS

On Thu, 17 Mar 2022, 13:49 Bryan Marfito, @.***> wrote:

Hi @hariiirs https://github.com/hariiirs, kindly check if you miss running any previous steps before running run_5.

— Reply to this email directly, view it on GitHub https://github.com/isce-framework/isce2/issues/448#issuecomment-1070523967, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKDZGJM7MAYJYKD4HGDCTY3VALTH3ANCNFSM5PDP2UBA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you were mentioned.Message ID: @.***>

[bjmarfito]

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

[hariiirs]

Dear Bryan

Yes, this is the command/arguments which I have used - Present working directory: /home/hari_s/....../Project/Descending/outputs/

stackSentinel.py -s /home/hari_s/...../Project/Descending/SLCs/ -o /home/hari_s/...../Project/Descending/orbits/ -d /home/hari_s/.....Project/DEM/demLat_N28_N33_Lon_E077_E081.dem.wgs84 -b '30.3 31.4 78.6 82.2' -W slc -n '1 2 3' -a /home/hari_s/...../Project/Descending/orbits/ -C geometry -e 0.65 -m 20210506 --num_proc 4

Regards Hari Shankar

On Fri, 18 Mar 2022 at 11:47, Bryan Marfito @.***> wrote:

Hi @hariiirs https://github.com/hariiirs, could you post the stackSentinel.py command and arguments that you used here?

— Reply to this email directly, view it on GitHub https://github.com/isce-framework/isce2/issues/448#issuecomment-1072066444, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKDZGJJ272K6A2QGYNQIWN3VAQNYJANCNFSM5PDP2UBA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you were mentioned.Message ID: @.***>

-- HS

[hardreddata]

Hi @hariiirs

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

See https://github.com/isce-framework/isce2/pull/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]

Dear Bryan

Thank you very much for your suggestion. Now let me try with one processor, and will revert you back the situation.

With regards Hari Shankar

On Tue, 22 Mar 2022 at 11:52, Russell Grew @.***> wrote:

Hi @hariiirs https://github.com/hariiirs

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

See #271 https://github.com/isce-framework/isce2/pull/271

The feedback from @yunjunz https://github.com/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.

Or just run the one process.

Cheers.

— Reply to this email directly, view it on GitHub https://github.com/isce-framework/isce2/issues/448#issuecomment-1074782808, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKDZGJJRF7YIYDBORKP4P3DVBFRJFANCNFSM5PDP2UBA . You are receiving this because you were mentioned.Message ID: @.***>

-- HS

[hariiirs]

Dear All

I have one doubt regarding the range and azimuth looks for Sentinel-1 TOPS SLC images while processing with ISCE for stacking and single-reference interferogram generation. The no. of azimuth and range looks are only single in each direction. But while processing it with ISCE then I had following confusion-

1) In stackSentinel.py, the default Azimuth Looks are 3 and Range Looks are 9. So shall I change the no. of looks in each direction while running this command. 2) The parameters (no. of looks in azimuth and range direction) of input_file required for make_single_reference_stack_isce. I think these parameters should be the same in both steps.

Can you please suggest what should be the range and azimuth looks for Sentinel-1 TOPS processing?

Many thanks Hari Shankar

On Thu, 24 Mar 2022 at 11:45, Hari Shankar @.***> wrote:

Dear Bryan

I have processed it with single process but still getting the same error message (attached).

With regards Hari Shankar

On Tue, 22 Mar 2022 at 12:49, Hari Shankar @.***> wrote:

Dear Bryan

Thank you very much for your suggestion. Now let me try with one processor, and will revert you back the situation.

With regards Hari Shankar

On Tue, 22 Mar 2022 at 11:52, Russell Grew @.***> wrote:

Hi @hariiirs https://github.com/hariiirs

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

See #271 https://github.com/isce-framework/isce2/pull/271

The feedback from @yunjunz https://github.com/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.

Or just run the one process.

Cheers.

— Reply to this email directly, view it on GitHub https://github.com/isce-framework/isce2/issues/448#issuecomment-1074782808, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKDZGJJRF7YIYDBORKP4P3DVBFRJFANCNFSM5PDP2UBA . You are receiving this because you were mentioned.Message ID: @.***>

-- HS

-- HS

-- HS

[OliviaDdy]

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

[hariiirs]

Yes, sure.

On Tue, 26 Apr 2022, 15:20 OliviaDdy, @.***> wrote:

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

— Reply to this email directly, view it on GitHub https://github.com/isce-framework/isce2/issues/448#issuecomment-1109589610, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKDZGJJCUGAP6FT2LQGDZJDVG636BANCNFSM5PDP2UBA . You are receiving this because you were mentioned.Message ID: @.***>

[hardreddata]

@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]

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

[ZGHHGZ]

@bjmarfito Hello, what should I do to handle a single burst for stackSentinel.py ? https://github.com/isce-framework/isce2/issues/756