home / github / issue_comments

Menu
  • GraphQL API
  • Search all tables

issue_comments: 107210623

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/411#issuecomment-107210623 https://api.github.com/repos/pydata/xarray/issues/411 107210623 MDEyOklzc3VlQ29tbWVudDEwNzIxMDYyMw== 2443309 2015-05-31T15:45:49Z 2015-05-31T15:45:49Z MEMBER

Okay. Glad to hear I was missing something. For large datasets, I was getting a MemoryError with orthogonal indexing as the array size increased like it did in my example.

The indexing details link you show does explain the behavior better but it is somewhat contradictory to the quote I listed above. I think it would be worth reconciling the docs on that point.

The station selection use case you bring up is exactly what I was going for. It would be nice if we could stay in xray / pandas after the indexing. Ideally, I don't want to do: xr_data.values[:, ys, xs] and then recreate a DataArray.

Lastly, is there an issue open for support of numpy fancy indexing? This is something that would be useful for my work and I could contribute to the effort beginning in July.

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