Skip to content

BurstSearch downloads S1C/D SAFEs but existing_safes() only discovers S1A/S1B #158

Description

@sholtkamp-AGH

BurstSearch successfully downloads Sentinel-1D burst SAFE directories, but the workflow then reports that no SAFE directories were found.

The downloaded directory names begin with S1D_, while BurstSearch.existing_safes() currently searches only for:

self.out_dir.glob("S1[AB]_*.SAFE")

The LocalSafeSearch SAFE and ZIP discovery patterns appear to have the same S1A/S1B limitation.

In src/sweets/download.py, BurstSearch.existing_safes() currently contains:

return sorted(self.out_dir.glob("S1[AB]_*.SAFE"))

LocalSafeSearch also appears to use S1[AB]_*.SAFE and S1[AB]_*.zip.

Changing the local patterns from S1[AB]_ to S1[ABCD]_ allows the downloaded Sentinel-1D directories to be discovered and the workflow to continue.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions