home / github / issue_comments

Menu
  • GraphQL API
  • Search all tables

issue_comments: 504238699

This data as json

html_url issue_url id node_id user created_at updated_at author_association body reactions performed_via_github_app issue
https://github.com/pydata/xarray/issues/3026#issuecomment-504238699 https://api.github.com/repos/pydata/xarray/issues/3026 504238699 MDEyOklzc3VlQ29tbWVudDUwNDIzODY5OQ== 43126798 2019-06-20T23:51:10Z 2019-06-20T23:51:10Z CONTRIBUTOR

For example, you might have a rectilinear grid in a non-geodetic coordinate system, for example a rotated pole:

<xarray.Dataset> Dimensions: (period: 7, x: 3, y: 3) Coordinates: height float64 2.0 lon (y, x) float64 137.6 138.1 138.6 137.6 ... 137.7 138.1 138.6 lat (y, x) float64 -21.71 -21.73 -21.74 ... -20.83 -20.85 -20.86 * y (y) float64 7.92 8.36 8.8 * x (x) float64 176.5 176.9 177.4 * period (period) object '1961-1980' '1981-2000' ... '2081-2100' Data variables: loc (period, y, x) float64 311.2 311.4 311.2 ... 316.0 316.0 315.6 scale (period, y, x) float64 1.231 1.223 1.192 ... 0.8923 0.8934 shape (period, y, x) float64 0.4358 0.4261 ... -0.001062 0.009387 rotated_pole |S1 b''

Obviously this case is a little more complicated, because x/y and lon/lat don't have a one-to-one correspondence. But I want to be able to write code that works with both cases, ideally without special casing stuff. Being able to have separately named dim and coordinate variables would help a lot.

However, now that I look at this example, I guess in my case I have both x/y and lat/lon in the coordinates anyway, so maybe I should just duplicate them, with different names.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  456769766
Powered by Datasette · Queries took 0.761ms · About: xarray-datasette