randomwalk
randomwalk spent every release getting an R simulation to run in the browser, not on a server.
Comparison · Analytics
gcube vs soilDB
A side-by-side editorial comparison of gcube and soilDB — release velocity, themes, recent moves, and the top alternatives to consider.
gcube vs soilDB: at a glance
What is gcube?
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.
What is soilDB?
The R front door to USDA soil data finishes a long deprecation cleanup and turns local-first.
soilDB is the R access layer for USDA-NRCS soil data: NASIS local databases, Soil Data Access, SoilWeb coverage services, and a widening set of curated national grids. The 2.9.x line closed out a multi-release deprecation cycle — column aliases and stringsAsFactors are gone, R 4.1 is the floor, and the bundled sample profile collections were rebuilt against the new schema. Recent work has shifted from adding query functions to making existing ones faster and usable against local SQLite or GeoPackage copies.
gcube vs soilDB: editorial side-by-side
gcube
0.0ANALYTICS
gcube's recent releases are all packaging metadata, not simulation code
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
soilDB
0.0ANALYTICS
The R front door to USDA soil data finishes a long deprecation cleanup and turns local-first.
◆ Current state
soilDB is the R access layer for USDA-NRCS soil data: NASIS local databases, Soil Data Access, SoilWeb coverage services, and a widening set of curated national grids. The 2.9.x line closed out a multi-release deprecation cycle — column aliases and stringsAsFactors are gone, R 4.1 is the floor, and the bundled sample profile collections were rebuilt against the new schema. Recent work has shifted from adding query functions to making existing ones faster and usable against local SQLite or GeoPackage copies.
◆ Where it's heading
The arc points at offline and local-first workflows. downloadSSURGO() and createSSURGO() keep gaining arguments for building and querying local SSURGO databases, and the query internals were rewritten as common table expressions so identical code runs against the remote service or a local file. Coverage is widening in parallel: FY26 SoilWeb maps now reach most OCONUS surveys, while fetchHWSD() and fetchSOLUS() pull in datasets outside the core NASIS/SSURGO pair. Federal URL churn — EDIT, SoilWeb, S3-hosted geometry — is a recurring maintenance tax the package absorbs on users' behalf.
◆ Prediction
Expect the next releases to keep extending parallel and offline SSURGO handling, since LAPPLY.FUN has just opened the door to arbitrary parallel backends, and to fold more curated SoilWeb and FAO datasets behind fetch* wrappers.
Alternatives to gcube and soilDB
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 soilDB.
fastml
fastml added survival modelling and leakage-proof resampling, moving past classification and regression.
abclass
abclass built out angle-based classifiers in 2022, then went quiet except for CRAN upkeep.
churon
churon is spending its entire release history getting a Rust ONNX binding through CRAN.
firatheme
firatheme woke up after four years and started fixing what ggplot2 changed underneath it.
bagyo
bagyo reached CRAN as a Philippine tropical cyclone dataset, with its tags stamped out of order.
See all gcube alternatives → · See all soilDB alternatives →
Recent activity from gcube and soilDB
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agosoilDBFY26 soil maps reach OCONUS; SSURGO downloads go parallel
- 4mo agosoilDBROSETTA v2 lands as the deprecated NASIS aliases are removed ⚡
- 5mo agogcubeGrant ID no longer uses a DOI
- 5mo agogcubeZenodo grant ID, publisher metadata and a ROR URL fix
- 6mo agogcubeRelease v1.4.2
- 7mo agogcubeRelease v1.4.1
- 7mo agogcubeInstallation instructions, spelling and funder descriptions
- 10mo agosoilDBNASIS record IDs now retrievable through Soil Data Access
- 11mo agosoilDBSpatial queries can pull columns from non-spatial tables
- 1y agosoilDBNASIS 7.4.3 metadata, plus HWSD and a local cache in 2.8.10
- 1y agogcubeRelease v1.3.7
- 1y agosoilDBQuery internals rewritten as CTEs for local SQLite support
Frequently asked questions
What is the difference between gcube and soilDB?
They serve adjacent needs but don't currently overlap on shipped themes. gcube and soilDB 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 gcube better than soilDB?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. gcube and soilDB 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 gcube?
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.
What are the best alternatives to soilDB?
Top soilDB alternatives in Analytics are ranked by recent ship velocity. Browse the "soilDB alternatives" section above for the current picks, or visit /alternatives/soildb for the full list with editorial commentary on each.