issue_comments: 658344415

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/4215#issuecomment-658344415 https://api.github.com/repos/pydata/xarray/issues/4215 658344415 MDEyOklzc3VlQ29tbWVudDY1ODM0NDQxNQ== 2448579 2020-07-14T18:36:37Z 2020-07-14T18:37:17Z MEMBER

formula_terms might make more sense here: https://github.com/xarray-contrib/cf-xarray/issues/34

Is that "putting the variables in these attributes in coords is out of scope for XArray" or "putting the variables in these attributes in coords is out of scope for decode_coords" or something else?

I think this is "we should put things in coords without adding a new flag". It is a behaviour change though. So maybe we should starting issuing a warning now.

I would say no however to ancillary_variables, since those are not really about coordinates and instead about linked data variables (like uncertainties).

The only way to link variables in xarray objects is to set them as coords. So I think it still makes sense in xarray-world to do this.

should preserving encoding be a separate PR?

Separate PR. It will be a reasonably big change throughout the code base.

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