-
Notifications
You must be signed in to change notification settings - Fork 41
made load_stac nicer to mismatch in band names #755
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
Closed
VictorVerhaert
wants to merge
13
commits into
master
from
issue752-load-stac-make-bands-metadata-flexible
Closed
Changes from 1 commit
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
2c04f73
made load_stac nicer to mismatch in band names
VictorVerhaert 66ea570
added changelog entry
VictorVerhaert 1446f44
made warning message more explicit
VictorVerhaert 56e0731
Merge remote-tracking branch 'origin/master' into issue752-load-stac-…
VictorVerhaert 4d350c4
processed pr comments
VictorVerhaert 5d9b6d4
removed caplog.clear and removed add_dim(bands) case
VictorVerhaert 83ef8eb
Issue #752/#755 anticipate absence of band dimension
soxofaan c344264
Issue #752/#755 document `warning` arg of `ensure_band_dimension`
soxofaan 1868c22
added preservation of bands in ensure_bands_dimension
VictorVerhaert 371eee5
Merge branch 'issue752-load-stac-make-bands-metadata-flexible' of htt…
VictorVerhaert 9c5a6d5
Revert "added preservation of bands in ensure_bands_dimension"
VictorVerhaert df7f662
made ensure_band_dimension private
VictorVerhaert 494b44a
Merge remote-tracking branch 'origin/master' into issue752-load-stac-…
soxofaan File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not really a fan of having a function in metadata that takes a warning as an argument just to log it. Logging could happen outside of this function imo
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah I was hesitant about that,
but forcing the caller to think of a warning message is to make clear that this function should only be used exceptionally
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in that case I would rename it to
replace_band_dimension
or evenset_band_dimension
as ensure sound like running some checks.Still not a big fan of the warning argument, but if we keep I'd at least make it optional.
I'm quickly working on a commit that also retains the existing bands so we don't lose fields like wavelength_um
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll add a note to the documentation to better explain this design
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note that for cases like this where there is doubt about the API that is added, simply making it somehow 'private' or 'internal' API can help to be future proof.