Sentinel-1C support

[odhondt]

Hello and thanks for this great piece of software!
Are there any plans to support S1C products?
Right now identify fails because the metadata doesn't fit some regex patterns, I guess.

[johntruckenbrodt]

Hi Olivier,
thanks for your interest in pyroSAR 😊.
I am afraid there might be a bit more to it. I assume you are getting the data from CDSE? In this case, there is some more work done to read the data. See #291, #324.
I tried downloading the data from there yesterday but failed. Nothing happened when pushing the download button, except that a progress bar appeared which stayed stuck at 0 %. Will try again asap.
Best,
John

[odhondt]

Hi John,

Thanks for your reply. Regarding #291, I believe the COG format is just an option, and the regular GRDH files are still accessible. I was able to download one this morning without any issues.

I've been experimenting a bit with the pyroSAR code to geocode an S1C scene. Unfortunately, I'm stuck because the orbits aren't available yet. But the product identification seems to work with minimal changes in the code. If I manage to make progress, I'll let you know.

Best,
Olivier

[johntruckenbrodt]

Hi Olivier,
I was now also able to download a regular GRDH product. The ones I tried to download over the Netherlands don't seem to be available anymore. Great that you're already looking into processing with pyroSAR. I'll also try to get to it soon. In case you're using the function pyroSAR.snap.geocode, I haven't used that one in years and cannot guarantee it works. And yes, I think orbit correction with external files is mandatory there, which is not really necessary.
Best,
John

[johntruckenbrodt]

@odhondt I think I have fixed reading and unpacking with #333. Could you check?

[odhondt]

@johntruckenbrodt Thanks! I have tried it with a SNAP 11 install on a product named S1C_IW_GRDH_1SDV_20250117T181329_20250117T181357_000624_000495_FC84.SAFE.zip.

• identify now works (though unzipping was never an issue in my case).
• geocoding returns RuntimeError: sensor not supported (yet).
  (TBH I don't really need the geocode function, I only use identify and get_OSV in my toolbox. I just tried it in order to give you some feedback! :)

update: adding 'S1C' on line 273 of util.py avoids throwing the exception, but the orbit file is still not there, so I still can't tell you if geocoding works correctly.

[johntruckenbrodt]

Thanks @odhondt. I have modified geocode in #333 to test it. Unfortunately SNAP itself does not support Sentinel-1C yet.
I have modified the OSV download functionality to not throw an error if the sub-url does not exist. So, when calling

scene.getOSV(returnMatch=True)

the function just returns None.

There are ideas about implementing different OSV sources: #276, #279. I have not yet found the time to get into it.

[odhondt]

Thanks for the new version @johntruckenbrodt ! I guess we now have to wait for ESA to upload their first 1C orbits and support the products in snap...

[johntruckenbrodt]

Yep, tension is rising.
Apparently SNAP 12 will add support and will be released some time in Q1/2025:
https://forum.step.esa.int/t/sentinel-1c-data/44018

[johntruckenbrodt]

Processing works like a charm with SNAP 12 🥳