Repository navigation
Canopy data pull moved to the tree-canopy repo - #70
Merged
Merged
Conversation
Updated the status of the automated pull of forest canopy data, including the new file path and added links to the relevant pull request.
…nopy Clarified the usage of DATACOMMONS_API_KEY for the canopy data pull.
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
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.
Per Loren's Oct 25 note, the canopy processing now lives beside its data in ModelEarth/tree-canopy as
pipeline/canopy-process.py(tree-canopy PR #1).Here:
process/canopy/canopy-process.pyandtests/test_canopy_process.pyremoved (the script carries its own--check), andprojects.mditem 7 plus the README'sDATACOMMONS_API_KEYline link to the new location. projects issue #63 has a comment with the same links.Made through the GitHub web editor, so it's four small commits on
patch-1; squash on merge if you prefer.