issue_comments: 191697006
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/706#issuecomment-191697006 | https://api.github.com/repos/pydata/xarray/issues/706 | 191697006 | MDEyOklzc3VlQ29tbWVudDE5MTY5NzAwNg== | 10050469 | 2016-03-03T10:29:08Z | 2016-03-03T10:29:08Z | MEMBER | I find @shoyer 's suggestion about custom accessor attributes very interesting! the simplest of my use cases would be quite easy to implement: ``` python MyLibclass MyLibGis(object): def init(self, xray_obj): self.obj = xray_obj self.georef = read_georef(xray_obj)
xray.register_accessor('gis', MyLibGis) user codeimport mylib import xray ds = xray.DataArray(...) ds = ds.gis.subset(shapefile='/path/to/shape') ``` This would already be quite cool! But would the mechanism allow to pass arguments to the
I guess that with these two mechanisms, I would be able to do almost everything I want to do with my netcdf files. However, one other very important use case for me would be to add lazy "diagnostic" variables to a netcdf dataset. For example, if an atmospheric model output file contains the variables |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
124915222 |