qqman
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
A side-by-side editorial comparison of austraits and wasserportal — 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.
A Berlin groundwater scraper grew a full IoT publishing pipeline in two days.
wasserportal scrapes groundwater and surface water monitoring data from Wasserportal Berlin — station metadata, water levels, quality series. For its first four years that was the whole product, with releases tracking the portal's own churn: a new API version in 2023, new three-letter variable codes, and a 2026 fix decoding pages as windows-1252 because the server declares UTF-8 but emits Latin-1. In June 2026 it added a ThingsBoard integration, then extended it to self-hosted instances two days later.
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.
wasserportal scrapes groundwater and surface water monitoring data from Wasserportal Berlin — station metadata, water levels, quality series. For its first four years that was the whole product, with releases tracking the portal's own churn: a new API version in 2023, new three-letter variable codes, and a 2026 fix decoding pages as windows-1252 because the server declares UTF-8 but emits Latin-1. In June 2026 it added a ThingsBoard integration, then extended it to self-hosted instances two days later.
The package is repositioning from a data-access library into the first half of a monitoring pipeline. 0.6.0 shipped push helpers, device discovery and cleanup, an importable dashboard and a GitHub Actions workflow; 0.7.0 immediately generalised the authentication so it works against self-hosted Community Edition rather than only the Cloud tier, and lifted the push from a five-station demo to the entire groundwater archive. The hardening detail in 0.7.0 — retries on 5xx, warnings when only one of two credentials is set — reads like a maintainer who has run this against a real deployment.
The obvious next step is extending the ThingsBoard path to the surface water stations, which the package has flagged as under-supported since 0.1.0. The entries show no other direction under construction.
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 wasserportal.
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 wasserportal alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — open-data — within Analytics. austraits and wasserportal 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 wasserportal 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 wasserportal alternatives in Analytics are ranked by recent ship velocity. Browse the "wasserportal alternatives" section above for the current picks, or visit /alternatives/wasserportal for the full list with editorial commentary on each.