-
Notifications
You must be signed in to change notification settings - Fork 374
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
Move file hosting to S3 via AWS public dataset #445
Comments
AWS Public Dataset approval has been granted. Need to setup new org and S3 bucket next (with CW logging enabled for analytics), post files, update the download manager, and document direct S3 download links. |
The S3 bucket has been setup and initial data transfer of v4 released files has kicked off. |
This is great news! What is the status of documentation? I'd suggest making a registry entry that documents these buckets. I think you can just fork the registry repo, add a yaml file with meta data, and make a PR. The biggest commitment is filling in the template. https://registry.opendata.aws/ thanks for all you do! |
The related PR (WIP) is awslabs/open-data-registry#853. |
That PR is ready to merge now. But looking at the path structure of the S3 bucket it has |
The AWS public data registry PR has been merged and the data is live. But it needs a little bit more automation for updates, and really versioned releases. |
I'm adding the missing 10m and 50m rasters now. |
Versioned will live in dirs like:
And latest stable release will live at the root: The same will be true for the naciscdn links:
And latest stable release will live at the root: |
The data has been hosted by FSU (huge thank you!) for the last 11 years.
NACIS (Natural Earth's formal project sponsor) is in discussions with AWS to host the data files in their public dataset program.
The text was updated successfully, but these errors were encountered: