[GRASS-dev] Re: [GRASS GIS] #699: v.buffer2 segfault: in Vect_get_isle_points()

GRASS GIS trac at osgeo.org
Mon Apr 4 06:10:34 EDT 2011


#699: v.buffer2 segfault:  in Vect_get_isle_points()
----------------------+-----------------------------------------------------
  Reporter:  neteler  |       Owner:  grass-dev@…              
      Type:  defect   |      Status:  closed                   
  Priority:  normal   |   Milestone:  7.0.0                    
 Component:  Vector   |     Version:  6.4.0 RCs                
Resolution:  fixed    |    Keywords:  v.buffer                 
  Platform:  All      |         Cpu:  All                      
----------------------+-----------------------------------------------------

Comment(by mmetz):

 Replying to [comment:26 mlennert]:
 > However, testing with the other example (see Mon, Oct 9 2006 08:02:33)
 from the old RT report gives the following, seems to reveal some remaining
 issues.
 >
 > First of all, I cannot reproduce the procedure exactly, as the v.buffer
 call with bufcolumn=lane_cout gives me
 >
 >
 {{{
 > GRASS 7.0.svn (nc_spm_06):~ > v.buffer vbuf_fill_bug bufcol=lane_count
 out=vbuf_fill_bug_lanes scale=150
 > ATTENTION : The bufcol option may contain bugs during the cleaning step.
 If
 >             you encounter problems, use the debug option or clean
 manually
 >             with v.clean tool=break; v.category step=0; v.extract -d
 >             type=area
 > ERREUR :The bufcol option requires a valid layer.
 }}}
 >
 > Looking at the table connection info:
 >
 {{{
 > GRASS 7.0.svn (nc_spm_06):~ > v.db.connect -p $OUTMAP
 > Vector map <vbuf_fill_bug> is connected by:
 > layer <1/vbuf_fill_bug> table <vbuf_fill_bug> in database
 </home/mlennert/GRASS/DATA/nc_spm_06/mlennert/dbf/> through driver <dbf>
 with key <cat>
 }}}
 >
 > the layer <1/vbuf_fill_bug> looks weird. This should be layer <1>, no ?
 (At least it is in dev6).

 The syntax is <number>/<name>, nothing wrong there. When using v.buffer(2)
 with the bufcolumn option, layer must be specified because it defaults to
 all layers (-1). Without the bufcolumn option, all features of the
 selected type should be buffered, also those without category in one of
 the map's layers.

 Markus M

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



More information about the grass-dev mailing list