[GRASS-dev] [GRASS GIS] #1464: Bug on v.buffer

[GRASS GIS]

#1464: Bug on v.buffer
----------------------+-----------------------------------------------------
 Reporter:  leonidas  |       Owner:  grass-dev@…              
     Type:  defect    |      Status:  new                      
 Priority:  normal    |   Milestone:  7.0.0                    
Component:  Vector    |     Version:  svn-trunk                
 Keywords:  v.buffer  |    Platform:  All                      
      Cpu:  All       |  
----------------------+-----------------------------------------------------

Comment(by martinl):

 Replying to [comment:5 neteler]:
 > Replying to [comment:4 mmetz]:
 > > Fixed in trunk in r51580, as long as GRASS is compiled with GEOS.
 Neither one of the two GRASS-internal buffering methods is working
 correctly. Moreover, the GEOS method is the only one allowing for internal
 buffers with negative distances. Should we disable v.buffer if GEOS is not
 available (rather have no result than a wrong result)?
 >
 > I suppose that GEOS is available for all relevant platforms nowadays
 (and it became
 > official OSGeo project yesterday). So I support this suggestion.

 +1 for disabling `v.buffer` when GRASS not compiled against GEOS.

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