← Back to home
Comparison · Analytics

animovement vs soilDBdata

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

Shared themes:r package

animovement vs soilDBdata: at a glance

FeatureanimovementsoilDBdata
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesanimal tracking, metapackage, pose estimation, data standardssoil data, test fixtures, nasis, data package
Last editorial update53m ago49m ago
WebsiteVisit →Visit →

What is animovement?

animovement stopped being a package and became a metapackage over seven focused ones.

animovement handles animal movement data — tracking output from pose-estimation and centroid trackers, cleaned into a standard form. Its 0.7.3 release, the first GitHub tag since November 2024, bundles the 0.5 through 0.7 development series and records a structural change: the codebase was split into aniframe, aniread, aniprocess, anicheck, animetric, anivis and anispace, which animovement now bundles and re-exports. The package has done this before at smaller scale, having renamed itself from trackballr in 0.2.0 to match a widened scope.

Read the full animovement 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 →

animovement vs soilDBdata: editorial side-by-side

A
animovement
ANALYTICS
0.0

animovement stopped being a package and became a metapackage over seven focused ones.

◆ Current state

animovement handles animal movement data — tracking output from pose-estimation and centroid trackers, cleaned into a standard form. Its 0.7.3 release, the first GitHub tag since November 2024, bundles the 0.5 through 0.7 development series and records a structural change: the codebase was split into aniframe, aniread, aniprocess, anicheck, animetric, anivis and anispace, which animovement now bundles and re-exports. The package has done this before at smaller scale, having renamed itself from trackballr in 0.2.0 to match a widened scope.

◆ Where it's heading

Development has moved to the constituent packages, which release far more often than animovement itself — aniframe, aniread and aniprocess have each shipped multiple times in 2026 while animovement tagged once. That makes animovement a stable install surface rather than where the work happens, and the ani_df data class plus the frame-rate to sampling-rate terminology change are the contracts holding the suite together. Optional dependencies are handled through animovement_install_suggested() against r-universe and Bioconductor mirrors.

◆ Prediction

With the split done and the constituent packages iterating independently, animovement releases are likely to become periodic roll-ups of the suite rather than carriers of new functionality.

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

See all animovement alternatives → · See all soilDBdata alternatives →

Recent activity from animovement and soilDBdata

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

  1. 1mo agoanimovementanimovement becomes a metapackage over seven packages
  2. 3mo agosoilDBdataMarshall Islands FY26 gSSURGO dataset added
  3. 1y agoanimovementread_animalta() patch
  4. 1y agoanimovementReaders for seven tracking and pose-estimation formats
  5. 1y agosoilDBdataMT663 fixtures refreshed for soilDB 2.8.3
  6. 1y agosoilDBdataNASIS purpose lists updated for siteothvegclass
  7. 1y agoanimovementtrackballr becomes animovement as scope widens
  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 animovement and soilDBdata?

Both compete on the same themes — r package — within Analytics. animovement 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 animovement better than soilDBdata?

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

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