Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create Python script to export to GEE #545

Merged
merged 4 commits into from
Jun 17, 2024
Merged

Conversation

jterry64
Copy link
Member

Pull request checklist

Please check if your PR fulfills the following requirements:

  • Make sure you are requesting to pull a topic/feature/bugfix branch (right side). Don't request your master!
  • Make sure you are making a pull request against the develop branch (left side). Also you should start your branch off our develop.
  • Check the commit's or even all commits' message styles matches our requested structure.
  • Check your code additions will fail neither code linting checks nor unit test.

Pull request type

Please check the type of change your PR introduces:

  • Bugfix
  • Feature
  • Code style update (formatting, renaming)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • Documentation content changes
  • Other (please describe):

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?

  • Yes
  • No

Other information

@codecov-commenter
Copy link

codecov-commenter commented Jun 13, 2024

Codecov Report

Attention: Patch coverage is 75.00000% with 1 line in your changes missing coverage. Please review.

Project coverage is 82.03%. Comparing base (b51894a) to head (ba51066).

Files Patch % Lines
app/tasks/cog_assets.py 50.00% 1 Missing ⚠️

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #545      +/-   ##
===========================================
- Coverage    82.03%   82.03%   -0.01%     
===========================================
  Files          126      126              
  Lines         5662     5665       +3     
===========================================
+ Hits          4645     4647       +2     
- Misses        1017     1018       +1     
Flag Coverage Δ
unittests 82.03% <75.00%> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@jterry64 jterry64 merged commit 070e63e into develop Jun 17, 2024
2 checks passed
@jterry64 jterry64 deleted the gtc-2851/export_cogs_to_gee branch June 17, 2024 15:59
@manukala6 manukala6 mentioned this pull request Jul 1, 2024
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants