[GRASS-user] Re: [GRASS-dev] ERROR: G_realloc: during r.to.vect call

[António Rocha]

Hello Markus

I believe it's ok:
projection: 1 (UTM)
zone:       -24
datum:      wgs84
ellipsoid:  wgs84
north:      9305500.00000001
south:      9095770.00000001
west:       444000
east:       689130
nsres:      30
ewres:      30
rows:       6991
cols:       8171
cells:      57123461

And my raster is:
|   Type of Map:  raster               Number of Categories: 
3               |
 |   Data Type:    
CELL                                                       |
 |   Rows:         
6991                                                       |
 |   Columns:      
8171                                                       |
 |   Total Cells:  
57123461                                                   |
 |        Projection: UTM (zone 
-24)                                          |
 |            N: 9305500.00000001    S: 9095770.00000001   Res:    
30         |
 |            E:     689130    W:     444000   Res:    
30                     |
 |   Range of data:    min = 0  max = 
3                                       |

So it matches. What might be causing this error?

Antonio

Markus Neteler wrote:
> 2010/11/18 António Rocha <antonio.rocha at deimos.com.pt>:
>   
>> Greetings
>>
>> I'm running GRASS (in Windows) and, for a specific raster, when I try to run
>> v.to.rast I get this error:
>> ERROR: G_realloc: unable to allocate 33760000 bytes at areas.c:678
>>
>> 1- Is this expectable?
>> 2- is there any fix for this? If not, does anyone has any suggestion to
>> avoid this error?
>>     
>
> Did you check the computation region with
> g.region -p
> ? Just to be sure that extent and resolution are right...
>
> Markus
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus signature database 5631 (20101118) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
>
>   



__________ Information from ESET NOD32 Antivirus, version of virus signature database 5632 (20101119) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com