[postgis-devel] [PostGIS] #1064: [raster] transform regress failing on 8.4 windows build

[PostGIS]

#1064: [raster] transform regress failing on 8.4 windows build
-----------------------------+----------------------------------------------
  Reporter:  robe            |       Owner:  dustymugs    
      Type:  defect          |      Status:  closed       
  Priority:  blocker         |   Milestone:  PostGIS 2.0.0
 Component:  postgis raster  |     Version:  trunk        
Resolution:  fixed           |    Keywords:               
-----------------------------+----------------------------------------------
Changes (by robe):

  * status:  assigned => closed
  * resolution:  => fixed


Old description:

> I'm not sure if its just something changed in my setup or not, but the
> rt_transform tests are failing on my 8.4 windows builds.  What's odd is
> that they are passing on my 9.0 and 9.1beta2 windows builds.
>
> I though it was maybe because I rebuilt gdal and perhaps my settings were
> off, but such things usually make all 3 fail.
>
> Anyrate attached is the regress failure.

New description:

 I'm not sure if its just something changed in my setup or not, but the
 rt_transform tests are failing on my 8.4 windows builds.  What's odd is
 that they are passing on my 9.0 and 9.1beta2 windows builds.

 I though it was maybe because I rebuilt gdal and perhaps my settings were
 off, but such things usually make all 3 fail.

 Anyrate attached is the regress failure.

--

Comment:

 Bborie,

 I apologize for the waste of time.  I figured out what is different about
 my 8.4.
 I had an extra line in my Pg 8.4 database launch script that had:

 {{{

 @SET GDAL_DATA=C:\projects\gdal\rel-trunk\share\gdal
 }}}

 That folder has a bunch of transform csv files.  It was alsoo at a time
 when I rebuilt GDAL so could also be a permission issue with that folder.

 and it was giving errors like the below in the log when transform was done
 ERROR 6: Unable to load PROJ.4 library ("libproj.dll"), creation of
 OGRCoordinateTransformation failed.

 Not sure why that line even matters unless they are proj 4.7 specific
 files and somehow force proj to override its standard behavior.

 Anyrate we didn't have it in our 9.0 and 9.1 pg launch scripts.  Once I
 got rid of that line all worked fine.  I'm not sure though what happens if
 people have that in their global environment variables.  They might run
 into the same issues I suppose as I think PostgreSQL pays attention to
 environment variables.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1064#comment:11>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.