issues: 261403591
This data as json
| id | node_id | number | title | user | state | locked | assignee | milestone | comments | created_at | updated_at | closed_at | author_association | active_lock_reason | draft | pull_request | body | reactions | performed_via_github_app | state_reason | repo | type |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 261403591 | MDU6SXNzdWUyNjE0MDM1OTE= | 1598 | Need better user control of _FillValue attribute in NetCDF files | 23199378 | closed | 0 | 9 | 2017-09-28T17:44:20Z | 2017-10-26T05:19:30Z | 2017-10-26T05:19:30Z | NONE | This issue is under discussion here: https://github.com/pydata/xarray/pull/1165 It is not desirable for us to have _FillValue = NaN for dimensions and coordinate variables. In trying to use xarray, _FillValue was carefully kept from these variables and dimensions during the creation of the un-resampled file and then were found to appear during the to_netcdf operation. This happens in spite of mask_and_scale=False is being used with xr.open_dataset I would hope that downstream code would have trouble with coordinates that don't make logical sense (time or place being NaN, for instance). We would prefer NOT to instantiate coordinate variable data with any fill value. Keeping NaNs out of coordinate variables, dimensions and minima and maxima is part of our QA/QC process to avoid downstream issues. |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/1598/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
completed | 13221727 | issue |