Skip to content
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

Support for zarr over fsspec reference ? #64

Open
steph-ben opened this issue Apr 28, 2022 · 1 comment
Open

Support for zarr over fsspec reference ? #64

steph-ben opened this issue Apr 28, 2022 · 1 comment

Comments

@steph-ben
Copy link

Thanks for this beautiful lib !

I try to use it with zarr generated with https://github.com/fsspec/kerchunk , which make usage of fsspec "Reference filesystem" . It allows indexing of existing NetCDF/GRIB files, than can be then loaded as a single dataset.

Eg. with python xarray I can load a zarr dataset with :

rpath = 's3://esip-qhub-public/noaa/hrrr/hrrr_best.json'
fs = fsspec.filesystem("reference", fo=rpath, remote_protocol='s3', remote_options={'anon':True})
ds = xr.open_dataset(fs.get_mapper(""), engine="zarr")

See this notebook for example

However it doesn't seem to be supported by this lib, I'm having the following error :

  • With S3 file : CORS error
  • With HTTP file : .zmetadata not found

Not much details here, but maybe you have some thoughts on this topic ?

@jhamman
Copy link

jhamman commented May 31, 2022

Hi @steph-ben - thanks for opening this issue. At present, zarr-js, which we use to read zarr data over http, does not have support for fsspec's reference filesystem.

Another issue issue to consider for you application is that datasets used by @carbonplan/maps need to be reprojected into multiscale web-mercator quad-trees. A typical processing workflow would be: fsspec->xarray->ndpyramid->zarr. You might want to check out ndpyramid's examples for how we've done this in the past.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants