Right, that works!
However, setting the mapset via the "database=" option is awkward, since
you need to know all the actual locations in the file/network system.
How about adding a "mapset=" option that resolves these more
transparently for the user?
Thanks,
Ben
Markus Neteler wrote:
On Thu, May 14, 2009 at 10:51 AM, Moritz Lennert
<[email protected]> wrote:
On 13/05/09 14:28, Markus Neteler wrote:
On Wed, May 13, 2009 at 2:05 PM, Benjamin Ducke
...
AFAIK, you can. The problem is that db.* modules use the mapset database
definition by default, but if you explicitely set the databse= parameter to
point to the dbf directory in PERMANENT, you should be able to access the
data.
ah ok - once this is verified please update/add a note in the
db/databaseintro.html
files.
thanks
Markus
--
Benjamin Ducke
Senior Geospatial Consultant
Oxford Archaeology
Janus House
Osney Mead
OX2 0ES
Oxford, U.K.
Tel: +44 (0)1865 263 800 (switchboard)
Tel: +44 (0)1865 980 758 (direct)
Fax :+44 (0)1865 793 496
[email protected]
------
Files attached to this email may be in ISO 26300 format (OASIS Open Document
Format). If you have difficulty opening them, please visit http://iso26300.info
for more information.
_______________________________________________
grass-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-dev
