Tplyr
Tplyr made clinical summary tables explain where every number came from.
Comparison · Analytics
GSODR vs tidytlg
A side-by-side editorial comparison of GSODR and tidytlg — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
GSODR vs tidytlg: at a glance
What is GSODR?
A weather-station data client that broke one return type to hand back distances instead of bare IDs.
GSODR fetches and tidies NOAA Global Surface Summary of the Day weather data for R. The 4.0.0 release made nearest_stations() return a data.table of full station metadata plus distance in kilometres rather than a character vector of station IDs, with a documented one-liner for anyone who only wanted the IDs. Nothing has shipped since March 2024.
What is tidytlg?
A tables-listings-graphs package that reached CRAN and then went quiet.
tidytlg generates clinical tables, listings, and graphs from tidyverse-style pipelines, maintained under the pharmaverse organisation. All four releases in the window are from a single eight-month stretch in 2023, and their content is CRAN preparation, a logging-dependency swap, and multi-file support. Release notes are merge lists rather than described changes.
GSODR vs tidytlg: editorial side-by-side
GSODR
0.0ANALYTICS
A weather-station data client that broke one return type to hand back distances instead of bare IDs.
◆ Current state
GSODR fetches and tidies NOAA Global Surface Summary of the Day weather data for R. The 4.0.0 release made nearest_stations() return a data.table of full station metadata plus distance in kilometres rather than a character vector of station IDs, with a documented one-liner for anyone who only wanted the IDs. Nothing has shipped since March 2024.
◆ Where it's heading
The package is mature and its releases read as upkeep: refreshing the internal ISD history database, dropping dependencies in favour of base and curl, and hardening the download path against station-year combinations that do not exist. The 4.0.0 change fits the same pattern of returning more structure by default rather than making callers query twice.
◆ Prediction
The most likely next release is another internal station-history refresh; there is no signal of new data sources or analysis features in these entries.
tidytlg
0.0ANALYTICS
A tables-listings-graphs package that reached CRAN and then went quiet.
◆ Current state
tidytlg generates clinical tables, listings, and graphs from tidyverse-style pipelines, maintained under the pharmaverse organisation. All four releases in the window are from a single eight-month stretch in 2023, and their content is CRAN preparation, a logging-dependency swap, and multi-file support. Release notes are merge lists rather than described changes.
◆ Where it's heading
The visible arc is getting onto CRAN and staying installable — vignette corrections per CRAN comments, a badge, a check fix, and replacing the timber logging package with logrx. The one functional addition is multiple-file support. There has been no release since October 2023, so on this evidence the package is stable or dormant rather than actively developing.
◆ Prediction
The entries give no signal about planned work; with nothing shipped in roughly two years, the more likely next event is a maintenance release triggered by a dependency or CRAN check than a feature.
Alternatives to GSODR and tidytlg
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 GSODR or tidytlg.
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 GSODR alternatives → · See all tidytlg alternatives →
Recent activity from GSODR and tidytlg
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2y agoGSODRnearest_stations() returns metadata and distances
- 2y agoGSODRStation history refresh and internal tidying
- 2y agotidytlgSwaps the timber logger for logrx
- 2y agoGSODRBad station-year requests warn instead of failing the batch
- 3y agotidytlgMultiple-file support and table-binding fixes
- 3y agotidytlgVignette update per CRAN comments
- 3y agotidytlgFirst CRAN release
Frequently asked questions
What is the difference between GSODR and tidytlg?
Both compete on the same themes — r-package — within Analytics. GSODR and tidytlg 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 GSODR better than tidytlg?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. GSODR and tidytlg 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 GSODR?
Top GSODR alternatives in Analytics are ranked by recent ship velocity. Browse the "GSODR alternatives" section above for the current picks, or visit /alternatives/gsodr for the full list with editorial commentary on each.
What are the best alternatives to tidytlg?
Top tidytlg alternatives in Analytics are ranked by recent ship velocity. Browse the "tidytlg alternatives" section above for the current picks, or visit /alternatives/tidytlg for the full list with editorial commentary on each.