there is also the thing about you're only supposed to be allowed to write to
things in the current mapset. (db.select doesn't write, other tools might..)
H
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/
On 14/05/09 11:39, Benjamin Ducke wrote:
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.
Well, if you are in the same location, all you have to do is replace
$MAPSET with PERMANEN
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,
On Thu, May 14, 2009 at 10:51 AM, Moritz Lennert
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= para
On 13/05/09 14:28, Markus Neteler wrote:
On Wed, May 13, 2009 at 2:05 PM, Benjamin Ducke
wrote:
Dear all,
I just came across an issue with vector maps in the PERMANENT mapset
and was wondering if anyone else had the same problem.
Whenever I want to get read access to a DBF attribute table for
OK, that clarifies it!
Thanks,
Ben
Markus Neteler wrote:
On Wed, May 13, 2009 at 2:05 PM, Benjamin Ducke
wrote:
Dear all,
I just came across an issue with vector maps in the PERMANENT mapset
and was wondering if anyone else had the same problem.
Whenever I want to get read access to a DBF a
On Wed, May 13, 2009 at 2:05 PM, Benjamin Ducke
wrote:
> Dear all,
>
> I just came across an issue with vector maps in the PERMANENT mapset
> and was wondering if anyone else had the same problem.
>
> Whenever I want to get read access to a DBF attribute table for
> a vector file in PERMANENT (whi
Dear all,
I just came across an issue with vector maps in the PERMANENT mapset
and was wondering if anyone else had the same problem.
Whenever I want to get read access to a DBF attribute table for
a vector file in PERMANENT (while logged into a user mapset),
e.g. using "db.select ", I get:
DBM
