tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
Comparison · Analytics
GSODR vs hoardr
A side-by-side editorial comparison of GSODR and hoardr — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:ropenscir-package
GSODR vs hoardr: 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 hoardr?
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.
GSODR vs hoardr: 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.
hoardr
0.0ANALYTICS
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
Expect the next release to be triggered by another CRAN check failure rather than by new functionality, matching every release since 2018.
Alternatives to GSODR and hoardr
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 hoardr.
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.
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 hoardr alternatives →
Recent activity from GSODR and hoardr
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1y agohoardrPaths use forward slashes on every platform
- 2y agoGSODRnearest_stations() returns metadata and distances
- 2y agoGSODRStation history refresh and internal tidying
- 2y agohoardrTest-only patch for a CRAN failure
- 2y agoGSODRBad station-year requests warn instead of failing the batch
- 3y agohoardrPatch release for maintainer handover
- 7y agohoardrFixes cache paths leaking between HoardClient instances
- 7y agohoardrFile-existence checks and full-path cache configuration
- 9y agohoardrCRAN disk-writing policy compliance
Frequently asked questions
What is the difference between GSODR and hoardr?
Both compete on the same themes — ropensci, r-package — within Analytics. GSODR 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.
Is GSODR better than hoardr?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. GSODR 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.
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 hoardr?
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.