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
The xr.Dataset constructed by open_virtual_dataset doesn't seem to correctly identify coordinates when the coordinate has more than one dimension. The bug seems to be in separate_coordson this line. The correct functionality could be to use the coordinates attribute within each variables .zattrs and maintain a set of all coordinate names
Note that the underlying kerchunk json does have this coordinate information since when you virtualize the dataset and materialize data, the coordinates are correct:
TomNicholas
changed the title
Missing xr.Coordinates from virtualized datasets
open_virtual_dataset returns some coordinates as data variables
Sep 16, 2024
The
xr.Dataset
constructed byopen_virtual_dataset
doesn't seem to correctly identify coordinates when the coordinate has more than one dimension. The bug seems to be inseparate_coords
on this line. The correct functionality could be to use thecoordinates
attribute within each variables.zattrs
and maintain a set of all coordinate namesHere is a reproducible example:
Note that the underlying kerchunk json does have this coordinate information since when you
virtualize
the dataset and materialize data, the coordinates are correct:The text was updated successfully, but these errors were encountered: