[GRASS-user] v.rast.stats error: "Unable to seek"

[Stefan Blumentrath]

Hi again Luis,

The error comes from v.to.rast (which is used inside v.rast.stats).

From the error message (which suggests that the G_fseek() function gets an invalid argument), it occurs most likely here: https://github.com/OSGeo/grass/blob/master/lib/gis/seek.c 
However, the root cause may be at a different place...

Could you try:

a) if assigning more memory to v.to.rast has any effect
v.to.rast input=PSU output=test use=cat memory=10000
b) if assigning category values to the raster causes problems
v.to.rast input=PSU output=test use=val value=1
in order to narrow down a bit?

Please also report v.info PSU -c (to see data types of the columns)...

Anyway, I guess here are people with C-knowledge required...

Cheers
Stefan

-----Original Message-----
From: Luís Moreira de Sousa <luis.de.sousa at protonmail.ch> 
Sent: tirsdag 2. februar 2021 15:56
To: Stefan Blumentrath <Stefan.Blumentrath at nina.no>
Cc: Micha Silver <tsvibar at gmail.com>; GRASS user list <grass-user at lists.osgeo.org>
Subject: RE: [GRASS-user] v.rast.stats error: "Unable to seek"

Thank you all for various replies. Some reactions:

1. The workstation has 32 GB of RAM and 12 CPU. What is the expected RAM requirements for v.rast.stats?

2. v.to.rast also fails, see below.

3. What would be the way to check the health of the vector? The table in Postgres at least is fully usable.



> v.to.rast input=PSU output=test use=cat
ERROR: Unable to seek: Invalid argument



--
Luís

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Monday, February 1, 2021 11:56 PM, Stefan Blumentrath <Stefan.Blumentrath at nina.no> wrote:

>
> So the vector contains about 20 million polygons, and the raster about 8 billion cells. (~=32GB ?)
>
> Does you computer have enough muscle for this?
>