PurpleAir
The R client for PurpleAir sensors keeps finding its time-averaging was wrong.
Comparison · Analytics
nert vs soilDB
A side-by-side editorial comparison of nert and soilDB — release velocity, themes, recent moves, and the top alternatives to consider.
nert vs soilDB: 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 soilDB?
The R front door to USDA soil data finishes a long deprecation cleanup and turns local-first.
soilDB is the R access layer for USDA-NRCS soil data: NASIS local databases, Soil Data Access, SoilWeb coverage services, and a widening set of curated national grids. The 2.9.x line closed out a multi-release deprecation cycle — column aliases and stringsAsFactors are gone, R 4.1 is the floor, and the bundled sample profile collections were rebuilt against the new schema. Recent work has shifted from adding query functions to making existing ones faster and usable against local SQLite or GeoPackage copies.
nert vs soilDB: 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.
soilDB
0.0ANALYTICS
The R front door to USDA soil data finishes a long deprecation cleanup and turns local-first.
◆ Current state
soilDB is the R access layer for USDA-NRCS soil data: NASIS local databases, Soil Data Access, SoilWeb coverage services, and a widening set of curated national grids. The 2.9.x line closed out a multi-release deprecation cycle — column aliases and stringsAsFactors are gone, R 4.1 is the floor, and the bundled sample profile collections were rebuilt against the new schema. Recent work has shifted from adding query functions to making existing ones faster and usable against local SQLite or GeoPackage copies.
◆ Where it's heading
The arc points at offline and local-first workflows. downloadSSURGO() and createSSURGO() keep gaining arguments for building and querying local SSURGO databases, and the query internals were rewritten as common table expressions so identical code runs against the remote service or a local file. Coverage is widening in parallel: FY26 SoilWeb maps now reach most OCONUS surveys, while fetchHWSD() and fetchSOLUS() pull in datasets outside the core NASIS/SSURGO pair. Federal URL churn — EDIT, SoilWeb, S3-hosted geometry — is a recurring maintenance tax the package absorbs on users' behalf.
◆ Prediction
Expect the next releases to keep extending parallel and offline SSURGO handling, since LAPPLY.FUN has just opened the door to arbitrary parallel backends, and to fold more curated SoilWeb and FAO datasets behind fetch* wrappers.
Alternatives to nert and soilDB
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 soilDB.
piecepackr
A board game graphics package runs one of the most disciplined deprecation cycles in R.
e2tree
The explainable-ensemble-tree package now measures whether its own explanations are faithful.
discretefdr
The discrete-data FDR package is being pared into one piece of a larger multiple-testing suite.
contentanalysis
A scientific-text analysis package moved from counting citations to classifying argument structure.
relialearnr
The teaching arm of an R reliability suite keeps pace with whatever its analysis siblings ship.
Recent activity from nert and soilDB
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agosoilDBFY26 soil maps reach OCONUS; SSURGO downloads go parallel
- 3mo agonertnert 1.0.0 — first stable release ⚡
- 4mo agosoilDBROSETTA v2 lands as the deprecated NASIS aliases are removed ⚡
- 10mo agosoilDBNASIS record IDs now retrievable through Soil Data Access
- 11mo agosoilDBSpatial queries can pull columns from non-spatial tables
- 1y agosoilDBNASIS 7.4.3 metadata, plus HWSD and a local cache in 2.8.10
- 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 agosoilDBQuery internals rewritten as CTEs for local SQLite support
Frequently asked questions
What is the difference between nert and soilDB?
They serve adjacent needs but don't currently overlap on shipped themes. nert and soilDB 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 soilDB?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. nert and soilDB 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 soilDB?
Top soilDB alternatives in Analytics are ranked by recent ship velocity. Browse the "soilDB alternatives" section above for the current picks, or visit /alternatives/soildb for the full list with editorial commentary on each.