Dependency analysis on package mapdata

General information

CRAN link link
Package version2.3.0
Number of strong dependencies3
Number of all dependencies3
Number of parent packages1
Max heaviness from parent packages3
Total heaviness from parent packages3
Number of parent packages (including Suggests and Enhances)1

Dependency heatmap

In the following dependency heatmap, rows are the parent packages of mapdata 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 mapdata.

Adjust heatmap size:
Base packages Depends graphics utils 0 0.5 1 Imported methods 0 1 2 Required packages 0 1 2 3 Heaviness from parents maps In total 3 packages are required directly or indirectly (3) when installing 'mapdata' (2.3.0) Depends Base packages that are required Contributed packages that are required Packages that are required for installing 'mapdata' The whole namespace is imported


Dependency table

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

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 mapdata: number of required packages that can be reduced if moving parent package to Suggests of mapdata.

Parent package Field imports importMethods importClasses Required packages Heaviness from parent on mapdata
maps Depends The whole set of functions/methods/classes from parent package is imported to the namespace of mapdata. 2 3

Analysis was done with pkgndep.