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/1017#issuecomment-255029826,https://api.github.com/repos/pydata/xarray/issues/1017,255029826,MDEyOklzc3VlQ29tbWVudDI1NTAyOTgyNg==,832092,2016-10-20T07:28:24Z,2016-10-20T07:28:24Z,NONE,"> I think we want the error here, given that this is one of the major motivations for allowing missing coordinate labels (not assuming invalid labels).

Yes. But, in that case you need a way to do the ""fill with NAN"" option without having to jump through too many hoops. How would you do that?
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,179052741
https://github.com/pydata/xarray/pull/1017#issuecomment-254727789,https://api.github.com/repos/pydata/xarray/issues/1017,254727789,MDEyOklzc3VlQ29tbWVudDI1NDcyNzc4OQ==,832092,2016-10-19T06:57:23Z,2016-10-19T06:57:23Z,NONE,"I have never encountered this case yet but ignoring that dimension seems like a bad idea to me. When I use a.reindex_like(b), I usually mean ""make a compatible with b"", so I assume the resulting index **and shape** is the same than (or at least compatible with) b. More importantly, I expect to be able to do binary operations between the re-indexed a and b. Ignoring the index like you propose would break that.

Given that, I would go with either an error, or treat the missing index like it was range() in this case, ie fill the extra values with NAN. I think I would have a slight preference for the later in my own code (wildcard axes), but in xarray I am unsure. The error might be more coherent.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,179052741
https://github.com/pydata/xarray/pull/1017#issuecomment-249785809,https://api.github.com/repos/pydata/xarray/issues/1017,249785809,MDEyOklzc3VlQ29tbWVudDI0OTc4NTgwOQ==,832092,2016-09-27T07:20:04Z,2016-09-27T07:21:02Z,NONE,"@shoyer Honestly, I have not thought that part (keep the tick labels for subsets) through (since I did not encounter an actual use case for that yet), I was more or less dumping my thought process in case you can make something useful out of it :). Nevertheless, those labels would not necessarily be non-sensical. In your image example above, it seems to me that knowing that the region of the image you are using comes (for example) from the center-right of the original image could be useful information. As for conveying that the dimension is special, I use a ""*"" next to the axis name to convey that it is a wildcard axis. It seems to go well with my current users.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,179052741
https://github.com/pydata/xarray/pull/1017#issuecomment-249498700,https://api.github.com/repos/pydata/xarray/issues/1017,249498700,MDEyOklzc3VlQ29tbWVudDI0OTQ5ODcwMA==,832092,2016-09-26T07:31:25Z,2016-09-26T07:31:25Z,NONE,"FWIW, I solved this issue in a slightly different way in my own labelled array project (https://github.com/liam2/larray) (that I still hope to one day merge with xarray -- I will probably need to rewrite my project on top of xarray because the ship as sailed concerning the user-facing API): by default, you get ""wildcard"" axes, which only have a size and no labels (they do get a range() labels on demand, so you can .sel on that dimension -- to speak in xarray vocabulary). Those wildcard labels are not as picky as normal labels: a wildcard axis compares equal/aligns to other axes as long as it has the same length. In practice, I guess it will be very similar to not having an index at all (and it is probably cleaner this way, but I didn't think of that at the time). All of this to say that yes, this PR is definitely a good idea and would make xarray useful in more situations, as I have hit a lot of cases where real range() labels like you have now made things a lot more painful than necessary. 

The only advantage I can think of now (except it was easier for me to implement it this way) of having a ""wildcard axis"" instead of no index/labels at all is that a subset could keep the information about which ""tick"" it comes from (again without blocking alignment). Not sure it's worth it though (I have actually not implemented it this way yet, but I was contemplating doing so).
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,179052741