home / github / issue_comments

Menu
  • GraphQL API
  • Search all tables

issue_comments: 163748764

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/674#issuecomment-163748764 https://api.github.com/repos/pydata/xarray/issues/674 163748764 MDEyOklzc3VlQ29tbWVudDE2Mzc0ODc2NA== 5635139 2015-12-10T21:04:18Z 2015-12-10T21:18:08Z MEMBER

I don't see any obvious reason reason why coords should be treated differently than data_vars as far as data alignment in the Dataset constructor goes.

Two possibilities: 1. coords would take precedence, and all the DataArrays would be aligned to those. This is equivalent to the second example where arrays are added on with __setitem__ after construction 2. Everything is aligned with an outer join, nothing takes precedence (which I think means the constructor can never fail for alignment reasons)

I would favor (1), since you can be explicit about what coords you want to end up with; if you don't have a preference, you can neglect to supply coords and get the outer join.

But it sounds like you may favor (2)?

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