-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow Sentinel-3 native names #111
Labels
Comments
remi-braun
added a commit
that referenced
this issue
Oct 30, 2023
…mes when trying to load a spectral band (#111)
Bands can be called with their name, ID or mapped name. See https://github.com/sertit/eoreader/blob/main/CI/SCRIPTS/test_bands.py for the tests |
remi-braun
added a commit
that referenced
this issue
Oct 31, 2023
remi-braun
added a commit
that referenced
this issue
Oct 31, 2023
bastiencyr
pushed a commit
that referenced
this issue
Feb 13, 2025
…mes when trying to load a spectral band (#111)
bastiencyr
pushed a commit
that referenced
this issue
Feb 13, 2025
bastiencyr
pushed a commit
that referenced
this issue
Feb 13, 2025
bastiencyr
pushed a commit
that referenced
this issue
Feb 13, 2025
…mes when trying to load a spectral band (#111)
bastiencyr
pushed a commit
that referenced
this issue
Feb 13, 2025
bastiencyr
pushed a commit
that referenced
this issue
Feb 13, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It is quite disturbing to have to mix mapped and raw Sentinel-3 bands.
It leads to too much friction i.e. which one is
Oa07
? IsOa03
mapped ? etc.-> It would be better to allow both aliases and raw bands.
The text was updated successfully, but these errors were encountered: