[GRASS-dev] About v.distance, v.what.vect (wrt "count points within...").

[Markus Metz]

Nikos Alexandris wrote:
> So here you go using data from spearfish60 [1][2][3]
>
>
> # in grass70 before the latest update
> time v.distance --v from=pareto_ref_points___pareto_ref_100m
> to=pareto_grid___OVER___ref_coi_points___pareto_grid___OVER___ref_100m___ON___classification_V___classification_200m_1
> column=gridcell_1 to_column=cat upload=to_attr dmax=0.0
>
> Finding nearest feature...
> Finding nearest areas...
> 26335 categories read from the map
> 26335 categories exist in the table
> 26335 categories read from the map exist in the table
> 26335 records updated
> v.distance complete.
>
> real    3m4.270s
> user    2m43.140s
> sys     0m2.870s
>
> # in grass70 after the latest update ( I only did "make" within the
> /vector/v.distance directory - correct?)

Correct. But there should not be and is no difference in speed because
v.distance is called both times with dmax=0.0.
>
> Finding nearest feature...
> Finding nearest areas...
> Update database...
> 26335 categories read from the map
> 26335 categories exist in the table
> 26335 categories read from the map exist in the table
> 26335 records updated
> v.distance complete.
>
> real    3m5.339s
> user    2m42.780s
> sys     0m3.040s
>
>
[snip]
> b. v.what.vect seems to be broken after latest update?

Bug in v.what.vect (trunk only) fixed in r43057

Markus M