Leverage pystac for deeper spatial dimension detection #739
Conversation
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
soxofaan
force-pushed
the
issue737-spatial-dim-metadata-parsing
branch
from
e5437ff to
132c99c
Compare
|
this relates as well to |
This was
linked to
issues
Feb 26, 2025
jdries
reviewed
Apr 1, 2025
| ( | ||
| # Item without cube:dimensions metadata -> assume spatial dimensions x and y | ||
| StacDummyBuilder.item(), | ||
| {"x": [None, None], "y": [None, None]}, |
There was a problem hiding this comment.
if no dimension metadata is present, I would assume a default cube with also temporal and bands dimension
There was a problem hiding this comment.
yes indeed, that is the topic of #743
this PR is just about improving the spatial extent detection if there is STAC metadata about that
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
for #737