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
However those computed ranges do not seem to get exposed and are thus not really accessible. Nevertheless they are quite important when displaying the data. Thus I propose to utilize the attrs field of the xarray.DataArray (which can hold arbitrary metadata) to provide the (computed) ranges.
Essentially I want to get the following:
Thanks @muendlein, that is a good idea. I'd would be inclined to set the new range attributes regardless of whether they are computed or set by the user.
Currently the data bounds will computed during aggregation if the x or y ranges are not provided explicitely:
However those computed ranges do not seem to get exposed and are thus not really accessible. Nevertheless they are quite important when displaying the data. Thus I propose to utilize the
attrs
field of the xarray.DataArray (which can hold arbitrary metadata) to provide the (computed) ranges.Essentially I want to get the following:
The text was updated successfully, but these errors were encountered: