[GRASS-dev] [grass-code I][557] Columns are wrong for v.overlay output using dbf

[grass-dev at lists.osgeo.org]

code I item #557, was opened at 2007-12-06 19:13
Status: Open
Priority: 3
Submitted By: Otto Dassau (dassau)
Assigned to: Nobody (None)
Summary: Columns are wrong for v.overlay output using dbf 
Issue type: library bug
Issue status: None
GRASS version: CVS HEAD
GRASS component: None
Operating system: Linux
Operating system version: lenny
GRASS CVS checkout date, if applies (YYMMDD): 071023


Initial Comment:
I wanted to overlay two files in a mapset "dbase" (using standard dbf driver) with following command:

v.overlay ainput="test at dbase" atype="area" alayer=1 binput="cities at dbase" btype="area" blayer=1 output="testcities" operator="or" olayer=1,0,0

the geometries are ok, but the attribute table of the output map is wrong. Columns and headers don't fit anymore as in the original input maps. Then I added a new mapset "sqlite" and used sqlite as database with the same command and files then it was ok.

v.overlay ainput="test2 at sqlite" atype="area" alayer=1 binput="cities2 at sqlite" btype="area" blayer=1 output="test2cities2" operator="or" olayer=1,0,0

I guess there must be a problem with the dbf. Is this a known problem? I tested several times and was able to reproduce it. 

Would be great if someone could have a look into it. Therefore I created a small location with the two files and put it here:

http://www.nature-consult.de/dassau/grass/gk3.tar.gz

kind regards,
 Otto
  





----------------------------------------------------------------------

You can respond by visiting: 
http://wald.intevation.org/tracker/?func=detail&atid=204&aid=557&group_id=21