Opened 9 years ago

Closed 4 years ago

#1361 closed enhancement (fixed)

GSoC v.net.* modules should have nlayer option

Reported by: mlennert Owned by: grass-dev@…
Priority: normal Milestone: 7.0.0
Component: Vector Version: unspecified
Keywords: vector, network, node costs Cc:
CPU: Unspecified Platform: All

Description

The great v.net.* modules created by Daniel Bundala in the 2009 GSoC round would be improved if they had the nlayer option allowing to indicate a different layer for nodes than for the network, as is the case in the original set of v.net.* modules. This would fit better with the default behaviour of v.net which adds points to layer 2 by default.

Moritz

Change History (5)

comment:1 Changed 9 years ago by mlennert

Just to be complete, these are the relevant modules:

  • v.net.allpairs
  • v.net.bridge
  • v.net.centrality
  • v.net.components
  • v.net.connectivity
  • v.net.distance (this would need a specific alayer option for the arcs)
  • v.net.flow (idem)
  • v.net.spanningtree
  • v.net.timetable

comment:2 Changed 9 years ago by mmetz

Keywords: vector network node costs added; nlayer v.net removed

Please try r48060.

Markus M

comment:3 Changed 7 years ago by hamish

Hi mmetz, a little off topic for this ticket, but should r52169 be backported to relbr64?

thanks, Hamish

comment:4 Changed 6 years ago by neteler

What is the state of the backport to relbranch64?

comment:5 Changed 4 years ago by neteler

Resolution: fixed
Status: newclosed

Closing since backport to G6 is unlikely to happen.

Note: See TracTickets for help on using tickets.