issue_comments: 789773514

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/pull/4979#issuecomment-789773514 https://api.github.com/repos/pydata/xarray/issues/4979 789773514 MDEyOklzc3VlQ29tbWVudDc4OTc3MzUxNA== 2448579 2021-03-03T14:57:19Z 2021-03-03T16:46:07Z MEMBER

There are also high-level methods that could use indexes in non-trivial ways. These methods become complicated when considering nD versions of IntervalIndex (or CellIndex that represents the appropriate bounds variable, https://github.com/pydata/xarray/issues/1475). I'm raising these so we can define the scope of the API.

  1. resample (CFTimeIndex and a DatetimeIntervalIndex)
  2. DatetimeAccessor & TimedeltaAccessor properties (CFTimeIndex and a DatetimeIntervalIndex)
  3. interp & interpolate_na,
  4. with IntervalIndex, these become regridding operations. Should we support hooks for these operations?
  5. differentiate, integrate, polyfit
  6. raise an error if not a "simple" 1D index?
  7. pad
  8. coarsen has to make choices about output index labels.
  9. sortby
  10. plotting
    1. plot.pcolormesh "infers" interval breaks along axes, which are really inferred bounds for the appropriate indexes.
    2. plot.step again uses bounds. In fact, we may even want step to be the default 1D plotting function if the axis has bounds attached.

Another perhaps-unintended use-case is that various accessors will try to use .indexes to cache state (https://github.com/pydata/xarray/issues/3268#issuecomment-539463105).

An example is CRSIndex, where the crs applies to all variables in a dataset but isn't associated with a dimension on any of the other variables (Maybe this is a good definition for a PropertyIndex). This would be used by rioxarray, salem and friends. Also consider a possible XgcmIndex that basically contains an Xgcm.Grid object (also satisfies the PropertyIndex definition). We would want to propagate such PropertyIndexes in all operations, and also optionally check them during alignment (?).

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