S7
S7 has stopped adding surface and started proving it holds up against R itself.
A side-by-side editorial comparison of maplegend and sftime — 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.
The spatiotemporal companion to sf, moving at the pace of the packages around it.
sftime extends sf with an active time column, giving R a data frame class for data that is both spatial and temporal. Its recent history is almost entirely integration work: 0.3.0 added conversion methods from spatstat point patterns, sftrack and sftraj movement objects and cubble data frames, plus dedicated tidyr::drop_na() and dplyr::dplyr_reconstruct() methods. The two releases since are a namespace version-check correction and a switch from the magrittr pipe to the native pipe in examples.
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.
sftime extends sf with an active time column, giving R a data frame class for data that is both spatial and temporal. Its recent history is almost entirely integration work: 0.3.0 added conversion methods from spatstat point patterns, sftrack and sftraj movement objects and cubble data frames, plus dedicated tidyr::drop_na() and dplyr::dplyr_reconstruct() methods. The two releases since are a namespace version-check correction and a switch from the magrittr pipe to the native pipe in examples.
The package's job is to be interoperable, so its releases follow whatever the surrounding spatial and tidyverse packages do. The dplyr_reconstruct() work is the clearest example of why that matters: inheriting sf's method caused column binding to silently return an sf object where an sftime object was expected, which is the kind of class-preservation bug that only surfaces two steps downstream. Development is sparse, roughly one release a year.
Expect further conversion methods as new spatiotemporal classes appear in the R spatial ecosystem, and continued tracking of dplyr and tidyr generics. The entries do not indicate any planned change to the sftime class itself.
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 sftime.
S7 has stopped adding surface and started proving it holds up against R itself.
R's torchvision is porting PyTorch's vision stack one task at a time — instance segmentation just landed.
The messy-date parser rewrote its core in Rust and came out 300x faster.
R help pages translated on demand by whichever LLM you point it at.
Thematic mapping in base R that finally got a theming system, then spent two years polishing legends.
qualtRics moved its contact functions onto XM Directory days before the old endpoints died.
See all maplegend alternatives → · See all sftime alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. maplegend and sftime 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 sftime 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 sftime alternatives in Analytics are ranked by recent ship velocity. Browse the "sftime alternatives" section above for the current picks, or visit /alternatives/sftime for the full list with editorial commentary on each.