Ticket #867 (closed defect: fixed)
Buidling DBMS support for Grass and GDAL (Tishampati Dhar)
|Reported by:||leo.lami||Owned by:||nobody|
|Priority:||major: does not work as expected||Milestone:|
|Component:||OGR Layer support||Version:||Trunk|
|Must Fix for Release:||Yes||Awaiting user input:||no|
The dbf driver doesn't work if I work with GRASS vector. This a collect of mail on the arguments:
I can confirm the dbf problem in QGIS/GRASS. I am running QGIS 0.9.0 26.10.2007 build. My OS is Vista but I don't think it matters. I am also running WINGRASS 6.3RC3 and I got the same problem so something is broken in winGRASS now. See the error messages for more info. The messages are from the CLI from within QGIS
$ db.connect -p driver:dbf database:$GISDBASE/$LOCATION_NAME/$MAPSET/dbf/ schema: group:
The connection set up looks fine to me, but if you try getting info in a specific layer:
$ v.db.connect map=dist2_net3 -c Invalid argument: can't _spawnl
GRASS_INFO_ERROR(260,1): Unable to start driver <dbf> GRASS_INFO_END(260,1)
If I try db.describe from winGRASS I get this:
db.describe -c table=dist2_net3 driver=dbf
invalid argument: can't _spawnl
Unable to start driver <dbf>
Benjamin wrote: There are many little annoyances with the GDAL linking. But they can all be rectified (at least I managed for version 1.4.4, don't know about 1.5 yet).
I think I left out that final bit in my last email.
Here it is. For 1.5, you will probably need to update the last bit somewhat, since I think all user tools are now in the "apps" subfolder.
Let me know how it's working for you.