Avoid using "Release 2" title for Tanager open data release#43
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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've been asked to avoid calling the new release of Tanager open data "Release 2" to avoid confusion. This MR leaves "Release 2" out of the STAC catalog title.
Note that
release2is still in the file paths, but we're not being asked to change things at that level. E.g. the first release files are still in GCS and data for the same scenes in the second release is actually different. We need to keep both sets of data files for end users consistency outside of these STAC catalogs (e.g. the "release 1" data is used directly in GEE without STAC being used at all in https://gee-community-catalog.org/projects/tanager/ and we don't want to break that).