[GRASS-user] v.to.db

Paolo Craveri pcraveri at gmail.com
Sun Jan 25 09:07:00 EST 2009


Hi

2009/1/20 Martin Landa <landa.martin at gmail.com>:
> Hi,

>
> should be fixed in r35515.
>
> Martin
>
> --
> Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa *
>

I have just updated   grass6.4 from svn but error remains.

ciao

-- 
-- 
Paolo C.
Lat. 44° 39' 11.08'' N  Long. 7° 23' 25.26'' E
-------------- next part --------------
GRASS 6.4.svn (spearfish60):~/script_grass > ./vtodb.sh -s
+ g.copy vect=archsites,mypoints --o
Copy vector <archsites at PERMANENT> to current mapset as <mypoints>
WARNING: Vector map <mypoints> already exists and will be overwritten
+ v.category in=mypoints out=mypoints2 layer=2 opt=add --o
WARNING: Vector map <mypoints2> already exists and will be overwritten
Processing features...
0 new centroids placed in output map
Copying attribute table(s)...
Building topology for vector map <mypoints2>...
Registering primitives...
25 primitives registered
25 vertices registered
Building areas...
 100%
0 areas built
0 isles built
Attaching islands...
Attaching centroids...
 100%
Number of nodes: 25
Number of primitives: 25
Number of points: 25
Number of lines: 0
Number of boundaries: 0
Number of centroids: 0
Number of areas: 0
Number of isles: 0
v.category complete. 25 features modified.
+ v.db.connect -d mypoints2 layer=1
+ db.droptable mypoints2 -f
Forcing ...
+ echo CREATE TABLE mypoints2_2 (cat integer, x double precision, y double precision)
+ db.execute
+ v.db.connect map=mypoints2 layer=2 key=cat table=mypoints2_2
The table <mypoints2_2> is now part of vector map <mypoints2> and may be
deleted or overwritten by GRASS modules
Select privileges were granted on the table
+ v.to.db mypoints2 layer=2 opt=cat col=cat
Reading features...
 100%
ERROR: Database connection not defined for layer 1. Use v.db.connect first.
+ v.to.db mypoints2 layer=2 opt=coor col=x,y
Reading features...
 100%
ERROR: Database connection not defined for layer 1. Use v.db.connect first.
+ v.db.addtable mypoints2 layer=1
Using vector map name as table name: mypoints2
Creating new DB connection based on default mapset settings...
Creating table with columns (cat integer)
The table <mypoints2> is now part of vector map <mypoints2> and may be
deleted or overwritten by GRASS modules
Select privileges were granted on the table
Reading features...
 100%
Updating database...
 100%
25 categories read from vector map (layer 1)
25 categories read from vector map don't exist in selection from table
25 records updated/inserted (layer 1)
Current attribute table links:
Vector map <mypoints2 at user1> is connected by:
layer <2> table <mypoints2_2> in database </home/paolo/grassdata/spearfish60/user1> through driver <dbf> with key <cat>
layer <1> table <mypoints2> in database </home/paolo/grassdata/spearfish60/user1> through driver <dbf> with key <cat>
+ v.to.db mypoints2 layer=2 opt=cat col=cat
Reading features...
 100%
Updating database...
 100%
25 categories read from vector map (layer 2)
25 categories read from vector map don't exist in selection from table
25 records updated/inserted (layer 2)
+ v.to.db mypoints2 layer=2 opt=coor col=x,y
Reading features...
 100%
Updating database...
 100%
25 categories read from vector map (layer 2)
25 records selected from table (layer 1)
25 categories read from vector map exist in selection from table
25 records updated/inserted (layer 2)


More information about the grass-user mailing list