collinear
collinear has broken its API twice to stop making the user pick thresholds.
Comparison · Analytics
dissmapr vs soilDBdata
A side-by-side editorial comparison of dissmapr and soilDBdata — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r package
dissmapr vs soilDBdata: at a glance
What is dissmapr?
dissmapr spent its first releases becoming citable rather than adding methods.
dissmapr provides an R workflow for compositional dissimilarity and turnover — occurrence data through spatial gridding and environmental linkage to order-wise dissimilarity and bioregional mapping. All three releases to date are infrastructure: a first citable archive in June 2026, then a maturity release aligning the package with the B-Cubed software development guide. The ten-function pipeline described in the notes has not changed across them.
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.
dissmapr vs soilDBdata: editorial side-by-side
dissmapr
0.0ANALYTICS
dissmapr spent its first releases becoming citable rather than adding methods.
◆ Current state
dissmapr provides an R workflow for compositional dissimilarity and turnover — occurrence data through spatial gridding and environmental linkage to order-wise dissimilarity and bioregional mapping. All three releases to date are infrastructure: a first citable archive in June 2026, then a maturity release aligning the package with the B-Cubed software development guide. The ten-function pipeline described in the notes has not changed across them.
◆ Where it's heading
The work is compliance-shaped rather than method-shaped: explicit @importFrom in place of whole-namespace imports, library() calls removed from package code, roughly 11 MB of development caches dropped, a runnable README quick-start, and Zenodo archival with CITATION.cff and codemeta.json. dissmapr moves in lockstep with its B-Cubed sibling invasimapr — both tagged 0.1.0 within three minutes of each other and 0.2.0 on the same day — so releases here reflect project-wide standards deadlines more than package-specific work. The stated roadmap of additional ecological distance metrics has not yet landed.
◆ Prediction
With standards work now signed off and R CMD check clean, the next release is the first real chance for the roadmap items — additional ecological distance metrics — to arrive.
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.
Alternatives to dissmapr 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 dissmapr or soilDBdata.
nert
nert put fourteen TERN datasets behind one dispatcher and called it stable.
scTypeEval
scTypeEval judges single-cell annotations without needing a ground truth to judge them against.
medrobust
medrobust made its partial-identification bounds usable by giving them confidence intervals.
probmed
probmed went from one probabilistic effect size to a family of them in sixteen days.
fluxnet-package
fluxnet keeps swapping its own plumbing — first a Python downloader, now a DuckDB backend.
See all dissmapr alternatives → · See all soilDBdata alternatives →
Recent activity from dissmapr and soilDBdata
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agodissmaprVersion bump; notes identical to 0.2.0
- 1mo agodissmaprB-Cubed standards alignment, docs overhaul and a citable DOI
- 1mo agodissmaprdissmapr v0.1.0: First citable release
- 3mo agosoilDBdataMarshall Islands FY26 gSSURGO dataset added
- 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 dissmapr and soilDBdata?
Both compete on the same themes — r package — within Analytics. dissmapr 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 dissmapr better than soilDBdata?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dissmapr 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 dissmapr?
Top dissmapr alternatives in Analytics are ranked by recent ship velocity. Browse the "dissmapr alternatives" section above for the current picks, or visit /alternatives/dissmapr 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.