[GRASS-user] v.to.db/v.what rast on large vector sets

Markus Neteler neteler at osgeo.org
Tue Aug 11 14:33:15 PDT 2015

On Mon, Aug 10, 2015 at 9:51 AM, patrick s. <patrick_gis at gmx.net> wrote:
> Dear grass-users
> First off all- sorry for "spamming" this user-list recently with questions.

That's fine!

> I don't know any grass-users that I could ask. So this list is the only
> feedback I can get for support and I am happy it works so well.  So my
> Thanks to all of you, for the recommendations given!
> Now my issue:
> I have a dataset with 30Mio Vectorpoints that need to get attributes added:
> the coordinates and the values of approx.60 rasters (resolution of 25m
> across Switzerland). While the processing of the raster-data was fast, this
> final join is very slow. Only adding x and y -coordinate is at 14% after 15h
> of processing; v.to.db currently still using 100%CPU. Is this expected
> behavior or an error of my system (Grass70 with SQLITE, Ubuntu 15.04)?

For easier testing, could you provide a simple cmd line example?
Ideally with the North Carolina dataset?

To simulate 30 mio Vector points, just set the raster resolution to cm
or the like.
An example with way less points is also fine, scaling it to more
points is easier than writing it from scratch...


More information about the grass-user mailing list