I have been trying to use the datasets available at AWS S3 bucket for my own SAR processes. I am downloading full folders for scenes, the unzipped ones as I need quite old data for my concerns, data older than 2 months and now part of LTA in Copernicus site.
However, I am finding that the folders do not contain the exact elements of what .SAFE folders contain, but rather renamed versions of their elements. This is making it impossible to process downloaded folders in SNAP or plugging it in in SAR processing libraries such as pyroSAR. Note, I do not need general sigma0 values already available but I need customized workflows that I need to apply using gpt, pyroSAR or SNAP. I cannot even open the downloaded folders in SNAP.
I have tried to create a .SAFE folder and zip it, but SNAP, pyroSAR and common workflows in gpt fail to recognize the products (either the directly downloaded ones or the ones that I saved as .SAFE folders and zipped them). My guess is that the structure and naming that SNAP, gpt or pyroSAR requires are missing with the data renaming that is performed in S3.
I just wanted to know if someone is actually working with GRD imagery downloaded from those buckets, and is able to work with it in SNAP or gpt workflows. I have been thinking to use those workflows in an EC2 instance directly, but since I cannot ready the products with gpt, my problem will still exist. Being able to reconstruct the .SAFE folder so we can process it with gpt will be extremely helpful.