webchem
Adding chemical databases with one hand while public ones close programmatic access with the other.
A side-by-side editorial comparison of c3dr and metatools — release velocity, themes, recent moves, and the top alternatives to consider.
A biomechanics C3D reader graduated through rOpenSci review to CRAN, then learned to write force plates.
c3dr reads and writes C3D motion-capture files in R, wrapping the EZC3D library. It cleared rOpenSci peer review and moved into the rOpenSci organisation in April 2025, reached CRAN a month later, and shipped force-platform export in c3d_write() in August. Releases are close together and each one has a clear single purpose.
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
metatools provides the utilities that build and check SDTM and ADaM datasets against their metadata in the pharmaverse. The 0.1.6 release in July 2024 is the substantive one: combine_supp() learned to handle zero-row supplemental data, to refuse QNAM columns already present in the source, and to route multiple QNAM values to the same IDVAR, alongside enhanced controlled-terminology checks and record-uniqueness verification. Nothing has shipped since.
c3dr reads and writes C3D motion-capture files in R, wrapping the EZC3D library. It cleared rOpenSci peer review and moved into the rOpenSci organisation in April 2025, reached CRAN a month later, and shipped force-platform export in c3d_write() in August. Releases are close together and each one has a clear single purpose.
The package is filling in the write side of the read/write pair. Reading was in place from the start; 0.2.0 extends c3d_write() to force-platform data on a direct user request, and the accompanying work preserves matrix structure on import and tracks upstream EZC3D changes. The review-era releases hardened validation and error messages, so the current cycle can be spent on capability rather than polish.
Expect further coverage of C3D block types in the writer and continued tracking of EZC3D releases; the changelog gives no signal of analysis features beyond file I/O.
metatools provides the utilities that build and check SDTM and ADaM datasets against their metadata in the pharmaverse. The 0.1.6 release in July 2024 is the substantive one: combine_supp() learned to handle zero-row supplemental data, to refuse QNAM columns already present in the source, and to route multiple QNAM values to the same IDVAR, alongside enhanced controlled-terminology checks and record-uniqueness verification. Nothing has shipped since.
The package's development has been concentrated on one function, combine_supp(), which is where the messy realities of supplemental qualifiers surface — whitespace in join keys, empty supp datasets, colliding names. 0.1.6 also drew three first-time contributors, which is the healthiest signal in the history, but no release has followed. Sibling packages have meanwhile been dropping metatools as a dependency.
Without a release in two years the package looks stable rather than active; the plausible trigger is a controlled-terminology or dplyr change that forces the checks to be updated.
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 c3dr or metatools.
Adding chemical databases with one hand while public ones close programmatic access with the other.
The spatiotemporal companion to sf, moving at the pace of the packages around it.
An interface to Europe's long-term ecosystem research network that went quiet after 2.0.
Spatial model assessment that spent the last year on cross-platform arithmetic and CRAN rules.
Stopped trusting the cloud to prepare its taxonomic databases and does the conversion locally.
Went from estimating felling dates to doing the crossdating that produces them.
See all c3dr alternatives → · See all metatools alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. c3dr and metatools 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. c3dr and metatools 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 c3dr alternatives in Analytics are ranked by recent ship velocity. Browse the "c3dr alternatives" section above for the current picks, or visit /alternatives/c3dr for the full list with editorial commentary on each.
Top metatools alternatives in Analytics are ranked by recent ship velocity. Browse the "metatools alternatives" section above for the current picks, or visit /alternatives/metatools for the full list with editorial commentary on each.