Re: [GRASS-dev] Re: v.category: opt=del was changed

2008-12-07 Thread Martin Landa
Hi,

2008/12/7 Hamish [EMAIL PROTECTED]:
 Maciek:
  default all categories should be selected. I don't see a reason to
  change the default behaviour in GRASS 7 either.

 Martin:
 new behaviour can be useful if you want to remove not all categories,
 but only selected one (well, you can always use v.edit for that).


 perhaps we should better define what the modules are supposed to do.
 v.edit is clearly for incisive/targeted edits to a vector map, so at
 the other end we could promote v.category as the general purpose/bulk
 category maintenance tool. This would mean less for learning curve
 required, and less opportunity for new user confusion.
 In the same vein I wonder if the new v.cat ids= option offers anything new;
 IMO such raw/low-level stuff should be held for advanced use in v.edit.
 e.g. the v.cat module description explains what the cat is by calling it
 a type of ID number. And then we provide both cat= and and ids= options.

v.category seems to be designed to edit vector layer categories
globally (all features in given layer). I have added 'id' parameter
because of v.edit-based wxGUI digitizer. This part has been already
removed from wxGUI. So not needed any more. From this perspective,
'id' parameter could be removed from v.category. If user want to
add/delete category(ies) only for subset of features v.edit can be
used.

From this point of view I would suggest to remove 'id' parameter from
v.category and change 'del' in G7 to delete categories globally in
given layer.

Martin

-- 
Martin Landa landa.martin gmail.com * http://gama.fsv.cvut.cz/~landa *
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev


[GRASS-dev] Re: v.category: opt=del was changed

2008-12-06 Thread Martin Landa
Hi,

2008/12/6 Maciej Sieczka [EMAIL PROTECTED]:

 $ v.category opt=print in=pts
 1
 2
 3

 $ v.category opt=del in=pts out=pts_delcat

 $ v.category opt=print in=pts_delcat
 2
 3

 I.e. only category 1 is removed.

yes, only cat '1' is removed ('1' is default value for 'cat' parameter)

to remove all categories use 'cat=-1'

 Such a change in user interface is not acceptable for GRASS 6. By

well, you are right (reverted r34750).

 default all categories should be selected. I don't see a reason to
 change the default behaviour in GRASS 7 either.

new behaviour can be useful if you want to remove not all categories,
but only selected one (well, you can always use v.edit for that).

Martin

-- 
Martin Landa landa.martin gmail.com * http://gama.fsv.cvut.cz/~landa *
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev


[GRASS-dev] Re: v.category: opt=del was changed

2008-12-06 Thread Maciej Sieczka

Martin Landa pisze:

2008/12/6 Maciej Sieczka [EMAIL PROTECTED]:



Such a change in user interface is not acceptable for GRASS 6. By


well, you are right (reverted r34750).


Cool.


default all categories should be selected. I don't see a reason to
 change the default behaviour in GRASS 7 either.


new behaviour can be useful if you want to remove not all categories,
 but only selected one (well, you can always use v.edit for that).


So, given that v.edit already provides the functionality of removing
selected categories only (tool=catdel cats=), I suggest to revert to old
v.category opt=del behavior in GRASS 7 as well. There is no big enough
reason to change the interface in this regard IMO. I don't insist though.

Cheers,
Maciek

--
Maciej Sieczka
www.sieczka.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev


Re: [GRASS-dev] Re: v.category: opt=del was changed

2008-12-06 Thread Hamish
Maciek:
  default all categories should be selected. I don't see a reason to
  change the default behaviour in GRASS 7 either.

Martin:
 new behaviour can be useful if you want to remove not all categories,
 but only selected one (well, you can always use v.edit for that).


perhaps we should better define what the modules are supposed to do.
v.edit is clearly for incisive/targeted edits to a vector map, so at
the other end we could promote v.category as the general purpose/bulk
category maintenance tool. This would mean less for learning curve
required, and less opportunity for new user confusion.

In the same vein I wonder if the new v.cat ids= option offers anything new;
IMO such raw/low-level stuff should be held for advanced use in v.edit.
e.g. the v.cat module description explains what the cat is by calling it
a type of ID number. And then we provide both cat= and and ids= options.
What's a non-ultra-power user to think?

I've now added a line in the help page to explain cat=


2c,
Hamish



  

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev