Tom Nicholas
Tom Nicholas
1000% that would be very useful. Then you can start changing things in your workflow to see if you can get it to "compile".
Thank you for writing this up @danielfromearth . > `earthaccess` currently processes datasets as a single list passed to `xr.combine_nested()` You could get around this by using VirtualiZarr directly. Soon...
_Some top-level comments._ > That seems less preferable in this case, because it would discard a sizable amount of valid measurement data. In this case, we want to avoid discarding...
It's unclear from your error report where virtualizarr is being invoked. But I suspect you could get past the error by adding whatever variable that error was raised on to...
> Is this use of loadable_variables unworkable then for this DMR++ case, or is there a way to still load the variable? I don't immediately know, sorry. Generally there isn't...
> But also I'm right in the middle of significantly refactoring how loadable_variables works (https://github.com/zarr-developers/VirtualiZarr/pull/477), and if you can wait until next week these issues might just all go away....
Actually the accessor syntax idea of having `ds.async.load()` is not possible because `async` is a reserved keyword in python, so `ds.async` raises a `SyntaxError`. So it would have to be...
This seems related and interesting: https://github.com/royerlab/czpeedy
My understanding is that with the `obstore` changes you don't need to use fsspec explicitly here, you just pass the path string
Oh sorry I must have misread your original report. Yeah IDK. @maxrjones ? @kylebarron 😅