← Back to home
Comparison · Analytics

mapsf vs pharmaverseadam

A side-by-side editorial comparison of mapsf and pharmaverseadam — release velocity, themes, recent moves, and the top alternatives to consider.

mapsf vs pharmaverseadam: at a glance

Featuremapsfpharmaverseadam
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themescartography, thematic-maps, spatial, base-graphicspharmaverse, clinical-data, adam, test-data
Last editorial update1h ago37m ago
WebsiteVisit →Visit →

What is mapsf?

Thematic mapping in base R that finally got a theming system, then spent two years polishing legends.

mapsf produces thematic maps on R's base graphics device — choropleths, proportional symbols, typology maps, rasters, and their combinations, with legends, scale bars, north arrows, and insets as composable elements. Version 1.0.0 was the structural release, introducing a theming system that deprecated eight scattered styling arguments and adding mf_png() and mf_svg() export helpers plus alpha transparency across map types. The 1.1.x and 1.2.x line since then has been steady refinement: background and extent control on the drawing functions, decimal and thousands-separator control in legends, and label placement arguments.

Read the full mapsf trajectory →

What is pharmaverseadam?

pharmaverseadam is the pharmaverse's test-data mirror, and it now covers neurology.

pharmaverseadam ships pre-built ADaM datasets generated by running the admiral family's own templates, so package authors and trainers have realistic analysis data without writing derivations first. The 1.3.0 release pulls in `ADAPET`, `ADTPET` and `ADNV` from admiralneuro and an anti-drug antibody dataset from admiral itself, and regenerates everything against current versions of seven upstream packages. Variables are now ordered and grouped to ADaM IG structure.

Read the full pharmaverseadam trajectory →

mapsf vs pharmaverseadam: editorial side-by-side

M
mapsf
ANALYTICS
0.0

Thematic mapping in base R that finally got a theming system, then spent two years polishing legends.

◆ Current state

mapsf produces thematic maps on R's base graphics device — choropleths, proportional symbols, typology maps, rasters, and their combinations, with legends, scale bars, north arrows, and insets as composable elements. Version 1.0.0 was the structural release, introducing a theming system that deprecated eight scattered styling arguments and adding mf_png() and mf_svg() export helpers plus alpha transparency across map types. The 1.1.x and 1.2.x line since then has been steady refinement: background and extent control on the drawing functions, decimal and thousands-separator control in legends, and label placement arguments.

◆ Where it's heading

The package has been consolidating control into fewer, more consistent places. Legend handling moved out to the maplegend package in 0.8.0 and the per-element mf_legend_* functions were deprecated in favor of arguments on the map calls themselves; theming replaced ad-hoc style arguments in 1.0.0; and recent releases keep propagating the same argument vocabulary — bg, extent, leg_val_rnd, leg_val_dec, leg_val_big — across every function that should accept it. Determinism is a visible concern too, with 1.2.1 fixing a seed so mf_distr() point positions stop moving between runs.

◆ Prediction

The recent releases are almost entirely argument-parity work across existing functions, so expect that to continue until the vocabulary is uniform rather than any new map type appearing.

P0.0

pharmaverseadam is the pharmaverse's test-data mirror, and it now covers neurology.

◆ Current state

pharmaverseadam ships pre-built ADaM datasets generated by running the admiral family's own templates, so package authors and trainers have realistic analysis data without writing derivations first. The 1.3.0 release pulls in `ADAPET`, `ADTPET` and `ADNV` from admiralneuro and an anti-drug antibody dataset from admiral itself, and regenerates everything against current versions of seven upstream packages. Variables are now ordered and grouped to ADaM IG structure.

◆ Where it's heading

Coverage tracks the pharmaverse's own therapeutic-area expansion with a lag of one release: pediatrics arrived in 1.1.0, metabolic in 1.2.0, neurology in 1.3.0. The other consistent thread is a slow move off development versions — 1.1.0 and 1.2.0 both had to pin unreleased upstream builds to get working templates, while 1.3.0 cites released versions throughout. Reorganising the reference page by therapeutic area is the same maturation showing up in documentation.

◆ Prediction

Expect the next release to follow the established pattern — a refresh against current upstream versions plus datasets from whichever admiral therapeutic-area package reaches a stable release next.

Alternatives to mapsf and pharmaverseadam

Other Analytics products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either mapsf or pharmaverseadam.

See all mapsf alternatives → · See all pharmaverseadam alternatives →

Recent activity from mapsf and pharmaverseadam

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1mo agomapsfLabel placement arguments and deterministic distribution plots
  2. 2mo agomapsfBackground and extent control across the drawing functions
  3. 5mo agopharmaverseadamNeurology and anti-drug antibody datasets added
  4. 7mo agomapsfPNG resolution control and legend number formatting
  5. 11mo agopharmaverseadamMetabolic therapeutic area datasets arrive
  6. 1y agomapsf1.0.0 introduces theming and deprecates eight style arguments
  7. 1y agopharmaverseadamPediatric ADVS added in an ad-hoc refresh
  8. 1y agomapsfPencil-sketch layers, ckmeans breaks, and border extraction
  9. 2y agomapsfGraticule label display fix
  10. 2y agopharmaverseadam1.0 declares the dataset collection stable
  11. 2y agopharmaverseadamFirst release of the ADaM dataset collection

Frequently asked questions

What is the difference between mapsf and pharmaverseadam?

They serve adjacent needs but don't currently overlap on shipped themes. mapsf and pharmaverseadam are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is mapsf better than pharmaverseadam?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. mapsf and pharmaverseadam are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.

What are the best alternatives to mapsf?

Top mapsf alternatives in Analytics are ranked by recent ship velocity. Browse the "mapsf alternatives" section above for the current picks, or visit /alternatives/mapsf for the full list with editorial commentary on each.

What are the best alternatives to pharmaverseadam?

Top pharmaverseadam alternatives in Analytics are ranked by recent ship velocity. Browse the "pharmaverseadam alternatives" section above for the current picks, or visit /alternatives/pharmaverseadam for the full list with editorial commentary on each.