Opened 9 years ago

Last modified 14 months ago

#1360 new enhancement

v.net.centrality: closeness is calculated per subcomponent, but should (at least optionally) be global

Reported by: mlennert Owned by: grass-dev@…
Priority: normal Milestone: 7.6.2
Component: LibVector Version: svn-develbranch6
Keywords: v.net.centrality closeness Cc:
CPU: Unspecified Platform: All

Description

In v.net.centrality, closeseness of a node is calculated as the mean cost to reach all other nodes. However, this obviously causes problems when some nodes are disconnected from the bulk of the network. See areas circled in yellow on the attached example map (result of v.net.centrality -a on spearfish roads map).

This means that some very disconnected points get high levels of closeness centrality because only their local subnetwork is taken into account.

Alternatives exist and one is described here. It would be nice to have at least the option to use this alternative measure of closeness.

Moritz

Attachments (1)

closeness.png (24.6 KB) - added by mlennert 9 years ago.

Download all attachments as: .zip

Change History (9)

Changed 9 years ago by mlennert

Attachment: closeness.png added

comment:1 Changed 4 years ago by martinl

Milestone: 7.0.07.0.5

comment:2 Changed 4 years ago by martinl

Milestone: 7.0.57.3.0

comment:3 Changed 4 years ago by martinl

Milestone: 7.3.07.4.0

Milestone renamed

comment:4 Changed 2 years ago by neteler

Milestone: 7.4.07.4.1

Ticket retargeted after milestone closed

comment:5 Changed 2 years ago by neteler

Milestone: 7.4.17.4.2

comment:6 Changed 20 months ago by martinl

Milestone: 7.4.27.6.0

All enhancement tickets should be assigned to 7.6 milestone.

comment:7 Changed 16 months ago by martinl

Milestone: 7.6.07.6.1

Ticket retargeted after milestone closed

comment:8 Changed 14 months ago by martinl

Milestone: 7.6.17.6.2

Ticket retargeted after milestone closed

Note: See TracTickets for help on using tickets.