← Back to home
Comparison · Analytics

aniprocess vs soilDBdata

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

Shared themes:r package

aniprocess vs soilDBdata: at a glance

FeatureaniprocesssoilDBdata
SectorAnalyticsAnalytics
Velocity score3.80.0
Sparks · 30d10
Top themesanimal tracking, signal processing, breaking changes, api designsoil data, test fixtures, nasis, data package
Last editorial update53m ago44m ago
WebsiteVisit →Visit →

What is aniprocess?

aniprocess rebuilt its filter API into three tiers and removed the old one outright.

aniprocess is the signal-processing half of the animovement ecosystem for animal movement data — smoothing, outlier flagging and gap handling for tracking coordinates. Version 0.3.0 restructured the entire public interface into three tiers: bare functions over a vector or a frame of coordinate columns, *_with() to select a method by name, and *_across() to apply one to a whole aniframe. Two functions were removed rather than deprecated, and argument names were normalized across the package.

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

aniprocess vs soilDBdata: editorial side-by-side

A
aniprocess
ANALYTICS
3.8

aniprocess rebuilt its filter API into three tiers and removed the old one outright.

◆ Current state

aniprocess is the signal-processing half of the animovement ecosystem for animal movement data — smoothing, outlier flagging and gap handling for tracking coordinates. Version 0.3.0 restructured the entire public interface into three tiers: bare functions over a vector or a frame of coordinate columns, *_with() to select a method by name, and *_across() to apply one to a whole aniframe. Two functions were removed rather than deprecated, and argument names were normalized across the package.

◆ Where it's heading

The redesign pushes aniframe metadata into the processing layer — *_across() reads sampling rate and the time column off the object instead of asking the caller, which is the division of labour aniframe's own class work assumes. Defaults are shifting toward not destroying information: filters preserve gaps unless inferring across them is the point, and a missing confidence score now warns rather than being read as a poor one. The bug fixes tell a consistent per-group story, with speed computed within each track so a step never forms across a track boundary.

◆ Prediction

With the across-style API landed and issue #29 (filter_by_pose) still open, the next release most likely extends the same three-tier pattern to pose data rather than adding more filters.

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

See all aniprocess alternatives → · See all soilDBdata alternatives →

Recent activity from aniprocess and soilDBdata

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

  1. 2d agoaniprocessThree-tier filter API; filter_aniframe() removed
  2. 3mo agoaniprocessCCMA, excursion and Gaussian filters; FFT passband fix
  3. 3mo agosoilDBdataMarshall Islands FY26 gSSURGO dataset added
  4. 1y agosoilDBdataMT663 fixtures refreshed for soilDB 2.8.3
  5. 1y agosoilDBdataNASIS purpose lists updated for siteothvegclass
  6. 4y agosoilDBdataSelected-set _View_1 tables enable SS=TRUE/FALSE testing
  7. 4y agosoilDBdataProof of concept: MT663 pedon and component .sqlite fixtures

Frequently asked questions

What is the difference between aniprocess and soilDBdata?

Both compete on the same themes — r package — within Analytics. aniprocess is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 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 aniprocess better than soilDBdata?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. aniprocess is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 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 aniprocess?

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