Kevin Schwarzwald

Clarify pydata#8728 in docs

2

- Add reference to numpy docs on view / copies in the corresponding section of the xarray docs, to help clarify pydata#8728 . - Add note that other xarray operations...

Lingering memory connections when extracting underlying `np.arrays` from datasets

6

### What is your issue? I know that generally, `ds2 = ds` connects the two objects in memory, and changes in one will also cause changes in the other. However,...

As `xagg` currently is, an additional weight grid can be added, but it is regridded to the `ds` grid. The code is already prepared for the possibility of regridding the...

`ds.interp()` breaks if (non-interpolating) dimension is not numeric

1

### What happened? I'm running `ds.interp()` using multi-dimensional new coordinates, using `xarray`'s broadcasting to expand the original dataset to new dimensions. In this case, I'm only interpolating on one dimension,...

Self-explanatory. For some reason, this wasn't caught by the unit tests. TO-DO: - Make sure unit tests correctly break when additional weights aren't included - Add additional weights support to...

Currently, polygon metadata gets saved as variables in `agg.to_dataset()`, but perhaps a more fitting place would be as coordinates.

Occasionally, `xa.aggregate()` modifies the inputted weightmap, which causes downstream issues if the weightmap is used again. An easy fix would be to add `wm = copy.deepcopy(wm)` at the start of...

A few versions ago, xagg launched a numba backend that can be accessed via: ``` with xa.set_options(impl='numba': agg = xa.aggregate(ds,wm) ``` This has drastically sped up calculations over the previous...