← Back to home
Comparison · Analytics

rempsyc vs soilDBdata

A side-by-side editorial comparison of rempsyc and soilDBdata — release velocity, themes, recent moves, and the top alternatives to consider.

rempsyc vs soilDBdata: at a glance

FeaturerempsycsoilDBdata
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesapa-formatting, psychology-research, statistical-tables, ggplot2soil data, test fixtures, nasis, data package
Last editorial update1h ago7h ago
WebsiteVisit →Visit →

What is rempsyc?

Publication-ready psychology tables and plots, tracking APA style as closely as the software allows.

rempsyc produces APA-formatted tables and figures for psychology research — nice_table() for results tables, plus plotting helpers for scatter plots, violin plots, densities and simple slopes. Its releases are CRAN submissions that bundle a long run of development versions, so each entry reads as a digest rather than a single change. The most recent, 0.2.0, added point labelling and per-group correlation statistics to nice_scatter and fixed nice_lm() failing on factor covariates with more than two levels.

Read the full rempsyc trajectory →

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.

Read the full soilDBdata trajectory →

rempsyc vs soilDBdata: editorial side-by-side

R
rempsyc
ANALYTICS
0.0

Publication-ready psychology tables and plots, tracking APA style as closely as the software allows.

◆ Current state

rempsyc produces APA-formatted tables and figures for psychology research — nice_table() for results tables, plus plotting helpers for scatter plots, violin plots, densities and simple slopes. Its releases are CRAN submissions that bundle a long run of development versions, so each entry reads as a digest rather than a single change. The most recent, 0.2.0, added point labelling and per-group correlation statistics to nice_scatter and fixed nice_lm() failing on factor covariates with more than two levels.

◆ Where it's heading

Two forces drive this package and neither is its own roadmap. The first is APA style: when the 7th edition advised against beta for standardized coefficients, the package switched its output to italic b with an asterisk. The second is the surrounding ecosystem — formatting is aligned to what lavaanExtra and afex produce, contrast handling was delegated to easystats' modelbased, and Excel correlation matrix export was handed entirely to the correlation package to cut maintenance.

◆ Prediction

The pattern of delegating functionality to specialist packages while keeping the formatting layer is well established and likely continues. Because releases bundle many small dev versions, the next one will probably again mix plotting refinements with fixes surfaced by upstream changes.

S
soilDBdata
ANALYTICS
0.0

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 rempsyc 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 rempsyc or soilDBdata.

See all rempsyc alternatives → · See all soilDBdata alternatives →

Recent activity from rempsyc and soilDBdata

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 3mo agosoilDBdataMarshall Islands FY26 gSSURGO dataset added
  2. 11mo agorempsycPoint labels and per-group correlations added to nice_scatter
  3. 1y agorempsycExcel correlation export delegated to the correlation package
  4. 1y agosoilDBdataMT663 fixtures refreshed for soilDB 2.8.3
  5. 1y agosoilDBdataNASIS purpose lists updated for siteothvegclass
  6. 2y agorempsycTable spacing control and a fix for name collision with afex
  7. 2y agorempsycStandardized coefficients switch to APA 7th edition b* notation
  8. 2y agorempsycLegend and standardization-check fixes
  9. 2y agorempsycnice_table starts coercing model objects automatically
  10. 4y agosoilDBdataSelected-set _View_1 tables enable SS=TRUE/FALSE testing
  11. 4y agosoilDBdataProof of concept: MT663 pedon and component .sqlite fixtures

Frequently asked questions

What is the difference between rempsyc and soilDBdata?

They serve adjacent needs but don't currently overlap on shipped themes. rempsyc 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 rempsyc better than soilDBdata?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. rempsyc 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 rempsyc?

Top rempsyc alternatives in Analytics are ranked by recent ship velocity. Browse the "rempsyc alternatives" section above for the current picks, or visit /alternatives/rempsyc 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.