osmextract
osmextract stopped throwing your OpenStreetMap downloads away at the end of every session.
A side-by-side editorial comparison of Athlytics and datefixR — 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 messy-date parser rewrote its core in Rust and came out 300x faster.
datefixR standardizes inconsistently formatted dates — the kind that arrive from spreadsheets and hand-entered clinical or survey data, with mixed separators, ambiguous orders, missing components, and month names in whatever language the source used. Version 2.0.0 rewrote the parsing core in Rust, reporting over 300x throughput against previous versions through fastpath handling of common formats and parallel column processing via a cores argument. Version 2.0.1 then spent itself cleaning up after that rewrite, restoring ordinal indicator support, stopping malformed dates from being silently cast to NA, and reinstating error messages that had gone missing.
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.
datefixR standardizes inconsistently formatted dates — the kind that arrive from spreadsheets and hand-entered clinical or survey data, with mixed separators, ambiguous orders, missing components, and month names in whatever language the source used. Version 2.0.0 rewrote the parsing core in Rust, reporting over 300x throughput against previous versions through fastpath handling of common formats and parallel column processing via a cores argument. Version 2.0.1 then spent itself cleaning up after that rewrite, restoring ordinal indicator support, stopping malformed dates from being silently cast to NA, and reinstating error messages that had gone missing.
Two long arcs meet here. The first is localization: Russian, Indonesian, German, Spanish month abbreviations, and experimental Roman numeral months accumulated release by release, with full translation of user-facing messages treated as a goal rather than a bonus. The second is the migration off R for the parsing hot path — internals began moving to C++ around 1.3.1 before the Rust rewrite replaced that work entirely. The 2.0.1 regressions show the cost of that move, since behavior that was implicit in the R implementation had to be re-specified.
The Rust core is one release into stabilization and 2.0.1 was entirely regression repair, so expect further correctness fixes against pre-2.0.0 behavior before any new format support lands.
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 datefixR.
osmextract stopped throwing your OpenStreetMap downloads away at the end of every session.
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 legend engine mapsf spun out, now covering legend types the parent map package can draw.
See all Athlytics alternatives → · See all datefixR alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. Athlytics and datefixR 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 datefixR 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 datefixR alternatives in Analytics are ranked by recent ship velocity. Browse the "datefixR alternatives" section above for the current picks, or visit /alternatives/datefixr for the full list with editorial commentary on each.