[GRASS-dev] Re: [GRASS GIS] #338: d.vect / v.univar does not work for layer > 1 ; v.db.join has bugs (corrected here)

[GRASS GIS]

#338: d.vect / v.univar does not work for layer > 1 ; v.db.join has bugs
(corrected here)
---------------------------+------------------------------------------------
  Reporter:  aprasad       |       Owner:  grass-dev at lists.osgeo.org
      Type:  defect        |      Status:  closed                   
  Priority:  major         |   Milestone:  6.4.0                    
 Component:  Vector        |     Version:  6.3.0                    
Resolution:  fixed         |    Keywords:  layers > 1               
  Platform:  MSWindows XP  |         Cpu:  x86-32                   
---------------------------+------------------------------------------------
Changes (by mlennert):

  * status:  new => closed
  * resolution:  => fixed

Comment:

 Replying to [ticket:338 aprasad]:
 > Two bugs:
 > 1) d.vect does not work for layer > 1 (blank display)

 I cannot confirm this. Can you be more precise, including output of
 'v.category [...] option=report' on your map ?

 > d.vect.thematic has a bug i.e., does not include the layer option in
 v.univar it uses - However, including this option does NOT help ...
 BECAUSE v.univar does not work for layers > 1 (gives no values)

 Again, I cannot confirm. Same remark as above.

 >- so used v.univar.sh which works (since it uses database, driver and
 table options - DON'T DEPRECATE IT YET)....BUT THEN, d.vect does not work
 for layers > 1 (blank display) - which is used by d.vect.thematic.

 v.univar.sh is different in that it is not linked to a specific vector map
 (its man page is misleading in that sense), you can use it to interrogate
 any column of any table in any database supported by grass, but no need
 for any link to specific maps.

 > 2) v.db.join: The layer option was missing in v.db.addcol and, in
 db.execute, 'driver' and 'database' options were missing thus breaking it
 for layer > 1

 Fixed in Revision 33971.


 > NOTE: I have a feeling that the v.* commands involving layer= is very
 buggy and insufficiently tested for layer > 1

 I rather strongly suspect that you are not using layers properly.

 Closing the bug.
 Moritz

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/338#comment:1>
GRASS GIS <http://grass.osgeo.org>