Regridding to physically invalid latitudes should probably warn or raise about xesmf HOT 2 CLOSED

Good suggestion. For longitude you can use whatever range, even (720, 1080), since ESMF will convert spheric coordinates to Cartesian coordinates for regridding calculation. It makes sense to check the range of latitudes.

Notes for who are using the low-level ESMPy:

ESMPy Regrid object takes a keyword argumentunmapped_action.

With
ESMF.Regrid(..., unmapped_action = ESMF.UnmappedAction.ERROR)
ESMPy will crash if there's any region that can't be mapped. For example if lat>90. But it will also crash if the target grid is larger than the source grid. I want to let the unmapped region be 0 without crashing the routine, so I am not using this option.

In xESMF I am setting
ESMF.Regrid(..., unmapped_action = ESMF.UnmappedAction.IGNORE)
so ESMPy will not throw any error.

ESMPy's error message is quite incomprehensible since the program often dies in the Fortran level, so I prefer adding high-level error checking in xESMF, instead of relying on ESMPy's error information.

from xesmf.

v0.1.1 now gives a warning if latitude is outside of [-90, 90]. See warn_lat_range() in backend.py

from xesmf.