poppr
A population-genetics workhorse in long-term maintenance, shipping only what CRAN demands.
A side-by-side editorial comparison of jmastats and rgoogleads — release velocity, themes, recent moves, and the top alternatives to consider.
A Japan Meteorological Agency client whose real product is keeping its bundled datasets current.
jmastats pulls weather and climate data from the Japan Meteorological Agency into R, and most of its releases exist to refresh the station and reference datasets it ships. Three of the four versions on record are dataset updates, dated by the month they were cut. The exception is 0.3.0, which taught jma_collect() to retrieve climatological normals derived from past observations.
A Google Ads API client for R that exists to stay one step ahead of deprecation.
rgoogleads gives R analysts access to the Google Ads API, and its release log is essentially a list of API versions cleared: v10, v11, v13, v14, v16. The last substantive code change was 0.9.2, which rebuilt gads_get_geo_targets() after Google started publishing its region reference as a zip archive instead of a plain CSV, forcing the function to download and unpack before reading.
jmastats pulls weather and climate data from the Japan Meteorological Agency into R, and most of its releases exist to refresh the station and reference datasets it ships. Three of the four versions on record are dataset updates, dated by the month they were cut. The exception is 0.3.0, which taught jma_collect() to retrieve climatological normals derived from past observations.
The package treats bundled data as the thing that must not go stale, and the retrieval API as broadly finished. Where code does change, it is about being a well-behaved client — request intervals to reduce server load, messages when returned data contains missing values, corrected station coordinates. Capability growth happens in single steps, roughly once a year.
The next release is most likely another dated dataset refresh; a further extension of jma_collect() to a new observation type is plausible but the entries show no specific one being prepared.
rgoogleads gives R analysts access to the Google Ads API, and its release log is essentially a list of API versions cleared: v10, v11, v13, v14, v16. The last substantive code change was 0.9.2, which rebuilt gads_get_geo_targets() after Google started publishing its region reference as a zip archive instead of a plain CSV, forcing the function to download and unpack before reading.
Development is reactive by design — the package changes when Google changes, and the notes rarely describe anything else. The deeper rework happened earlier, in 0.7.0, when request generation was centralised into gads_make_request() and gads_customer() was rewritten onto SearchStream after the old get method was retired. Since then the structure has held and releases have thinned to version bumps, with the most recent gap running over a year.
The next release will be a migration to a newer Google Ads API version, and on this history it will arrive when the current one nears sunset rather than on any schedule of the maintainer's own.
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 jmastats or rgoogleads.
A population-genetics workhorse in long-term maintenance, shipping only what CRAN demands.
An urban accessibility toolkit that grew into a distributional-equity toolkit.
The Carpentries' lesson skin, rebuilt on Bootstrap 5 with dark mode and a wider reach.
A project-bound modelling package that shipped its final scenario workflow and stopped.
A Facebook Marketing API client for R whose release schedule belongs to Meta, not its author.
The utility layer under KWB's R packages, growing by accretion one helper at a time.
See all jmastats alternatives → · See all rgoogleads alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. jmastats and rgoogleads 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. jmastats and rgoogleads 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 jmastats alternatives in Analytics are ranked by recent ship velocity. Browse the "jmastats alternatives" section above for the current picks, or visit /alternatives/jmastats for the full list with editorial commentary on each.
Top rgoogleads alternatives in Analytics are ranked by recent ship velocity. Browse the "rgoogleads alternatives" section above for the current picks, or visit /alternatives/rgoogleads for the full list with editorial commentary on each.