tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
Comparison · Analytics
osmextract vs Tplyr
A side-by-side editorial comparison of osmextract and Tplyr — release velocity, themes, recent moves, and the top alternatives to consider.
osmextract vs Tplyr: at a glance
What is osmextract?
osmextract stopped throwing your OpenStreetMap downloads away at the end of every session.
osmextract downloads OpenStreetMap extracts from Geofabrik, BBBike and openstreetmap.fr and translates them into sf objects via GDAL. The 0.6.0 release moved its download cache from `tempdir()` to a persistent `tools::R_user_dir()` location and raised the R floor to 4.1.0 to get it. It also made spatial `place` inputs self-clipping: pass an sf or bbox object and the boundary is now set to match, so only the relevant slice of a country-sized extract is processed.
What is Tplyr?
Tplyr made clinical summary tables explain where every number came from.
Tplyr builds clinical summary tables through a layered grammar — count, descriptive statistics, and shift layers assembled onto a table object. The 1.0.0 release added a traceability metadata framework that lets a user ask which source rows produced any given cell, and later releases extended it to cases the first pass missed. The package is maintained by Atorus within the pharmaverse ecosystem.
osmextract vs Tplyr: editorial side-by-side
osmextract
0.0ANALYTICS
osmextract stopped throwing your OpenStreetMap downloads away at the end of every session.
◆ Current state
osmextract downloads OpenStreetMap extracts from Geofabrik, BBBike and openstreetmap.fr and translates them into sf objects via GDAL. The 0.6.0 release moved its download cache from `tempdir()` to a persistent `tools::R_user_dir()` location and raised the R floor to 4.1.0 to get it. It also made spatial `place` inputs self-clipping: pass an sf or bbox object and the boundary is now set to match, so only the relevant slice of a country-sized extract is processed.
◆ Where it's heading
Two threads run through every release. One is chasing GDAL — SQL syntax adjusted for 3.10, ogr2ogr options fixed for 3.9, and an `osmconf.ini` that 0.6.0 finally keeps automatically in sync with whatever sf or GDAL provides rather than shipping a snapshot. The other is the road-network extraction added experimentally in 0.3.1, which has been quietly accumulating real routing semantics since: `access = no` links retained when the mode-specific tag permits them, a `oneway` column by default for driving, and `motor_vehicle` always included.
◆ Prediction
Given that `oe_get_network()` has gained transport-mode detail in three separate releases while remaining flagged as experimental, the next substantive work is most likely there — either more modes or a formal exit from experimental status.
Tplyr
0.0ANALYTICS
Tplyr made clinical summary tables explain where every number came from.
◆ Current state
Tplyr builds clinical summary tables through a layered grammar — count, descriptive statistics, and shift layers assembled onto a table object. The 1.0.0 release added a traceability metadata framework that lets a user ask which source rows produced any given cell, and later releases extended it to cases the first pass missed. The package is maintained by Atorus within the pharmaverse ecosystem.
◆ Where it's heading
Post-1.0 work has been about completing the metadata story and filling gaps in layer composition rather than adding table types — metadata for missing subjects, add_anti_join(), missing-subject rows, data limiting, and fixes to nested count layers where an inner value appears under several outer groups. Releases cluster tightly after a major version, then go quiet, and the window ends with a patch issued days after the release it corrects.
◆ Prediction
Further releases will most likely continue closing traceability and nested-layer edge cases rather than introducing new layer types, following the pattern of both post-1.0 feature releases.
Alternatives to osmextract and Tplyr
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 osmextract or Tplyr.
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.
datasetjson
datasetjson rebuilt its object model to track the CDISC Dataset-JSON 1.1 schema.
See all osmextract alternatives → · See all Tplyr alternatives →
Recent activity from osmextract and Tplyr
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 4mo agoosmextractDownloads move to a persistent cache outside tempdir ⚡
- 1y agoosmextractoe_match gains a version argument for historical extracts
- 1y agoosmextractRouting semantics sharpen for driving and restricted-access links
- 2y agoosmextract51 new openstreetmap.fr regions and a GDAL 3.9 fix
- 2y agoTplyrMissing-subject metadata, add_anti_join(), and nested-layer fixes
- 3y agoosmextractNon-Geofabrik downloads were saved under the wrong filename
- 3y agoTplyrMetadata vignette fix and parenthesis hugging
- 3y agoTplyrDenominator logic fix ahead of CRAN release
- 3y agoTplyrReverse-dependency fix
- 3y agoTplyr1.0.0 introduces the traceability metadata framework ⚡
- 3y agoosmextractHelp files regenerated for valid HTML5
Frequently asked questions
What is the difference between osmextract and Tplyr?
They serve adjacent needs but don't currently overlap on shipped themes. osmextract and Tplyr 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 osmextract better than Tplyr?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. osmextract and Tplyr 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 osmextract?
Top osmextract alternatives in Analytics are ranked by recent ship velocity. Browse the "osmextract alternatives" section above for the current picks, or visit /alternatives/osmextract for the full list with editorial commentary on each.
What are the best alternatives to Tplyr?
Top Tplyr alternatives in Analytics are ranked by recent ship velocity. Browse the "Tplyr alternatives" section above for the current picks, or visit /alternatives/tplyr for the full list with editorial commentary on each.