If the input vector has been prepared with v.net and
v.net.allpairs should use cost columns, further preparation is
of the input vector required. In contrast to the output of v.net
and the behaviour of other v.net.* modules, v.net.allpairs
uses the same layer to read cost columns for arcs and to read node
categories. Therefore new, unique categories for points must be added
to the layer with cost columns for lines with v.category.
If abcolumn is not given then then the same costs are used for
forward and backward arcs.
# prepare network: connect archsites to roads with threshold 200 v.net input=roads@PERMANENT points=archsites@PERMANENT \ output=roads_net operation=connect thresh=200 # verify result v.category input=roads_net option=report # only lines should have a category in layer 1 # only points should have a category in layer 2 # shortest path between all points with categories 1 - 5 in layer 2 v.net.allpairs input=roads_net layer=2 cats=1-5 out=roads_net_all v.db.select roads_net_all
from\to 1 3 4 5 1 0 18820.386 17206.651 17373.274 3 18820.386 0 1739.079 9040.575 4 17206.651 1739.079 0 7426.84 5 17373.274 9040.575 7426.84 0
Last changed: $Date$