collinear
collinear has broken its API twice to stop making the user pick thresholds.
Comparison · Analytics
clinify vs soilDBdata
A side-by-side editorial comparison of clinify and soilDBdata — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r package
clinify vs soilDBdata: at a glance
What is clinify?
clinify is closing the gap between flextable defaults and regulatory table specs.
clinify shapes clinical trial tables into the Word deliverables regulatory submissions require, wrapping flextable and officer. Version 0.4.0 is on CRAN and is almost entirely typographic control: spanner rules that follow the header instead of hard-coded column numbers, header padding named for where the space actually sits, and explicit row pitch. The structural release was 0.3.0, which introduced document objects and broke three APIs to get there.
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.
clinify vs soilDBdata: editorial side-by-side
clinify
2.5ANALYTICS
clinify is closing the gap between flextable defaults and regulatory table specs.
◆ Current state
clinify shapes clinical trial tables into the Word deliverables regulatory submissions require, wrapping flextable and officer. Version 0.4.0 is on CRAN and is almost entirely typographic control: spanner rules that follow the header instead of hard-coded column numbers, header padding named for where the space actually sits, and explicit row pitch. The structural release was 0.3.0, which introduced document objects and broke three APIs to get there.
◆ Where it's heading
The package is working through the places where flextable's defaults and a statistical reporting spec disagree, and the notes are unusually explicit about why each default is wrong — a cell's bottom border draws below its bottom padding, so space under a header moves the rule rather than opening a gap beneath it; flextable leaves rows at a nominal quarter inch when the spec names an exact pitch. Each addition is built to survive an organisation's own clinify_table_default() rather than assuming clinify's styling runs last.
◆ Prediction
Header, spanner and row-pitch control all landed together, so the next gap in the same series is title and footnote geometry — the remaining page furniture that 0.3.0's two-part split left roughly specified.
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 clinify 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 clinify or soilDBdata.
nert
nert put fourteen TERN datasets behind one dispatcher and called it stable.
scTypeEval
scTypeEval judges single-cell annotations without needing a ground truth to judge them against.
medrobust
medrobust made its partial-identification bounds usable by giving them confidence intervals.
probmed
probmed went from one probabilistic effect size to a family of them in sixteen days.
fluxnet-package
fluxnet keeps swapping its own plumbing — first a Python downloader, now a DuckDB backend.
See all clinify alternatives → · See all soilDBdata alternatives →
Recent activity from clinify and soilDBdata
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 15d agoclinifySpanner rules, header padding and exact row pitch
- 3mo agosoilDBdataMarshall Islands FY26 gSSURGO dataset added
- 1y agoclinifyDocument objects: clindoc() and multi-table output ⚡
- 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 clinify and soilDBdata?
Both compete on the same themes — r package — within Analytics. clinify is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is clinify better than soilDBdata?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. clinify is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to clinify?
Top clinify alternatives in Analytics are ranked by recent ship velocity. Browse the "clinify alternatives" section above for the current picks, or visit /alternatives/clinify 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.