Timothy W. Hilton

I'm also wondering about this one. It's not straightforward to use getvar on a large number of WRF output files (see [issue 94](https://github.com/NCAR/wrf-python/issues/94)); seems xarray could help with this.

Thanks, @clyne, for the update! It's nice to know that the slowdown in wrf-python development these past six months doesn't indicate it's being phased out. I'm also open to helping...

I'm experiencing the same thing. I'd love to get some insight.

> This happens with any ERA data? @RichardScottOZ, I don't know, honestly, I've only tried with the ERA5 data I am trying to use. I've regridded to a higher resolution...

> Looks like you have location array based data, x/y coords are 2d, but code that raises the error expects to see 1d x/y coords. That's true, yes... This particular...

> Does this work: > > xds_1d = xds.rio.reproject( > "EPSG:2193", > src_geoloc_array=( > xds.coords["x"].values, > xds.coords["y"].values, > ), > > georeferencing_convention="PIXEL_CENTER", > ) @snowman2 it does not, unfortunately... It...

My sense from the documentation is that this array is within the intended use cases (that is, an xarray dataset with 2-dimensional X and Y grid locations roughly 2000 rows...

Same (or very similar) thing happens for me with grouped box and violin plots. ```python mport hvplot import hvplot.xarray import xarray as xr import numpy as np from bokeh.models import...

just noting this is still happening in v11.1. The suggested workaround of using time series features doesn't really help. ```python import hvplot import hvplot.xarray import matplotlib.ticker import numpy as np...