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/pull/589#issuecomment-146371615,https://api.github.com/repos/pydata/xarray/issues/589,146371615,MDEyOklzc3VlQ29tbWVudDE0NjM3MTYxNQ==,1217238,2015-10-08T00:06:57Z,2015-10-08T00:06:57Z,MEMBER,"@jhamman I think fixed the things you pointed out.

@ocefpaf I agree with you about `decode_cf`. I'm going to leave the current name for now, but we should change/deprecate it in v0.7.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,108271509
https://github.com/pydata/xarray/pull/589#issuecomment-143334183,https://api.github.com/repos/pydata/xarray/issues/589,143334183,MDEyOklzc3VlQ29tbWVudDE0MzMzNDE4Mw==,1217238,2015-09-25T19:40:33Z,2015-09-25T19:40:33Z,MEMBER,"I believe fill values, packing/unpacking and time units are all included in CF conventions by reference, but I agree that the name `decode_cf` may be confusing. The issue is that I want a practical single option for `open_dataset` that can disable all of xray's decoding options (which don't always work), just so the data can be examined. These conventions include NUG, COORDS, CF and even some xray specific conventions (so far, only for encoding coordinates without data variables).

 Perhaps rather than `decode_cf=True`, we should have `raw=False` or `decode=True`?
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,108271509
https://github.com/pydata/xarray/pull/589#issuecomment-143299023,https://api.github.com/repos/pydata/xarray/issues/589,143299023,MDEyOklzc3VlQ29tbWVudDE0MzI5OTAyMw==,1217238,2015-09-25T17:40:36Z,2015-09-25T17:40:36Z,MEMBER,"@ocefpaf could you elaborate a little bit on why you think `encoding` could be confusing to Pythonistas? To me, the word makes sense because the data can be ""coded"" on disk according to various conventions and compression settings. This is similar to the situation with Unicode strings and bytes -- you can encode Unicode in various ways into bytes.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,108271509