lstar
A single-cell data store commits to Zarr v3 and range-readable hosting across four language surfaces
Comparison · Analytics
quanteda vs soilDBdata
A side-by-side editorial comparison of quanteda and soilDBdata — release velocity, themes, recent moves, and the top alternatives to consider.
quanteda vs soilDBdata: at a glance
What is quanteda?
Text analysis in R keeps optimising its token internals — and builds a path out to torch
quanteda is a mature framework for quantitative text analysis in R. Since the 4.0 rewrite around external-pointer tokens objects, releases have concentrated on the internals: recompilation control, memory reduction on concatenation, type-table consistency between tokens and dfm objects. The newest release adds tokens_recompile() for explicit ID reassignment, stops query functions from recompiling implicitly, and returns dense rather than sparse tensors from as.tensor() with arguments passed through to torch.
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.
quanteda vs soilDBdata: editorial side-by-side
quanteda
2.5ANALYTICS
Text analysis in R keeps optimising its token internals — and builds a path out to torch
◆ Current state
quanteda is a mature framework for quantitative text analysis in R. Since the 4.0 rewrite around external-pointer tokens objects, releases have concentrated on the internals: recompilation control, memory reduction on concatenation, type-table consistency between tokens and dfm objects. The newest release adds tokens_recompile() for explicit ID reassignment, stops query functions from recompiling implicitly, and returns dense rather than sparse tensors from as.tensor() with arguments passed through to torch.
◆ Where it's heading
Two threads run in parallel. The dominant one is performance and correctness housekeeping on the tokens_xptr representation introduced in 4.0 — each release closes another case where the external-pointer path diverged from the plain tokens path. The quieter thread points outward: as.matrix() returning a document-by-position integer matrix and as.tensor() handing off to torch::torch_tensor() make the tokenised corpus directly consumable by neural models rather than only by quanteda's own bag-of-words machinery.
◆ Prediction
The tensor and matrix export path is the least mature part of the surface and gained arguments in this release rather than settling, so expect further work there before the token internals change again.
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 quanteda 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 quanteda or soilDBdata.
moderndive
The ModernDive teaching package learns to render inside the browser that runs its own textbook
glmbayes
A GPU-accelerated Bayesian GLM package buys its way into the standard R Bayesian toolchain
hydroloom
USGS puts a type system over its river network toolkit so errors surface at dispatch
chromConverter
The chromatography file-format translator keeps absorbing vendor formats one release at a time
slope
A year after gutting itself for a C++ rewrite, SLOPE is back to polishing the interface
See all quanteda alternatives → · See all soilDBdata alternatives →
Recent activity from quanteda and soilDBdata
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 12d agoquantedaExplicit token recompilation and a denser path out to torch
- 3mo agosoilDBdataMarshall Islands FY26 gSSURGO dataset added
- 1y agoquantedaCorpus chunking and cheaper token concatenation
- 1y agoquantedaFaster concatenation and a dfm_lookup naming fix
- 1y agosoilDBdataMT663 fixtures refreshed for soilDB 2.8.3
- 1y agosoilDBdataNASIS purpose lists updated for siteothvegclass
- 2y agoquantedaMinor test and documentation fixes
- 2y agoquantedaPlatform-specific test and installation fixes
- 2y agoquantedaCRAN v4.0 ⚡
- 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 quanteda and soilDBdata?
They serve adjacent needs but don't currently overlap on shipped themes. quanteda is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is quanteda better than soilDBdata?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. quanteda is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to quanteda?
Top quanteda alternatives in Analytics are ranked by recent ship velocity. Browse the "quanteda alternatives" section above for the current picks, or visit /alternatives/quanteda 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.