-
Notifications
You must be signed in to change notification settings - Fork 0
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
New Dataset: GPM IMERG Zarr Pyramid #128
Comments
@abarciauskas-bgse This collection is available in our staging catalog: Let me know if there are any changes that need to be made. |
@ividito thank you for working on this - that link is to the existing CMIP6 kerchunk dataset, is there another link for |
Sorry about that @abarciauskas-bgse, it was the wrong link. Correct link here: https://staging-stac.delta-backend.com/collections/GPM_3IMERGDF_zarr |
@ividito sorry for the additional work but could we actually remove this dataset? We have decided to deprioritize the zarr pyramid support for now, as it's not a current request of VEDA. |
Contact Details
[email protected]
URL/DOI
No response
Data License Identifier
No response
Data Location
s3://nasa-eodc-public/GPM_3IMERGDF.07
Size Estimate
19.3 MiB
Number of Items
797
Description
Zarr pyramid for GPM IMERG dataset subset (June 1-8, 2000)
Collection Creation Notebook
https://github.com/developmentseed/stac-explorer/blob/main/notebooks/create-stac-for-cmr-collections.ipynb
Item Creation Notebook
n/a
Checklist
This is zarr data so these items do not apply
Files are valid COGs. Userio cogeo validate
COGs appear to be correctAny additional info you think is relevant, possibly including spatial or temporal subset if applicable?
Metadata:
The notebook for collection creation creates metadata for GPM IMERG itself. They pyramid metadata has important modifications:
"multiscale": true,
is a part of each renders object"url": "s3://nasa-eodc-public/GPM_3IMERGDF.07"
Data files (zarr store):
s3://nasa-eodc-public/
is a public bucket (in the SMCE VEDA AWS account). We could in theory publish the data from that bucket but I would assume there are or could be some configurations fors3://veda-data-store-staging
which we want use for this data (such as monitoring and access controls) if we are to publish it to the VEDA STAC API.To Do
The text was updated successfully, but these errors were encountered: