nanoparquet
nanoparquet is chasing byte-level agreement with the Java and Rust Parquet readers, not feature count.
A side-by-side editorial comparison of Athlytics and maplegend — release velocity, themes, recent moves, and the top alternatives to consider.
A Strava analytics package spent its 1.0 cycle surviving rOpenSci review, not adding features.
Athlytics computes endurance-training metrics — ACWR, EWMA load, efficiency factor, decoupling, personal bests — from Strava exports. Every release in view is review-driven: test-suite consolidation, dataset renames, styler passes, and a substantial robustness pass over the metric calculations and stream parsers. 1.0.6 explicitly changes nothing but packaging metadata.
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.
Athlytics computes endurance-training metrics — ACWR, EWMA load, efficiency factor, decoupling, personal bests — from Strava exports. Every release in view is review-driven: test-suite consolidation, dataset renames, styler passes, and a substantial robustness pass over the metric calculations and stream parsers. 1.0.6 explicitly changes nothing but packaging metadata.
The package is optimising for credibility rather than surface area. It completed rOpenSci peer review, moved to an offline ZIP export workflow with hardened TCX/GPX parsing, corrected the EWMA half-life mapping, and deliberately softened its ACWR language away from injury-risk claims. Version numbers are also being published out of order, which makes the feed a poor guide to what shipped when.
With review complete and packaging metadata frozen for archival, the next substantive release is more likely to extend metric coverage or data sources than to continue polishing; nothing in these entries points to a specific new metric.
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.
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 Athlytics or maplegend.
nanoparquet is chasing byte-level agreement with the Java and Rust Parquet readers, not feature count.
poissonreg gave its models away to parsnip and kept the glue — now it just keeps glmnet honest.
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.
See all Athlytics alternatives → · See all maplegend alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. Athlytics and maplegend 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. Athlytics and maplegend 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 Athlytics alternatives in Analytics are ranked by recent ship velocity. Browse the "Athlytics alternatives" section above for the current picks, or visit /alternatives/athlytics for the full list with editorial commentary on each.
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.