Add xarray-specific encoding convention for pd.IntervalArray #10483
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #2847
Following the proposal in #8005 (comment), this PR adds encoding/decoding machinery for
pd.IntervalArray
objects. I use an ad-hoc convention:__xarray_bounds__
. This is not configurable at the moment."closed"
, and"dtype"
(this is always"pandas_interval"
).It is possible to create an IntervalArray with Datetime and Timedelta objects so I've stuck the IntervalCoder first in the encoding pipeline, and last in the decoding pipeline. That way it stays independent.
TODO:
decode_intervals
kwarg?