issue_comments

Table actions

3 rows where issue = 811933067 and user = 6628425 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

  • spencerkclark · 3 ✖

issue 1

  • Times not decoding due to time_reference being in another variable · 3 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
782739934 https://github.com/pydata/xarray/issues/4927#issuecomment-782739934 https://api.github.com/repos/pydata/xarray/issues/4927 MDEyOklzc3VlQ29tbWVudDc4MjczOTkzNA== spencerkclark 6628425 2021-02-20T19:51:34Z 2021-02-20T19:51:34Z MEMBER

Yeah, I understand, these kinds of metadata issues can be frustrating to deal with, especially when things are close to being valid, but not quite. That said, I'm afraid I would be -1 on adding special logic to handle this to xarray, though I'm open to being convinced if others feel otherwise.

(The time bounds logic is a bit different, because there are indeed CF Conventions pertaining to that).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Times not decoding due to time_reference being in another variable 811933067
782735912 https://github.com/pydata/xarray/issues/4927#issuecomment-782735912 https://api.github.com/repos/pydata/xarray/issues/4927 MDEyOklzc3VlQ29tbWVudDc4MjczNTkxMg== spencerkclark 6628425 2021-02-20T19:20:47Z 2021-02-20T19:20:47Z MEMBER

@kmuehlbauer thanks -- in my reading of the table under Section 4.4.1 (Attributes for time coordinate variable) it seems like the actual value of the date should appear in the units attribute of the time coordinate (matching the "time_reference" or "time_coverage_start" variable is a separate condition).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Times not decoding due to time_reference being in another variable 811933067
782733509 https://github.com/pydata/xarray/issues/4927#issuecomment-782733509 https://api.github.com/repos/pydata/xarray/issues/4927 MDEyOklzc3VlQ29tbWVudDc4MjczMzUwOQ== spencerkclark 6628425 2021-02-20T19:02:02Z 2021-02-20T19:02:02Z MEMBER

Sorry for chiming in a bit late -- I just want to make sure, is this truly valid under the CF Conventions? It seems to open the door for ambiguity; e.g. it's a pathological example, but one could imagine a "time_reference" variable named in the form of a date. In that case what takes precedence when decoding the times, the value of the date in the name, or the value the variable refers to?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Times not decoding due to time_reference being in another variable 811933067

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]);