#1477: error running v.what.vect under Windows/Osgeo4w
--------------------------+-------------------------------------------------
  Reporter:  lutra        |       Owner:  grass-dev@…              
      Type:  defect       |      Status:  closed                   
  Priority:  major        |   Milestone:  6.4.3                    
 Component:  Vector       |     Version:  svn-trunk                
Resolution:  invalid      |    Keywords:                           
  Platform:  MSWindows 7  |         Cpu:  Unspecified              
--------------------------+-------------------------------------------------

Comment(by lutra):

 > This is a QGIS (or better to say GRASS plugin) bug. You should report it
 in QGIS tracker.

 Probably is not true.

 I made a few further tests, using various QGIS standalone installers,
 that were all made using osgeo4w packages. Every installer was shipped
 with his own copy/version of GRASS. I obtain the GRASS version by
 issuing g.version from the GRASS shell.

 From QGIS 1.5 to 1.7 it all works fine. Things got broken with QGIS
 1.7.1 which ships GRASS 6.4.2


 The command I tested were


 {{{
 v.what.vect vector=pontos@mapset_agueda =point layer=1 column=puppa
 qvector=freguesias@mapset_agueda =area layer=1 qcolumn=NOME_COM
 }}}




 {{{
 v.generalize input=provincias@mapset_agueda type=area layer=1 -c
 type=boundary method=douglas threshold=100 look_ahead=7 reduction=50
 slide=0.5 angle_thresh=3 degree_thresh=0 closeness_thresh=0
 betweeness_thresh=0 alpha=1.0 beta=1.0 iterations=1 layer=1 output=puppa
 }}}



 They works ok with

 QGIS 1.5
 GRASS 6.4.0svn (2010)

 QGIS 1.6
 GRASS 6.4.0 (2010)

 QGIS 1.7
 GRASS 6.4.1 (2011)



 They don't work with

 QGIS 1.7.1
 GRASS 6.4.2RC148715M (2011)



 The QGIS/GRASS plugin hasn't changed between QGIS 1.7 and 1.7.1

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

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

Reply via email to