Make STAC -> ODC conversion more robust to missing extension data #351
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.
Support for Collection -> Product
Collection
that includes "Item Assets" extension then you can create Datacube product from that.dtype,nodata
will be read from thatSupport for STAC Items without Projection extension
For more information see #297, essentially if there is no projection extension found on an item, then we create Dataset object with "faked" grid, Dataset's
.extent
is still valid and so data can be loaded from that Dataset, one just can't know what native resolution and projections are. But so long as user supplies desired resolution and projection for loaded data it's not a problem.