Skip to content

don't use fill_value for coords

Tobias Koelling requested to merge coords_no_fill_value into main

Coords shouldn't have missing values and according to the zarr v2 specification, null / None does just that.

The previous value of 0 is a really bad choice, because that's a common valid value for coordinates and thus leads to missing values in the resulting datasets.

fixes #9 (closed)

Merge request reports