[GRASS-user] v.whar.vect does not respond

[Nikos Alexandris]

Nikos wrote:
> > + exec v.distance from=burned_area_sample_1_points to=sample_1_grid
> > column=gridcell to_column=cat upload=to_attr dmax=0.0 from_layer=1
> > to_layer=1
> > 100%
> > 100%
> > 100%
> > 
> > ## Here it waits... waits... maybe just wait? I am _sure_
> > it did not take too long some last time when I tried this with the
> > same map(s) ##


Hamish:
> ok so v.distance is taking a very long time.

> can you try with "v.what.vect --vebose" ? that should give some more
> messages from v.distance instead of just 100% 100% 100%.

# almost the same as above
# executing the script with "-x"
v.what.vect test_1 col=gridcell qvect=sample_1_grid qcol=cat --v

+ [ -z /usr/local/grass-6.5.svn ]
+ [ test_1 != @ARGS_PARSED@ ]
+ exec g.parser /usr/local/grass-6.5.svn/scripts/v.what.vect test_1
col=gridcell qvect=sample_1_grid qcol=cat --v
+ [ -z /usr/local/grass-6.5.svn ]
+ [ @ARGS_PARSED@ != @ARGS_PARSED@ ]
+ exec v.distance from=test_1 to=sample_1_grid column=gridcell
to_column=cat upload=to_attr dmax=0.0 from_layer=1 to_layer=1
Finding nearest lines...
 100%
 100%
Finding nearest areas...
 100%

# not much...

> also, you can turn on the debug messages:
> g.gisenv set="DEBUG=1"

ok, DEBUG=2 did the trick and shows lots of update messages:
---%<---
D2/2: SQL: update test_1 set gridcell = 1276 where cat = 194
...
D2/2: SQL: update test_1 set gridcell = 1277 where cat = 205
D2/2: SQL: update test_1 set gridcell = 1277 where cat = 206
D2/2: SQL: update test_1 set gridcell = 1277 where cat = 207
---%<---

Seems to work fine but slow(er)!?

# off-topic: DEBUG=3 creates some impressive visual effect where, at
some points, you see the output scrolling from top to bottom :-) #

Thanks, Nikos

> I see one in v.distance "G_debug(3, "SQL: %s", db_get_string(&stmt));"
> maybe more DB troubles?