issue_comments

Table actions

4 rows where issue = 159222357 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

  • Bug in multiplying datasets? Removes coordinates for lats · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
224685210 https://github.com/pydata/xarray/issues/877#issuecomment-224685210 https://api.github.com/repos/pydata/xarray/issues/877 MDEyOklzc3VlQ29tbWVudDIyNDY4NTIxMA== jormelton 9618134 2016-06-08T18:31:14Z 2016-06-08T18:31:14Z NONE

Yep, that fixed it. Perhaps it could raise a flag if it removes a coordinate as a result of small mismatches in the coordinates? The mismatch was very small (and surprising as the grid area file was actually made from the other file by using cdo cdo gridarea infile outfile). Thanks @jhamman and @shoyer for the help.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Bug in multiplying datasets? Removes coordinates for lats 159222357
224680348 https://github.com/pydata/xarray/issues/877#issuecomment-224680348 https://api.github.com/repos/pydata/xarray/issues/877 MDEyOklzc3VlQ29tbWVudDIyNDY4MDM0OA== shoyer 1217238 2016-06-08T18:14:46Z 2016-06-08T18:14:46Z MEMBER

There's likely a slight difference in the latitude values due to numerical precision and rounding.

Try using reindex or reindex_like with method='nearest':

gridarea = gridarea.reindex_like(ncscd_d30cm, method='nearest', tolerance=0.01)

This is an tricky thing to fix automatically because we need some heuristic to pick a default tolerance. See https://github.com/pydata/pandas/issues/9817 for related discussion on the pandas side.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Bug in multiplying datasets? Removes coordinates for lats 159222357
224675672 https://github.com/pydata/xarray/issues/877#issuecomment-224675672 https://api.github.com/repos/pydata/xarray/issues/877 MDEyOklzc3VlQ29tbWVudDIyNDY3NTY3Mg== jormelton 9618134 2016-06-08T17:58:45Z 2016-06-08T17:58:45Z NONE

Sorry, I tried a few different ways so that output must have been from an earlier one. I just reconfirmed, If make them all DataArray, I have the same problem.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Bug in multiplying datasets? Removes coordinates for lats 159222357
224672528 https://github.com/pydata/xarray/issues/877#issuecomment-224672528 https://api.github.com/repos/pydata/xarray/issues/877 MDEyOklzc3VlQ29tbWVudDIyNDY3MjUyOA== jhamman 2443309 2016-06-08T17:48:11Z 2016-06-08T17:48:11Z MEMBER

Something looks wrong in your example (I updated you markdown syntax btw).

Python ncscd_total30cm = gridarea.cell_area * ncscd_d30cm

should return a DataArray, not a Dataset as you have shown. Can you check to make sure you are multiplying two DataArrays?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Bug in multiplying datasets? Removes coordinates for lats 159222357

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