tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of excluder and geotargets — release velocity, themes, recent moves, and the top alternatives to consider.
A Qualtrics data-cleaning package that has been in maintenance mode since its CRAN acceptance.
excluder marks, checks, and excludes online-survey rows that fail quality criteria — duplicate responses, suspicious IP or geolocation, screen resolution, completion duration, preview rows. The mark_*/check_*/exclude_* verb trio and the column-renaming helpers are the whole public surface. Recent releases are dependency chasing and test robustness rather than new exclusion criteria.
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.
excluder marks, checks, and excludes online-survey rows that fail quality criteria — duplicate responses, suspicious IP or geolocation, screen resolution, completion duration, preview rows. The mark_*/check_*/exclude_* verb trio and the column-renaming helpers are the whole public surface. Recent releases are dependency chasing and test robustness rather than new exclusion criteria.
The package is stable and its maintenance load comes from things it does not control: the {iptools} package leaving CRAN, {tidyselect} deprecating the .data pronoun, IP-geolocation tests breaking when the underlying address data shifts. Much of that work is about staying installable, not about better exclusions. Note that several of these entries were backfilled into the feed within the same two-minute window and are not in version order.
The next release will most likely be another dependency or CRAN-check response rather than a new exclusion criterion, following the pattern of the last three.
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 excluder 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 excluder alternatives → · See all geotargets alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. excluder 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. excluder 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 excluder alternatives in Analytics are ranked by recent ship velocity. Browse the "excluder alternatives" section above for the current picks, or visit /alternatives/excluder 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.