I extracted and downloaded Sentinel-1 SLC bursts from two images using the CDSE utilities (GitHub - eu-cdse/utilities - Documentation - Sentinel-1 SLC Bursts). To do this I run the following commands:
docker run -it -v /home/username:/home/ubuntu -e AWS_ACCESS_KEY_ID=<AWS_ACCESS_KEY_ID> -e AWS_SECRET_ACCESS_KEY=<AWS_SECRET_ACCESS_KEY> cdse_utilities sentinel1_burst_extractor.sh -o /home/ubuntu -n S1A_IW_SLC__1SDV_20240814T171540_20240814T171607_055212_06BAD3_C31B.SAFE -p vv -s iw3 -r 30345
docker run -it -v /home/username:/home/ubuntu -e AWS_ACCESS_KEY_ID=< AWS_ACCESS_KEY_ID> -e AWS_SECRET_ACCESS_KEY=<AWS_SECRET_ACCESS_KEY> cdse_utilities sentinel1_burst_extractor.sh -o /home/ubuntu -n S1A_IW_SLC__1SDV_20240826T171541_20240826T171608_055387_06C154_3B5B.SAFE -p vv -s iw3 -r 30345
If I try to read the downloaded bursts in SNAP 11 everything seems to work fine. Then, I tried to coregister the two bursts with the following graph:
By opening the result, I can note that the slave image has been cut:
Note that before applying the back-geocoding operation the slave image is not cut and represent the entire area of the burst as expected.
If I try instead to apply the same graph (i.e. apply orbit + back-geocoding) using as inputs the bursts extracted using the TOPS Split SNAP function on the original data (i.e. S1A_IW_SLC__1SDV_20240814T171540_20240814T171607_055212_06BAD3_C31B.SAFE.zip and S1A_IW_SLC__1SDV_20240826T171541_20240826T171608_055387_06C154_3B5B.SAFE.zip) I can get the expected result with no cut on the slave image:
Is SNAP 11 supposed to support the output of the CDSE utilities for burst extraction? Any insight about where could be the issue and how to eventually solve it?