Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for sarsen calibration #215

Open
system123 opened this issue Jul 29, 2022 · 8 comments
Open

Add support for sarsen calibration #215

system123 opened this issue Jul 29, 2022 · 8 comments

Comments

@system123
Copy link
Contributor

sarsen (https://github.com/bopen/sarsen) is a fairly recent initiative to re-implement Sentinel-1 preprocessing and calibration using modern Python libraries such as Dask and XArray. This enables better scalability over distributed clusters of workers and removes the reliance on SNAP for preprocessing (which we can all agree is sometimes a pain to work with).

It would be nice if PyroSAR wrapped sarsen as an alternative SAR preprocessing backend, so that existing pipelines could be moved to use sarsen with little to no change in code.

@johntruckenbrodt
Copy link
Owner

Interesting idea, @system123! I've followed the development a little but haven't tried it out myself yet. Sur looks promising. I'll give this issue a help wanted label as I might not be able to look into it in the near future. Maybe you or somebody else would like to collect some ideas here or develop something right away..

@system123
Copy link
Contributor Author

I'm happy to take a look at it when I get a free moment - but when I start work on it I will post here, in case someone else wants to give it some attention before then.

@MarkusZehner
Copy link
Contributor

MarkusZehner commented Mar 28, 2024

I have a workflow to get custom RTC from Planetary Computer and thought of handling the downloaded scenes with pyroSAR to reduce duplicates. Maybe we can use some of that?

@johntruckenbrodt
Copy link
Owner

@MarkusZehner are the MPC products processed with sarsen? I know they financed the RTC implementation in it but always thought that the products are still processed using Catalyst:
https://planetarycomputer.microsoft.com/dataset/sentinel-1-rtc

@MarkusZehner
Copy link
Contributor

@johntruckenbrodt the linked gist downloads GRD and COP GLO-30 from MPC and uses sarsen to process locally to RTC. The RTC data available at MPC has visibly worse correction: https://github.com/microsoft/PlanetaryComputerExamples/blob/main/tutorials/customizable-rtc-sentinel1.ipynb

@johntruckenbrodt
Copy link
Owner

@MarkusZehner I misinterpreted your message above and thought you directly get the RTC products from Planetary Computer (PC). I now understand that you do your own custom processing based on sarsen with some modifications (and just get the GRD products from PC). This is really interesting, especially since you mentioned that sarsen processes each polarization by its own instead of reusing the RTC correction layer for each (as it should be). Moreover, there hasn't been much activity in the sarsen repo lately so I wonder whether it is worth the effort.

@whatnick
Copy link

whatnick commented Oct 9, 2024

This was interesting unfortunately it looks like Sarsen development has stalled and may not be worth adding for now.

@johntruckenbrodt
Copy link
Owner

@whatnick yes unfortunately this is the case. However, B-Open, the company behind it, is currently actively developing Python SAR processors which will go open-source eventually. I don't know whether this will be part of sarsen though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants