qqman
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
A side-by-side editorial comparison of spanishoddata and symengine — release velocity, themes, recent moves, and the top alternatives to consider.
spanishoddata spent a year finding out its 2020-2021 data was quietly incomplete.
spanishoddata provides access to Spain's open mobility origin-destination datasets from the Ministry of Transport, converting them into DuckDB and parquet for analysis at scale. Nearly every release in this window is a data-fidelity fix rather than a feature: district-to-municipal reaggregation was wrong for the 2020-2021 vintage, literal 'NA' strings in the source CSVs broke DuckDB enum casting, and the Amazon S3 metadata bucket turned out to be truncated at March 2021, silently hiding data.
An R symbolic-maths binding whose changelog is really the C++ core's release notes.
symengine gives R access to the SymEngine computer algebra core for symbolic expressions, matrices and sets. The tracked feed carries the upstream C++ library's releases rather than R-binding changes, so what shows here is core work: parser fixes, locale-independent double parsing, an SOVERSION bump and matrix transpose corrections. Feature growth in the core has slowed considerably since the 0.9 and 0.10 releases.
spanishoddata provides access to Spain's open mobility origin-destination datasets from the Ministry of Transport, converting them into DuckDB and parquet for analysis at scale. Nearly every release in this window is a data-fidelity fix rather than a feature: district-to-municipal reaggregation was wrong for the 2020-2021 vintage, literal 'NA' strings in the source CSVs broke DuckDB enum casting, and the Amazon S3 metadata bucket turned out to be truncated at March 2021, silently hiding data.
The package is in a trust-building phase. The pattern across 0.2.1 through 0.2.6 is the maintainers repeatedly discovering that upstream metadata and the package's own aggregation were misrepresenting what data existed, then fixing it and adding a check so it surfaces next time. That is now backed by infrastructure: comprehensive unit tests plus weekly live-data runs on GitHub workers that alert maintainers when the upstream ministry changes something. The last feature release sits outside the six-entry window, which is itself the story.
Expect continued upstream-tracking fixes as the ministry's API and S3 layout shift, with the experimental quick-access and checksum functions the most likely candidates for promotion to stable.
symengine gives R access to the SymEngine computer algebra core for symbolic expressions, matrices and sets. The tracked feed carries the upstream C++ library's releases rather than R-binding changes, so what shows here is core work: parser fixes, locale-independent double parsing, an SOVERSION bump and matrix transpose corrections. Feature growth in the core has slowed considerably since the 0.9 and 0.10 releases.
The upstream core has moved from adding capability — serialization, a first simplify(), set types, matrix expressions, LLVM support — toward maintenance: build fixes, dependency support such as Flint3, and correctness patches. For R users the practical consequence is that new symbolic features arrive only as fast as the binding exposes them, which this feed does not report on.
Expect further upstream maintenance releases tracking LLVM and Flint versions; nothing in these notes signals a new capability push.
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 spanishoddata or symengine.
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
The R package for CODATA constants rebuilt its symbol table on NIST's naming so future updates stop being hand work.
The R client for AusTraits spends its releases chasing the dataset it reads.
A ggplot2 layer for seasonal adjustment output, filling in one plot type at a time.
A fossil-record simulator that quietly grew a trait-evolution engine.
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
See all spanishoddata alternatives → · See all symengine alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. spanishoddata and symengine 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. spanishoddata and symengine 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 spanishoddata alternatives in Analytics are ranked by recent ship velocity. Browse the "spanishoddata alternatives" section above for the current picks, or visit /alternatives/spanishoddata for the full list with editorial commentary on each.
Top symengine alternatives in Analytics are ranked by recent ship velocity. Browse the "symengine alternatives" section above for the current picks, or visit /alternatives/symengine-r for the full list with editorial commentary on each.