home / github / issues

Menu
  • GraphQL API
  • Search all tables

issues: 152888663

This data as json

id node_id number title user state locked assignee milestone comments created_at updated_at closed_at author_association active_lock_reason draft pull_request body reactions performed_via_github_app state_reason repo type
152888663 MDExOlB1bGxSZXF1ZXN0Njg3ODU0NzM= 842 Fix #665 decode_cf_timedelta 2D 950575 closed 0     8 2016-05-03T22:26:34Z 2016-05-14T00:36:12Z 2016-05-04T17:11:59Z CONTRIBUTOR   0 pydata/xarray/pulls/842

Long time listener first time caller :wink:

I am not 100% about this PR though. I think that there are cases when we need the actual data rather than the timedelta. In this notebook we have wave period ('mper') that should be seconds ranging 0-30 and not those big numpy timedelta numbers.

I know that I can get that behavior with decode_times=True when opening the dataset, but then the time coordinate get decoded as well. (Maybe I am way off and there is a way to do this.)

{
    "url": "https://api.github.com/repos/pydata/xarray/issues/842/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
    13221727 pull

Links from other tables

  • 0 rows from issues_id in issues_labels
  • 8 rows from issue in issue_comments
Powered by Datasette · Queries took 0.832ms · About: xarray-datasette