Opened 10 years ago
Last modified 6 years ago
#2566 new enhancement
v.net.*: allow separate output for each starting point
| Reported by: | mlennert | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | 7.6.2 |
| Component: | Vector | Version: | svn-trunk |
| Keywords: | v.net.iso v.net.alloc network graph | Cc: | |
| CPU: | Unspecified | Platform: | Unspecified |
Description
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:
- 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.
- 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
Change History (9)
comment:1 by , 9 years ago
| Milestone: | 7.1.0 → 7.2.0 |
|---|
comment:3 by , 8 years ago
| Milestone: | 7.2.1 → 7.2.2 |
|---|
comment:4 by , 7 years ago
| Milestone: | 7.2.2 → 7.4.0 |
|---|
All enhancement tickets should be assigned to 7.4 milestone.
comment:6 by , 6 years ago
| Milestone: | 7.4.1 → 7.4.2 |
|---|
comment:7 by , 6 years ago
| Milestone: | 7.4.2 → 7.6.0 |
|---|
All enhancement tickets should be assigned to 7.6 milestone.
Note:
See TracTickets
for help on using tickets.
Milestone renamed