issue_comments

Table actions

6 rows where issue = 99847237 and user = 1197350 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 1

  • rabernat · 6 ✖

issue 1

  • Fix datetime decoding when time units are 'days since 0000-01-01 00:00:00' · 6 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
131178257 https://github.com/pydata/xarray/pull/523#issuecomment-131178257 https://api.github.com/repos/pydata/xarray/issues/523 MDEyOklzc3VlQ29tbWVudDEzMTE3ODI1Nw== rabernat 1197350 2015-08-14T16:51:27Z 2015-08-14T16:51:27Z MEMBER

I am the least knowledgeable person here regarding numpy and pandas development. The issues should probably be opened by someone else.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Fix datetime decoding when time units are 'days since 0000-01-01 00:00:00' 99847237
131109207 https://github.com/pydata/xarray/pull/523#issuecomment-131109207 https://api.github.com/repos/pydata/xarray/issues/523 MDEyOklzc3VlQ29tbWVudDEzMTEwOTIwNw== rabernat 1197350 2015-08-14T13:43:32Z 2015-08-14T13:43:32Z MEMBER

Regarding the non-standard calendar support, is it worth opening issues in numpy / pandas?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Fix datetime decoding when time units are 'days since 0000-01-01 00:00:00' 99847237
131095419 https://github.com/pydata/xarray/pull/523#issuecomment-131095419 https://api.github.com/repos/pydata/xarray/issues/523 MDEyOklzc3VlQ29tbWVudDEzMTA5NTQxOQ== rabernat 1197350 2015-08-14T12:43:47Z 2015-08-14T12:43:47Z MEMBER

Ok, thanks for the thoughtful discussion. I understand why you both feel this shouldn't be implemented in xray. My one objection to the discussion is that I don't think that climatological time is such a "niche" issue--processing climate model output (much of which has no specific calendar date associated with it but still has seasonal cycles, etc.) seems like one of the most useful applications for xray.

I come at this from a very practical point of view. I need to use certain datasets (e.g. WOA13, POP model output) for my research and teaching. I want to teach xray in my fall physical oceanography class---it is perfect for teaching because it "just works" and allows students to quickly load data and do basic analysis easily. This PR request would allow me to do that. I understand the counter-arguments, but I don't know exactly how I should proceed if this can't be part of xray. The options seem to be:

1) Don't use the datasets 2) Don't use xray 3) Use xray without time support

Is there something else I'm missing?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Fix datetime decoding when time units are 'days since 0000-01-01 00:00:00' 99847237
130424018 https://github.com/pydata/xarray/pull/523#issuecomment-130424018 https://api.github.com/repos/pydata/xarray/issues/523 MDEyOklzc3VlQ29tbWVudDEzMDQyNDAxOA== rabernat 1197350 2015-08-12T19:45:42Z 2015-08-12T19:45:42Z MEMBER

Here is another example of a dataset with a similar time encoding issue. This is a valid OpenDAP URL: http://data.nodc.noaa.gov/thredds/dodsC/woa/WOA13/DATAv2/temperature/netcdf/decav/1.00/woa13_decav_t16_01v2.nc

The time units are 'months since 0000-01-01 00:00:00'. This is the very popular World Ocean Atlas. Since it is a monthly climatology, the dates are referenced to year 0.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Fix datetime decoding when time units are 'days since 0000-01-01 00:00:00' 99847237
129268281 https://github.com/pydata/xarray/pull/523#issuecomment-129268281 https://api.github.com/repos/pydata/xarray/issues/523 MDEyOklzc3VlQ29tbWVudDEyOTI2ODI4MQ== rabernat 1197350 2015-08-10T01:22:22Z 2015-08-10T01:22:22Z MEMBER

@ocefpaf Unfortunately no OPenDAP endpoint, but I put a sample file on our ftp server ftp://ftp.ldeo.columbia.edu/pub/rpa/pop_sample/b40.1850.track1.2deg.wcm.007.pop.h.0100-01.nc

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Fix datetime decoding when time units are 'days since 0000-01-01 00:00:00' 99847237
129190075 https://github.com/pydata/xarray/pull/523#issuecomment-129190075 https://api.github.com/repos/pydata/xarray/issues/523 MDEyOklzc3VlQ29tbWVudDEyOTE5MDA3NQ== rabernat 1197350 2015-08-09T14:09:47Z 2015-08-09T14:09:47Z MEMBER

@ocefpaf NCAR is one of the lead institutions in terms of the CF conventions. Yet the CESM POP model, also developed at NCAR, has this "year 0" issue! To me this suggests that any practical, real-world application will need to deal with special cases like this one. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Fix datetime decoding when time units are 'days since 0000-01-01 00:00:00' 99847237

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE [issue_comments] (
   [html_url] TEXT,
   [issue_url] TEXT,
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [created_at] TEXT,
   [updated_at] TEXT,
   [author_association] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [performed_via_github_app] TEXT,
   [issue] INTEGER REFERENCES [issues]([id])
);
CREATE INDEX [idx_issue_comments_issue]
    ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
    ON [issue_comments] ([user]);