tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of geotargets and pharmaverseadam — release velocity, themes, recent moves, and the top alternatives to consider.
Geospatial targets grew from two raster helpers into a tiling and multi-backend pipeline layer.
geotargets extends the targets pipeline framework with target factories that know how to serialise geospatial objects — terra rasters and vectors, stars arrays, raster collections, and VRT references. It completed rOpenSci review and transferred ownership during 0.3.0. Writing behaviour is now configurable through per-target arguments and package-level options.
pharmaverseadam is the pharmaverse's test-data mirror, and it now covers neurology.
pharmaverseadam ships pre-built ADaM datasets generated by running the admiral family's own templates, so package authors and trainers have realistic analysis data without writing derivations first. The 1.3.0 release pulls in `ADAPET`, `ADTPET` and `ADNV` from admiralneuro and an anti-drug antibody dataset from admiral itself, and regenerates everything against current versions of seven upstream packages. Variables are now ordered and grouped to ADaM IG structure.
geotargets extends the targets pipeline framework with target factories that know how to serialise geospatial objects — terra rasters and vectors, stars arrays, raster collections, and VRT references. It completed rOpenSci review and transferred ownership during 0.3.0. Writing behaviour is now configurable through per-target arguments and package-level options.
The arc runs from 'targets can hold a SpatRaster' to 'targets can hold a tiled, dynamically branched raster workflow with controlled datatype and driver.' Recent work is about giving users control over how objects hit disk — datatype, driver, metadata sidecars, pass-through arguments to the underlying writers — which is where correctness problems in geospatial pipelines actually live. External contributors are driving a visible share of it.
Expect continued work on write-path fidelity and format coverage rather than new target types, since the last two releases both resolved metadata and driver defaults that were silently losing information.
pharmaverseadam ships pre-built ADaM datasets generated by running the admiral family's own templates, so package authors and trainers have realistic analysis data without writing derivations first. The 1.3.0 release pulls in `ADAPET`, `ADTPET` and `ADNV` from admiralneuro and an anti-drug antibody dataset from admiral itself, and regenerates everything against current versions of seven upstream packages. Variables are now ordered and grouped to ADaM IG structure.
Coverage tracks the pharmaverse's own therapeutic-area expansion with a lag of one release: pediatrics arrived in 1.1.0, metabolic in 1.2.0, neurology in 1.3.0. The other consistent thread is a slow move off development versions — 1.1.0 and 1.2.0 both had to pin unreleased upstream builds to get working templates, while 1.3.0 cites released versions throughout. Reorganising the reference page by therapeutic area is the same maturation showing up in documentation.
Expect the next release to follow the established pattern — a refresh against current upstream versions plus datasets from whichever admiral therapeutic-area package reaches a stable release next.
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 geotargets or pharmaverseadam.
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 geotargets alternatives → · See all pharmaverseadam alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. geotargets and pharmaverseadam 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. geotargets and pharmaverseadam 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 geotargets alternatives in Analytics are ranked by recent ship velocity. Browse the "geotargets alternatives" section above for the current picks, or visit /alternatives/geotargets for the full list with editorial commentary on each.
Top pharmaverseadam alternatives in Analytics are ranked by recent ship velocity. Browse the "pharmaverseadam alternatives" section above for the current picks, or visit /alternatives/pharmaverseadam for the full list with editorial commentary on each.