home / github / issue_comments

Menu
  • Search all tables
  • GraphQL API

issue_comments: 145299557

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/605#issuecomment-145299557 https://api.github.com/repos/pydata/xarray/issues/605 145299557 MDEyOklzc3VlQ29tbWVudDE0NTI5OTU1Nw== 1217238 2015-10-03T23:44:07Z 2015-10-03T23:44:07Z MEMBER

My hesitation with adding coord_keys is two-fold: 1. This would make the xray data model more complex. I would really prefer to avoid this. 2. It's not clear to me that the order of names in the coordinates attribute is meaningful according to CF conventions: "The value of the coordinates attribute is a blank separated list of the names of auxiliary coordinate variables. There is no restriction on the order in which the auxiliary coordinate variables appear in the coordinates attribute string."

A better way to handle this might be to write a xray-cf packages (see #461 for another use case), which registers the .cf namespace on Dataset/DataArray objects. Then we could have ds.cf.plot, which automatically plots according to CF conventions, and could even do things like automatically plot with cartopy if relevant. This means less domain specific details in xray, and could be a good model for other similar extension projects (e.g., xgcm).

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  109589162
Powered by Datasette · Queries took 78.532ms · About: xarray-datasette