ST_GeogFromText should swap longitude when latitude crosses 90 deg

[tomvantilburg]

ST_GeogFromText calculates back from 90 (92 becomes 88 etc.) when entering a latitude higher than 90. This would make (a bit of) sense if the longitude would be swapped by 180 deg, (going over the pole) but it doesn't.

[tomvantilburg]

Reproduce with: SELECT ST_AsText(ST_GeogFromText('POINT(10 91)'))

[munderwood]

I agree that the current behaviour poses a problem. Silently turning (10, 91) into (-170, 89) would definitely be better than turning it into (10, 89) as happens now.

An even better option might be to throw an error, preventing the INSERT/UPDATE operation that is trying to set a latitude greater than 90. Best of all would be if there were a flag with which the DBA could make the choice of behaviour. Something like SET out_of_range_latitudes TO wrap|reject|reflect, for example. (I personally don't see any reason to have the "reflect" option for new databases, but it could be used in existing databases for backward compatibility of behaviour.)

[robe]

oh and this one. I do not consider this a blocker.

[pramsey]

If I evaluate bearing, then altitude

POINT(10 91) == POINT(-170 89)

If I evaluate altitude, then bearing

POINT(10 91) == POINT(10 89)

I don't think there's any stronger case for flipping to the alternate hemisphere than there is for not doing so. That just leaves erroring out or not, and the case in both bearing and altitude coercion is that a NOTICE is raised, which seems sufficient for me.

postgis24=# SELECT ST_AsText(ST_GeogFromText('POINT(10 91)'));
NOTICE:  Coordinate values were coerced into range [-180 -90, 180 90] for GEOGRAPHY
  st_astext   
--------------
 POINT(10 89)
(1 row)