lstar
A single-cell data store commits to Zarr v3 and range-readable hosting across four language surfaces
Comparison · Analytics
nert vs soilDBdata
A side-by-side editorial comparison of nert and soilDBdata — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:soil datar package
nert vs soilDBdata: at a glance
What is nert?
nert put fourteen TERN datasets behind one dispatcher and called it stable.
nert is an R client for the TERN data API, reaching its first stable release in May 2026 after a year of milestone-tagged development. Version 1.0.0 exposes eleven functions covering fourteen datasets — SMIPS, ASC, AET, eight SLGA soil attributes, Soil Beta Diversity, Canopy Height and Land Surface Phenology — through a single read_tern(dataset_id, ...) dispatcher plus collect_tern_data() for batch extraction across locations and date ranges. Coverage sits at 83% overall with every reader at 100%.
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.
nert vs soilDBdata: editorial side-by-side
nert
0.0ANALYTICS
nert put fourteen TERN datasets behind one dispatcher and called it stable.
◆ Current state
nert is an R client for the TERN data API, reaching its first stable release in May 2026 after a year of milestone-tagged development. Version 1.0.0 exposes eleven functions covering fourteen datasets — SMIPS, ASC, AET, eight SLGA soil attributes, Soil Beta Diversity, Canopy Height and Land Surface Phenology — through a single read_tern(dataset_id, ...) dispatcher plus collect_tern_data() for batch extraction across locations and date ranges. Coverage sits at 83% overall with every reader at 100%.
◆ Where it's heading
The release history is unusual in that most of its tags are not releases: Milestone 1, 2 and 4 were pushed within eight minutes of each other in July 2025 purely as grant reporting and audit markers, with no user-facing content. What the 1.0.0 notes emphasise instead is test discipline — 310 deterministic offline tests, snapshot pins on every TERN bucket path and filename template, and mocked COG reads so R CMD check never touches the network. That is a client built on the assumption that the remote API's URL structure will change underneath it.
◆ Prediction
The notes describe pre-CRAN review polish and itemise remaining check NOTEs in cran-comments.md, so the next move is most likely a CRAN submission rather than additional dataset coverage.
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 nert 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 nert or soilDBdata.
quanteda
Text analysis in R keeps optimising its token internals — and builds a path out to torch
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
See all nert alternatives → · See all soilDBdata alternatives →
Recent activity from nert and soilDBdata
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3mo agonertnert 1.0.0 — first stable release ⚡
- 3mo agosoilDBdataMarshall Islands FY26 gSSURGO dataset added
- 1y agonertGrant audit tag: project Milestone 4
- 1y agonertGrant audit tag: project Milestone 2
- 1y agonertGrant audit tag: project Milestone 1
- 1y agonertv0.0.1 - First release
- 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 nert and soilDBdata?
Both compete on the same themes — soil data, r package — within Analytics. nert 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 nert better than soilDBdata?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. nert 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 nert?
Top nert alternatives in Analytics are ranked by recent ship velocity. Browse the "nert alternatives" section above for the current picks, or visit /alternatives/nert 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.