id,node_id,number,title,user,state,locked,assignee,milestone,comments,created_at,updated_at,closed_at,author_association,active_lock_reason,draft,pull_request,body,reactions,performed_via_github_app,state_reason,repo,type
654889988,MDU6SXNzdWU2NTQ4ODk5ODg=,4215,setting variables named in CF attributes as coordinate variables,2448579,closed,0,,,5,2020-07-10T16:17:08Z,2021-04-19T03:32:02Z,2021-04-19T03:32:02Z,MEMBER,,,,"This came up in #2844 by @DWesl (see also #3689)

Currently we have `decode_coords` which sets variables named in `attrs[""coordinates""]` as coordinate variables.

There are a number of other CF attributes that can contain variable names.
1. bounds
1. grid_mapping
1. ancillary_variables
1. cell_measures
1. maybe more?

 As in #3689 it's hard to see why a lot of these variables named in these attributes would be useful as ""data variables"".

**Question**: Should we allow `decode_coords` to control whether variables mentioned in these attributes are set as coordinate variables?

cc @jthielen ","{""url"": ""https://api.github.com/repos/pydata/xarray/issues/4215/reactions"", ""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,completed,13221727,issue