TidyDensity
A distribution catalogue that grows by one family at a time, and rarely breaks anything.
A side-by-side editorial comparison of nflseedR and soilDB — release velocity, themes, recent moves, and the top alternatives to consider.
nflseedR rewrote its simulator from scratch and put the original on a deprecation clock.
nflseedR computes NFL standings, playoff seeding and draft order, and simulates seasons to produce playoff probabilities. Version 2.0.0 replaced the engine rather than extending it: nfl_standings() and nfl_simulations() are new implementations, and the original compute_division_ranks(), compute_conference_seeds(), compute_draft_order() and simulate_nfl() are all slated for deprecation. The two releases since have been correctness fixes and a CRAN-requested documentation styling change.
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.
nflseedR computes NFL standings, playoff seeding and draft order, and simulates seasons to produce playoff probabilities. Version 2.0.0 replaced the engine rather than extending it: nfl_standings() and nfl_simulations() are new implementations, and the original compute_division_ranks(), compute_conference_seeds(), compute_draft_order() and simulate_nfl() are all slated for deprecation. The two releases since have been correctness fixes and a CRAN-requested documentation styling change.
The direction is toward a leaner, faster package with fewer dependencies, and the deprecation plan is stated openly — retiring simulate_nfl() is described as the step that lets the dependency list shrink significantly. Tiebreaker coverage has been filled in to the point where only net touchdowns remain unimplemented, and load_sharpe_games() has been handed off to nflreadr. Requiring R 4.1 for the native pipe is the same instinct applied to the language floor.
The deprecations are announced but not executed, so the next substantive release most likely removes simulate_nfl() and the older standings helpers and drops the dependencies that were the stated reason for the rewrite. Net-touchdown tiebreaking is the one gap the entries explicitly leave open.
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.
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.
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.
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 nflseedR or soilDB.
A distribution catalogue that grows by one family at a time, and rarely breaks anything.
College football's open data client hit v2 — and now reports how many API calls you have left.
The USA phenology data client rebuilt its entire stack and stopped handing users -9999 as a number.
GeneNMF rebuilt how it derives meta-programs, changing every result it had produced.
Publication-ready psychology tables and plots, tracking APA style as closely as the software allows.
A spatial-statistics utility package exists to be depended on, and is built accordingly.
See all nflseedR alternatives → · See all soilDB alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. nflseedR 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. nflseedR 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.
Top nflseedR alternatives in Analytics are ranked by recent ship velocity. Browse the "nflseedR alternatives" section above for the current picks, or visit /alternatives/nflseedr for the full list with editorial commentary on each.
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.