S1 SLC Products + Burst Grouping

As many people have observed, the S1 SLC products for a specific area of interest don’t always have perfectly matching bursts. For example, the 1st burst in one product may correspond to the 2nd burst in another product.

The upshot is that we’re left with a smaller common area to coregister and fewer burst overlaps to apply Enhanced Spectral Diversity – i.e., determine and apply a global azimuth shift.

I wonder if/how/when the S1TBX will be able to handle this.

Edit: here’s an example over Vienna (overlap in purple).

Esteban
SkyGeo

We do handle some cases of this. It could be there are some scenarios that still give it trouble. What are the full product file names for the pairs?

Hi Luis,

I wonder whether there’s some feature in the S1TBX which could be used for extracting, for example, nine contiguous bursts for a given area of interest. And so, if we wanted to create a stack of SLCs, we’d need access to more than one SLC product per acquisition date, so as to ensure a minimum number of bursts is available.

Here’s the list of image names:

S1A_IW_SLC__1SDV_20150320T165025_20150320T165052_005118_00670A_F9F9
S1A_IW_SLC__1SDV_20150706T165030_20150706T165057_006693_008F32_CB50
S1A_IW_SLC__1SDV_20151103T165031_20151103T165058_008443_00BEF0_2749
S1A_IW_SLC__1SDV_20150212T165024_20150212T165052_004593_005A71_EE46
S1A_IW_SLC__1SDV_20150119T165025_20150119T165053_004243_005290_068A
S1A_IW_SLC__1SDV_20150308T165025_20150308T165052_004943_0062D6_28B9
S1A_IW_SLC__1SDV_20150811T165029_20150811T165056_007218_009DF7_2835
S1A_IW_SLC__1SDV_20141202T165027_20141202T165054_003543_0042BA_4B82
S1A_IW_SLC__1SDV_20150107T165026_20150107T165053_004068_004E99_5348
S1A_IW_SLC__1SDV_20141214T165027_20141214T165054_003718_0046B4_7196
S1A_IW_SLC__1SDV_20150224T165025_20150224T165052_004768_005E98_BDD0
S1A_IW_SLC__1SDV_20150519T165028_20150519T165055_005993_007B90_CE1A
S1A_IW_SLC__1SDV_20150916T165031_20150916T165058_007743_00AC29_3387
S1A_IW_SLC__1SDV_20141108T165028_20141108T165055_003193_003AD4_142D
S1A_IW_SLC__1SDV_20141027T165028_20141027T165055_003018_003709_5729
S1A_IW_SLC__1SDV_20151127T165044_20151127T165111_008793_00C8A5_6935
S1A_IW_SLC__1SDV_20150401T165026_20150401T165052_005293_006B1D_A34A
S1A_IW_SLC__1SDV_20151115T165042_20151115T165109_008618_00C3C5_27EE
S1A_IW_SLC__1SDV_20150507T165037_20150507T165104_005818_0077B7_BD8E
S1A_IW_SLC__1SDV_20150425T165027_20150425T165054_005643_0073B4_834E
S1A_IW_SLC__1SDV_20150531T165029_20150531T165056_006168_008065_CD85
S1A_IW_SLC__1SDV_20150718T165031_20150718T165058_006868_00943E_7FDF
S1A_IW_SLC__1SDV_20141015T165028_20141015T165055_002843_00334D_ADF4
S1A_IW_SLC__1SDV_20151010T165031_20151010T165058_008093_00B587_F5D0
S1A_IW_SLC__1SDV_20141120T165027_20141120T165055_003368_003E93_1191
S1A_IW_SLC__1SDV_20150612T165030_20150612T165057_006343_008584_E4FF
S1A_IW_SLC__1SDV_20150413T165026_20150413T165053_005468_006FA2_E572
S1A_IW_SLC__1SDV_20150904T165030_20150904T165057_007568_00A787_101C
S1A_IW_SLC__1SDV_20150730T165032_20150730T165059_007043_00992E_9097
S1A_IW_SLC__1SDV_20141226T165026_20141226T165053_003893_004AB1_8DFA
S1A_IW_SLC__1SDV_20150823T165030_20150823T165057_007393_00A2B2_F809
S1A_IW_SLC__1SDV_20150928T165031_20150928T165058_007918_00B0E9_3B66
S1A_IW_SLC__1SDV_20151022T165031_20151022T165058_008268_00BA62_42DE
S1A_IW_SLC__1SDV_20150131T165025_20150131T165052_004418_005666_AA8A
S1A_IW_SLC__1SDV_20151209T165041_20151209T165108_008968_00CDA6_62A1
S1A_IW_SLC__1SDV_20150320T165025_20150320T165052_005118_00670A_1963

And here’s the list of image IDs:

