[postgis-users] Antipodal issues in upgrade

Timmons, Ryan P ryan.p.timmons at lmco.com
Wed Aug 20 17:16:47 PDT 2014

I'm having some trouble with an upgrade, following http://www.postgis.org/documentation/manual-svn/postgis_installation.html#hard_upgrade

Specifically I am going from Postgres 8.3.10, postgis "1.5 USE_GEOS=1 USE_PROJ=1 USE_STATS=1"   (given by select postgis_version())
to Postgres 9.3.5, postgis "2.1 USE_GEOS=1 USE_PROJ=1 USE_STATS=1"

When restoring I got this error:
ERROR:  Antipodal (180 degrees long) edge detected!
CONTEXT:  COPY voevents_general, line 15242, column hgc_bbox: "0103000020E610000001000000050000007ADFF8DA330165C000000000008056C05B087250C2EC274000000000008056C05B..."

Appears the entire table is unpopulated after that error.  From http://trac.osgeo.org/postgis/ticket/1046 it seems the antipodal check was added between the versions I'm transitioning between

Is there a function to find all rows in my old 1.5 version that will fail this check?  I don't see anything obvious in http://postgis.net/docs/manual-1.5/ch08.html#PostGIS_GeographyFunctions .

Or, is there a way to have the upgrade script fail only the rows violating this condition?  ( I suspect it is a small portion of the data, and not a useful field for the rows having this problem) .


Ryan Timmons
Research Scientist, O/A014S
Control Systems & Information Sciences
Lockheed Martin SSC
Cell: 248-895-1935

More information about the postgis-users mailing list