A cruder way might be to make a new 1-point vector map and
then overlay it.
nothing crude about that method, if anything I'd call it a little
less direct, but safer. shrug, v.in.ascii + v.patch added to the
FAQ as an alternate method. (many roads to get there...)
I couldn't get the attribute manager working. I tried an old favorite v.in.db. I exported the wedge_tomb table, added what I needed. Now I'm trying to import it. This is what's happening
GRASS 6.4.1 (Mega_Ireland):~ > v.in.db --overwrite table=wedge_tomb driver=sqlite database=/Users/kurtsprings/Document/wedge.db x=nat_grid_e y=nat_grid_n key=cat output=wedge_tomb
WARNING: Vector map <wedge_tomb> already exists and will be overwritten
DBMI-SQLite driver error:
Unable to open database: unable to open database file
WARNING: Unable to open database </Users/kurtsprings/Document/wedge.db> by
driver <sqlite>
ERROR: Unable to open database <$GISDBASE/$LOCATION_NAME/$MAPSET/sqlite.db>
by driver <sqlite>
I had been able to do this a year ago, but I can't find my notes on this. Any ideas as to what I'm doing wrong?
Kurt
On Sep 24, 2011, at 10:27 AM, Martin Landa wrote:
Hi,
2011/9/24 Hamish <hamish_b@yahoo.com>:
A cruder way might be to make a new 1-point vector map and
then overlay it.
nothing crude about that method, if anything I'd call it a little
less direct, but safer. shrug, v.in.ascii + v.patch added to the
why safer?
Anyway using this method you are producing extra vector map used only
for patching.
On Sat, Sep 24, 2011 at 5:46 PM, Kurt Springs <ferret_bard@mac.com> wrote:
I couldn't get the attribute manager working. I tried an old favorite v.in.db. I exported the wedge_tomb table, added what I needed. Now I'm trying to import it. This is what's happening
GRASS 6.4.1 (Mega_Ireland):~ > v.in.db --overwrite table=wedge_tomb driver=sqlite database=/Users/kurtsprings/Document/wedge.db x=nat_grid_e y=nat_grid_n key=cat output=wedge_tomb
WARNING: Vector map <wedge_tomb> already exists and will be overwritten
DBMI-SQLite driver error:
Unable to open database: unable to open database file
WARNING: Unable to open database </Users/kurtsprings/Document/wedge.db> by
driver <sqlite>
ERROR: Unable to open database <$GISDBASE/$LOCATION_NAME/$MAPSET/sqlite.db>
by driver <sqlite>
I had been able to do this a year ago, but I can't find my notes on this. Any ideas as to what I'm doing wrong?
This can be a sqlite problem. Recent sqlite refuses to open a database
file if any other file in the same directory is kept open by any other
application. This is a new feature of new versions of sqlite (not
GRASS), I remember that this was not an issue about a year ago. You
could check if you have any other application running that has opened
some files there, e.g. QGIS. Just a guess.
Markus M
On Sep 24, 2011, at 10:27 AM, Martin Landa wrote:
Hi,
2011/9/24 Hamish <hamish_b@yahoo.com>:
A cruder way might be to make a new 1-point vector map and
then overlay it.
nothing crude about that method, if anything I'd call it a little
less direct, but safer. shrug, v.in.ascii + v.patch added to the
why safer?
Anyway using this method you are producing extra vector map used only
for patching.
I just reran it with everything but grass closed. I'm still having the problem.
Kurt
On Sep 24, 2011, at 12:02 PM, Markus Metz wrote:
On Sat, Sep 24, 2011 at 5:46 PM, Kurt Springs <ferret_bard@mac.com> wrote:
I couldn't get the attribute manager working. I tried an old favorite v.in.db. I exported the wedge_tomb table, added what I needed. Now I'm trying to import it. This is what's happening
GRASS 6.4.1 (Mega_Ireland):~ > v.in.db --overwrite table=wedge_tomb driver=sqlite database=/Users/kurtsprings/Document/wedge.db x=nat_grid_e y=nat_grid_n key=cat output=wedge_tomb
WARNING: Vector map <wedge_tomb> already exists and will be overwritten
DBMI-SQLite driver error:
Unable to open database: unable to open database file
WARNING: Unable to open database </Users/kurtsprings/Document/wedge.db> by
driver <sqlite>
ERROR: Unable to open database <$GISDBASE/$LOCATION_NAME/$MAPSET/sqlite.db>
by driver <sqlite>
I had been able to do this a year ago, but I can't find my notes on this. Any ideas as to what I'm doing wrong?
This can be a sqlite problem. Recent sqlite refuses to open a database
file if any other file in the same directory is kept open by any other
application. This is a new feature of new versions of sqlite (not
GRASS), I remember that this was not an issue about a year ago. You
could check if you have any other application running that has opened
some files there, e.g. QGIS. Just a guess.
Markus M
On Sep 24, 2011, at 10:27 AM, Martin Landa wrote:
Hi,
2011/9/24 Hamish <hamish_b@yahoo.com>:
A cruder way might be to make a new 1-point vector map and
then overlay it.
nothing crude about that method, if anything I'd call it a little
less direct, but safer. shrug, v.in.ascii + v.patch added to the
why safer?
Anyway using this method you are producing extra vector map used only
for patching.
I meant to say. I reran v.in.db with all other programs closed as Markus Metz suggested. I still got the error message:
GRASS 6.4.1 (Mega_Ireland):~ > v.in.db --overwrite table=wedge_tomb driver=sqlite database=/Users/kurtsprings/Document/wedge.db x=nat_grid_e y=nat_grid_n key=cat output=wedge_tomb
WARNING: Vector map <wedge_tomb> already exists and will be overwritten
DBMI-SQLite driver error:
Unable to open database: unable to open database file
WARNING: Unable to open database </Users/kurtsprings/Document/wedge.db> by
driver <sqlite>
ERROR: Unable to open database <$GISDBASE/$LOCATION_NAME/$MAPSET/sqlite.db>
by driver <sqlite>
I've used this method successfully before Lion.
When I tried the wxGUI Attribute manager, as in you video, I was unable to access anything in the fields to make entries. I'd try to recreate it, but I did something to the my $LOCATION in my struggle with it and am trying to reload an older version from my lap top. GRASS apparently does not like time machine.
So much for something that should only take a few minutes.
Kurt
On Sep 24, 2011, at 12:41 PM, Martin Landa wrote:
2011/9/24 Kurt Springs <ferret_bard@mac.com>:
I just reran it with everything but grass closed. I'm still having the problem.
sorry, what means "I just reran it with everything"? Please provide
more detailed info. What means that "grass closed"? OS, etc...
On Sat, Sep 24, 2011 at 9:06 PM, Kurt Springs <ferret_bard@mac.com> wrote:
Sorry about that.
I meant to say. I reran v.in.db with all other programs closed as Markus Metz suggested. I still got the error message:
GRASS 6.4.1 (Mega_Ireland):~ >
This is really 6.4.1? We have made tons of fixes in 6.4.svn, if
you could update it would be cool and would either already
solve it for you are enable us to track it better down.
v.in.db --overwrite table=wedge_tomb driver=sqlite database=/Users/kurtsprings/Document/wedge.db x=nat_grid_e y=nat_grid_n key=cat output=wedge_tomb
WARNING: Vector map <wedge_tomb> already exists and will be overwritten
DBMI-SQLite driver error:
Unable to open database: unable to open database file
With "lsof" you could check who has opened the file (dunno where lsof
is on Mac), something like:
On Sun, Sep 25, 2011 at 12:40 AM, Markus Neteler <neteler@osgeo.org> wrote:
Hi Kurt,
I can understand your frustration. But...
On Sat, Sep 24, 2011 at 9:06 PM, Kurt Springs <ferret_bard@mac.com> wrote:
Sorry about that.
I meant to say. I reran v.in.db with all other programs closed as Markus Metz suggested. I still got the error message:
GRASS 6.4.1 (Mega_Ireland):~ >
This is really 6.4.1? We have made tons of fixes in 6.4.svn, if
you could update it would be cool and would either already
solve it for you are enable us to track it better down.
v.in.db --overwrite table=wedge_tomb driver=sqlite database=/Users/kurtsprings/Document/wedge.db x=nat_grid_e y=nat_grid_n key=cat output=wedge_tomb
WARNING: Vector map <wedge_tomb> already exists and will be overwritten
DBMI-SQLite driver error:
Unable to open database: unable to open database file
With "lsof" you could check who has opened the file (dunno where lsof
is on Mac), something like:
What I wanted to suggest was that another program but grass may keep
files in that folder, or even the sqlite database itself open.
You could try to close grass, open the database with sqlite or
sqlitebrowser and see if that works, then open grass and again try to
open the sqlite database not with grass but with sqlite or
sqlitebrowser. At least then we would know if the problem is with
sqlite or with grass.