home / github / issue_comments

Menu
  • GraphQL API
  • Search all tables

issue_comments: 564297100

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/1850#issuecomment-564297100 https://api.github.com/repos/pydata/xarray/issues/1850 564297100 MDEyOklzc3VlQ29tbWVudDU2NDI5NzEwMA== 13301940 2019-12-10T22:55:13Z 2019-12-10T22:55:13Z MEMBER

I assume you are about to implement some general functionality but what to know where to put it?

This is correct.

One of the things we've been exploring is a "general resample utility" that would both enable fluid translation between data at different temporal intervals (this is one of the use cases) and be aware of things like time boundary variable . The fundamental concepts here are analogous to ESMF's regridder's:

  • Create a source axis, i.e. the axis that your original data is on,
  • Create a destination axis, i.e. the axis that you want to convert your data to,
  • Create an AxisRemapper object by passing the source and destination axis you created previously,
  • Finally, convert your data from the source axis to the destination axis, using the AxisRemapper object you created in previous step.

We have a general, low-level prototype in https://github.com/coderepocenter/AxisUtilities. We think that it would be beneficial to have this functionality in xarray instead of it residing in yet another xarray related package.

For the time being, my main question is: where (in xarray) would something like this reside?

Note:

I am happy to open a separate issue to discuss the merits of having this functionality in xarray.

Cc @maboualidev

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