You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am not entirely sure what the purpose of the .zmetadata file is and therefore I am not sure whether this is supposed to be written or not.
This is just something that is different when opening and saving one of the Geozarr examples.
I will add the link to the example datasets when I have a more reliable internet connection
The text was updated successfully, but these errors were encountered:
"Finally, it’s worth noting that Xarray writes (and attempts to read) “consolidated metadata” by default (the .zmetadata file), which is another non-standard Zarr extension, albeit one implemented upstream in Zarr-Python. You do not need to write consolidated metadata to make Zarr stores readable in Xarray, but because Xarray can open these stores much faster, users will see a warning about poor performance when reading non-consolidated stores unless they explicitly set consolidated=False. See Consolidated Metadata for more details."
I am not entirely sure what the purpose of the .zmetadata file is and therefore I am not sure whether this is supposed to be written or not.
This is just something that is different when opening and saving one of the Geozarr examples.
I will add the link to the example datasets when I have a more reliable internet connection
The text was updated successfully, but these errors were encountered: