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

Nikos Alexandris nikos.alexandris at felis.uni-freiburg.de
Thu Aug 12 12:53:14 EDT 2010


Nikos A:
> For the records
> 
> > I am breaking the never-ending process... who cares what "time ..." will
> > return. It is still running!!
> 
> time v.what.vect --v vector=pareto_ref_points___pareto_ref_30m
> qvect=pareto_grid___OVER___ref_coi_points___pareto_grid___OVER___ref_30m___
> ON___classification_V___classification_500m_1 column=gridcell_1 qcolumn=cat
> Finding nearest lines...
> Finding nearest areas...
> ^C
> 
> real    317m9.500s
> user    0m12.230s
> sys     0m10.120s

Skipping the v.db.dropcol step I get:

time v.what.vect --v vector=pareto_ref_points___pareto_ref_30m 
qvect=pareto_grid___OVER___ref_coi_points___pareto_grid___OVER___ref_30m___ON___classification_V___classification_500m_1 
column=gridcell_1 qcolumn=cat
Finding nearest lines...
Finding nearest areas...
292317 categories read from the map
292317 categories exist in the table
292317 categories read from the map exist in the table
292317 records updated
v.distance complete.

real    0m47.338s <~ !^1000
user    0m23.100s
sys     0m16.510s

I am about to jump in to the lake [1] thinking how many nights I've spend on 
this. No comments please. In the end of the day(s, weeks, months) reaching a 
solution was my wish so I should be happy. I just need some time to accept 
it... :-? Maybe file a ticket for it as well?

Moritz, MarkusM, thanks once again :-)
(will try within the next days the v.vect.stats).



[1] 7.814375, 48.012126


More information about the grass-dev mailing list