← Back to home
Comparison · Analytics

ecodive vs rATTAINS

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

Shared themes:r-package

ecodive vs rATTAINS: at a glance

FeatureecodiverATTAINS
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesmicrobiome, ecology, diversity-metrics, unifracwater-quality, epa-data, r-package, api-wrapper
Last editorial update1h ago3h ago
WebsiteVisit →Visit →

What is ecodive?

ecodive rebuilt itself into a broad diversity-metric library, breaking as it went

ecodive computes alpha and beta diversity metrics for ecological and microbiome count data, including phylogenetic measures like Faith's PD and the UniFrac family. The 2.0.0 rewrite expanded it from a handful of metrics to roughly fourteen alpha and thirty beta measures while flipping the expected input orientation to samples-as-rows. Subsequent releases have been spent settling the normalisation interface that expansion exposed.

Read the full ecodive trajectory →

What is rATTAINS?

The R client for EPA water quality data spent two releases undoing its own promises about data shape.

rATTAINS wraps the EPA's ATTAINS API, which holds state water quality assessments and impaired-waters listings. The package reached 1.0.0 by promising stable, consistently rectangled return structures, then walked that promise back in 1.1.0 when it dropped the dependency doing the rectangling. As of 1.2.0 it also requires an API key, because ATTAINS itself began requiring one in May 2026.

Read the full rATTAINS trajectory →

ecodive vs rATTAINS: editorial side-by-side

E
ecodive
ANALYTICS
0.0

ecodive rebuilt itself into a broad diversity-metric library, breaking as it went

◆ Current state

ecodive computes alpha and beta diversity metrics for ecological and microbiome count data, including phylogenetic measures like Faith's PD and the UniFrac family. The 2.0.0 rewrite expanded it from a handful of metrics to roughly fourteen alpha and thirty beta measures while flipping the expected input orientation to samples-as-rows. Subsequent releases have been spent settling the normalisation interface that expansion exposed.

◆ Where it's heading

This is a package that made its breaking changes deliberately and in a cluster. After 2.0.0 reoriented input and removed the weighted parameter, 2.1.0 superseded rescale with norm, and 2.2.6 changed norm's default from percent to none and removed it from some beta functions entirely. That last one matters more than it reads: normalisation defaults silently change the numbers a metric returns, and the direction is toward making the user state their choice rather than inheriting one.

◆ Prediction

With the metric surface broad and the normalisation interface now explicit, expect the next releases to stabilise — documentation and edge-case handling around CLR and rarefaction rather than another interface break.

R
rATTAINS
ANALYTICS
0.0

The R client for EPA water quality data spent two releases undoing its own promises about data shape.

◆ Current state

rATTAINS wraps the EPA's ATTAINS API, which holds state water quality assessments and impaired-waters listings. The package reached 1.0.0 by promising stable, consistently rectangled return structures, then walked that promise back in 1.1.0 when it dropped the dependency doing the rectangling. As of 1.2.0 it also requires an API key, because ATTAINS itself began requiring one in May 2026.

◆ Where it's heading

The direction is toward a thinner, lower-maintenance wrapper. Caching went in 0.1.4 when hoardr was archived, tidyjson and janitor went earlier, tibblify went in 1.1.0, and each removal handed a little more data-shaping responsibility back to the user — the current advice is to pass .unnest = FALSE and rectangle the results with whatever tidying package you prefer. Release cadence is slow and mostly reactive: upstream API terms, archived dependencies, and compatibility with test tooling account for most of the log. The package's centre of gravity is staying installable and honest about what ATTAINS returns rather than smoothing it over.

◆ Prediction

Given the pattern, the next release is likelier to be a compatibility or upstream-driven fix than new endpoint coverage; how the API key requirement affects users in scripted and CI contexts is the obvious open question the entries do not yet answer.

Alternatives to ecodive and rATTAINS

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 ecodive or rATTAINS.

See all ecodive alternatives → · See all rATTAINS alternatives →

Recent activity from ecodive and rATTAINS

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

  1. 1mo agorATTAINSATTAINS now requires an API key, and the package follows
  2. 4mo agoecodiveNormalisation now defaults to none, with CLR zero warnings
  3. 7mo agoecodiveecodive 2.2.2
  4. 8mo agorATTAINSThe tibblify dependency goes, and with it the stable data shapes
  5. 10mo agoecodiverescale superseded by norm; crash fixes after the 2.0.0 rewrite
  6. 10mo agoecodive2.0.0 expands to ~14 alpha and ~30 beta diversity metrics
  7. 1y agorATTAINSTest suite updated for vcr v2
  8. 3y agorATTAINS1.0.0 commits to stable return structures via tibblify
  9. 3y agorATTAINSCaching removed after hoardr was archived
  10. 4y agorATTAINSRequests retry on timeout, with offline detection

Frequently asked questions

What is the difference between ecodive and rATTAINS?

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

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

Top ecodive alternatives in Analytics are ranked by recent ship velocity. Browse the "ecodive alternatives" section above for the current picks, or visit /alternatives/ecodive for the full list with editorial commentary on each.

What are the best alternatives to rATTAINS?

Top rATTAINS alternatives in Analytics are ranked by recent ship velocity. Browse the "rATTAINS alternatives" section above for the current picks, or visit /alternatives/rattains for the full list with editorial commentary on each.