issue_comments

Table actions

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

issue 1

  • Explaining xarray in a single picture · 3 ✖

author_association 1

  • MEMBER · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1189294740 https://github.com/pydata/xarray/issues/6771#issuecomment-1189294740 https://api.github.com/repos/pydata/xarray/issues/6771 IC_kwDOAMm_X85G4zKU TomNicholas 35968931 2022-07-19T16:21:23Z 2022-07-19T16:21:23Z MEMBER

Whilst trying to use this figure to explain our data model to someone at SciPy I realised that we also need separate versions of this figure for just a DataArray / Variable too, because new users struggle to understand which parts of this diagram are still present in a single DataArray / Variable.

 
{
    "total_count": 3,
    "+1": 3,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Explaining xarray in a single picture 1300534066
1180550253 https://github.com/pydata/xarray/issues/6771#issuecomment-1180550253 https://api.github.com/repos/pydata/xarray/issues/6771 IC_kwDOAMm_X85GXcRt dcherian 2448579 2022-07-11T15:25:03Z 2022-07-11T15:25:03Z MEMBER

I'm working on a mini-tutorial introducing xarray for some folks in our genetics community

We are currently reworking https://tutorial.xarray.dev/intro.html and would love to either add your material or link to it if you're creating a consolidated collection of genetics-related material. xref (https://github.com/pydata/xarray/issues/3564). We don't have a "domain-specific" section yet but are planning to create one after SciPy.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Explaining xarray in a single picture 1300534066
1180512949 https://github.com/pydata/xarray/issues/6771#issuecomment-1180512949 https://api.github.com/repos/pydata/xarray/issues/6771 IC_kwDOAMm_X85GXTK1 TomNicholas 35968931 2022-07-11T14:53:43Z 2022-07-11T14:53:43Z MEMBER

Hi @alimanfoo, thanks for raising this.

I would've thought that latitude and longitude would be 1-dimensional coordinate variables, yet they are drawn as 2-D arrays?

I think that if you assume that the axes of your grid data align with the cardinal directions (East-West / North-South) then you would expect latitude and longitude to be 1D, but if they don't align then the coordinates would need be 2D (i.e. if x and y are merely arbitrary lines along the Earth's surface).

I agree with you though that 2D lat/lon grids are unnecessarily confusing, especially for non-geoscience users.

I like the second diagram you showed more (it's also a neater version of the labelled one I made here). I think it's debatable whether elevation and land_cover constitute coordinates or data variables, but I have no strong opinion on that.

As for improvements, I think it would be clearer to at least use the second image over the first, and perhaps we could improve it further.

 
{
    "total_count": 2,
    "+1": 2,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Explaining xarray in a single picture 1300534066

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