[GRASS-dev] [GRASS GIS] #2304: Problems with add category to all features workflow

[GRASS GIS]

#2304: Problems with add category to all features workflow
--------------------------+--------------------------------
  Reporter:  wenzeslaus   |      Owner:  grass-dev@…
      Type:  defect       |     Status:  new
  Priority:  normal       |  Milestone:  7.1.0
 Component:  Default      |    Version:  unspecified
Resolution:               |   Keywords:  v.edit, v.category
       CPU:  Unspecified  |   Platform:  Unspecified
--------------------------+--------------------------------

Comment (by mlennert):

 Replying to [comment:5 wenzeslaus]:
 > Unresolved:
 >

 >  * `v.category` has a parameter/option option while `v.edit` has a
 parameter tool

 The two modules do different things and I don't really see it as a problem
 that the parameters have different names.

 >  * `v.category` builds topology when there was no change

 v.category only does this when there is an output map and for any new map
 topology has to be built, so again, I don't see this as a problem.

 >  * `v.category` does nothing for `option=step`; using `option=sum` under
 the same conditions gives a result if there is something else to add, it
 is not in the example in manual

 There is no option=step. step is a separate parameter which allows to
 change the default step of 1 when v.category creates new cat values.

 >  * v.category says 0 features modified. when it finished report or print
 but it seems redundant I wouldn't expect something else when using report
 or print and not providing output

 I cannot reproduce this.


 >  * in GUI query tool, you will see that it shows only one layer and one
 category
 >   * now I see that layers are there but they are represented as separate
 maps which is not what I would expect since (layers are "inside" the map);
 I missed that before because I was querying more than one map and I
 considered the other (folded) row as one of the other maps
 >   * this needs separate ticket

 IMHO this behavior is debatable, but definitely not a bug.

 I again suggest closing this bug, as there is no actual bug report in
 here.

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/2304#comment:6>
GRASS GIS <http://grass.osgeo.org>