issue_comments

Table actions

3 rows where author_association = "CONTRIBUTOR" and issue = 187208913 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

issue 1

  • New infer_intervals keyword for pcolormesh · 3 ✖

author_association 1

  • CONTRIBUTOR · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
258461994 https://github.com/pydata/xarray/pull/1079#issuecomment-258461994 https://api.github.com/repos/pydata/xarray/issues/1079 MDEyOklzc3VlQ29tbWVudDI1ODQ2MTk5NA== ocefpaf 950575 2016-11-04T15:26:25Z 2016-11-04T15:26:25Z CONTRIBUTOR

We definitely ignore cell boundaries -- they don't (yet) have any place in the xarray data model.

Even though I would love to have that functionality I do not believe it is high priority. cell boundaries is a corner case, at least in my field of work, and 99% of the time it is OK to infer the intervals. Also, the name of the key word is quite clear: infer_intervals.

Maybe you could only add a note in the docs mentioning that the cell boundaries might exist?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   New infer_intervals keyword for pcolormesh 187208913
258382469 https://github.com/pydata/xarray/pull/1079#issuecomment-258382469 https://api.github.com/repos/pydata/xarray/issues/1079 MDEyOklzc3VlQ29tbWVudDI1ODM4MjQ2OQ== ocefpaf 950575 2016-11-04T09:33:42Z 2016-11-04T09:33:42Z CONTRIBUTOR

Yes, it is a special case for pcolormesh though

A special case that I love. In the old Matlab day we had horrible hacks to get pcolor to work properly :smile:

I'm not sure if the additional complexity added by cell boundaries is on the xarray devs priority list...

That is fine. Maybe a warning in the docs would be nice. So people can revert to a "manual" plotting to get the boundaries right.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   New infer_intervals keyword for pcolormesh 187208913
258378187 https://github.com/pydata/xarray/pull/1079#issuecomment-258378187 https://api.github.com/repos/pydata/xarray/issues/1079 MDEyOklzc3VlQ29tbWVudDI1ODM3ODE4Nw== ocefpaf 950575 2016-11-04T09:12:47Z 2016-11-04T09:12:47Z CONTRIBUTOR

Is infer_intervals creating coordinate bounds for plotting? It looks like it. What about when we do have cell boundaries in the dataset? (See http://cfconventions.org/cf-conventions/v1.6.0/cf-conventions.html#cell-boundaries). Will those be ignored and the inferred one used?

(Sorry if I am only making noise here and this does not make sense. In that case just ignore my comment.)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   New infer_intervals keyword for pcolormesh 187208913

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