tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of datasetjson and parzer — release velocity, themes, recent moves, and the top alternatives to consider.
datasetjson rebuilt its object model to track the CDISC Dataset-JSON 1.1 schema.
datasetjson reads and writes CDISC Dataset-JSON, the JSON replacement for SAS transport files in clinical-trial submissions. The package went from a thin reader in 2023 to a redesigned interface in 0.3.0 that targets the 1.1.0 schema, uses yyjsonr as its JSON backend, and exposes column metadata as first-class arguments. Development is contributor-driven inside the Atorus and pharmaverse orbit.
A coordinate parser whose entire job is surviving how badly humans write latitude and longitude.
parzer converts messy coordinate strings — degrees, minutes, seconds, assorted symbols, arbitrary whitespace — into decimal degrees. Development is slow and sporadic, with three-year gaps between releases, and the work splits between C++ performance in the internal scrub() path and a long tail of parsing bugs. The most recent release, 0.4.4, fixed two genuinely dangerous ones: a leading space could silently drop a negative sign, and an E in a longitude string returned NA while a W parsed fine.
datasetjson reads and writes CDISC Dataset-JSON, the JSON replacement for SAS transport files in clinical-trial submissions. The package went from a thin reader in 2023 to a redesigned interface in 0.3.0 that targets the 1.1.0 schema, uses yyjsonr as its JSON backend, and exposes column metadata as first-class arguments. Development is contributor-driven inside the Atorus and pharmaverse orbit.
The package's roadmap is not its own — it tracks a CDISC standard that is still moving, and 0.3.0 is what happens when the standard revises: object model, read and write paths, and JSON backend all changed together. Performance was addressed in the same pass, which matters because submission datasets are large enough that a slow serialiser is a real constraint.
The next significant release will most likely follow the next Dataset-JSON schema revision rather than an internal roadmap, given that 0.3.0 was driven entirely by the 1.1.0 update.
parzer converts messy coordinate strings — degrees, minutes, seconds, assorted symbols, arbitrary whitespace — into decimal degrees. Development is slow and sporadic, with three-year gaps between releases, and the work splits between C++ performance in the internal scrub() path and a long tail of parsing bugs. The most recent release, 0.4.4, fixed two genuinely dangerous ones: a leading space could silently drop a negative sign, and an E in a longitude string returned NA while a W parsed fine.
The package has settled its scope — 0.4.1 explicitly rewrote the documentation to say it parses coordinates rather than validates them — and now moves only when someone finds a string it mishandles. Recent work has also been about shedding weight: Rcpp dependence reduced, the C++ requirement dropped from DESCRIPTION, suggested dependencies removed, and the vignette builder moved to Quarto. Maintainership passed to a new maintainer in 2022 and the package has stayed within rOpenSci.
The next release will most likely be another batch of parsing edge cases reported by users, since that is what every release since 0.2.0 has been. Nothing in these entries points to new functionality.
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 datasetjson or parzer.
A tables-listings-graphs package that reached CRAN and then went quiet.
Tplyr made clinical summary tables explain where every number came from.
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
See all datasetjson alternatives → · See all parzer alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. datasetjson and parzer 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. datasetjson and parzer 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 datasetjson alternatives in Analytics are ranked by recent ship velocity. Browse the "datasetjson alternatives" section above for the current picks, or visit /alternatives/datasetjson for the full list with editorial commentary on each.
Top parzer alternatives in Analytics are ranked by recent ship velocity. Browse the "parzer alternatives" section above for the current picks, or visit /alternatives/parzer for the full list with editorial commentary on each.