r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
A side-by-side editorial comparison of maplegend and refsplitr — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Author disambiguation for bibliometrics, still grinding on the hard part: which names are the same person.
refsplitr parses Web of Science reference records into tidy data and tries to resolve which author strings belong to the same researcher, then georeferences their institutional addresses for network and map visualizations. The active work is squarely on the disambiguation core: 1.2.3 continues refining the author grouping algorithm and 1.2.1 adjusted ORCID ID matching. Earlier, 1.2.0 replaced the address parsing algorithm and changed the default georeferencing option for author institutions.
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.
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.
Expect the remaining combined map types to acquire matching legends and the val_* formatting arguments to reach the types that still lack them.
refsplitr parses Web of Science reference records into tidy data and tries to resolve which author strings belong to the same researcher, then georeferences their institutional addresses for network and map visualizations. The active work is squarely on the disambiguation core: 1.2.3 continues refining the author grouping algorithm and 1.2.1 adjusted ORCID ID matching. Earlier, 1.2.0 replaced the address parsing algorithm and changed the default georeferencing option for author institutions.
Development has narrowed to the two operations that determine whether the output is usable — grouping author name variants and resolving addresses to coordinates. Everything else has been shedding: the maptools dependency was removed once that package was deprecated, and visualization changes are mostly about surfacing records the pipeline could not resolve, as with plot_net_country() returning fixable_countries so users can correct and rerun. Release notes are terse and defer to NEWS, so the changelog itself carries little detail.
Expect further incremental passes on author grouping and ORCID matching rather than new outputs; that algorithm is the package's accuracy ceiling and the last several releases have all touched it.
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 refsplitr.
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
crul took mocking back from webmockr and made it a property of the client itself
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
See all maplegend alternatives → · See all refsplitr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. refsplitr is currently shipping more aggressively (velocity 5.0 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. refsplitr is currently shipping more aggressively (velocity 5.0 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.
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.
Top refsplitr alternatives in Analytics are ranked by recent ship velocity. Browse the "refsplitr alternatives" section above for the current picks, or visit /alternatives/refsplitr for the full list with editorial commentary on each.