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/32#issuecomment-36472462,https://api.github.com/repos/pydata/xarray/issues/32,36472462,MDEyOklzc3VlQ29tbWVudDM2NDcyNDYy,6509590,2014-03-02T23:55:51Z,2014-03-02T23:55:51Z,NONE,"Many thanks! I hadn't realized the `indexed_by` behavior for integer indexers - that's great. In that case my `__delitem__` suggestion becomes superfluous anyway, since what I described can be achieved by `indexed_by` as it appears.

The new polyglot aka xray looks very impressive - and the name is cool...
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,28575097
https://github.com/pydata/xarray/issues/32#issuecomment-36467822,https://api.github.com/repos/pydata/xarray/issues/32,36467822,MDEyOklzc3VlQ29tbWVudDM2NDY3ODIy,6509590,2014-03-02T21:33:17Z,2014-03-02T21:33:17Z,NONE,"Many thanks for the clarification. `np.squeeze` was used in slocum to remove a dimension that had been shrunk down to one value (then via `views`, now via `indexed_by`).  The idea was to get the resulting Dataset as small as possible before dumping it and sending it over a _very_ low bandwidth email link.  If a dimension with only one element (like `height_above_ground` in the example) can be neglected in terms of size impact, it's not worth the trouble with `np.squeeze`. Otherwise it would be nice to have it back.  Thanks in any case.

>  I think the right behavior would be to delete every variable that uses the dimension.

How about deleting it _from_ every variable that uses the dimension to be deleted, and only keep index 0 if there were multiple values along that dimension. That would seem closer to what happens in a n-dimensional coordinate system if I get rid of one axis?
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,28575097