Closed MarkusZehner closed 5 months ago
I see a problem with the solution in #185 as there is a backwards incompatability if the geometry column is simply added. I tried to work around this via checks and the special flag to use the geometry. but this is already required at creation of the archive.
Another idea is to just add a refinement to the select method:
The second option would leave the database as-is and reduce the needed ajustments to a read method for the geometry and a call within the select funtion, See #282. What do you think?
I guess the issue is not really closed yet but is being addressed in https://github.com/johntruckenbrodt/pyroSAR/pull/296.
The following is caused by only no-data values in an S1 scene over the DEM/Area of interest to process the data. Using the geometry of the scene's metadata, as in #185, instead of the footprint, would not consider those scenes in a select, reducing unnecessary data processing up to the shell commands below.
Centos
Micromamba env
0.22.1
shell commands: