Generating config files for sweets running in radar coordinates #228
Unanswered
Pinoquio1891
asked this question in
Q&A
Replies: 1 comment 1 reply
-
Hi, just checking what you're looking to do- you want to run sweets, meaning go all the way up the processing chain to unwrapped interferograms, but do it only for one burst in radar coordinates? Or were you also hoping to have multiple bursts stitched together geographically at some stage, but still do the early parts in radar coordinates? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi!
Currently I am working with point targets (retro reflectors) and in order to avoid any interpolation artifacts the aim is to run all analysis in radar coordinates. As far as I understood, in principle, Dolphin would be adequate for monitoring / analyzing positions in this case. It appears Dolphin accepts co-registered stacks as input I could create e.g. with ISCE2 or maybe Sweets / Compass? In order to maintain things within one framework I would prefer using either Sweets or Compass. Looking at the code I saw that compass can generate co-registered images in radar coordinates passing -g radar to s1_cslc but I did not see any possibility to already add this flag in the config file generation e.g. s1_geocode_stack, which sweets calls - and in deed it might seem strange to be able to generate radar coordinate output with a function / workflow named 'geocode', but in order to not to duplicate code could be the most obvious way. Or is there any other possibility yet to generate these stacks with compass? Maybe @hfattahi can give some hint?
Cheers
Christian
Beta Was this translation helpful? Give feedback.
All reactions