issue_comments: 442906486

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-442906486 https://api.github.com/repos/pydata/xarray/issues/1603 442906486 MDEyOklzc3VlQ29tbWVudDQ0MjkwNjQ4Ng== 5635139 2018-11-29T16:46:52Z 2018-11-29T16:46:52Z MEMBER

And broadening out further:

Default behavior: all 1-dimensional coordinates each have their own, single index (pandas.Index), unless explicitly stated.

This is basically how I think of indexes - as a performant lookup data structure, rather than a feature of the schema. An RDBMS in a good corollary there.

Now, maybe there's enough overlap between the data access and the data schema that we should let them couple - e.g. would you want to be able to run .sel on any coord, even 2D? While it's possible in concept, it could guide users to inefficient operations.

We probably don't need to answer this question to proceed, but I'd be interested whether others see indexes as a property of the schema / I'm missing something.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   262642978