home / github / issue_comments

Menu
  • Search all tables
  • GraphQL API

issue_comments: 217170260

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-217170260 https://api.github.com/repos/pydata/xarray/issues/844 217170260 MDEyOklzc3VlQ29tbWVudDIxNzE3MDI2MA== 1217238 2016-05-05T14:33:28Z 2016-05-05T14:33:28Z MEMBER

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".

On Thu, May 5, 2016 at 7:05 AM, Kyle Wilcox notifications@github.com wrote:

@ocefpaf https://github.com/ocefpaf I agree that xarray model consistent should take precedence. I also use this method to (mostly) pull out coordinate variables and can continue to use netCDF4.Dataset to do that.

— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/pydata/xarray/pull/844#issuecomment-217163460

{
    "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 1.296ms · About: xarray-datasette