Opened 14 years ago
Last modified 6 years ago
#1360 new enhancement
v.net.centrality: closeness is calculated per subcomponent, but should (at least optionally) be global
| Reported by: | mlennert | Owned by: | |
|---|---|---|---|
| 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)
Change History (9)
by , 14 years ago
| Attachment: | closeness.png added |
|---|
comment:1 by , 9 years ago
| Milestone: | 7.0.0 → 7.0.5 |
|---|
comment:2 by , 8 years ago
| Milestone: | 7.0.5 → 7.3.0 |
|---|
comment:3 by , 8 years ago
| Milestone: | 7.3.0 → 7.4.0 |
|---|
comment:5 by , 7 years ago
| Milestone: | 7.4.1 → 7.4.2 |
|---|
comment:6 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