[GRASS5] v.overlay errors

[Hamish]

[today's 5.7]


While running v.overlay I'm getting a zillion errors that look
like this:

...
WARNING: Cannot insert new row: insert into coast_bound6h values ( 2552,
         null, 3054 )
DBMI-DBF driver error:
SQL parser error in statement:
insert into coast_bound6h values ( 1, 14011, null )
Error in db_execute_immediate()
SQL parser error in statement:
insert into coast_bound6h values ( 2, 1, null )
Error in db_execute_immediate()
SQL parser error in statement:
insert into coast_bound6h values ( 3, 14265, null )
Error in db_execute_immediate()
SQL parser error in statement:
insert into coast_bound6h values ( 4, 1, null )
Error in db_execute_immediate()
SQL parser error in statement:
insert into coast_bound6h values ( 5, 14304, null )
Error in db_execute_immediate()
SQL parser error in statement:
insert into coast_bound6h values ( 6, 1, null )
Error in db_execute_immediate()
SQL parser error in statement:
insert into coast_bound6h values ( 7, null, 1 )
Error in db_execute_immediate()
SQL parser error in statement:
insert into coast_bound6h values ( 8, null, 109 )
Error in db_execute_immediate()
SQL parser error in statement:
insert into coast_bound6h values ( 9, null, 110 )
Error in db_execute_immediate()
SQL parser error in statement:
insert into coast_bound6h values ( 10, null, 111 )
Error in db_execute_immediate()
...


(14011, 14265, and 14304 are my 3 area categories in vect_A)


The command line looks something like:

v.overlay ain=vect_A bin=vect_B op=xor out=coast_bound6h

I don't think vect_A is connected to a database; don't know about
vect_B.


The other odd thing is vect_A's coor file is ~5.7mb, vect_B's coor file
is ~6.2mb, and currentlt vect_C's coor file is up to 14.2mb .. shouldn't
it be smaller than the sum of the two inputs?

It's still running now, the coor file is slowly growing in size..


?

Hamish