[GRASS-user] grass-user Digest, Vol 157, Issue 33

GRASS GRASS user
1

Hi Everyone,
I think I figured out the problem.
I found that the problem was only the size or number of attributes in the point layer when I dropped and reduced the attributes it worked very fast and with no problem.
I am interested to know the limitations in GRASS GIS in terms of the number of features or attributes, if there is any reference, please let me know.

Thanks,

Mehrdad

ᐧ

···

Mehrdad Varedi

2

Hi

Mehrdad Varedi <varedi@gmail.com> schrieb am Di., 28. Mai 2019, 19:38:

Subject: Re: [GRASS-user] v.what.vect never ends, SQLite warning

Hi Everyone,
I think I figured out the problem.
I found that the problem was only the size or number of attributes in the point layer when I dropped and reduced the attributes it worked very fast and with no problem.
I am interested to know the limitations in GRASS GIS in terms of the number of features or attributes, if there is any reference, please let me know.

Yes, please see

https://grasswiki.osgeo.org/wiki/GRASS_GIS_Performance#Vector_management

Best
Markus

3

Thank you, Markus, for sharing.

The link you send indicates that the SQLite supports up to 2000 columns and the size can be 140TB. In my case, the number of columns was 60 that majority of them had REAL types. It had around 250K rows. My guess is that it is not the SQLite issue and something in between causes the problem. Maybe something on my computer or the way GRASS interacts with SQLite (probably some setting such as buffer size, on my computer etc. might be an issue)

If you are aware of any settings that I could play with, please let me know to speed up (read/write or Import / export) of layers in GRASS.

Kind regards,

Mehrdad

ᐧ

···

Mehrdad Varedi