Stac validation #9
Merged
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
dannymandel
approved these changes
May 20, 2024
|
Also, one other thought I had…is this validator able to accessed programmatically? Would be nice for us to run an automated test that ensures we pass it when we write out the results. |
|
Going to merge this one and will look at getting the stac validator hooked up in a followup PR. |
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.
Changed the STAC output to conform with validator.
While working with the stac_browser, found the structure of the STAC content was a bit off. Found a validator at https://github.com/stac-utils/stac-validator which works well. Adjusted the generated STAC record to be valid and now bb and temporal range work as expected in the browser.