tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of admiralophtha and geotargets — release velocity, themes, recent moves, and the top alternatives to consider.
Ophthalmology ADaM support is migrating its derivations upstream into admiral core.
admiralophtha supplies ophthalmology-specific ADaM templates and vignettes — ADBCVA, ADOE, ADVFQ — on top of admiral. Releases arrive roughly twice a year and are dominated by template and vignette modernisation plus a long, deliberate deprecation of the package's own criterion-flag helper in favour of admiral::derive_vars_crit_flag(). The 1.5.0 release advances that deprecation to its warning phase and adds a template explorer.
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.
admiralophtha supplies ophthalmology-specific ADaM templates and vignettes — ADBCVA, ADOE, ADVFQ — on top of admiral. Releases arrive roughly twice a year and are dominated by template and vignette modernisation plus a long, deliberate deprecation of the package's own criterion-flag helper in favour of admiral::derive_vars_crit_flag(). The 1.5.0 release advances that deprecation to its warning phase and adds a template explorer.
The arc is consolidation: functions the package invented are being retired as admiral core grows generic equivalents, leaving admiralophtha as the place where ophthalmology conventions are documented. Recent releases spend their weight on templates and vignettes — VFQ guidance alignment, IOP parameter mapping, subject-key options — rather than new exported code. Deprecations are run on a fixed six-month, one-release-per-phase clock, which makes the migration path unusually legible.
derive_var_bcvacritxfl() should reach its error phase and then removal over the next two releases, with the accompanying work being ADBCVA vignette and template edits rather than new functions.
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.
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 admiralophtha or geotargets.
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 admiralophtha alternatives → · See all geotargets alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. admiralophtha and geotargets 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. admiralophtha and geotargets 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 admiralophtha alternatives in Analytics are ranked by recent ship velocity. Browse the "admiralophtha alternatives" section above for the current picks, or visit /alternatives/admiralophtha for the full list with editorial commentary on each.
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.