JT Thielen

In general, I like the idea of a new, separate attribute because it allows the `units` attribute to have at least some guarantee of sanity for users and libraries using...

Possibly relevant to https://github.com/Unidata/MetPy/issues/886.

@dopplershift and @jrleeman: The general problem at play here seems to be that the dimensions of the data are not present as coordinates, and having x and y dimension coordinates...

Also, @atmosmattbrewer, to directly answer your last question, I don't believe there is any extra xarray manipulation that you are missing; it is simply a problem with MetPy's `cross_section()` not...

As requested, here is the code I used: https://gist.github.com/jthielen/8881d32d08d625c75c906a7e8ad7583f This issue with WRF, however, relates to something I've been wondering about for a little while now. I have some of...

Also, tagging @tjwixtrom, since we talked at AMS about this and he has done [some similar work](https://github.com/tjwixtrom/wrf_post_processor).

@atmosmattbrewer Now with MetPy's [`assign_crs`](https://unidata.github.io/MetPy/v1.0/api/generated/metpy.xarray.html#metpy.xarray.MetPyDataArrayAccessor.assign_crs) and [`assign_y_x`](https://unidata.github.io/MetPy/v1.0/api/generated/metpy.xarray.html#metpy.xarray.MetPyDataArrayAccessor.assign_y_x) helpers (as of version 1.0, which is still unreleased, and since RC1 is somewhat incomplete, I'd recommend using current master branch), everything should...

@atmosmattbrewer Here's the demo: https://nbviewer.jupyter.org/urls/dl.dropbox.com/s/ymmj7nrznbqdicp/hrrr_cross_section_demo.ipynb.

This particular example with HRRR is a 519 MB grib2 file, so probably not best to include in the docs or maybe even python-training. I have some post-processed FV3-LAM output...

> I just discovered this issue - thanks for tagging the salem issue @jthielen . > > Yes, I do believe that something better than wrf-python and separate from MetPy...