feat: add zarr store - #89
Conversation
Code CoverageDetailsDiff against mainResults for commit: d74acfb Minimum allowed coverage is ♻️ This comment has been updated with latest results |
6b4ae98 to
ab0855e
Compare
|
Currently, we only have DanubeHis and no other provider supporting Zarr, so it is difficult to properly test this part. I will continue once we add another provider that supports Zarr. The Zarr endpoint still needs to be implemented, along with the related tests. |
|
I do not understand why fsspec, aiohttp and requests dependencies are needed here. |
ebb5e6c to
fe4b763
Compare
Code CoverageDetailsDiff against mainResults for commit: 5c1aef6 Minimum allowed coverage is ♻️ This comment has been updated with latest results |
|
requires changes from CS-SI/eodag#2112 |
branch is merged in EODAG -> PR is now ready |
This PR improves the way Zarr stores are exposed and accessed through the /data endpoint, allowing Zarr data to be accessed in a cloud-native way.
The endpoint
/data/{federation_backend}/{collection_id}/{item_id}/zarrexposes the Zarr store as an HTTP filesystem, follows the standard Zarr + fsspec access pattern. Clients can access the data remotely using common libraries such as zarr, xarray, or dask without downloading the full store.Exemple usage: