home / github / issues

Menu
  • Search all tables
  • GraphQL API

issues: 112085412

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
112085412 MDU6SXNzdWUxMTIwODU0MTI= 628 Remove the encoding attribute from xray.DataArray? 1217238 closed 0     4 2015-10-19T07:11:36Z 2019-03-01T18:00:08Z 2019-03-01T18:00:08Z MEMBER      

As described in the dev version of our documentation on encoding, we now support a keyword argument for controlling how netCDF files are written to disk with to_netcdf: http://xray.readthedocs.org/en/latest/io.html#reading-encoded-data

We still retain the feature that there is an "encoding" dictionary that sticks around with xray Variable objects, which stores how they were compressed/encoded on disk. This can be occasionally handy. It means, for example, that we always write out netCDF files with the same time units as the files we read from disk.

It might make sense to eliminate this feature for the sake of significantly simplifying xray's internal data model. For cases where it really matters, users can now use the encoding keyword argument to to_netcdf instead. This would leave three attributes on the Variable object: dims, _data and attrs.

Thoughts?

{
    "url": "https://api.github.com/repos/pydata/xarray/issues/628/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  completed 13221727 issue

Links from other tables

  • 2 rows from issues_id in issues_labels
  • 4 rows from issue in issue_comments
Powered by Datasette · Queries took 0.657ms · About: xarray-datasette