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

Tracking Issue: Sync GCS holdings to AWS S3 #134

Open
jbusecke opened this issue Apr 24, 2024 · 1 comment
Open

Tracking Issue: Sync GCS holdings to AWS S3 #134

jbusecke opened this issue Apr 24, 2024 · 1 comment

Comments

@jbusecke
Copy link
Collaborator

I set up this issue to keep track of efforts to sync the ingested data to AWS S3.

Feedback very welcome and more details and discussions coming soon.

@Balinus
Copy link

Balinus commented Sep 26, 2024

Can a warning be added directly on the AWS Zarr store? Currently, Zarr store is first between the zarr and netcdf store files. We had the impression it was the favored way to get the data. There is also no warning that the sync is broken.

https://registry.opendata.aws/cmip6/

Cheers!

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

No branches or pull requests

2 participants