xarray-contrib / xarray-contrib/pint-xarray

improvements for the `PintIndex`

Open
#268 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
119
Forks
15
PR merge metrics
No merged PRs in 30d

Description

This is a list of tasks we skipped in #163:

  • figure out how to properly recreate an index from changed coordinates (#269)
  • modify the IndexSelResult returned by the wrapped index' .sel
  • implement concat
  • implement stack and unstack
  • implement join
  • implement reindex_like
  • figure out how to best compare indexes with compatible but not identical units

For each of the methods, we also need to see if we can deprecate any of the workaround methods in the .pint namespace.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the skipped work from #163 and the changed-coordinate case in #269. Then examine PintIndex and its .sel behavior alongside the listed operations: concat, stack, unstack, join, and reindex_like. Done means implementing the agreed index behavior, resolving compatible-unit comparisons, and identifying obsolete .pint workaround methods.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.