Skip to content
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

Allow datetime.timedelta coordinates. #55

Closed
akleeman opened this issue Mar 7, 2014 · 4 comments · Fixed by #292
Closed

Allow datetime.timedelta coordinates. #55

akleeman opened this issue Mar 7, 2014 · 4 comments · Fixed by #292

Comments

@akleeman
Copy link
Contributor

akleeman commented Mar 7, 2014

This would allow you to have coordinates which are offsets from a time coordinates which comes in handy when dealing with forecast data where the 'time' coordinate might be the forecast run time and you then want a 'lead' coordinate which is an offset from the run time.

@shoyer
Copy link
Member

shoyer commented Mar 8, 2014

In fact, I have a fix for this in #54. See utils.safe_cast_to_index.

@shoyer
Copy link
Member

shoyer commented Mar 8, 2014

It would be useful, however, to have automatic encoding/decoding of such variables to NETCDF.

@shoyer
Copy link
Member

shoyer commented May 16, 2014

For a full solution, it would be great if pandas included a TimeDeltaIndex so we don't have to use an index with dtype=object. Here is the pandas issue: pandas-dev/pandas#3009

@shoyer
Copy link
Member

shoyer commented Oct 9, 2014

pandas.TimedeltaIndex will finally arrive in the next version of pandas. It would be nice to support it with properly encoding/decoding.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants