Tobias Kölling

Thanks @rly for coming back on this. I agree, this issue still persists and might become worse in Zarr v3. There's another aspect which might be problematic: From [CF-Conventions §2.5.1](http://cfconventions.org/Data/cf-conventions/cf-conventions-1.11/cf-conventions.html#missing-data):...

Yes, I'd agree the core issue is: xarray treats zarr's `fill_value` as `NaN`, unconditionally. In many cases, that is a really bad behavior. With the recent discussion, I guess I...

> Here's an idea: for V3 arrays (and maybe even also V2), we can use the `_FillValue` attribute for this. Rather than removing it from the attrs I'd vote for...

I just stumbled across this, having a similar use case. For now, using 0.3.3 seems to be fine for me as well.

I completely agree. There's a large overlap and that CF-based time handling will work on top of the current zarr variant. If zarr should opt for not handling dates and...

For reference, I discovered that more proper handling of leap seconds is already discussed since quite a while by the CF community in cf-convention/cf-conventions#148. As that issue seems to progress...

I am playing around a bit with zarr on top of [IPFS](https://ipfs.io) and have a use case similar to what @agstephens wrote: distributing datasets globally where only some nodes store...

I just had another thought about the idea of making a content id available to higher level APIs and tracking it through computations: If there would be a mechanism for...

My current understanding of how things in a Browser work roughly is: you simply can't do any blocking wait for doing any IO or waiting for other "threads" (web workers)....

I didn't know that a synchronous request actually exists in the Web (but [XMLHttpRequest.open()](https://developer.mozilla.org/de/docs/Web/API/XMLHttpRequest#open) with `async=False` clearly is one). Based on this it should be relatively easy to build a...