2011/3/29 António Rocha <[email protected]>: > Hello Markus > Unfortunely, I get this error when I run other datasets. In this case, a > landCover with all CELLS and spatial resolution of 30. The problem is that > North carolina sample is too small. > r.to.vect -v input=FULL@PERMANENT output=FULL feature=area > I get this: > Default driver / database set to: > driver: dbf > database: $GISDBASE/$LOCATION_NAME/$MAPSET/dbf/ > Extracting areas... > Building topology for vector map <PT_National_2000_FULL>... > R4243000ERROR: G_realloc: unable to allocate 16976004 bytes at > struct_alloc.c:133 > > It has created a vector but I cannot display and I cannot use v.info (it > says that I need to build topology). > And If I try to build topology I get and error and before this warning: > Coor files of vector map <PT_National_2000_FULL@PERMANENT> is larger than it > should be (241464079 bytes excess) > > So my questions are: > 1- Is any fix for this? > 2- If not, is there any defined limit for a raster in order to be converted > to vector? > Since this is an out-of-memory error, you could try grass 7 and in your terminal
export GRASS_VECTOR_LOW_MEM=1 before running r.to.vect. This will reduce memory requirements while building topology. Large File Support is probably not needed here, but nowadays a good thing to have, just in case. Markus M > > Markus Neteler wrote: >> >> 2011/3/23 António Rocha <[email protected]>: >> >>> >>> A couple of months ago I sent a few messages regarding a memorry error >>> with >>> r.to.vect (it was allocating to many information and data). My question >>> is, >>> sicne r.to.vect was not updated, is there any raster or vector lib update >>> that had any impact on this? >>> >> >> Did you post a test case? Best done with the North Carolina sample >> data set. Otherwise it is hard to replicate... >> >> Markus >> _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
