The LatLonProjection doesn't map coordinates into projection coordinates when the coordinates are outside the range -360 - 360

[metmikel]

Versions impacted by the bug

Tested in v5.9.1

What went wrong?

This is a similar issue to #1500 , however, it occurs when some of the projection coordinates are outside the range -360 - 360. Setting the central longitude for the LatLonProjection using the setCentralLon method doesn't help as that method normalises the longitude into the range -180 - 180.
We have worked around this by using the setDefaultMapArea method rather than setCentralLon, but it would be good if setCentralLon did not normalise the central longitude. The fix for #1500 in #1509 will also suffer from this issue. The ECMWF IFS data attached demostrates this issue.

Relevant stack trace

Relevant log messages

ifs_hres_20260110T1800_step003h_tmp2m.zip

If you have an example file that you can share, please attach it to this issue.

If so, may we include it in our test datasets to help ensure the bug does not return once fixed?
Note: the test datasets are publicly accessible without restriction.

Yes

Code of Conduct

• I agree to follow the UCAR/Unidata Code of Conduct