fillpattern
Pattern fills for ggplot2, hardened against the ways users write sizes
Comparison · Analytics
soilDBdata vs spEDM
A side-by-side editorial comparison of soilDBdata and spEDM — release velocity, themes, recent moves, and the top alternatives to consider.
soilDBdata vs spEDM: at a glance
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.
What is spEDM?
Spatial causal discovery in R, one exposed method per release
spEDM brings empirical dynamic modeling to spatial data — cross mapping, convergent cross mapping and pattern causality over spatial vector and raster inputs, with the numerics in C++ behind S4 generics. The recent releases have exposed geographical pattern causality and spatially convergent partial cross mapping at the R level with vignettes, and 1.12 turns to consolidating the API. It is part of the stscl family alongside the temporal-domain tEDM, with which it shares both its C++ core and its maintainer.
soilDBdata vs spEDM: editorial side-by-side
soilDBdata
0.0ANALYTICS
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.
spEDM
0.0ANALYTICS
Spatial causal discovery in R, one exposed method per release
◆ Current state
spEDM brings empirical dynamic modeling to spatial data — cross mapping, convergent cross mapping and pattern causality over spatial vector and raster inputs, with the numerics in C++ behind S4 generics. The recent releases have exposed geographical pattern causality and spatially convergent partial cross mapping at the R level with vignettes, and 1.12 turns to consolidating the API. It is part of the stscl family alongside the temporal-domain tEDM, with which it shares both its C++ core and its maintainer.
◆ Where it's heading
The cadence is steady and predictable: each release surfaces one more EDM method as an R-level API with a vignette, then spends the rest of its notes on parameter-handling consistency across the generics. Breaking changes are frequent and deliberate — argument renames, parameter reordering, NA-handling defaults — which reads as a package still settling its interface while the method surface expands. Shared changes appear in tEDM within days, so interface churn lands on both packages at once.
◆ Prediction
Expect the next release to expose another causality variant at the R level with an accompanying vignette, and to continue renaming or reordering parameters toward consistency across the spatial and temporal packages.
Alternatives to soilDBdata and spEDM
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 soilDBdata or spEDM.
gcube
gcube's recent releases are all packaging metadata, not simulation code
cubist
The R port of Quinlan's Cubist gets reproducibility fixes, not new modelling
ggstats
ggstats keeps widening what a coefficient or Likert plot can be
ecodive
ecodive rebuilt itself into a broad diversity-metric library, breaking as it went
simStateSpace
State-space data simulation for R, filled in one function at a time
See all soilDBdata alternatives → · See all spEDM alternatives →
Recent activity from soilDBdata and spEDM
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3mo agosoilDBdataMarshall Islands FY26 gSSURGO dataset added
- 4mo agospEDMData slicing for large-scale pattern causality, plus API breaks
- 6mo agospEDMspEDM 1.11
- 6mo agospEDMSpatially convergent partial cross mapping reaches the R API
- 8mo agospEDMRaster cross mapping with anisotropic embedding
- 11mo agospEDMConfigurable distance metrics and multithreaded distance computation
- 1y agospEDMSpatial logistic map exposed at the R level
- 1y agosoilDBdataMT663 fixtures refreshed for soilDB 2.8.3
- 1y agosoilDBdataNASIS purpose lists updated for siteothvegclass
- 4y agosoilDBdataSelected-set _View_1 tables enable SS=TRUE/FALSE testing
- 4y agosoilDBdataProof of concept: MT663 pedon and component .sqlite fixtures
Frequently asked questions
What is the difference between soilDBdata and spEDM?
They serve adjacent needs but don't currently overlap on shipped themes. soilDBdata and spEDM 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 soilDBdata better than spEDM?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. soilDBdata and spEDM 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 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.
What are the best alternatives to spEDM?
Top spEDM alternatives in Analytics are ranked by recent ship velocity. Browse the "spEDM alternatives" section above for the current picks, or visit /alternatives/spedm for the full list with editorial commentary on each.