You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We implemented the pointwise indexing methods (isel_points and sel_points) before we had MultiIndex support. Would it make sense to update these methods to return objects with coordinates defined as a MultiIndex?
If we can finish up @fujiisoup's work (#1473) bringing indexing with broadcasting to xarray, then we can possibly do away with sel_points and isel_points instead.
This doesn't resolve the issue of whether the indexed coordinates should be in a MultiIndex or not. This does make a certain amount of sense, but to be honest, I'm a little divided here -- I'm still not entirely happy with how MultiIndex works in xarray (see #1426 for more discussion).
We implemented the pointwise indexing methods (
isel_points
andsel_points
) before we had MultiIndex support. Would it make sense to update these methods to return objects with coordinates defined as a MultiIndex?Current behavior:
yields:
Maybe it makes sense to return an object with a MultiIndex like:
xref: #214, #475, #507
The text was updated successfully, but these errors were encountered: