issue_comments: 143302566
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/pull/589#issuecomment-143302566 | https://api.github.com/repos/pydata/xarray/issues/589 | 143302566 | MDEyOklzc3VlQ29tbWVudDE0MzMwMjU2Ng== | 950575 | 2015-09-25T17:52:19Z | 2015-09-25T17:52:19Z | CONTRIBUTOR |
That comparison is what I meant. The concept is the same, as you said, but what comes to mind is the unicode/bytes situation and not netCDF compression and the various conventions. I guess that what I do not like in the docs is the fact that compression and conventions are bagged together as "encoding." I see compression as "encoding," but I cannot see all the conventions as encoding . Also, encoding or not, those are not CF rules to be called Anyway, the docs are good and understandable,. My comments above are just minor issues I have with CF, NUG, and netCDF writing. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
108271509 |