← Back to home
Comparison · Analytics

ibis.iSDM vs soilDBdata

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

ibis.iSDM vs soilDBdata: at a glance

Featureibis.iSDMsoilDBdata
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesr-package, species-distribution-models, terra, spatialsoil data, test fixtures, nasis, data package
Last editorial update58m ago8h ago
WebsiteVisit →Visit →

What is ibis.iSDM?

A raster-to-terra migration is the only readable change in a feed of merge notes.

ibis.iSDM fits integrated species distribution models in R. Its release notes are GitHub's auto-generated pull-request lists, so most tags say only which branch was merged and by whom. The one release with a written note, 0.0.5, records the migration from raster to terra across the whole package, with an explicit warning that established code may break.

Read the full ibis.iSDM 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 →

ibis.iSDM vs soilDBdata: editorial side-by-side

I
ibis.iSDM
ANALYTICS
0.0

A raster-to-terra migration is the only readable change in a feed of merge notes.

◆ Current state

ibis.iSDM fits integrated species distribution models in R. Its release notes are GitHub's auto-generated pull-request lists, so most tags say only which branch was merged and by whom. The one release with a written note, 0.0.5, records the migration from raster to terra across the whole package, with an explicit warning that established code may break.

◆ Where it's heading

Direction cannot be read from this feed with any confidence - three of the four visible tags carry nothing beyond merge titles and a full-changelog link. What is visible is a 2023 spent on dependency modernisation and dev-branch merges, ending with a 0.1.1 tag that December and nothing since.

◆ Prediction

These entries do not support a prediction; the notes would have to carry written content before a direction could be read from them.

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 ibis.iSDM 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 ibis.iSDM or soilDBdata.

See all ibis.iSDM alternatives → · See all soilDBdata alternatives →

Recent activity from ibis.iSDM and soilDBdata

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

  1. 3mo agosoilDBdataMarshall Islands FY26 gSSURGO dataset added
  2. 1y agosoilDBdataMT663 fixtures refreshed for soilDB 2.8.3
  3. 1y agosoilDBdataNASIS purpose lists updated for siteothvegclass
  4. 2y agoibis.iSDMVersion 0.1.1
  5. 3y agoibis.iSDMVersion 0.0.7
  6. 3y agoibis.iSDMVersion 0.0.6
  7. 3y agoibis.iSDMraster replaced by terra across the package
  8. 4y agosoilDBdataSelected-set _View_1 tables enable SS=TRUE/FALSE testing
  9. 4y agosoilDBdataProof of concept: MT663 pedon and component .sqlite fixtures

Frequently asked questions

What is the difference between ibis.iSDM and soilDBdata?

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

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

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