-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
drop_sel indices in dimension that doesn't have coordinates? #4658
Comments
I don't know of an easy way (which does not mean that there is none). Line 4038 in ff6b1f5
by |
dcherian
changed the title
question/feature request: how to drop indices in dimension that doesn't have coordinates?
drop_sel indices in dimension that doesn't have coordinates?
Dec 7, 2020
Can I work on this? |
Sure. PRs are always welcome! |
mesejo
added a commit
to mesejo/xarray
that referenced
this issue
Jan 17, 2021
- Use get_index(dim) in drop_sel - Add drop_isel
mesejo
added a commit
to mesejo/xarray
that referenced
this issue
Jan 17, 2021
- Use get_index(dim) in drop_sel - Add drop_isel
max-sixty
pushed a commit
that referenced
this issue
Jan 18, 2021
* Closes #4658 - Use get_index(dim) in drop_sel - Add drop_isel * address issues in PR * extract dict creation out of the loop
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
I am trying to drop particular indices from a dimension that doesn't have coordinates.
Following: drop_sel() documentation,
but leaving out the coordinate labels:
gives me an error.
Describe the solution you'd like
I would think
drop_isel
should exist and work in analogy todrop_sel
asisel
does tosel
.Describe alternatives you've considered
As far as I know, I could either create coordinates especially to in order to drop, or rebuild a new dataset. Both are not congenial. (I'd be grateful to know if there is actually a straightforward way to do this I've overlooked.
The text was updated successfully, but these errors were encountered: