Compatibility with `Burst2Safe`

[Jaapel]

Hi @scottstanie !

I have been trying to reduce the data volumes used by making use of burst endpoints and using the Burst2Safe library to make them reabable by the s1-reader. This works, but sweets makes use of COMPASS, which again makes use of burst-db to obtain burst bounding boxes and consistent burst naming.

When I run sweets against the burst SLCs, I get many warnings about the geometries not being correct (which makes sense!), and I wonder how I can contribute to make this work, and hopefully finally integrate into sweets. From a scan through the code it seems that burst-db makes use of pre-existing databases (ESA).

How could I make this work with the Burst2SAFE, whose geometries differ from the original frames coming from ESA?

[scottstanie]

Hi, I can't recall- had I pointed you at this attempt of mine?
isce-framework/dolphin#565 (reply in thread)

I did burst2stack to get all the the dates I wanted, then ran compass on it directly

mkdir data
burst2stack --rel-orbit 46 --start-date '2019-01-01' --end-date '2022-01-01' --pols 'VV' --swaths 'IW3' --extent 138.78593 37.55812 139.1150 37.7795 --output-dir 'data/' --all-anns
sardem --data-source COP --output-type float32 --output-format GTiff -o dem.tif --bbox 138.5 37.4 139.3 37.9
eof --search-path data/ --save-dir orbits/ --force-asf

I then did sweets config --bbox 138.78593 37.55812 139.1150 37.7795 --start 2019-01-01 ... and while I did get some errors for the config step (possibly from things you've recently fixed?) it made a valid config file which knew to skip the download/dem/orbit step, and jumped straight to making the geocoded burst SLCs.

One key step that Forrest notes on Burst2Safe is that you need the --all-anns flag for isce3 compatibility (since s1-reader looks for the IW2 annotation, regardless of which subswath you are processing).
Tagging @mirzaees since she also looked at this recently