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/733#issuecomment-177036328,https://api.github.com/repos/pydata/xarray/issues/733,177036328,MDEyOklzc3VlQ29tbWVudDE3NzAzNjMyOA==,1217238,2016-01-30T01:06:59Z,2016-01-30T01:06:59Z,MEMBER,"At the very least, we should advertise this feature in the documentation. But given how surprising people find it, it might be even better to remove it...
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,129630652
https://github.com/pydata/xarray/issues/733#issuecomment-176863363,https://api.github.com/repos/pydata/xarray/issues/733,176863363,MDEyOklzc3VlQ29tbWVudDE3Njg2MzM2Mw==,1217238,2016-01-29T17:04:44Z,2016-01-29T17:04:44Z,MEMBER,"This is an unadvertised feature, though I agree that it may be more trouble than it's worth -- xarray implicitly creates coordinates like `range(n)` when coordinates corresponding to a dimension are missing from the netCDF file.

The original intent (see https://github.com/pydata/xarray/pull/245) was for more faithful roundtripping of netCDF files, which may not have all coordinate variables defined. Arguably, it would make more sense to only do this when a certain `encoding` parameter is found (e.g., `{'trivial_index': True}`), indicating that xarray created the coordinate itself.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,129630652