r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
Comparison · Analytics
maplegend vs rbmi
A side-by-side editorial comparison of maplegend and rbmi — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
maplegend vs rbmi: at a glance
What is maplegend?
The legend engine mapsf spun out, now covering legend types the parent map package can draw.
maplegend draws the legends for base-R thematic maps, extracted from mapsf so both packages could evolve the legend vocabulary independently. It has been catching up to the map types it has to serve: 0.6.0 added choro_point, choro_line, and choro_symb for choropleth legends rendered on circles, lines, and symbols, following the histogram legend type in 0.4.0. Considerable effort has gone into behaving correctly when the plot aspect ratio is not 1, which required refactoring most of the package in 0.4.0 and still produced a proportional-symbol segment sizing fix in 0.6.3.
What is rbmi?
Reference-based multiple imputation for trials, now shipping without Bayesian support by default.
rbmi implements reference-based multiple imputation for longitudinal clinical trial data with missing values — the estimand machinery regulators expect for handling intercurrent events and dropout. The consequential recent change was 1.3.0 moving rstan from a hard dependency to Suggests, which takes Bayesian imputation out of the default install. Since then the work has been documentation and nomenclature discipline: 1.6.1 standardized on MNAR over a mixed NMAR/MNAR vocabulary and deprecated the nmar.rm argument accordingly.
maplegend vs rbmi: editorial side-by-side
maplegend
0.0ANALYTICS
The legend engine mapsf spun out, now covering legend types the parent map package can draw.
◆ Current state
maplegend draws the legends for base-R thematic maps, extracted from mapsf so both packages could evolve the legend vocabulary independently. It has been catching up to the map types it has to serve: 0.6.0 added choro_point, choro_line, and choro_symb for choropleth legends rendered on circles, lines, and symbols, following the histogram legend type in 0.4.0. Considerable effort has gone into behaving correctly when the plot aspect ratio is not 1, which required refactoring most of the package in 0.4.0 and still produced a proportional-symbol segment sizing fix in 0.6.3.
◆ Where it's heading
This is a support library whose backlog is defined by its caller. Every legend type mapsf can produce needs a matching legend renderer, and the release notes are dominated by spacing, offset, and border details — box_cex for symbol spacing, NA box placement in horizontal choropleth legends, text overflow when no_data is set. The shared vocabulary with mapsf is being maintained deliberately, with val_rnd, val_big, and val_dec propagating through legend types release by release. Version numbering is not monotonic in this feed, with 0.4.0 published seconds after 0.5.0.
◆ Prediction
Expect the remaining combined map types to acquire matching legends and the val_* formatting arguments to reach the types that still lack them.
rbmi
2.5ANALYTICS
Reference-based multiple imputation for trials, now shipping without Bayesian support by default.
◆ Current state
rbmi implements reference-based multiple imputation for longitudinal clinical trial data with missing values — the estimand machinery regulators expect for handling intercurrent events and dropout. The consequential recent change was 1.3.0 moving rstan from a hard dependency to Suggests, which takes Bayesian imputation out of the default install. Since then the work has been documentation and nomenclature discipline: 1.6.1 standardized on MNAR over a mixed NMAR/MNAR vocabulary and deprecated the nmar.rm argument accordingly.
◆ Where it's heading
The package is optimizing for adoption friction over feature breadth. Dropping a compiled Stan dependency from the default install, deprecating a bespoke seed argument in favor of base set.seed(), and aligning lsmeans() behavior and weight naming with emmeans all point the same direction — behave like a conventional R package rather than a specialized one. Documentation work in 1.6.1 covering @return on every exported function and executable examples reads as preparation for validation scrutiny rather than user demand.
◆ Prediction
Given the FAQ vignette's validation statement and the recent documentation completeness pass, the next work is more likely qualification and estimand documentation than new imputation methods.
Alternatives to maplegend and rbmi
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 maplegend or rbmi.
DoseFinding
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
webmockr
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
crul
crul took mocking back from webmockr and made it a property of the client itself
dendroNetwork
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
chattr
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
See all maplegend alternatives → · See all rbmi alternatives →
Recent activity from maplegend and rbmi
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 22d agorbmiMNAR nomenclature standardized, documentation completed
- 2mo agomaplegendContinuous legend formatting and aspect-ratio segment fix
- 4mo agomaplegendChoropleth legends on points, lines and symbols
- 7mo agomaplegendPackage-wide refactor for non-unity aspect ratios, histogram legends
- 7mo agomaplegendSingle-modality legends allowed for typo, symb and prop_line
- 1y agomaplegendAlpha transparency and redraw on device resize
- 1y agomaplegendOffset and symbol sizing aligned with mapsf
- 1y agorbmirstan demoted to Suggests, Bayesian imputation now opt-in ⚡
- 2y agorbmirbmi v1.2.5
Frequently asked questions
What is the difference between maplegend and rbmi?
Both compete on the same themes — r-package — within Analytics. rbmi is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is maplegend better than rbmi?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. rbmi is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to maplegend?
Top maplegend alternatives in Analytics are ranked by recent ship velocity. Browse the "maplegend alternatives" section above for the current picks, or visit /alternatives/maplegend for the full list with editorial commentary on each.
What are the best alternatives to rbmi?
Top rbmi alternatives in Analytics are ranked by recent ship velocity. Browse the "rbmi alternatives" section above for the current picks, or visit /alternatives/rbmi for the full list with editorial commentary on each.