Create Python script to export to GEE #545
Merged
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.
Pull request checklist
Please check if your PR fulfills the following requirements:
Pull request type
Please check the type of change your PR introduces:
Issue Number: GTC-2851
What is the new behavior?
Add option to export COGs to GEE by created copy to GCS and creating a COG-backed asset using the GEE API.
COGs are stored in the forma-250 GCS project in the bucket
data-api-gee-assets
. They have the naming convention{dataset}/{implementation}.tif
. The GEE assets are in the forma-250 GEE project with the asset ID{dataset}/{implementation}
.I didn't implement versioning to start with, since that might quickly use up a lot of space in GCS/GEE and would be confusing to GEE users. So for now, assuming the asset is simply using the latest version in the API. I'm thinking we can revisit this in the future if there's a use case for better versioning.
Does this introduce a breaking change?
Other information