[GRASS-dev] [GRASS GIS] #502: wxgui / osgeo4w: db.describe execution failed

[Michael Barton]

On Feb 20, 2009, at 10:00 AM, <grass-dev-request at lists.osgeo.org> wrote:

> Date: Fri, 20 Feb 2009 10:09:05 -0000
> From: "GRASS GIS" <trac at osgeo.org>
> Subject: [GRASS-dev] [GRASS GIS] #502: wxgui / osgeo4w: db.describe
> 	execution failed
> To: undisclosed-recipients:;
> Message-ID: <040.7806610de8996e5f24c200e36fdf6045 at osgeo.org>
> Content-Type: text/plain; charset="utf-8"
>
> #502: wxgui / osgeo4w: db.describe execution failed
> ---------------------- 
> +-----------------------------------------------------
> Reporter:  hamish    |       Owner:  grass-dev at lists.osgeo.org
>     Type:  defect    |      Status:  new
> Priority:  major     |   Milestone:  6.4.0
> Component:  Database  |     Version:  6.4.0 RCs
> Keywords:  osgeo4w   |    Platform:  MSWindows XP
>      Cpu:  x86-32    |
> ---------------------- 
> +-----------------------------------------------------
> Hi,
>
> latest OSGeo4W binary install of 6.4.0rc3 on windows xp.
>
> using the wxpython GUI.
>
> Spearfish: add vector map
>
> select roads. (or any other map)
> don't even press [ok].
>
> pop up error:
> {{{
> window title: Error in command execution db.describe.exe
>
> Execution failed 'db.describe.exe -c --q table=roads driver=dbf
> database=C:/DocumentsandSettings/Hamish/grassdata/spearfish60/ 
> PERMANENT/dbf/'
>
> Details:
> Error: Unable to open database
> <C:/DocumentsandSettings/Hamish/grassdata/spearfish60/PERMANENT/dbf/>
> }}}
>
> perhaps it is something to do with the spaces being stripped out of
> "DocumentsandSettings" ??
>
>
> after that the map renders ok, but I get the same error if I try to  
> query
> the vector map.
>
> querying the elevation.10m raster map spits out some error messages  
> to the
> output window but then scrolls away and gives good data. (sorry  
> already
> gone, no cut&paste)
>
>
> Hamish

Hamish,

Just helped a visiting student install the OSGeo4W GRASS yesterday and  
hit several of the issues you mention. This one is easy to work  
around, but I don't know how to fix.

The problem is because db.describe won't parse path names with spaces-- 
at least in our case. When we moved the GRASS database to C:/grassdata  
all worked fine.

Michael