Ahoj Maciek, v.distance should be fixed in CVS (not tested with 3d lines...)
Martin 2007/10/13, Maciej Sieczka <[EMAIL PROTECTED]>: > Martin Landa wrote: > > > should be fixed in CVS. > > After brief testing looks OK. Thanks much Martin! > > Soon after I noticed v.to.db didn't report 3d length, I had > the same problem with v.distance (looking for a workaround), > which I noted down in the same ticket. Copying the note below: > > Same request applies to v.distance. It apparently assumes > input points are flat too. Consider 2 3d points: > > $ v.out.ascii start_3d > 571600|5722275.5|1|1 > > $ v.out.ascii end_3d > 571610|5722275.5|4|1 > > The distance between them is about 10.440307. Yet, > v.distance claims it's round 10: > > $ v.distance -p from=start_3d to=end_3d upload=cat,dist > col=to_cat,dist > from_cat|to_cat|dist > 1|1|10.000000 > > Maciek > -- Martin Landa <[EMAIL PROTECTED]> * http://gama.fsv.cvut.cz/~landa * _______________________________________________ grass-dev mailing list [email protected] http://grass.itc.it/mailman/listinfo/grass-dev
