Initial hooks for additional STAC collection fields #929
+101
−2
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.
We'd like to enable explorer/stac as a provider endpoint for CEOS connected data assets. The CEOS folks have recommended the addition of the following fields into an explorer/stac Collection response:
Ref: https://github.com/radiantearth/stac-spec/blob/master/collection-spec/collection-spec.md
This PR provides the initial hooks to support these three fields. Defaults (and hardcoded) to
Nonevalues in this PR.The content for each of these fields is not directly available in an ODC product def so will likely need to be compiled from ODC datasets, possibly in a similar manner to
summary._stores._find_product_fixed_metadata()-- this can be a separate PR.I don't have a full test/integration suite for explorer (yet) so I confess this PR is both a preliminary integration test and an opportunity for the package maintainers (and others) to help inform the approach. I look forward to your reviews and comments!
📚 Documentation preview 📚: https://datacube-explorer--929.org.readthedocs.build/en/929/