You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yet another bug with .cf.add_bounds... This one was already present before the 2D addition, but it would have been quite infrequent with 1D coordinates.
The interpolation / extrapolation estimates are not aware of the cyclic nature of the longitude.
Sadly, a quick internet search hasn't given me any pointers towards tools that already take this into account, except for projection-based tools (like pyproj).
We could have a check for "longitude" that looks for jumps and wraps the coordinates, but that jump threshold would be arbitrary. It's nonetheless the simplest way out I see, before parsing grid_mapping into pyproj objects.
The text was updated successfully, but these errors were encountered:
Yet another bug with
.cf.add_bounds
... This one was already present before the 2D addition, but it would have been quite infrequent with 1D coordinates.The interpolation / extrapolation estimates are not aware of the cyclic nature of the longitude.
MWE:
yields:
but we would expect:
Sadly, a quick internet search hasn't given me any pointers towards tools that already take this into account, except for projection-based tools (like pyproj).
We could have a check for "longitude" that looks for jumps and wraps the coordinates, but that jump threshold would be arbitrary. It's nonetheless the simplest way out I see, before parsing
grid_mapping
intopyproj
objects.The text was updated successfully, but these errors were encountered: