#1357: v.net.salesman and forward/backward movement cost
----------------------------------------------------------------------------------------------+
Reporter: lluis | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 6.4.2
Component: Vector | Version: unspecified
Keywords: v.net.salesman,network, vector, network analysis, travel cost, forward, backward | Platform: Linux
Cpu: x86-64 |
----------------------------------------------------------------------------------------------+
I'm doing some '''network analysis''' with GRASS GIS and I'm surprised
because is not possible to consider forward/backward costs movements in
v.net.salesman as it is possible with the v.net.path module. I would like
to see this option in upcoming releases of GRASS because I believe that
this enhancement could be so valuable for grass users
I'm working with streets of a city, so distinguish between one-way streets
and bidirectional streets is something critical for me.
I'm working with grass 6.4.2svn under Ubuntu
Congratulations for your work
#1357: v.net.salesman and forward/backward movement cost
----------------------------------------------------------------------------------------------+
Reporter: lluis | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 7.0.0
Component: Vector | Version: unspecified
Keywords: v.net.salesman,network, vector, network analysis, travel cost, forward, backward | Platform: Linux
Cpu: x86-64 |
----------------------------------------------------------------------------------------------+
Changes (by Lluis):
* cc: Lluis (added)
Comment:
Great! It seems to work properly. I've been doing some tests using open
street map cartography, and it seems that I'm getting valid results. I
will try to do more tests but it seems to work correctly.
Thanks a lot for your work and effort, Moritz!
Lluís
Replying to [comment:2 mlennert]:
> Replying to [comment:1 mmetz]:
> > Implemented in grass 7, r46229, please test!
>
> Here are the results of an abritrary test on in the NC demo dataset:
>
> [http://geog-pc40.ulb.ac.be/grass/equalcost.png equal cost in both
directions]
>
> [http://geog-pc40.ulb.ac.be/grass/diffcost.png different cost in each
direction for one way streets]
>
> I'll attach the script with the relevant commands I used.
>
> At first view, the results seem to be coherent, but probably need more
detailed testing.
>
> Moritz
>
>
>
#1357: v.net.salesman and forward/backward movement cost
----------------------------------------------------------------------------------------------+
Reporter: lluis | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 7.0.0
Component: Vector | Version: unspecified
Keywords: v.net.salesman,network, vector, network analysis, travel cost, forward, backward | Platform: Linux
Cpu: x86-64 |
----------------------------------------------------------------------------------------------+
Comment(by mmetz):
Replying to [comment:4 mlennert]:
> Replying to [comment:3 Lluis]:
> > Thanks a lot for your work and effort, Moritz!
>
> Markus did the work, I just did the testing, so I think the thanks
should go to him.
Thanks to both of you for additional testing!
>
> I think this should be backported at least to grass6dev.
>
OK.
BTW, there is also v.net.steiner using the same cost for both directions,
no option to define different forward/backward moving costs.
#1357: v.net.salesman and forward/backward movement cost
----------------------------------------------------------------------------------------------+
Reporter: lluis | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 7.0.0
Component: Vector | Version: unspecified
Keywords: v.net.salesman,network, vector, network analysis, travel cost, forward, backward | Platform: Linux
Cpu: x86-64 |
----------------------------------------------------------------------------------------------+
Comment(by mlennert):
Replying to [comment:5 mmetz]:
> Replying to [comment:4 mlennert]:
> > Replying to [comment:3 Lluis]:
> > > Thanks a lot for your work and effort, Moritz!
> >
> > Markus did the work, I just did the testing, so I think the thanks
should go to him.
>
> Thanks to both of you for additional testing!
> >
> > I think this should be backported at least to grass6dev.
> >
> OK.
>
> BTW, there is also v.net.steiner using the same cost for both
directions, no option to define different forward/backward moving costs.
Another module where this might be an issue is v.net.components. Actually
there is no cost parameter at all in this module, but strong or weak
connection is defined by direction, and I don't understand how this
direction is defined.
