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

OSGeo4W trac_osgeo4w at osgeo.org
Tue Mar 16 17:05:46 EDT 2010

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

 > Ah ok, you're not running from the OSGeo4W shell.  If you use the
 "standard" command
 > prompt you need to run {{{o4w_env.bat}}} to setup the environment for
 OSGeo4W.  Without it {{{%OSGEO4W_ROOT%}}} is unset and {{{gdal16.bat}}}
 won't set proper paths.

 new log attached.

 The gdal python commands issued from the osego4w shell are working this
 way. I see no changes when issuing the same one from the gdal tools plugin
 (qgis launched from the very same osgeo4w shell)

 Traceback (most recent call last):
 File "C:\OSGeo4W\apps\gdal-16\bin\gdal_proximity.py", line 35, in
 import gdal
 ImportError: No module named gdal

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

More information about the osgeo4w-dev mailing list