home / github / issue_comments

Menu
  • Search all tables
  • GraphQL API

issue_comments: 217171905

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/pull/844#issuecomment-217171905 https://api.github.com/repos/pydata/xarray/issues/844 217171905 MDEyOklzc3VlQ29tbWVudDIxNzE3MTkwNQ== 950575 2016-05-05T14:40:09Z 2016-05-10T22:47:52Z CONTRIBUTOR

Well, if you guys are mostly excited about using this for coordinate variables, another consistent choice would be to return a list of matching DataArrays. But if we want to return a Dataset, we should only do data variables, because it's weird to lose all the describing coordinates when you match, e.g., standard_name="air_temperature".

We agree with you and I prefer to return a Dataset.

Right now we always go to netCDF4-python to do this low-level CF interpretation stuff. If we start using xarray for that task we should improve xarray, to take advantage of the conventions (CF/SGRID/UGRID), instead of using xarray to just find the coords data. (For example: creating the z coordinates from non-dimension coordinates and add that to the Dataset coords automatically.)

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