home / github / issue_comments

Menu
  • GraphQL API
  • Search all tables

issue_comments: 1527918654

This data as json

html_url issue_url id node_id user created_at updated_at author_association body reactions performed_via_github_app issue
https://github.com/pydata/xarray/issues/7790#issuecomment-1527918654 https://api.github.com/repos/pydata/xarray/issues/7790 1527918654 IC_kwDOAMm_X85bEjA- 14983768 2023-04-28T18:08:16Z 2023-04-28T18:08:16Z NONE

The zarr store does indeed use an integer in this case according to the .zmetadata file: { "metadata": { ".zattrs": {}, ".zgroup": { "zarr_format": 2 }, "time/.zarray": { "chunks": [ 2 ], "compressor": { "blocksize": 0, "clevel": 5, "cname": "lz4", "id": "blosc", "shuffle": 1 }, "dtype": "<i8", "fill_value": -25567, "filters": null, "order": "C", "shape": [ 2 ], "zarr_format": 2 }, "time/.zattrs": { "_ARRAY_DIMENSIONS": [ "time" ], "calendar": "proleptic_gregorian", "units": "days since 1900-01-01 00:00:00" } }, "zarr_consolidated_format": 1 } Once again the values in the zarr store are correct given the units, but xarray misreads the fill value for some reason: python z_new_fill = zarr.open('from_xarray_new_fill.zarr','r') z_new_fill["time"][:] array([ 0, 44926])

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  1685803922
Powered by Datasette · Queries took 0.899ms · About: xarray-datasette