issue_comments

Table actions

4 rows where issue = 28600785 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 3

author_association 2

issue 1

  • OpenDAP loaded Dataset has lon/lats with type 'object'. · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
38417320 https://github.com/pydata/xarray/issues/39#issuecomment-38417320 https://api.github.com/repos/pydata/xarray/issues/39 MDEyOklzc3VlQ29tbWVudDM4NDE3MzIw shoyer 1217238 2014-03-24T07:21:02Z 2014-03-24T07:21:02Z MEMBER

I believe this was fixed by #54.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   OpenDAP loaded Dataset has lon/lats with type 'object'. 28600785
36484609 https://github.com/pydata/xarray/issues/39#issuecomment-36484609 https://api.github.com/repos/pydata/xarray/issues/39 MDEyOklzc3VlQ29tbWVudDM2NDg0NjA5 akleeman 514053 2014-03-03T06:28:32Z 2014-03-03T06:28:32Z CONTRIBUTOR

@shoyer You're right I can serialize the latitude object directly from that opendap url ... but after some manipulation I run into this:

ipdb> print fcst dimensions: latitude = 31 longitude = 46 time = 7 variables: object latitude(latitude) units:degrees_north _CoordinateAxisType:Lat object longitude(longitude) units:degrees_east _CoordinateAxisType:Lon datet... time(time) standard_name:time _CoordinateAxisType:Time units:hours since 2014-03-03 00:0... ipdb> fcst.dump('./test.nc') *** TypeError: illegal primitive data type, must be one of ['i8', 'f4', 'u8', 'i1', 'U1', 'S1', 'i2', 'u1', 'i4', 'u2', 'f8', 'u4'], got object

Currently tracking down exactly whats going on here.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   OpenDAP loaded Dataset has lon/lats with type 'object'. 28600785
36484363 https://github.com/pydata/xarray/issues/39#issuecomment-36484363 https://api.github.com/repos/pydata/xarray/issues/39 MDEyOklzc3VlQ29tbWVudDM2NDg0MzYz ebrevdo 1794715 2014-03-03T06:21:33Z 2014-03-03T06:21:33Z CONTRIBUTOR

Indices also have an .inferred_type getter. unfortunately it doesn't seem to return true type names...

In [13]: pandas.Index([1,2,3]).inferred_type Out[13]: 'integer'

In [14]: pandas.Index([1,2,3.5]).inferred_type Out[14]: 'mixed-integer-float'

In [15]: pandas.Index(["ab","cd"]).inferred_type Out[15]: 'string'

In [16]: pandas.Index(["ab","cd",3]).inferred_type Out[16]: 'mixed-integer'

On Sun, Mar 2, 2014 at 10:14 PM, Stephan Hoyer notifications@github.comwrote:

This is because coordinates are loaded as pandas.Index objects... which don't always faithfully preserve the type of the underlying object (see pydata/pandas#6471 https://github.com/pydata/pandas/issues/6471).

I believe serialization should still work though thanks to a work around I added for dtype=object. Do let me know if this is not the case. One solution to make this less awkward would be to wrap pandas.Index in something that keeps track of the dtype of the original arguments for use in mathematical expression.

Reply to this email directly or view it on GitHubhttps://github.com/akleeman/xray/issues/39#issuecomment-36484122 .

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   OpenDAP loaded Dataset has lon/lats with type 'object'. 28600785
36484122 https://github.com/pydata/xarray/issues/39#issuecomment-36484122 https://api.github.com/repos/pydata/xarray/issues/39 MDEyOklzc3VlQ29tbWVudDM2NDg0MTIy shoyer 1217238 2014-03-03T06:14:38Z 2014-03-03T06:14:38Z MEMBER

This is because coordinates are loaded as pandas.Index objects... which don't always faithfully preserve the type of the underlying object (see https://github.com/pydata/pandas/issues/6471).

I believe serialization should still work though thanks to a work around I added for dtype=object. Do let me know if this is not the case. One solution to make this less awkward would be to wrap pandas.Index in something that keeps track of the dtype of the original arguments for use in mathematical expression.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   OpenDAP loaded Dataset has lon/lats with type 'object'. 28600785

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