home / github / issue_comments

Menu
  • GraphQL API
  • Search all tables

issue_comments: 790967872

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/pull/4979#issuecomment-790967872 https://api.github.com/repos/pydata/xarray/issues/4979 790967872 MDEyOklzc3VlQ29tbWVudDc5MDk2Nzg3Mg== 1828519 2021-03-04T21:45:53Z 2021-03-04T21:45:53Z CONTRIBUTOR

2D lat/lon arrays could be as expensive to store as the image itself, even though the values can be computed on the fly with very cheap arithmetic.

Just wanted to mention in case it comes up later, this is true for some datasets and for others the lon/lats are not uniformly spaced so they can't be calculated (just based on the way the satellite instrument works). They have to be loaded from the original dataset (on-disk file). For a while in the Satpy library we were storing 2D dask arrays for the lon/lat coordinates until we realized xarray was sometimes computing them and we didn't want that.

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