← Back to home
Comparison · Analytics

austraits vs ggdemetra

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

austraits vs ggdemetra: at a glance

Featureaustraitsggdemetra
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesplant-traits, open-data, ecology, zenodoseasonal-adjustment, ggplot2, time-series, tramo-seats
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

What is austraits?

The R client for AusTraits spends its releases chasing the dataset it reads.

austraits is the R access layer for the AusTraits plant trait database, and its release history is almost entirely a record of keeping pace with two upstream systems it does not control: the austraits.build data releases and the Zenodo archive that hosts them. The most recent release adds a version-dispatch layer so the same package can read both v4.x and v5.0.0 data. Three of the four visible tags were backfilled to GitHub within 23 minutes of each other, so version order and publication order do not agree.

Read the full austraits trajectory →

What is ggdemetra?

A ggplot2 layer for seasonal adjustment output, filling in one plot type at a time.

ggdemetra is a thin, focused bridge: it puts RJDemetra's seasonal adjustment results — TRAMO-SEATS and X-13 models — into ggplot2 geoms and autoplot methods. Development runs in short bursts separated by long quiet stretches, and the most recent work has been correcting SI ratio handling rather than adding surface. The API is small enough that a single function rename counts as the notable change in a release.

Read the full ggdemetra trajectory →

austraits vs ggdemetra: editorial side-by-side

A
austraits
ANALYTICS
0.0

The R client for AusTraits spends its releases chasing the dataset it reads.

◆ Current state

austraits is the R access layer for the AusTraits plant trait database, and its release history is almost entirely a record of keeping pace with two upstream systems it does not control: the austraits.build data releases and the Zenodo archive that hosts them. The most recent release adds a version-dispatch layer so the same package can read both v4.x and v5.0.0 data. Three of the four visible tags were backfilled to GitHub within 23 minutes of each other, so version order and publication order do not agree.

◆ Where it's heading

The package is converging on a stable public vocabulary and a versioned internal. Sites became locations across every join, plot and extract function; the extract_ and print family filled out at 1.0.0; and by 2.2.2 the core functions each carry a switch on the detected data version rather than assuming one schema. The visible cost of that is dependency churn — plotting packages moved to Suggests, which the notes admit can leave core functions unable to run.

◆ Prediction

Given that every release so far has been triggered by an upstream austraits.build or Zenodo change, the next one most likely follows the next data release rather than any independent roadmap. The entries do not indicate new analysis capability being planned in the client itself.

G
ggdemetra
ANALYTICS
0.0

A ggplot2 layer for seasonal adjustment output, filling in one plot type at a time.

◆ Current state

ggdemetra is a thin, focused bridge: it puts RJDemetra's seasonal adjustment results — TRAMO-SEATS and X-13 models — into ggplot2 geoms and autoplot methods. Development runs in short bursts separated by long quiet stretches, and the most recent work has been correcting SI ratio handling rather than adding surface. The API is small enough that a single function rename counts as the notable change in a release.

◆ Where it's heading

The package has been steadily completing its coverage of the seasonal adjustment output surface: component extractors and autoplot methods in 0.2.3, SI ratio plotting in 0.2.5, then two releases of corrections to make SI ratios behave under TRAMO-SEATS jSA models and when no seasonal component is exported. Alongside that, the naming is being tidied — y_forecast() became raw(), and init_ggplot() shortened the setup boilerplate. This reads as a package approaching the edge of its intended scope and spending its effort on correctness.

◆ Prediction

Two consecutive releases fixing SI ratios under TRAMO-SEATS suggest that code path is the least settled part of the package, so further corrections there are the most likely next move. The entries give no indication of new model families or plot types being planned.

Alternatives to austraits and ggdemetra

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 austraits or ggdemetra.

See all austraits alternatives → · See all ggdemetra alternatives →

Recent activity from austraits and ggdemetra

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

  1. 2y agoggdemetrasiratio() fix when TRAMO-SEATS exports no seasonal component
  2. 2y agoggdemetraraw() replaces y_forecast(); new init_ggplot() helper
  3. 2y agoggdemetraRe-tagged moments later as 0.2.7
  4. 2y agoaustraitsSupport for AusTraits 5.0.0 data and the rebuilt Zenodo API
  5. 3y agoggdemetraSI ratio plotting functions land
  6. 3y agoaustraitsextract_taxa, lookup_trait and print methods arrive
  7. 3y agoaustraitsVignette build and extract_ function polish
  8. 3y agoaustraitssite becomes location across the API; AusTraits 3.0.2+ support
  9. 5y agoggdemetrats2df() conversion helper and geom_outlier date fix
  10. 6y agoggdemetrageom_arima no longer recomputes the model

Frequently asked questions

What is the difference between austraits and ggdemetra?

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

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

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

What are the best alternatives to ggdemetra?

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