[GRASS5] [bug #4250] (grass) v.out.ogr: CHAR columns are trimmed to 80 chars when writing shp
Maciek Sieczka via RT
grass-bugs at intevation.de
Fri Apr 7 04:24:52 EDT 2006
Hamish wrote:
> what does 'dbview -e' say about the dbf coulumns before and after export?
### the dbf BEFORE export
$ dbview -e /home/grassdata/caves_utm33/wlasnosc2/dbf/test.dbf
Field Name Type Length Decimal Pos
Cat N 11 0
Parcel no C 80 0
Maps use C 80 0
Maps class C 80 0
Maps cover C 20 0
Owner cod N 11 0
Owner nam C 249 0
Owner nmb N 11 0
Owner loc C 80 0
Tenant cod N 11 0
Tenant nam C 80 0
Tenant loc C 80 0
Host cod N 11 0
Area N 20 6
Lndrcl lev N 11 0
Lndrcl clt N 11 0
### the dbf AFTER export
$ dbview -e /home/john/test/test.dbf
Field Name Type Length Decimal Pos
Cat N 11 0
Parcel no C 80 0
Maps use C 80 0
Maps class C 80 0
Maps cover C 80 0
Owner cod N 11 0
Owner nam C 80 0
Owner nmb N 11 0
Owner loc C 80 0
Tenant cod N 11 0
Tenant nam C 80 0
Tenant loc C 80 0
Host cod N 11 0
Area N 24 15
Lndrcl lev N 11 0
Lndrcl clt N 11 0
### Interesting is that the "Area" attribute properties changed too, isn't
### that wrong?
> what if you just copy the $MAPSET/dbf/ file to be with your .shp file?
If I do that, the relationship between objects in the shapefile and dbf file
is lost. Querries in QGIS prove that. Apparently the dbf is somewhat processed
by v.out.ogr when writing a shapefile.
Maciek
-------------------------------------------- Managed by Request Tracker
More information about the grass-dev
mailing list