tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of geotargets and hoardr — 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.
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
hoardr manages local cache directories for other R packages — where files go, how they are keyed, whether they exist. It underpins caching in several rOpenSci data clients. The last functional additions were in 2018; everything since is a patch issued because CRAN reported a test failure or the maintainer changed.
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.
hoardr manages local cache directories for other R packages — where files go, how they are keyed, whether they exist. It underpins caching in several rOpenSci data clients. The last functional additions were in 2018; everything since is a patch issued because CRAN reported a test failure or the maintainer changed.
This is infrastructure that has reached its final shape. Three of the last three releases were reactive: two responses to CRAN test-failure notifications, one to a maintainer handover. The single behavioural change in that stretch — forward slashes in paths on every operating system — is a consistency fix for downstream packages rather than a feature. Its release cadence is set by CRAN's checks, not by demand.
Expect the next release to be triggered by another CRAN check failure rather than by new functionality, matching every release since 2018.
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 hoardr.
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.
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.
datasetjson rebuilt its object model to track the CDISC Dataset-JSON 1.1 schema.
See all geotargets alternatives → · See all hoardr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package, ropensci — within Analytics. geotargets and hoardr 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 hoardr 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 hoardr alternatives in Analytics are ranked by recent ship velocity. Browse the "hoardr alternatives" section above for the current picks, or visit /alternatives/hoardr for the full list with editorial commentary on each.