At the moment I solve it by splitting the label data ("category 3; category 12
..") to separate database backend columns. Use such modules like v.db.addcol,
v.db.select and v.db.update to create own columns for each crossing category.
But unfortunately it takes a little bit too long...
Regards,
Christian.
Am Dienstag, den 24.06.2008, 15:32 +0200 schrieb Christian Schwartze:
Zitat von Hamish <hamish_b@yahoo.com>:
> > Christian Schwartze
> > Ok and thanks, better to look at first within GRASS if
> > eveything is working fine
> >(in cats/ full category values) Because the reduced line
> > comes from QGIS
> > (selection tool). I forgot to say that following r.cross I
> > do a conversion with
> > r.to.vect and export the result to a shapefile. So the
> > original label vals were
> > mapped to dbf-column type "C". But why exporting only 80 chars?
>
>
> Does v.db.select show the cut string?
> which DB backend? (dbf?)v.db.select shows the full length of column label for all data rows - nothing
is
missing. I use dbf backend.
>
> "db.describe -c vect_map" ?ncols:3
Column 1:cat:INTEGER
Column 2:value:INTEGER
Column 3:label:CHARACTERChristian.
>
>
> Hamish
>
>
>
>
>
>----------------------------------------------------------------
This mail was sent through http://webmail.uni-jena.de
_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user
----------------------------------------------------------------
This mail was sent through http://webmail.uni-jena.de