Martin Landa <landa.martin <at> gmail.com> writes: > > Hi, >
> note that you can create a new vector map also using v.edit or v.in.ascii, > e.g. > v.edit map=Skuska1 tool=create I am using create new vector map with v.digit for this test (It's wrong way?) but table created with v.db.addtable for this vector map (problem with editing I had also with editing [add, drop, rename column] exist vector map for example contour derived from dmt with r.contour), but when I am using v.edit to create new vector map and create table and I am trying add column is working now (working add, drop, rename column from wxpython ATM, cli also), but I am updating my system before. It is different to creating vector map with v.digit and v.edit for this tests. . > 3) v.db.connect map=Skuska1 table=Skuska1 -o This is not needed, v.db.addtable connects newly created table to the vector map. Yes, I know. > Assuming, that 'Polana_a_okolie_1k10000_5m' is your current mapset. It > works for me (6.4.0svn, GNU/Linux). Yes 'Polana_a_okolie_1k10000_5m' is my current mapset. My OS is GNU/Linux distributuon: Archlinux GRASS version: grass-6.4.svn_src_snapshot_2009_07_04 Cpu: i686, x86-64 But now is vector editing work good (updating my system Archlinux on both computer i686, x86-64), or this problem related with I am using v.digit to create new vector map instead of v.edit? Thanks Martin. Tomas _______________________________________________ grass-user mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-user
