osmapiR
osmapiR is the rare API client that tracks its server's wiki revision numbers in the changelog.
A side-by-side editorial comparison of maplegend and S7 — 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.
S7 has stopped adding surface and started proving it holds up against R itself.
S7 is R's third-generation object system, built to unify the S3 and S4 lineages rather than add a fourth. The design work landed in 0.2.0, which reworked the default constructor, extended base-class coverage, and added a backward-compatibility shim so `@` property access works on R older than 4.3. Everything since has been maintenance: property setters gained a `check` escape hatch, and two consecutive releases exist mainly to keep the package compiling against R-devel 4.6.
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.
S7 is R's third-generation object system, built to unify the S3 and S4 lineages rather than add a fourth. The design work landed in 0.2.0, which reworked the default constructor, extended base-class coverage, and added a backward-compatibility shim so `@` property access works on R older than 4.3. Everything since has been maintenance: property setters gained a `check` escape hatch, and two consecutive releases exist mainly to keep the package compiling against R-devel 4.6.
The changelog is thinning by design — 0.1.0 was a months-long feature dump, 0.2.0 a coordinated architectural revision, 0.2.2 a single line about internal R-devel support. That shape usually means an API the maintainers consider settled, where the remaining work is tracking the host language rather than extending the system. The one recurring theme is validation cost: repeated releases have made validation less frequent, more targeted, or skippable outright.
Expect continued small releases pinned to R-devel changes rather than new class-system features, with any further movement most likely in the validation and property-setter path that the last two feature changes both touched.
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 S7.
osmapiR is the rare API client that tracks its server's wiki revision numbers in the changelog.
ymlthis retired itself, naming Quarto as the reason it no longer needs to exist.
forestly built an interactive safety review tool, then taught it to produce submission-ready RTF.
pharmaverseadam is the pharmaverse's test-data mirror, and it now covers neurology.
pkglite's whole job is knowing which files in an R package are text — and it keeps getting better at guessing.
gMCPLite exists to be gMCP without Java, and its releases guard that boundary rather than extend it.
See all maplegend alternatives → · See all S7 alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. maplegend and S7 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. maplegend and S7 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.
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 S7 alternatives in Analytics are ranked by recent ship velocity. Browse the "S7 alternatives" section above for the current picks, or visit /alternatives/s7 for the full list with editorial commentary on each.