randomwalk
randomwalk spent every release getting an R simulation to run in the browser, not on a server.
A side-by-side editorial comparison of gcube and washdata — release velocity, themes, recent moves, and the top alternatives to consider.
gcube's recent releases are all packaging metadata, not simulation code
gcube simulates biodiversity data cubes — generating occurrence points, sampling them under configurable detection bias, and designating them to a grid — as a testbed for the B-Cubed project's indicator tooling. The visible release history is almost entirely metadata and release-automation work: Zenodo grant IDs, ROR URL fixes, publisher fields, funder and rights-holder descriptions. The simulation functionality itself is not what these entries are about.
washdata is a fixed survey dataset; eight years of releases have changed only its packaging.
A data package distributing the Urban Water and Sanitation Survey, on CRAN since January 2018. No release has altered the data. The 2018 pair added survey country, year and aim to DESCRIPTION and fixed a README link; everything since — 2020, 2024 and the January 2026 release — is documentation, formatting, badges, repository refreshes and updates for a new rhub version.
gcube simulates biodiversity data cubes — generating occurrence points, sampling them under configurable detection bias, and designating them to a grid — as a testbed for the B-Cubed project's indicator tooling. The visible release history is almost entirely metadata and release-automation work: Zenodo grant IDs, ROR URL fixes, publisher fields, funder and rights-holder descriptions. The simulation functionality itself is not what these entries are about.
The February 2026 cluster reads as a package wiring up its archival identity rather than developing: four releases in four days, one of them explicitly a test of the GitHub release path. That is characteristic of research software preparing to be cited — a Zenodo DOI, correct funder attribution and a checklist-compliant description are the deliverables when the funder requires them. Substantive work on mapping functions and grid designation appears earlier and only through tutorial fixes.
With the Zenodo integration and metadata now settled, expect attention to return to the simulation functions themselves, most likely driven by what the sibling indicator packages need to test against.
A data package distributing the Urban Water and Sanitation Survey, on CRAN since January 2018. No release has altered the data. The 2018 pair added survey country, year and aim to DESCRIPTION and fixed a README link; everything since — 2020, 2024 and the January 2026 release — is documentation, formatting, badges, repository refreshes and updates for a new rhub version.
Nothing is heading anywhere, and for a dataset package that is the point: the value is a citable, unchanging artifact, and the release history exists to keep it installable as R's toolchain moves. The maintenance cadence matches the maintainer's other nutrition packages, which received the same repository-refresh treatment in the same period. Note also that the tags are backfilled out of order — v0.1.0 carries a later stamp than v0.1.2.
Expect further releases only when CRAN checks or infrastructure require them; there is no indication the survey data itself will be extended.
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 gcube or washdata.
randomwalk spent every release getting an R simulation to run in the browser, not on a server.
fastml added survival modelling and leakage-proof resampling, moving past classification and regression.
abclass built out angle-based classifiers in 2022, then went quiet except for CRAN upkeep.
churon is spending its entire release history getting a Rust ONNX binding through CRAN.
firatheme woke up after four years and started fixing what ggplot2 changed underneath it.
bagyo reached CRAN as a Philippine tropical cyclone dataset, with its tags stamped out of order.
See all gcube alternatives → · See all washdata alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. gcube and washdata 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. gcube and washdata 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 gcube alternatives in Analytics are ranked by recent ship velocity. Browse the "gcube alternatives" section above for the current picks, or visit /alternatives/gcube for the full list with editorial commentary on each.
Top washdata alternatives in Analytics are ranked by recent ship velocity. Browse the "washdata alternatives" section above for the current picks, or visit /alternatives/washdata for the full list with editorial commentary on each.