[GRASS-user] v.color takes a long time for 2E6 records

[Markus Metz]

On Wed, May 30, 2018 at 11:50 PM, Mehrdad Varedi <varedi at gmail.com> wrote:
>
> Hi Everyone,
>
> When using v.color on a map with 2 Million points, it takes more than 24
hours (I guess the last time it took near 40 hours). The CPU is busy less
than 20% on a 8 core machine and a lot of memory is available (50% at least
is empty out of the 16 GB). Is there a way that I could accelerate the
processing? Is it normal at all?

A reason could be that the vector uses dbf as database driver. Database
drivers other than dbf can make use of an index, therefore you could verify
the database driver for WM195 with v.db.connect -p

If the vector uses dbf, you can switch to the default sqlite driver with

db.connect -d

then verify with db.connect -p

now make a copy of the vector and try again v.colors.

HTH,

Markus M


>
> Here is the command I am using:
>
> v.colors -c --verbose map=WM195 at Waterlix use=attr column=BRProbH
color=gyr rgb_column=ColorH
>
> Thanks for your help in advance,
>
>
> Mehrdad
>
> --
> Mehrdad Varedi
>
>
> _______________________________________________
> grass-user mailing list
> grass-user at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-user/attachments/20180531/6d258ef3/attachment.html>