issue_comments: 269878256

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/issues/1084#issuecomment-269878256 https://api.github.com/repos/pydata/xarray/issues/1084 269878256 MDEyOklzc3VlQ29tbWVudDI2OTg3ODI1Ng== 1217238 2016-12-31T19:09:19Z 2017-01-01T00:18:20Z MEMBER

@spencerkclark

partial datetime string indexing would be a must

The good news here is that almost all this logic lives in pandas's Python code and should be straightforward to duplicate. I can point you to the relevant locations if you're having trouble figuring this out.

An additional requirement would be serialization to netCDF files.

It should be quite straightforward to integrate this into xarray's existing serialization logic.

From a mechanics perspective, do we want this sort of index to live totally inside xarray or should it be in a separate package?

We could go either way here, but for now I think it makes sense to keep this in xarray proper.

Here's why:

  • We already have a bunch of CF-conventions specific logic related to serialization in xarray. Logically it makes sense to keep this together.
  • This will be a strict improvement over xarray's current handling of netcdf time objects.
  • I suspect most users who are interested combining netCDF times and pandas (e.g., if they want to a NetCDFTimeIndex in a DataFrame) are already using xarray, or at least willing to install it.
 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   187591179