Opened 9 years ago

Last modified 15 months ago

#1357 new enhancement

v.net.salesman and forward/backward movement cost

Reported by: lluis Owned by: grass-dev@…
Priority: normal Milestone: 7.6.2
Component: Vector Version: unspecified
Keywords: v.net.salesman, network, vector, network analysis, travel cost, forward, backward Cc: lluis@…, Lluis
CPU: x86-64 Platform: Linux

Description

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

Lluís

Attachments (1)

v_net_salesman_test.sh (1.1 KB) - added by mlennert 9 years ago.
commands used for testing

Download all attachments as: .zip

Change History (17)

comment:1 Changed 9 years ago by mmetz

Milestone: 6.4.27.0.0

Implemented in grass 7, r46229, please test!

Markus M

comment:2 in reply to:  1 ; Changed 9 years ago by mlennert

Replying to mmetz:

Implemented in grass 7, r46229, please test!

Here are the results of an abritrary test on in the NC demo dataset:

equal cost in both directions

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

Changed 9 years ago by mlennert

Attachment: v_net_salesman_test.sh added

commands used for testing

comment:3 in reply to:  2 ; Changed 9 years ago by Lluis

Cc: Lluis added

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 mlennert:

Replying to mmetz:

Implemented in grass 7, r46229, please test!

Here are the results of an abritrary test on in the NC demo dataset:

equal cost in both directions

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

comment:4 in reply to:  3 ; Changed 9 years ago by mlennert

Replying to 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. ;-)

I think this should be backported at least to grass6dev.

Moritz

comment:5 in reply to:  4 ; Changed 9 years ago by mmetz

Replying to mlennert:

Replying to 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.

Markus M

comment:6 in reply to:  5 Changed 9 years ago by mlennert

Replying to mmetz:

Replying to mlennert:

Replying to 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.

Moritz

comment:7 Changed 5 years ago by neteler

What is the state here? G7 done and G6 wontfix?

comment:8 in reply to:  7 Changed 5 years ago by mlennert

Replying to neteler:

What is the state here? G7 done and G6 wontfix?

I would definitely say wontfix for G6. For G7, v.net.steiner still does not have directions, so as a reminder maybe this bug should either be renamed, or a different bug opened for v.net.steiner.

comment:9 Changed 4 years ago by martinl

Milestone: 7.0.07.0.5

comment:10 Changed 4 years ago by martinl

Milestone: 7.0.57.3.0

comment:11 Changed 4 years ago by martinl

Milestone: 7.3.07.4.0

Milestone renamed

comment:12 Changed 2 years ago by neteler

Milestone: 7.4.07.4.1

Ticket retargeted after milestone closed

comment:13 Changed 2 years ago by neteler

Milestone: 7.4.17.4.2

comment:14 Changed 22 months ago by martinl

Milestone: 7.4.27.6.0

All enhancement tickets should be assigned to 7.6 milestone.

comment:15 Changed 18 months ago by martinl

Milestone: 7.6.07.6.1

Ticket retargeted after milestone closed

comment:16 Changed 15 months ago by martinl

Milestone: 7.6.17.6.2

Ticket retargeted after milestone closed

Note: See TracTickets for help on using tickets.