search

landam / grass-gis-git-migration-test

0 stars 0 forks source link

v.net.*: allow separate output for each starting point #147

Open landam opened 5 years ago

landam commented 5 years ago

Reported by mlennert on 29 Jan 2015 11:34 UTC When using v.net.iso (also v.net.alloc and maybe others) with several different starting points, I have to relaunch the module on each point if I want separate output for each point and not an isochrone or allocation only for the closest point. So I loop over the different starting points. However, at each run, v.net.iso has to reconstruct the graph which takes time making the loop quite slow.

Two ideas come to mind that might accelerate this:

  1. Integrate the loop into the modules, e.g. with a flag indicating that you want separate output per starting node. In this situation, the content of output option would become a basename for all output maps.

  2. Create a system which keeps the contructed graph in memory or in a file allowing to use it over different runs.

Any of this sound feasible ?

Moritz

GRASS GIS version and provenance

svn-trunk

Migrated-From: https://trac.osgeo.org/grass/ticket/2566

landam commented 5 years ago

Comment by neteler on 5 May 2016 14:08 UTC Milestone renamed

landam commented 5 years ago

Comment by neteler on 28 Dec 2016 15:04 UTC Ticket retargeted after milestone closed

landam commented 5 years ago

Modified by @landam on 5 May 2017 20:40 UTC

landam commented 5 years ago

Comment by @landam on 1 Sep 2017 20:28 UTC All enhancement tickets should be assigned to 7.4 milestone.

landam commented 5 years ago

Comment by neteler on 26 Jan 2018 11:40 UTC Ticket retargeted after milestone closed

landam commented 5 years ago

Modified by neteler on 12 Jun 2018 20:48 UTC

landam commented 5 years ago

Comment by @landam on 25 Sep 2018 16:51 UTC All enhancement tickets should be assigned to 7.6 milestone.

landam commented 5 years ago

Comment by @landam on 25 Jan 2019 21:07 UTC Ticket retargeted after milestone closed