Cartopy 0.26.0 currently breaks some plots using geoviews and projections, which removed "lon_0" key from some projections. For example, the bottom cell on the readthedocs page titled "Reading Structured Grids" (https://uxarray.readthedocs.io/en/latest/user-guide/structured.html) currently has a crash instead of a plot. The crash is KeyError: 'lon_0' being raised from a line like if (isinstance(crs, ccrs.PlateCarree) and not isinstance(proj, ccrs.PlateCarree) and crs.proj4_params['lon_0'] != 0): inside of geoviews.
@rajeeja created holoviz/geoviews#884 to provide a fix upstream; it has already been accepted and merged into geoviews's main branch. According to comment in thread there, it sounds like the timeline for the next geoviews release is hopefully in the next couple of weeks.
Should we introduce pins like geoviews<=1.15.1, cartopy<0.26.0 to uxarray in the meantime? Pros: uxarray users' plots would work as expected, and not remain broken while awaiting a new geoviews release. Cons: this would block #1773 until the new geoviews release, because that PR would pin cartopy >=0.26.0 in order to support matplotlib>=3.11, solving #1542 and #1772.
(Didn't add the "fix-upstream" label yet; should add it after either adding those version pins or definitively deciding not to.)
Cartopy 0.26.0 currently breaks some plots using geoviews and projections, which removed "lon_0" key from some projections. For example, the bottom cell on the readthedocs page titled "Reading Structured Grids" (https://uxarray.readthedocs.io/en/latest/user-guide/structured.html) currently has a crash instead of a plot. The crash is
KeyError: 'lon_0'being raised from a line likeif (isinstance(crs, ccrs.PlateCarree) and not isinstance(proj, ccrs.PlateCarree) and crs.proj4_params['lon_0'] != 0):inside of geoviews.@rajeeja created holoviz/geoviews#884 to provide a fix upstream; it has already been accepted and merged into geoviews's main branch. According to comment in thread there, it sounds like the timeline for the next geoviews release is hopefully in the next couple of weeks.
Should we introduce pins like
geoviews<=1.15.1, cartopy<0.26.0to uxarray in the meantime? Pros: uxarray users' plots would work as expected, and not remain broken while awaiting a new geoviews release. Cons: this would block #1773 until the new geoviews release, because that PR would pincartopy >=0.26.0in order to supportmatplotlib>=3.11, solving #1542 and #1772.(Didn't add the "fix-upstream" label yet; should add it after either adding those version pins or definitively deciding not to.)