home / github

Menu
  • GraphQL API
  • Search all tables

issue_comments

Table actions
  • GraphQL API for issue_comments

2 rows where issue = 340757861 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 2

  • shoyer 1
  • czr137 1

author_association 2

  • CONTRIBUTOR 1
  • MEMBER 1

issue 1

  • interp over time coordinate · 2 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
404641052 https://github.com/pydata/xarray/issues/2284#issuecomment-404641052 https://api.github.com/repos/pydata/xarray/issues/2284 MDEyOklzc3VlQ29tbWVudDQwNDY0MTA1Mg== czr137 6153603 2018-07-12T20:31:37Z 2018-07-12T20:31:37Z CONTRIBUTOR

Thanks, I will gladly exercise patience until then.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  interp over time coordinate 340757861
404628605 https://github.com/pydata/xarray/issues/2284#issuecomment-404628605 https://api.github.com/repos/pydata/xarray/issues/2284 MDEyOklzc3VlQ29tbWVudDQwNDYyODYwNQ== shoyer 1217238 2018-07-12T19:44:37Z 2018-07-12T19:44:37Z MEMBER

Thanks for bringing this up.

@fujiisoup actually implemented interpolation for datetime64 as part of writing interp_like() , which will be in the next release of xarray (0.10.8). With the current development version of xarray: ``` In [6]: import numpy as np

In [7]: ds.interp(lat=60.5, lon=211, time=np.datetime64('2013-01-01T03:14:37')) Out[7]: <xarray.Dataset> Dimensions: () Coordinates: lat float64 60.5 lon int64 211 time datetime64[ns] 2013-01-01T03:14:37 Data variables: air float64 273.5 Attributes: Conventions: COARDS title: 4x daily NMC reanalysis (1948) description: Data is from NMC initialized reanalysis\n(4x/day). These a... platform: Model references: http://www.esrl.noaa.gov/psd/data/gridded/data.ncep.reanaly... ```

However, you do currently need to wrap your indexer explicitly in a np.datetime64 object. It would be nice to support casting strings to dates, somewhat like what we do in .sel(). This would be a good candidate for a pull request.

(I'll try to release 0.10.8 soon, maybe within the next week)

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  interp over time coordinate 340757861

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]);
Powered by Datasette · Queries took 10.919ms · About: xarray-datasette