isce3 based processing wrapped in PyroSAR

[whatnick]

It would be interesting to wrap isce3 + python API in the pyrosar processing pipeline since it has efficient C++ codebase and is opensource.

[johntruckenbrodt]

Absolutely! I've been playing around a bit with ISCE3 but so far have not had the time to do any further integration.
I wouldn't say this is a bug though 😉.

[whatnick]

The bug tag was the default assigned, but definitely an enhancement request. Something I would love to work on weekends given ISCE3 does have a Python wrapper in place. Will probably need to be in a conda env to bypass build requirements. If you draft a PR or some initial design ideas I can play along.

[johntruckenbrodt]

Thanks for picking this up again! Before we get started, let's consider the use cases. Are you interested in a general Python interface for ISCE or "just" a Python wrapper for a specific use case? For example, there is this one to process RTC products:
https://github.com/opera-adt/RTC

This is mostly Python and surely a good starting point.

I am on leave in June so can't actively work on it but we can start talking it through.

[whatnick]

Mostly a facade using the existing Python API for ISCE3. The interest in PyroSAR would be to standardize processes such a provisioning of the DEM and allow comparative switching between different RTC processors.

[johntruckenbrodt]

Okay sounds great. So in this case I think it would be most straightforward to add a submodule isce3 with a function geocode copying the needed parameter names from the snap.geocode function. For starters this could be very minimal and more parameters can be added as needed. Sounds like a plan?

[whatnick]

Sounds like a great starting point as a facade. This is going to be the most likely usage pattern.

…

On Sat, 14 June 2025, 17:48 John Truckenbrodt, ***@***.***> wrote: *johntruckenbrodt* left a comment (johntruckenbrodt/pyroSAR#322) <#322 (comment)> Okay sounds great. So in this case I think it would be most straightforward to add a submodule isce3 with a function geocode copying the needed parameter names from the snap.geocode function. For starters this could be very minimal and more parameters can be added as needed. Sounds like a plan? — Reply to this email directly, view it on GitHub <#322 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADX7BGIBFL7WYYYEF65JL33DPLFPAVCNFSM6AAAAABPTSBLRWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSNZSGQ3TAOJWGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[johntruckenbrodt]

Great. This should give us an understanding of how to best do it. Once this works, we can generalize the interface further.

[johntruckenbrodt]

Might be of interest: https://github.com/forrestfwilliams/MultiRTC