[osgeo4w-dev] [osgeo4w] #161: gdal utilities issues

OSGeo4W trac_osgeo4w at osgeo.org
Tue Mar 16 08:06:40 EDT 2010

#161: gdal utilities issues
Reporter:  lutra   |       Owner:  osgeo4w-dev at lists.osgeo.org
    Type:  defect  |      Status:  new                        
Priority:  major   |   Component:  Package                    
 Version:          |    Keywords:  gdal, gdal utilities       

 lately I have made quite a lot (>20) fresh osgeo4w installations on
 windows platforms (xp,vista and seven) and I'm pretty sure I can confirm
 the problem.

 I have been told that have been a little controversy about this matter,
 you'll forgive me if I completely misunderstand what is going on (also
 because I'm no osgeo4w/gdal guru), so don't hesitate to close this ticket.
 In this case if you can give me (us) an explanation/hint I will

 All started when testing under windows a plugin for qgis called "gdal
 tools" a nice interface for many gdal utilities: the plugin works fine
 under linux but under windows has problems apparently because of issues
 with the osgeo4w gdal utilities.

 This should be confirmed by the fact that the same tools under fwtools
 work fine.

 A few details:

 *) under windows XP all the tools that are in the form of .exe files work
 fine (both from  the command line and from the plugin)

 *) the same tools under Vista/Seven return errors (both from  the command
 line and from the plugin) like

 "gdalinfo.exe has stopped working"


 "gdalbuildvrt.exe has stopped working"

 eventually they produce the correct output

 this doesn't happens with fwtools binaries.


 Under all windows versions there are also issues with the tools in the
 form of python scripts

 *) If during the osgeo4w install it is added *just* the
 gdal16/gdal16-python libraries/packages, then all
 the gdal utilities that are wrote in python fail to work. The error is
 always like (both from  the command line and from the plugin):


 'import site' failed; use -v for traceback
 Traceback (most recent call last):
   File "c:/osgeo4w/apps/gdal-16/bin/gdal_merge.py", line 31, in <module>
     import gdal
 ImportError: No module named gdal


 *) I then tested also to install with osgeo4w the gdal/gdal-python
 libraries/packages (I know, probably not a good idea, but was just a
 test). This way the gdal merge utility then seems to work (as also
 rgb2pct), while all others still fail, example:

 gdal.Polygonize() not available.  You are likely using "old gen"
 bindings or an older version of the next gen bindings.

 Traceback (most recent call last):
 File "C:\osgeo4w\apps\gdal-16\bin\gdal_proximity.py", line 170, in
 gdal.ComputeProximity( srcband, dstband, options,
 AttributeError: 'module' object has no attribute 'ComputeProximity'

Ticket URL: <http://trac.osgeo.org/osgeo4w/ticket/161>
OSGeo4W <http://trac.osgeo.org/osgeo4w>
OSGeo4W is the Windows installer for the OSGeo stack.

More information about the osgeo4w-dev mailing list