23a9832f-790e-4203-88b8-cf74d79a7825
e270c14d-49ad-4941-90af-3d4e4d6086ea
b35c6902-46cb-4016-8377-49ff55689322
5d36a914-02a5-4e86-a33a-6e630bce3368
ade1d5f5-c580-454a-a410-c912d6912f59
addd86f8-7ee7-459d-802a-b23dea29ca28
df0de17d-417b-43d3-b698-1ab55a0dca54
681bb6c7-b766-4fc8-94d7-711b4d489022
50e34e60-0868-4dd7-91cd-50aa806e0485
cfa8742e-7ab6-4b27-a79f-1facab774f03
a993ca4b-b663-41b3-8619-d0e80aeec722
8bdf8d78-09de-4149-a633-167bec4e0e2d
237784f7-d2bc-4916-b3cb-45d9d97143a9
a3e40f52-8101-4db2-a972-f3ca88526db5
e46a4216-2930-4d0b-81ea-b6959cb81554
647fe84d-d855-4ff0-b9cb-774d98f521b9
88d2cffa-123f-45b2-bdaf-84e437ec54d1
80fc073b-418e-4d93-8f09-4660caca1713
0a93767e-1d3d-4aa3-b6ec-d3b83ba7db62
69463be0-f46b-47b5-b813-5a45df0589e4
99e48352-6a80-4cb1-9252-4979d6386a85
7f510398-f6a8-44cd-96fd-4c438050306a
a39a273c-c619-4795-9105-509641a14d31
a44dbf0a-b85b-40dd-9c9b-2428696c97df
9dbf58dc-de43-428b-8b8d-77b7749a3354
f445afbe-ea76-4941-b73d-0e30dcad47c8
4383852c-edab-4cab-baeb-4b6373af7c8a
f2264dff-a44e-4dbb-80aa-e1b2720914fb
cc83eb2b-5026-485a-afca-9677861fe2b5
f66b73ca-5e3b-460d-941d-0573bf61c0c8
f1735c9c-51fd-4cea-8afc-b88d512b9b5a
bfaef305-7695-4e5a-9014-90096d996cc9
838c3c99-6268-4411-a082-43699db6d8b6
53946a41-f28e-4f13-bedb-9d3bb47eb572
0f49049b-69a0-4515-bf44-ccde90597a3e
0853d7e6-aefc-433f-b2b4-c58b23a86845

Esteban
SkyGeo

Hi Luis (@lveci),

I wonder whether there’s any recommended practice for addressing this issue with the S1 Slice Assembly feature, in combination with the Virtual Stack Processing feature.

Regards,

Esteban
SkyGeo

Hi Luis,

In order to address this issue, I’ve been using the following graph:

So, I assemble them first and then select bursts in the TOPSARSplit op using the wktAoi parameter. However, this approach does not always work. For example, when I coregister these products:

Date: 20150807 (master)

  1. S1A_IW_SLC__1SSV_20150807T005110_20150807T005137_007150_009C22_E118.zip
  2. S1A_IW_SLC__1SSV_20150807T005134_20150807T005202_007150_009C22_71C5.zip

Date: 20150527

  1. S1A_IW_SLC__1SSV_20150527T005106_20150527T005133_006100_007E93_C1ED.zip
  2. S1A_IW_SLC__1SSV_20150527T005132_20150527T005159_006100_007E93_969F.zip

I get this (note that @junlu already found a possible explanation for this):

Do you think this could be added as a standard graph in the S1TBX? I also hope that this issue has a fix.

Please let me know.

Thanks,

Esteban

Could you attach the graph. thanks

Yes, of course (see attachment). Note that I’m using the ${parameter_name} convention to pass parameters when calling gpt, and that sometimes makes the Graph Builder draw wrong arcs.

coregister_subswath.xml (5.6 KB)

Hi Luis,

Would you let me know if there are any plans to address this issue in the next release?

Thanks,

Esteban

The graph builder does not know what to do with the ${parameter_name} parameters. It’s only expecting actual parameter values. It’s different then in the command line where you would pass in these parameters.

Hi Luis,

I actually meant the issue I’m having when using the graph with these input products:

Date: 20150807 (master)

  1. S1A_IW_SLC__1SSV_20150807T005110_20150807T005137_007150_009C22_E118.zip
  2. S1A_IW_SLC__1SSV_20150807T005134_20150807T005202_007150_009C22_71C5.zip

Date: 20150527

  1. S1A_IW_SLC__1SSV_20150527T005106_20150527T005133_006100_007E93_C1ED.zip
  2. S1A_IW_SLC__1SSV_20150527T005132_20150527T005159_006100_007E93_969F.zip

which results in the following invalid bursts (see missing data):

I’ve been looking into the xml metadata of those SLCs (zip files as delivered by ESA). It seems that the SliceAssembly op fails due to a missing burst for the products acquired on 20150527. I will contact the scihub support for this, though I can imagine you may want the toolbox to properly handle this exception.

Here’s a visual on how I concluded that there’s a missing burst by loading the geolocationGridPoint xml elements in QGIS:


Date: 20150807 (this one is fine, as the beginning and end of bordering bursts overlap)
1st Slice


1st and 2nd Slice


Date: 20150527 (you can see the missing burst in swath 1)
1st Slice


1st and 2nd Slice

Note that the azimuthAnxTime parameter also reveals the missing burst.