issue_comments: 660180546

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/4234#issuecomment-660180546 https://api.github.com/repos/pydata/xarray/issues/4234 660180546 MDEyOklzc3VlQ29tbWVudDY2MDE4MDU0Ng== 2448579 2020-07-17T15:46:15Z 2020-07-17T15:46:15Z MEMBER

See similar discussion for sparse here: https://github.com/pydata/xarray/issues/3245

asarray makes sense to me.

I think we are also open to special as_sparse, as_dense, as_cupy that return xarray objects with converted arrays.

A to_numpy_data method (or as_numpy?) would always coerce to numpy appropriately.

IIRC there's some way to read from disk to GPU, isn't there? So it makes sense to expose that in our open_* functions.

Re: index variables.Can we avoid this for now? Or are there going to be performance issues? The general problem will be handled as part of the index refactor (we've deferred pint support for indexes for this reason).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   659129613