Just an idea, but what if we were to have a small STAC-GeoParquet catalog for these datasets? I think that could provide a few nice benefits:
- showing how to visualize the data from a STAC catalog matches typical use cases in the VEDA ecosystem better than from a URL as far as I can tell
- it would serve as an example of how to use STAC well with Zarr/Icechunk, following on from the guidance that Julia put together last year
- we could use the catalog for other, non-visualization use-cases
I guess the downsides are yet another STAC catalog and a bit more work relative to just testing URLs
Originally posted by @maxrjones in #384
We now have a set of virtual datasets that should be published to STAC so that they are easily discoverable for demonstration purposes and to prototype integration for future VEDA instances and services to utilize them.
Here is the guidance Julia wrote about how to publish Zarr datasets to STAC: https://guide.cloudnativegeo.org/cookbooks/zarr-stac-report/data-producers. I am curious @maxrjones if you think we should publish all of the underlying files as STAC items (ref: https://guide.cloudnativegeo.org/cookbooks/zarr-stac-report/data-producers/#virtual-dataset-in-an-external-file). At least, in the case of collections already published in CMR, we could point to a CMR query which returns all the associated underlying files.
To facilitate access, I would assume we would want to use the datacube and providers extension. I was also curious if there is an extension to store information about how to authenticate + authorize for access. A quick google search led me to https://github.com/stac-extensions/authentication whose most recent contributor is our very own @alukach 🎉
Datasets:
Any others I am missing? @siddharth0248
Originally posted by @maxrjones in #384
We now have a set of virtual datasets that should be published to STAC so that they are easily discoverable for demonstration purposes and to prototype integration for future VEDA instances and services to utilize them.
Here is the guidance Julia wrote about how to publish Zarr datasets to STAC: https://guide.cloudnativegeo.org/cookbooks/zarr-stac-report/data-producers. I am curious @maxrjones if you think we should publish all of the underlying files as STAC items (ref: https://guide.cloudnativegeo.org/cookbooks/zarr-stac-report/data-producers/#virtual-dataset-in-an-external-file). At least, in the case of collections already published in CMR, we could point to a CMR query which returns all the associated underlying files.
To facilitate access, I would assume we would want to use the datacube and providers extension. I was also curious if there is an extension to store information about how to authenticate + authorize for access. A quick google search led me to https://github.com/stac-extensions/authentication whose most recent contributor is our very own @alukach 🎉
Datasets:
Any others I am missing? @siddharth0248