Thanks for the replies. db.connect would do what I want, but I think my issue is a bit more tricky. Actually, I use GRASS7 as a backend for some WPS processes, and as it seems to me: every WPS process creates a temporary workspace. I may be able to run v.db.connect via WPS, but it would have effect on a vector map (which is also temporary), so it has nothing to do with the next process I want to execute. The reason I wish to use dbf driver instead of SQLite is the following: There's a package called Geo-MHYDAS, which had a module m.definput [1]. This module gives the error message: ERROR: Sorry, but only dbf driver accepted. So that is why I want to find an "universal" solution. Any thoughts?
Cheers, Levente [1]: http://www.openfluid-project.org/resources/docs/mhydas/en/segmentation/html/m.definput.html 2013/7/3 Hamish <[email protected]> > MarkusM: > > > Note that the dbf/ subdirectory in the mapset must exist or must be > > created by the user. > > I think that usually it gets created as needed automatically. There > may still be a few places it doesn't, if so file a ticket to fix.. > (did a long audit for that in grass6 some time ago, tested in grass7 > last week & it was automatically created as needed.) > > > Hamish > >
_______________________________________________ grass-user mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-user
