guest wrote (Wed, Apr 5 2006 12:07:18):
If v.build.polylines in run on a topologicaly clean, self-closed boundary,
the output will be an "incorrect bondary", twice that long as the input.
I have to add that the input boundary *has to* be a single line already (ie. 1
boundary with 2 snapped nodes) for the bug to pop up. Such a line is the
'parcel' vector from the location available at
http://www.biol.uni.wroc.pl/sieczka/udostepnione/grass/poly/poly.tar.bz2.
If v.build.polylines is run on a boundary that is consisted of more than 2
nodes it will work fine though.
The bug is still there.
Maciek
-------------------------------------------- Managed by Request Tracker