[GRASS-dev] [GRASS GIS] #2045: r.to.vect: use less memory

GRASS GIS trac at osgeo.org
Wed Jun 29 00:58:17 PDT 2016

#2045: r.to.vect: use less memory
  Reporter:  mlennert     |      Owner:  grass-dev@…
      Type:  enhancement  |     Status:  closed
  Priority:  normal       |  Milestone:  7.0.5
 Component:  Raster       |    Version:  svn-trunk
Resolution:  fixed        |   Keywords:  r.to.vect
       CPU:  Unspecified  |   Platform:  Unspecified

Comment (by mmetz):

 Replying to [comment:25 mlennert]:
 > Replying to [comment:20 mmetz]:
 > > Replying to [comment:19 mlennert]:
 > > >
 > > > Data and info provided via private mail.
 > >
 > > I have received the data, thanks!
 > >
 > > >
 > > > Previous posters have also reported that setting GRASS_VECTOR_LOWMEM
 didn't make much of a difference, so maybe the problem is there ?
 > >
 > > I don't think so. Without GRASS_VECTOR_LOWMEM, v.build needs about 26
 GB of RAM. With GRASS_VECTOR_LOWMEM, v.build needs about 11 GB of RAM
 > A question that came up in a discussion with colleagues: could this
 memory need be determined before building topology and possibly check for
 enough available memory / warn the user ?

 Unfortunately not because the number of features is unknown when topology
 building starts. What could be done is counting primitives without
 building topology, then estimate memory requirements just for these
 primitives. The number of areas can not be estimated.

Ticket URL: <https://trac.osgeo.org/grass/ticket/2045#comment:26>
GRASS GIS <https://grass.osgeo.org>

More information about the grass-dev mailing list