simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
Comparison · Analytics
lavaanExtra vs soilDBdata
A side-by-side editorial comparison of lavaanExtra and soilDBdata — release velocity, themes, recent moves, and the top alternatives to consider.
lavaanExtra vs soilDBdata: at a glance
What is lavaanExtra?
SEM reporting helpers converging on APA output, one CRAN resubmission at a time.
lavaanExtra provides shorthand syntax and formatted output around lavaan structural equation models - write_lavaan() to build model strings, and nice_* functions for fit tables, plots, and modification indices. Three of the six visible releases exist only to satisfy CRAN resubmission: a unicode problem, a dependency version check, tests running without suggested packages. The substance sits in 0.1.5, 0.1.8, and 0.1.9.
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.
lavaanExtra vs soilDBdata: editorial side-by-side
lavaanExtra
0.0ANALYTICS
SEM reporting helpers converging on APA output, one CRAN resubmission at a time.
◆ Current state
lavaanExtra provides shorthand syntax and formatted output around lavaan structural equation models - write_lavaan() to build model strings, and nice_* functions for fit tables, plots, and modification indices. Three of the six visible releases exist only to satisfy CRAN resubmission: a unicode problem, a dependency version check, tests running without suggested packages. The substance sits in 0.1.5, 0.1.8, and 0.1.9.
◆ Where it's heading
The package generalises its own vocabulary as it goes: lavaan_ind() became lavaan_defined() once it turned out to extract any user-defined parameter, and lavaan_cov() was split so lavaan_cor() covers actual correlations. Methodological positions are taken alongside the API - dropping the estimate argument from lavaan_reg() to force reporting both standardized and unstandardized values, and updating the RMSEA benchmark to Schreiber (2017). Rémi Thériault maintains it next to rempsyc, which formats output to match. Note that 0.1.5 restates the whole 0.1.4.x development series in one body.
◆ Prediction
The pattern points to another nice_* helper aimed at a reporting step that currently needs hand formatting, arriving with the usual CRAN resubmission behind it.
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 lavaanExtra 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 lavaanExtra or soilDBdata.
ibis.iSDM
A raster-to-terra migration is the only readable change in a feed of merge notes.
anyflights
A nycflights13 generator whose recent work is all about the data being right.
vinereg
Conditional density and log-likelihood fill out a vine copula regression package.
stringx
A drop-in string API for base R, kept alive by upstream check failures.
healthyR.data
From a bundled hospital dataset to a live CMS API client.
See all lavaanExtra alternatives → · See all soilDBdata alternatives →
Recent activity from lavaanExtra and soilDBdata
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3mo agosoilDBdataMarshall Islands FY26 gSSURGO dataset added
- 1y agosoilDBdataMT663 fixtures refreshed for soilDB 2.8.3
- 1y agosoilDBdataNASIS purpose lists updated for siteothvegclass
- 2y agolavaanExtraCRAN resubmission for a unicode problem
- 2y agolavaanExtralavaan_ind renamed to lavaan_defined; thresholds supported
- 2y agolavaanExtranice_modindices flags redundant items
- 3y agolavaanExtraSuggested dependency versions checked correctly
- 3y agolavaanExtraTests run without suggested dependencies
- 3y agolavaanExtraFit benchmarks updated and correlations split from covariances
- 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 lavaanExtra and soilDBdata?
They serve adjacent needs but don't currently overlap on shipped themes. lavaanExtra 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 lavaanExtra better than soilDBdata?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. lavaanExtra 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 lavaanExtra?
Top lavaanExtra alternatives in Analytics are ranked by recent ship velocity. Browse the "lavaanExtra alternatives" section above for the current picks, or visit /alternatives/lavaanextra 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.