A GPU-accelerated Bayesian GLM package buys its way into the standard R Bayesian toolchain
soilDBdata alternatives
The best soilDBdata alternatives in analytics tools, ranked by Sparkpulse's velocity_score.
Updated Aug 17, 2026
Looking for the best alternatives to soilDBdata? Sparkpulse tracks and ranks 12 alternatives in analytics tools by shipping velocity — how frequently each ships meaningful updates, verified from official changelogs. For reference, soilDBdata shipped 0 meaningful updates in the last 30 days and carries a velocity score of 0.0 out of 10 in 2026. The alternatives below are ranked the same way, so you're comparing real release momentum, not marketing claims.
About soilDBdata
soilDBdata exists so soilDB's tests can run without a NASIS connection.
soilDBdata is a data-only package supplying NASIS and gSSURGO sample datasets as .sqlite assets, installed separately by soilDB's GitHub Actions so unit tests that would otherwise need database access can run. It began as a proof of concept carrying MT663 pedon and component tables used in soil survey coursework, and its most recent release adds a Marshall Islands FY26 gSSURGO dataset. Releases are infrequent and driven by what the parent package needs to test.
Velocity 0.0 · Last update 1h ago
Top 12 alternatives to soilDBdata
Ranked by recent ship velocity. Tap any card for the full editorial breakdown, or pivot to a head-to-head.
Accessible palettes generated from one seed, with every audit number computed on the hex you actually get
A single-cell data store commits to Zarr v3 and range-readable hosting across four language surfaces
A C++ mesh renderer grinding through CRAN's gate, one policy fix at a time
A provenance-first corpus tool hands its verification core to agents over MCP
Registration fusion mapping goes bidirectional, and a vertex-indexing bug that silently returned wrong coordinates is fixed
Text analysis in R keeps optimising its token internals — and builds a path out to torch
The ModernDive teaching package learns to render inside the browser that runs its own textbook
Continuous-time mediation effects get standardized centrality, six years into steady patch work
Four dormant years end with a modernization pass and an off-by-one fix in the C++ core
A VAR-model fitting package acquiring the standard R methods it launched without
USGS puts a type system over its river network toolkit so errors surface at dispatch
soilDBdata vs alternatives — shipping velocity at a glance
Velocity score (0–10) and meaningful releases shipped in the last 30 days, from official changelogs. Higher = shipping faster.
| Product | Velocity | Sparks · 30d | Focus areas | Latest release |
|---|---|---|---|---|
| soilDBdata (baseline) | 0.0 | 0 | soil datatest fixturesnasis | — |
| glmbayes | 6.3 | 1 | bayesian-statisticsgeneralized-linear-modelsopencl | OpenCL split out to nmathopencl; insight and bayestestR integration |
| palettecore | 6.3 | 1 | accessibilitycolor-sciencedata-visualization | palettecore 0.2.0 |
| lstar | 5.0 | 0 | single-cell-genomicszarrwasm | lstar 0.2.0 |
| scimesh | 5.0 | 0 | scientific-visualizationcran-compliancer-bindings | — |
| vahtian | 3.8 | 1 | reproducibilityprovenancemcp | vahtian 0.2.0 |
| regfusionr | 3.8 | 1 | neuroimagingcoordinate-mappingfreesurfer | Version 0.3.0 -- vol_to_fsaverage, many convenience functions and fixes |
| quanteda | 2.5 | 0 | text-analysisnatural-language-processingr-package | CRAN v4.0 |
| moderndive | 2.5 | 0 | statistics-educationwebrregression | — |
| cTMed | 2.5 | 0 | mediation-analysiscontinuous-time-modelsr-package | — |
| haze | 2.5 | 0 | neuroimagingmesh-processinginterpolation | — |
| fitVARMxID | 2.5 | 0 | time-seriesstructural-equation-modelingr-package | — |
| hydroloom | 0.0 | 0 | hydrologynetwork-analysisgeospatial | hydroloom v1.2.0 |
The 12 best soilDBdata alternatives, in depth
1. glmbayes · velocity 6.3
A GPU-accelerated Bayesian GLM package buys its way into the standard R Bayesian toolchain.
Over the last 30 days glmbayes shipped 1 meaningful update vs soilDBdata's 0, most recently “OpenCL split out to nmathopencl; insight and bayestestR integration”. Its velocity score of 6.3/10 blends that with longer-term release cadence.
Where soilDBdata leans on soil data, test fixtures and nasis, glmbayes focuses on bayesian statistics, generalized linear models and opencl.
Over the last 30 days glmbayes has been shipping faster than soilDBdata — a point in its favour if release momentum matters to you.
Full glmbayes trajectory → · Compare soilDBdata vs glmbayes →
2. palettecore · velocity 6.3
Accessible palettes generated from one seed, with every audit number computed on the hex you actually get.
Over the last 30 days palettecore shipped 1 meaningful update vs soilDBdata's 0, most recently “palettecore 0.2.0”. Its velocity score of 6.3/10 blends that with longer-term release cadence.
Where soilDBdata leans on soil data, test fixtures and nasis, palettecore focuses on accessibility, color science and data visualization.
Over the last 30 days palettecore has been shipping faster than soilDBdata — a point in its favour if release momentum matters to you.
Full palettecore trajectory → · Compare soilDBdata vs palettecore →
3. lstar · velocity 5.0
A single-cell data store commits to Zarr v3 and range-readable hosting across four language surfaces.
Its velocity score of 5.0/10 reflects longer-term release cadence; its most recent meaningful update was “lstar 0.2.0”.
Where soilDBdata leans on soil data, test fixtures and nasis, lstar focuses on single cell genomics, zarr and wasm.
lstar and soilDBdata have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
4. scimesh · velocity 5.0
A C++ mesh renderer grinding through CRAN's gate, one policy fix at a time.
Its velocity score of 5.0/10 reflects longer-term release cadence.
Where soilDBdata leans on soil data, test fixtures and nasis, scimesh focuses on scientific visualization, cran compliance and r bindings.
scimesh and soilDBdata have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
5. vahtian · velocity 3.8
A provenance-first corpus tool hands its verification core to agents over MCP.
Over the last 30 days vahtian shipped 1 meaningful update vs soilDBdata's 0, most recently “vahtian 0.2.0”. Its velocity score of 3.8/10 blends that with longer-term release cadence.
Where soilDBdata leans on soil data, test fixtures and nasis, vahtian focuses on reproducibility, provenance and mcp.
Over the last 30 days vahtian has been shipping faster than soilDBdata — a point in its favour if release momentum matters to you.
6. regfusionr · velocity 3.8
Registration fusion mapping goes bidirectional, and a vertex-indexing bug that silently returned wrong coordinates is fixed.
Over the last 30 days regfusionr shipped 1 meaningful update vs soilDBdata's 0, most recently “Version 0.3.0 -- vol_to_fsaverage, many convenience functions and fixes”. Its velocity score of 3.8/10 blends that with longer-term release cadence.
Where soilDBdata leans on soil data, test fixtures and nasis, regfusionr focuses on neuroimaging, coordinate mapping and freesurfer.
Over the last 30 days regfusionr has been shipping faster than soilDBdata — a point in its favour if release momentum matters to you.
Full regfusionr trajectory → · Compare soilDBdata vs regfusionr →
7. quanteda · velocity 2.5
Text analysis in R keeps optimising its token internals — and builds a path out to torch.
Its velocity score of 2.5/10 reflects longer-term release cadence; its most recent meaningful update was “CRAN v4.0”.
Where soilDBdata leans on soil data, test fixtures and nasis, quanteda focuses on text analysis, natural language processing and r package.
quanteda and soilDBdata have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full quanteda trajectory → · Compare soilDBdata vs quanteda →
8. moderndive · velocity 2.5
The ModernDive teaching package learns to render inside the browser that runs its own textbook.
Its velocity score of 2.5/10 reflects longer-term release cadence.
Where soilDBdata leans on soil data, test fixtures and nasis, moderndive focuses on statistics education, webr and regression.
moderndive and soilDBdata have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full moderndive trajectory → · Compare soilDBdata vs moderndive →
9. cTMed · velocity 2.5
Continuous-time mediation effects get standardized centrality, six years into steady patch work.
Its velocity score of 2.5/10 reflects longer-term release cadence.
Where soilDBdata leans on soil data, test fixtures and nasis, cTMed focuses on mediation analysis, continuous time models and r package.
cTMed and soilDBdata have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
10. haze · velocity 2.5
Four dormant years end with a modernization pass and an off-by-one fix in the C++ core.
Its velocity score of 2.5/10 reflects longer-term release cadence.
Where soilDBdata leans on soil data, test fixtures and nasis, haze focuses on neuroimaging, mesh processing and interpolation.
haze and soilDBdata have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
11. fitVARMxID · velocity 2.5
A VAR-model fitting package acquiring the standard R methods it launched without.
Its velocity score of 2.5/10 reflects longer-term release cadence.
Where soilDBdata leans on soil data, test fixtures and nasis, fitVARMxID focuses on time series, structural equation modeling and r package.
fitVARMxID and soilDBdata have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full fitVARMxID trajectory → · Compare soilDBdata vs fitVARMxID →
12. hydroloom · velocity 0.0
USGS puts a type system over its river network toolkit so errors surface at dispatch.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “hydroloom v1.2.0”.
Where soilDBdata leans on soil data, test fixtures and nasis, hydroloom focuses on hydrology, network analysis and geospatial.
hydroloom and soilDBdata have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full hydroloom trajectory → · Compare soilDBdata vs hydroloom →
Frequently asked questions
What are the best alternatives to soilDBdata?
The top soilDBdata alternatives we currently track in analytics tools are glmbayes, palettecore, lstar, scimesh, vahtian, ranked by recent ship velocity.
How is this list of soilDBdata alternatives ranked?
Alternatives are ranked by Sparkpulse's velocity_score — release cadence + 30-day spark count + sector-relative ship rate.
Can I compare soilDBdata directly with one of these alternatives?
Yes — every card has a "Compare with soilDBdata" link to a side-by-side /compare page.