issue_comments: 624384220
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/4016#issuecomment-624384220 | https://api.github.com/repos/pydata/xarray/issues/4016 | 624384220 | MDEyOklzc3VlQ29tbWVudDYyNDM4NDIyMA== | 34353851 | 2020-05-06T00:54:38Z | 2020-05-06T00:54:38Z | NONE | I think another solution you could add an aleat microsecond or nanosecond field ... in the datetime index and the index should be different. You could test if there are colision in the index (it means the index<->time is not empty like the sort algorithm, something similar to https://en.wikipedia.org/wiki/Radix_sort) It is like the reverse of this solution Add another coordinate could be overloaded and xarray is very powerful to extract slice of time ds.sel(time =slice('2000-06-01', '2000-06-10')) http://xarray.pydata.org/en/stable/time-series.html#datetime-indexing I hope it could be useful. Regards Javier Ruano El mié., 29 abr. 2020 17:34, Javier Ruano javier.ruanno@gmail.com escribió:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
609108666 |