qqman
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
A side-by-side editorial comparison of austraits and etn — release velocity, themes, recent moves, and the top alternatives to consider.
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.
etn stopped being an RStudio-server package and became something you can run anywhere.
etn is the R client for the European Tracking Network's acoustic telemetry database, maintained at INBO. The 3.0.0 release routes queries through an API served by the companion etnservice package, so the package no longer requires a session on the ETN RStudio server. Credentials moved out of a connection object and into .Renviron, and the data model was rescoped in 2.0.0 around tag_serial_number so acoustic work is one scope among several rather than the whole package.
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.
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.
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.
etn is the R client for the European Tracking Network's acoustic telemetry database, maintained at INBO. The 3.0.0 release routes queries through an API served by the companion etnservice package, so the package no longer requires a session on the ETN RStudio server. Credentials moved out of a connection object and into .Renviron, and the data model was rescoped in 2.0.0 around tag_serial_number so acoustic work is one scope among several rather than the whole package.
Two arcs run in parallel: widening access, and making room for non-acoustic data. The access work has been deliberate — an API-backed beta in 2024, then a stable release that picks the transport automatically and checks that a local etnservice install matches the deployed one, because the same query returning different results by transport would be worse than requiring the server. The Darwin Core export added in 2.1.0 points the same outward direction, moving data to OBIS and GBIF instead of keeping it in the ETN silo.
The cpod scope named in the 2.0.0 notes is the most likely next addition, now that the naming and the API transport are both in place to carry it.
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 etn.
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
The R package for CODATA constants rebuilt its symbol table on NIST's naming so future updates stop being hand work.
A ggplot2 layer for seasonal adjustment output, filling in one plot type at a time.
A fossil-record simulator that quietly grew a trait-evolution engine.
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
An MMRM tabulation package that has published nothing since its 2024 CRAN releases.
See all austraits alternatives → · See all etn alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — open-data — within Analytics. austraits and etn 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. austraits and etn 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.
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.
Top etn alternatives in Analytics are ranked by recent ship velocity. Browse the "etn alternatives" section above for the current picks, or visit /alternatives/etn-r for the full list with editorial commentary on each.