Dependency analysis on package mapStats

General information

CRAN link link
Package version2.4
Number of strong dependencies83
Number of all dependencies83
Number of parent packages9
Max heaviness from parent packages49
Total heaviness from parent packages62
Number of parent packages (including Suggests and Enhances)9
Max co-heaviness from parent packages ("Hmisc" and "reshape2")5

Dependency heatmap

In the following dependency heatmap, rows are the parent packages of mapStats and columns are the dependency packages that each parent package brings in. On the right side of the heatmap, there are three barplot annotations: 1. number of imported functions/S4 methods/S4 classes from parent packages; 2. number of dependency packages from each parent package; 3. heaviness of each parent package on mapStats.

Adjust heatmap size:


Dependency table

"Import" information is from the NAMESPACE file of mapStats.

imports: number of imported functions/objects; importMethods: number of imported S4 methods; importClasses: number of imported S4 classes.

Required packages: number of strong dependency packages for each of the parent package (or in other words, number of dependency packages the parent package brings in).

Heaviness from parent on mapStats: number of required packages that can be reduced if moving parent package to Suggests of mapStats.

Parent package Field imports importMethods importClasses Required packages Heaviness from parent on mapStats
survey Depends The whole set of functions/methods/classes from parent package is imported to the namespace of mapStats. 15 5
maptools Depends The whole set of functions/methods/classes from parent package is imported to the namespace of mapStats. 9 1
lattice Depends The whole set of functions/methods/classes from parent package is imported to the namespace of mapStats. 5 0
Hmisc Imports 1 0 0 67 49
classInt Imports 3 0 0 10 5
reshape2 Imports 1 0 0 12 2
RColorBrewer Imports 1 0 0 0 0
colorspace Imports 1 0 0 5 0
sp Imports 1 0 0 7 0

Analysis was done with pkgndep.