home / github / issue_comments

Menu
  • GraphQL API
  • Search all tables

issue_comments: 442902327

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/1603#issuecomment-442902327 https://api.github.com/repos/pydata/xarray/issues/1603 442902327 MDEyOklzc3VlQ29tbWVudDQ0MjkwMjMyNw== 5635139 2018-11-29T16:36:20Z 2018-11-29T16:36:20Z MEMBER

I broadly agree with @benbovy 's proposal.

One question that I think is worth being clear on is what additional contracts do multiple indexes on a dimension have over individual indexes?

e.g. re: Coordinates: * level_1 (x) object 'a' 'a' 'b' 'b' * level_2 (x) int64 1 2 1 2 Multi-indexes: pandas.MultiIndex [level_1, level_2]

Am I right in thinking the Multi-indexes is only a helpful note to users, rather than conveying anything about how data is accessed?

@fujiisoup 's poses a good case of this question:

ds.sel(multi=list_of_pairs) can probably be replaced by ds.sel(x=..., y=...), but how about reindex along MultiIndex?

(and separately, I think we can do much of this before adding the ability to set custom indexes, which would be cool but further from where we are, I think)

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