[postgis-users] Assistance with ST_Transform in Ver. 1.5.1returning projection error
Paragon Corporation
lr at pcorp.us
Fri Sep 17 15:04:02 PDT 2010
Tom,
I think the PostGIS 1.3 should error out too so probably a bug in PostGIS
1.3 that was corrected in later releases.
The problem is 80 13 can't be projected to any area covered in 32613 (which
is utm zone 13 covering a 6 degree strip )
Just tested on my 1.5 and it errors out as well.
Leo
http://www.postgis.us
_____
From: postgis-users-bounces at postgis.refractions.net
[mailto:postgis-users-bounces at postgis.refractions.net] On Behalf Of Tom
Kessler
Sent: Friday, September 17, 2010 11:16 AM
To: postgis-users at postgis.refractions.net
Subject: [postgis-users] Assistance with ST_Transform in Ver. 1.5.1returning
projection error
I recently upgraded from Postgis 1.3 to 1.5 and started seeing projection
errors returned from pgsql triggers. I was able to reduce the problem to the
behavior of this simple query:
In 1.3 the following two queries work without error:
Select astext(st_transform
(GeomFromText('POINT( -80 13 )',4326), 32613))
Select astext(st_transform
(GeomFromText('POINT( 80 13 )',4326), 32613))
In 1.5 the first query works and the second one returns a "couldn't project
point - lat or long exceeded limits error."
My 1.3 version is:
POSTGIS="1.3.1" GEOS="3.0.0rc4-CAPI-1.3.3" PROJ="Rel. 4.5.0, 22 Oct 2006"
USE_STATS
My 1.5 full version is:
POSTGIS="1.5.1" GEOS="3.2.2-CAPI-1.6.2" PROJ="Rel. 4.7.1, 23 September 2009"
LIBXML="2.6.32" USE_STATS
proj4text in both spatial_ref_sys SRID entries is identical...Is this
related to need for grid-shift files?
Thanks in advance.
Tom
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20100917/6cf5fa20/attachment.html>
More information about the postgis-users
mailing list