← Back to home
Comparison · Analytics

dubicube vs soilDBdata

A side-by-side editorial comparison of dubicube and soilDBdata — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:r package

dubicube vs soilDBdata: at a glance

FeaturedubicubesoilDBdata
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesbiodiversity, data cubes, bootstrapping, uncertaintysoil data, test fixtures, nasis, data package
Last editorial update54m ago49m ago
WebsiteVisit →Visit →

What is dubicube?

dubicube grew from a bootstrap helper into the uncertainty layer other B-Cubed packages call.

dubicube supplies bootstrapping and confidence-interval machinery for biodiversity data cubes in the B-Cubed project. The 0.10–0.12 series added the things a library needs to be depended on rather than copied: automatic detection of group-specific versus whole-cube bootstrapping, an optional boot backend, and then a second capability area in 0.12.0 with data quality diagnostics and cube filtering. The sibling indicator package b3gbi now delegates its confidence intervals here.

Read the full dubicube trajectory →

What is 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.

Read the full soilDBdata trajectory →

dubicube vs soilDBdata: editorial side-by-side

D
dubicube
ANALYTICS
0.0

dubicube grew from a bootstrap helper into the uncertainty layer other B-Cubed packages call.

◆ Current state

dubicube supplies bootstrapping and confidence-interval machinery for biodiversity data cubes in the B-Cubed project. The 0.10–0.12 series added the things a library needs to be depended on rather than copied: automatic detection of group-specific versus whole-cube bootstrapping, an optional boot backend, and then a second capability area in 0.12.0 with data quality diagnostics and cube filtering. The sibling indicator package b3gbi now delegates its confidence intervals here.

◆ Where it's heading

Release notes are terse — usually one line and an issue number — but the direction is legible in what gets automated. Decisions the caller used to make explicitly are being inferred: resampling scope in 0.10.0, the no-bias option in 0.11.0, and process_cube_args threaded through filter_cube() so the filtering path matches cube processing. The diagnostics work in 0.12.x is the newer line, and 0.12.2's rename of the heatmap option to rule suggests that surface is still settling.

◆ Prediction

The diagnostics and filtering additions have needed a follow-up fix in each of the two releases since they landed, so the next release is most likely more consolidation there rather than a new capability area.

S
soilDBdata
ANALYTICS
0.0

soilDBdata exists so soilDB's tests can run without a NASIS connection.

◆ Current state

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.

◆ Where it's heading

Development follows soilDB rather than leading it: assets get bumped when a soilDB version changes, and purpose lists are updated when soilDB adds a table. The one release that changed what testing is possible was v0.1.1, which added selected-set _View_1 tables alongside whole tables so both SS=TRUE and SS=FALSE code paths could be exercised. Four-year gaps between releases are normal here and do not indicate abandonment — a fixture package only needs to move when the fixtures go stale.

◆ Prediction

The recent addition is a new geography rather than a new table structure, so further releases most likely continue broadening dataset coverage as soilDB gains regions to test against.

Alternatives to dubicube and soilDBdata

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 dubicube or soilDBdata.

See all dubicube alternatives → · See all soilDBdata alternatives →

Recent activity from dubicube and soilDBdata

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1mo agodubicubePackage build fixes
  2. 3mo agosoilDBdataMarshall Islands FY26 gSSURGO dataset added
  3. 3mo agodubicubeFilter vignette documentation and rule-function fix
  4. 3mo agodubicubeprocess_cube_args in filter_cube(); heatmap option renamed to rule
  5. 4mo agodubicubeData quality diagnostics and cube filtering
  6. 5mo agodubicubeZenodo grant ID and metadata fixes
  7. 6mo agodubicubeNo-bias bootstrap option automated
  8. 1y agosoilDBdataMT663 fixtures refreshed for soilDB 2.8.3
  9. 1y agosoilDBdataNASIS purpose lists updated for siteothvegclass
  10. 4y agosoilDBdataSelected-set _View_1 tables enable SS=TRUE/FALSE testing
  11. 4y agosoilDBdataProof of concept: MT663 pedon and component .sqlite fixtures

Frequently asked questions

What is the difference between dubicube and soilDBdata?

Both compete on the same themes — r package — within Analytics. dubicube and soilDBdata 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 dubicube better than soilDBdata?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dubicube and soilDBdata 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 dubicube?

Top dubicube alternatives in Analytics are ranked by recent ship velocity. Browse the "dubicube alternatives" section above for the current picks, or visit /alternatives/dubicube for the full list with editorial commentary on each.

What are the best alternatives to soilDBdata?

Top soilDBdata alternatives in Analytics are ranked by recent ship velocity. Browse the "soilDBdata alternatives" section above for the current picks, or visit /alternatives/soildbdata for the full list with editorial commentary on each.