keltonhalbert
commented
1 year ago It appears that with some modification, I can force it to work. I first have a statically defined proj string that I assign, and then have to manually specify force and tolerance values. If this is anticipated or expected behavior, feel free to close the issue. However, there is a lot of example code out there that uses the previous approach, so maybe still worth fixing?
import xarray as xr
from pyproj import CRS
import fsspec
import metpy
import pint
HRRR_PROJ_STR = "+proj=lcc +a=6371229 +b=6371229 +lon_0=262.5 +lat_0=38.5 +lat_1=38.5 +lat_2=38.5 +type=crs"
def main():
print(xr.__version__)
print(metpy.__version__)
url = "simplecache::gs://high-resolution-rapid-refresh/hrrr.20230303/conus/hrrr.t00z.wrfsfcf00.grib2"
ds = xr.open_dataset(fsspec.open_local(url, simplecache={'cache-storage': '/tmp'}), engine="cfgrib",
backend_kwargs={'filter_by_keys': {'typeOfLevel': 'surface', 'shortName': 'cape' }})
print(ds)
ds = ds.metpy.assign_crs(CRS(HRRR_PROJ_STR).to_cf())
ds = ds.metpy.parse_cf().metpy.assign_y_x(force=False, tolerance=None)
print(ds)
if __name__ == "__main__":
main()
jthielen
What went wrong?
I spent some time looking through open issues and stack overflow to make sure I am doing this correctly, but it appears MetPy 1.4 with Python 3.10 is broken with the assign_y_x accessor. Previously this worked in adding the X and Y coordinates in meters to HRRR grib data, but running the example provided no longer works. Downgrading to MetPy 1.3 didn't fix the issue either, but it could be something tied up in upgrading from Python 3.8 to Python 3.10.
I also tried setting the tolerance argument (100 meters, 1000 meters, 3000 meters, and 6000 meters), and still am not having success. Any suggestions or ideas to recover this functionality?
Operating System
Linux
Version
1.4
Python Version
3.10
Code to Reproduce
Errors, Traceback, and Logs