tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
Comparison · Analytics
geotargets vs webmockr
A side-by-side editorial comparison of geotargets and webmockr — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:ropensci
geotargets vs webmockr: at a glance
What is geotargets?
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.
What is webmockr?
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
webmockr intercepts HTTP requests in R tests and returns stubbed responses, and since 1.0.0 it covers all three clients that matter — httr, httr2 and crul. The releases through 2025 have been about shedding dependencies: internal R6 classes unexported in 2.1.0, crul demoted from Imports to Suggests in the same release, and the mutual dependency with vcr severed in 2.2.0. The package now installs and runs without pulling in the rest of the rOpenSci HTTP stack.
geotargets vs webmockr: editorial side-by-side
geotargets
0.0ANALYTICS
Geospatial targets grew from two raster helpers into a tiling and multi-backend pipeline layer.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
webmockr
0.0ANALYTICS
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
◆ Current state
webmockr intercepts HTTP requests in R tests and returns stubbed responses, and since 1.0.0 it covers all three clients that matter — httr, httr2 and crul. The releases through 2025 have been about shedding dependencies: internal R6 classes unexported in 2.1.0, crul demoted from Imports to Suggests in the same release, and the mutual dependency with vcr severed in 2.2.0. The package now installs and runs without pulling in the rest of the rOpenSci HTTP stack.
◆ Where it's heading
Two arcs run in sequence. The first is coverage — multiple queued responses in 0.7.0, basic auth mocking, async through crul, then httr2 — building out what can be stubbed. The second, starting with 2.0.0, is correctness and independence: stubs are now deleted if an error occurs mid-construction rather than lingering half-built, partial matching arrives for bodies and queries, and the dependency graph is pruned release by release. The 2.2.0 split from vcr landed within a minute of crul's release taking mocking control into its own clients.
◆ Prediction
RequestPattern is documented as still exported in 2.1.0 but slated for removal, so the next major release is where that lands. Expect continued dependency pruning rather than new client support — the three clients that exist are already covered.
Alternatives to geotargets and webmockr
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 webmockr.
Tplyr
Tplyr made clinical summary tables explain where every number came from.
rlistings
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
hoardr
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
gigs
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
riem
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
See all geotargets alternatives → · See all webmockr alternatives →
Recent activity from geotargets and webmockr
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1y agowebmockrvcr dependency severed
- 1y agowebmockrInternal classes unexported; crul becomes an optional dependency
- 1y agogeotargetsGuards sozip metadata option against GDAL below 3.7
- 1y agogeotargetsVRT targets, datatype control, and GPKG default for vectors
- 1y agowebmockrFailed stub construction cleans up; partial matching extends to bodies and queries
- 1y agogeotargetsstars backend and dynamically branched raster tiles ⚡
- 2y agowebmockrhttr2 joins httr and crul as a supported client ⚡
- 2y agogeotargetsFirst release: raster, vector, and collection targets
- 3y agowebmockrQueued responses, body matching and integer status codes fixed
- 3y agowebmockrRegex URI matching fixed
Frequently asked questions
What is the difference between geotargets and webmockr?
Both compete on the same themes — ropensci — within Analytics. geotargets and webmockr 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.
Is geotargets better than webmockr?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. geotargets and webmockr 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.
What are the best alternatives to geotargets?
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.
What are the best alternatives to webmockr?
Top webmockr alternatives in Analytics are ranked by recent ship velocity. Browse the "webmockr alternatives" section above for the current picks, or visit /alternatives/webmockr for the full list with editorial commentary on each.