fillpattern
Pattern fills for ggplot2, hardened against the ways users write sizes
Comparison · Analytics
rdataone vs soilDBdata
A side-by-side editorial comparison of rdataone and soilDBdata — release velocity, themes, recent moves, and the top alternatives to consider.
rdataone vs soilDBdata: at a glance
What is rdataone?
The R client for DataONE ships slow, correctness-focused maintenance
rdataone is the R client for the DataONE federated research-data network, handling authentication, upload and retrieval of data packages against member nodes. Recent work is concentrated on correctness in the upload path — rightsHolder persistence, public-read flags applied across all objects in a package, and edge cases in archive() — plus dependency trimming. The feed's version stamps are unreliable: 2.2.2 carries a later publication date than 2.3.0, which cites 2.2.2 as its own predecessor.
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.
rdataone vs soilDBdata: editorial side-by-side
rdataone
0.0ANALYTICS
The R client for DataONE ships slow, correctness-focused maintenance
◆ Current state
rdataone is the R client for the DataONE federated research-data network, handling authentication, upload and retrieval of data packages against member nodes. Recent work is concentrated on correctness in the upload path — rightsHolder persistence, public-read flags applied across all objects in a package, and edge cases in archive() — plus dependency trimming. The feed's version stamps are unreliable: 2.2.2 carries a later publication date than 2.3.0, which cites 2.2.2 as its own predecessor.
◆ Where it's heading
This is long-cycle infrastructure maintenance, not feature development. Release intervals run to years, and the content is dominated by access-control correctness, CRAN compliance and TLS/platform fixes rather than new client capability. The one consistent thread is hardening how permissions and checksums survive a round trip to a member node.
◆ Prediction
Expect continued low-frequency releases driven by CRAN check failures and platform TLS changes, with any functional work staying in the upload and permissions path rather than the query surface.
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 rdataone 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 rdataone or soilDBdata.
gcube
gcube's recent releases are all packaging metadata, not simulation code
cubist
The R port of Quinlan's Cubist gets reproducibility fixes, not new modelling
ggstats
ggstats keeps widening what a coefficient or Likert plot can be
ecodive
ecodive rebuilt itself into a broad diversity-metric library, breaking as it went
simStateSpace
State-space data simulation for R, filled in one function at a time
See all rdataone alternatives → · See all soilDBdata alternatives →
Recent activity from rdataone and soilDBdata
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3mo agosoilDBdataMarshall Islands FY26 gSSURGO dataset added
- 4mo agordataonePermission bugs fixed in data package uploads
- 8mo agordataoneWindows TLS 1.2 fix unblocks client connections
- 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
- 5y agordataoneSHA-256 checksums and changed lazyLoad behaviour
- 6y agordataonedataone 2.1.4
- 6y agordataonedataone 2.1.3
- 7y agordataonedataone 2.1.2
Frequently asked questions
What is the difference between rdataone and soilDBdata?
They serve adjacent needs but don't currently overlap on shipped themes. rdataone 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 rdataone better than soilDBdata?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. rdataone 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 rdataone?
Top rdataone alternatives in Analytics are ranked by recent ship velocity. Browse the "rdataone alternatives" section above for the current picks, or visit /alternatives/rdataone 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.