issue_comments: 42642338
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/112#issuecomment-42642338 | https://api.github.com/repos/pydata/xarray/issues/112 | 42642338 | MDEyOklzc3VlQ29tbWVudDQyNjQyMzM4 | 1217238 | 2014-05-09T08:04:52Z | 2014-05-09T08:04:52Z | MEMBER | Thanks for asking! Looking at CDAT, it does indeed appear that it has objects which are very similar in spirit to the xray Dataset and DataArray. I think some of the major distinguishing features of xray would be:
1. Design:
- xray is targeted at a broader audience: anyone who needs a labeled, multi-dimensional array. I would like to avoid tight coupling to any particular domain, and keep xray as a more generic analysis tool for working with labeled N-dimensional arrays.
- However, I'm sure that CDAT has some useful features and designs. If there are any particular aspects that you particular appreciate and think might belong in xray, I would be very interested to hear about them. Note: I found the source code for UV-CDAT on GitHub: https://github.com/UV-CDAT/uvcdat |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
32763132 |