Explore moving metadata from veda-config to STAC #176
Conversation
This file contains 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
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.
Goal: Explore whether there is information currently in veda-config that could be loaded from STAC instead. Preferring standard STAC fields, such that the information seamlessly surfaces in other applications like STAC Browser.
infoDescriptionto a sub-heading under the STAC collectiondescriptionunitfromlayer/info/unitto STAC dataset valueslayer/info/sourceto provider information and ensure there is at least oneprovider:producerdefined for each collectionJust an exploration w/ @smohiudd, not currently intended for merging.