You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Basically, depending on where you download your data from, you either get:
All bands in 10m resolution (resampled, no suffix)
All bands in native resolution (10m, 20m, or 60m)
All bands in all resolutions (10m, 20m, and 60m)
1, 2, and 3 are all somewhat contradictory. We could easily support each of these on their own, but supporting all 3 in combination is hard:
A. Remove resolution from the regex (only supports 1)
B. Replace resolution with a wildcard (only supports 1 and 2)
C. Include 10m in the regex (only supports 3)
In order to prioritize the highest resolution, maybe we could sort the glob results lexicographically and choose the first one only? But that feels really sloppy and could probably break for more complicated hypothetical datasets.
Description
I have a Sentinel 2 scene with the following files (e.g. in
./test_scene/
):I would expect any of the following to work:
However the
filename_glob
andfilename_regex
are setup in such a way that none of the above are recognized as valid Sentinel 2 scenes.Steps to reproduce
see above
Version
0.6.0.dev0
The text was updated successfully, but these errors were encountered: