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/3390#issuecomment-650903191,https://api.github.com/repos/pydata/xarray/issues/3390,650903191,MDEyOklzc3VlQ29tbWVudDY1MDkwMzE5MQ==,1053153,2020-06-29T04:52:11Z,2020-06-29T04:52:11Z,CONTRIBUTOR,"> What about the case of no missing values, when other wouldn't be needed?
> Could the same dtype be returned then? This is my case, since I'm
> re-purposing where to do sel for non-dimension coordinates.
>
> Could you give a concrete example of what this would look like?
>
> It seems rather unlikely to me to have an example of where with drop=True
> where the condition is *exactly* aligned with the grid, such that there
> are no missing values.
>
> I guess it could happen if you're trying to index out exactly one element
> along a dimension?
>
That's exactly right.  I am just selecting one slice of a data array, using
`data.where(data.coords['stain'] == 'DAPI')`.

> In the long term, the cleaner solution for this will be some form for
> support for more flexibly / multi-dimensional indexing.
>
Agreed.  Once I actually get things running, I'll be ready to try and
contribute fixes for all my TODOs that reference xarray github issues.  :)
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,505493879
https://github.com/pydata/xarray/issues/3390#issuecomment-650889746,https://api.github.com/repos/pydata/xarray/issues/3390,650889746,MDEyOklzc3VlQ29tbWVudDY1MDg4OTc0Ng==,1053153,2020-06-29T03:49:27Z,2020-06-29T03:49:27Z,CONTRIBUTOR,"What about the case of no missing values, when `other` wouldn't be needed?  Could the same `dtype` be returned then?  This is my case, since I'm re-purposing `where` to do `sel` for non-dimension coordinates.

I'm capable of just recasting for my use case, if this is becoming an idea that would be difficult to maintain/document.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,505493879
https://github.com/pydata/xarray/issues/3390#issuecomment-649861589,https://api.github.com/repos/pydata/xarray/issues/3390,649861589,MDEyOklzc3VlQ29tbWVudDY0OTg2MTU4OQ==,1053153,2020-06-25T23:08:52Z,2020-06-25T23:37:47Z,CONTRIBUTOR,"If `drop=True`, would it be problematic to return the same dtype or allow `other`?

My use case is a simple slicing of a dataset -- no missing values.   The use of `where` is due to one of selections being on a non-dimension coordinate (#2028).  

I can workaround using `astype`, but will say I was mildly surprised by this feature.  I now understand why it's there.  Our code is old and the data is intermediate and never deeply inspected -- I only noticed this when we started using a memory-intensive algorithm and surprised how much space was taken by our supposed uint16 data.  :)","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,505493879