[ivca-cz]

Hello Yuxiao,

I have encountered a strange behaviour in the coregistration step of S1 data (see the screenshot and log attached). When I click to see the extracted/coregistered images, the number of coregistered images is higher than the number of the extracted ones. In fact, the last two coregistered images have a large black area (missing lines), and one of the previous ones has a small black area (missing pixels). But, if I click to see the extracted images, I can see only about half of them… the same problem encountered for the area size of 10 km.

using the version of 24-aug (this morning it was the latest linux-compiled version)

Thank you, Ivana

list of data used:
S1A_IW_SLC__1SDV_20141014T050100_20141014T050127_002821_0032E1_FB57.SAFE
S1A_IW_SLC__1SDV_20141026T050100_20141026T050128_002996_003697_1489.SAFE
S1A_IW_SLC__1SDV_20141201T050100_20141201T050127_003521_00423E_02E5.SAFE
S1A_IW_SLC__1SDV_20141225T050059_20141225T050126_003871_004A37_D639.SAFE
S1A_IW_SLC__1SDV_20150118T050058_20150118T050126_004221_005218_F5E8.SAFE
S1A_IW_SLC__1SDV_20150130T050058_20150130T050125_004396_0055E9_B17A.SAFE
S1A_IW_SLC__1SDV_20150223T050058_20150223T050125_004746_005E0D_2A5B.SAFE
S1A_IW_SLC__1SDV_20150307T050058_20150307T050125_004921_006251_27EA.SAFE
S1A_IW_SLC__1SDV_20150319T050058_20150319T050125_005096_006686_2526.SAFE
S1A_IW_SLC__1SDV_20150412T050059_20150412T050126_005446_006F0E_241A.SAFE
S1A_IW_SLC__1SDV_20150424T050059_20150424T050126_005621_007335_3EF1.SAFE
S1A_IW_SLC__1SDV_20150506T050058_20150506T050125_005796_007731_8616.SAFE
S1A_IW_SLC__1SDV_20150518T050058_20150518T050125_005971_007B27_2602.SAFE
S1A_IW_SLC__1SDV_20150530T050101_20150530T050128_006146_007FBC_6A64.SAFE
S1A_IW_SLC__1SDV_20150611T050102_20150611T050129_006321_0084E5_3D28.SAFE
S1A_IW_SLC__1SDV_20150623T050102_20150623T050130_006496_0089E5_FA3D.SAFE
S1A_IW_SLC__1SDV_20150705T050102_20150705T050129_006671_008E9A_4034.SAFE
S1A_IW_SLC__1SDV_20150717T050103_20150717T050130_006846_00939F_7F1E.SAFE
S1A_IW_SLC__1SDV_20150729T050104_20150729T050131_007021_009897_D0C7.SAFE
S1A_IW_SLC__1SDV_20150822T050105_20150822T050132_007371_00A219_A811.SAFE
S1A_IW_SLC__1SDV_20150903T050105_20150903T050132_007546_00A6E6_526A.SAFE
S1A_IW_SLC__1SDV_20150915T050106_20150915T050133_007721_00AB97_609C.SAFE
S1A_IW_SLC__1SDV_20151021T050106_20151021T050133_008246_00B9C7_193A.SAFE
S1A_IW_SLC__1SDV_20151114T050107_20151114T050134_008596_00C323_6048.SAFE
S1A_IW_SLC__1SDV_20151126T050107_20151126T050133_008771_00C807_69FC.SAFE
S1A_IW_SLC__1SDV_20151208T050106_20151208T050133_008946_00CD03_142C.SAFE
S1A_IW_SLC__1SDV_20151220T050106_20151220T050133_009121_00D1D3_3FE1.SAFE
S1A_IW_SLC__1SDV_20160101T050105_20160101T050132_009296_00D6D0_0981.SAFE
S1A_IW_SLC__1SDV_20160113T050105_20160113T050132_009471_00DBD3_058E.SAFE
S1A_IW_SLC__1SDV_20160125T050104_20160125T050131_009646_00E0EF_C631.SAFE
S1A_IW_SLC__1SDV_20160206T050104_20160206T050131_009821_00E5FD_3739.SAFE
S1A_IW_SLC__1SDV_20160218T050104_20160218T050131_009996_00EB24_6F60.SAFE
S1A_IW_SLC__1SDV_20160301T050104_20160301T050131_010171_00F01D_97D8.SAFE
S1A_IW_SLC__1SDV_20160313T050104_20160313T050131_010346_00F533_93E6.SAFE
S1A_IW_SLC__1SDV_20160325T050105_20160325T050132_010521_00FA13_750E.SAFE
S1A_IW_SLC__1SDV_20160406T050105_20160406T050132_010696_00FF2D_E126.SAFE
S1A_IW_SLC__1SDV_20160418T050106_20160418T050133_010871_010476_B1AD.SAFE
S1A_IW_SLC__1SDV_20160430T050106_20160430T050133_011046_0109EB_17EF.SAFE
S1A_IW_SLC__1SDV_20160512T050110_20160512T050137_011221_010F75_4AE6.SAFE
S1A_IW_SLC__1SDV_20160524T050110_20160524T050137_011396_01152F_4169.SAFE

Attachments:

You must be logged in to view attached files.

[Yuxiao]

your log and lasterror.mat does not correspond with what you described here.

please send them again.

[ivca-cz]

ok, once more with a different master

Attachments:

You must be logged in to view attached files.

[Yuxiao]

Dear Ivana,

Among your warnings, there’s this one:

“Your S1A imgfile: /media/DATA/mosty_ova/124_IW2_precorbs/SLC/S1A_IW_SLC__1SDV_20151021T050106_20151021T050133_008246_00B9C7_193A.SAFE/measurement/s1a-iw2-slc-vv-20151021t050107-20151021t050132-008246-00b9c7-005.tiff seems to be corrupted and NO HEADER INFO can be read!!! Further Process with this image may lead to error!!!

Your S1A imgfile: /media/DATA/mosty_ova/124_IW2_precorbs/SLC/S1A_IW_SLC__1SDV_20151021T050106_20151021T050133_008246_00B9C7_193A.SAFE/measurement/s1a-iw2-slc-vv-20151021t050107-20151021t050132-008246-00b9c7-005.tiff seems to be corrupted and NO HEADER INFO can be read!!! Further Process with this image may lead to error!!!”

which I believe explains what is wrong in your slave image.

There’s another one here:
” List of Images for which the coregistration failed:
20151021″
which says this image failed for coregistration.

Please check the status for those images corrupted. The easiest way is to re-download those images.

The lasterror.mat says “Error in s1a_meta(): can not find SENTINEL xml file!” but I can’t locate this error in your log so I am puzzled how you get that error. Can you replicate it?

yuxiao

p.s. I will make that warning more obvious in the next version of sarproz.

[ivca-cz]

Yes,

you are right. I noticed this warning, expected that there is a problem with this image and it could not be extracted/coregistered. But I did not put it away, you are right. And after, I could not understand why “37 images could not be extracted” (and lots of extracted images could not be viewed, mostly from 2016) and why there are black areas in two/three of the coregistered images (different from this one (May 2016), I expected problems with this one).

Now, when I put this problematic image away, everything works fine… thank you.

Ivana

[Author]

Posts