← Back to home
Comparison · Analytics

rATTAINS vs trendseries

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

Shared themes:r-package

rATTAINS vs trendseries: at a glance

FeaturerATTAINStrendseries
SectorAnalyticsAnalytics
Velocity score0.03.8
Sparks · 30d01
Top themeswater-quality, epa-data, r-package, api-wrappertime-series, econometrics, r-package, seasonal-decomposition
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

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 →

What is trendseries?

A trend-extraction toolkit grows a full decomposition engine, seasonal components and all.

trendseries extracts trends from economic time series through two pipe-friendly functions, backed by an unusually broad method set — Hodrick-Prescott in one- and two-sided variants, Baxter-King, Christiano-Fitzgerald, Hamilton regression, Beveridge-Nelson, unobserved components, plus the moving average and smoothing family. The 1.4 release adds decomposition proper: an exported decompose_series() that splits a series into trend, seasonal, and remainder across five methods and guarantees the components add back to the original values.

Read the full trendseries trajectory →

rATTAINS vs trendseries: editorial side-by-side

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.

T
trendseries
ANALYTICS
3.8

A trend-extraction toolkit grows a full decomposition engine, seasonal components and all.

◆ Current state

trendseries extracts trends from economic time series through two pipe-friendly functions, backed by an unusually broad method set — Hodrick-Prescott in one- and two-sided variants, Baxter-King, Christiano-Fitzgerald, Hamilton regression, Beveridge-Nelson, unobserved components, plus the moving average and smoothing family. The 1.4 release adds decomposition proper: an exported decompose_series() that splits a series into trend, seasonal, and remainder across five methods and guarantees the components add back to the original values.

◆ Where it's heading

The package is moving from breadth of methods to rigour about what those methods produce. Recent work has been about defaults and guarantees rather than new filters: the unobserved components model now derives its signal-to-noise ratios from Hodrick-Prescott lambdas so the default output is economically interpretable, decomposition carries an exact additive identity, and a log transform gives a uniform multiplicative variant across every method. Naming is being tidied in the same spirit, with group_vars deprecated in favour of group_cols. Side-by-side method comparison — passing several methods and getting each one's components as separate columns — suggests an audience that treats method choice as a research question rather than a setting.

◆ Prediction

Expect the comparison and diagnostic side to keep developing, since the package now produces multiple decompositions of the same series and offers no ranking between them; the entries give no indication of new filters being queued.

Alternatives to rATTAINS and trendseries

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

See all rATTAINS alternatives → · See all trendseries alternatives →

Recent activity from rATTAINS and trendseries

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

  1. 15d agotrendseriesDecomposition becomes a first-class operation, five methods deep
  2. 1mo agorATTAINSATTAINS now requires an API key, and the package follows
  3. 3mo agotrendseriesMulti-column trends and economically grounded UCM defaults
  4. 8mo agorATTAINSThe tibblify dependency goes, and with it the stable data shapes
  5. 10mo agotrendseriesFirst production release with 21 trend extraction methods
  6. 1y agorATTAINSTest suite updated for vcr v2
  7. 3y agorATTAINS1.0.0 commits to stable return structures via tibblify
  8. 3y agorATTAINSCaching removed after hoardr was archived
  9. 4y agorATTAINSRequests retry on timeout, with offline detection

Frequently asked questions

What is the difference between rATTAINS and trendseries?

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

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

What are the best alternatives to trendseries?

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