New Dataset: GPM IMERG Zarr Pyramid

Contact Details

aimee@developmentseed.org

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. Use rio cogeo validate
• COGs appear to be correct

Any 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:

• temporal extent in both the data cube extension and collection metadata is only for June 1-8, 2000
• "multiscale": true, is a part of each renders object
• The URL should be included in 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 for s3://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

• Open PR for publishing those datasets to the Staging API
• Notify QA / move ticket to QA state
• Once approved, merge and close