issue_comments: 697928722
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/issues/4452#issuecomment-697928722 | https://api.github.com/repos/pydata/xarray/issues/4452 | 697928722 | MDEyOklzc3VlQ29tbWVudDY5NzkyODcyMg== | 1217238 | 2020-09-23T19:34:48Z | 2020-09-23T19:34:48Z | MEMBER | I agree that there's is no good reason to use concat_characters for zarr, which supports normal fixed-width string datatypes. For netCDF, we do need concat_character for the "NC_CHAR" dtype, which is used to store strings in lieu of a true fixed width string dtype. It's ugly, but otherwise we won't be able to round-trip string dtype arrays from xarray into netCDF3 files. This note from NetCDF.jl does a nice job of explaining. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
707571360 |