issue_comments

Table actions

2 rows where issue = 363326726 and user = 14808389 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

  • keewis · 2 ✖

issue 1

  • xarray potential inconstistencies with cftime · 2 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
787459912 https://github.com/pydata/xarray/issues/2437#issuecomment-787459912 https://api.github.com/repos/pydata/xarray/issues/2437 MDEyOklzc3VlQ29tbWVudDc4NzQ1OTkxMg== keewis 14808389 2021-02-28T14:19:33Z 2021-02-28T14:20:25Z MEMBER

the issue is that without more information (units, reference date, calendar), xarray can't decode these integers correctly. For example, if the units are days your data would span more than 100 years, but if we assume milliseconds that would be about 2 hours. Same for reference date and calendar: if they are chosen incorrectly, the decoded data will be completely wrong.

You will have to check either the data provider's website or contact them and ask for help (it seems they started offering their data as netcdf files about two weeks ago so this might actually be a issue with their conversion code). Once you have that information we can help you with the code necessary to convert using xarray.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   xarray potential inconstistencies with cftime 363326726
787059836 https://github.com/pydata/xarray/issues/2437#issuecomment-787059836 https://api.github.com/repos/pydata/xarray/issues/2437 MDEyOklzc3VlQ29tbWVudDc4NzA1OTgzNg== keewis 14808389 2021-02-27T11:40:09Z 2021-02-27T11:52:49Z MEMBER

@spencerkclark: if the dataset linked to above is a good example, that would be

<tt>ds.info()</tt> ``` xarray.Dataset { dimensions: id = 37 ; time = 1380 ; variables: float32 runoff_mean(time, id) ; runoff_mean:units = m3/s ; runoff_mean:long_name = GRDC calculated from daily data ; float32 flag(time, id) ; flag:long_name = percentage of valid values used for calculation from daily data ; float32 area(id) ; area:units = km2 ; area:long_name = catchment area ; object country(id) ; country:long_name = country name ; country:iso2 = ISO 3166-1 alpha-2 - two-letter country code ; float32 geo_x(id) ; geo_x:units = degree_east ; geo_x:long_name = station longitude (WGS84) ; float32 geo_y(id) ; geo_y:units = degree_north ; geo_y:long_name = station latitude (WGS84) ; float32 geo_z(id) ; geo_z:units = m ; geo_z:long_name = station altitude (m above sea level) ; object owneroforiginaldata(id) ; owneroforiginaldata:long_name = Owner of original data ; object river_name(id) ; river_name:long_name = river name ; object station_name(id) ; station_name:long_name = station name ; float32 timezone(id) ; timezone:units = 00:00 ; timezone:long_name = utc offset, in relation to the national capital ; int64 time(time) ; time:long_name = time ; int32 id(id) ; id:long_name = grdc number ; // global attributes: :title = Mean daily discharge (Q) ; :Conventions = CF-1.7 ; :references = grdc.bafg.de ; :institution = GRDC ; :history = Download from GRDC Database, 26/02/2021 ; :missing_value = -999.000 ; } ```

so no units or calendar attributes on time

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   xarray potential inconstistencies with cftime 363326726

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