I actually favor -180 to 180 as well.  Feel free to leave this as is, but in the future I'd like to get the code consistently using these nautical lat lon ranges.  I originally used 0 to 360 since that what the forecast data used but as it turns out (due to that pesky dateline bug you point out) we'll need more intelligent logic.

nit: maybe rename this to to nautical_latlon?