Feature: execute graphs with beam-dimap input

Hi all, I’m using pyroSAR to create, group, and then execute a graph via SNAP, the last of which via gpt from pyroSAR.snap.auxil. It seems to me that this operation fails if I want to use .dim BEAM-DIMAP formatted intermediate products from SNAP as inputs to my workflow (It’s raising RuntimeError: data format not supported). The same graph also fails in the SNAP graph tool, but works fine if I execute it via gpt in the command line.

From what I’ve seen in the code, I’m guessing that I can only execute graphs with pyroSAR that contain compressed formats (e.g. SAFE .zips) in their READ nodes?

I also wanted to ask if this might be a feature in which more people might be interested / that would be easy to implement?

[pbrotoisworo]

Thanks for the pointers. I’ll give this a shot and I’ll update this thread if I have any other concerns.

[johntruckenbrodt]

Hi @jonathom. I agree, this would be a great addition. So far Sentinel-1 scenes can only be processed if they are either in the original zip or unpacked in a .SAFE folder. The function pyroSAR.drivers.identify is responsible for this. It tries to read the scene with the available SAR scene drivers (like pyroSAR.drivers.SAFE), which all inherit from the class pyroSAR.drivers.ID.
In order to make all this work it would need a new class for the BEAM-DIMAP format that makes use of this mechanism. For starters not all methods that are suggested by the ID class have to be implemented. Then it would be easy for the gpt function to identify the source product and execute the workflow accordingly.

@konstantinschellenberg you have written some class right? Would you be willing to contribute it?