rjd3highfreq
rjd3highfreq ships whatever the Java side ships, and only occasionally says what that was.
A side-by-side editorial comparison of n2kanalysis and wasserportal — release velocity, themes, recent moves, and the top alternatives to consider.
n2kanalysis has spent eight years wiring INLA models to an S3 bucket.
n2kanalysis is the analysis framework behind INBO's nature monitoring networks, wrapping INLA model fitting with a manifest-driven pipeline whose intermediate objects live in S3. Capability has arrived in discrete lumps: hurdle models with imputation and a manifest-to-bash converter in 0.3.1, SPDE spatial elements in INLA models in 0.4.0, and in 0.4.1 a connect_inbo_s3() function that makes temporary credentials available to the R functions.
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.
n2kanalysis is the analysis framework behind INBO's nature monitoring networks, wrapping INLA model fitting with a manifest-driven pipeline whose intermediate objects live in S3. Capability has arrived in discrete lumps: hurdle models with imputation and a manifest-to-bash converter in 0.3.1, SPDE spatial elements in INLA models in 0.4.0, and in 0.4.1 a connect_inbo_s3() function that makes temporary credentials available to the R functions.
Development is slow, institutional, and driven by the modeling needs of specific monitoring programmes rather than a product roadmap. The pattern across the window is a new model class when the ecology requires one, then a stretch of infrastructure work around storage, credentials and pipeline efficiency. The 0.4.1 release is characteristic — a credentials helper, better result retrieval, more tests and a code-style pass, with no modeling change at all. Much of the early history is recorded only as merge-commit titles, so the release record thins out the further back it goes.
Expect the next substantive release to add another INLA model variant as a monitoring programme needs it, with S3 and credential handling continuing to absorb the maintenance effort in between.
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 n2kanalysis or wasserportal.
rjd3highfreq ships whatever the Java side ships, and only occasionally says what that was.
audubon's release feed is almost entirely Renovate bumping the JavaScript toolchain behind its Japanese text splitter.
affiner is quietly turning a grid transformation helper into a small computational geometry library.
ageproR spent two years chasing a moving file format, then added the recruitment models that justify the effort.
ledger adds a Rust toolchain fallback, so beancount imports work whether or not the Python tooling is installed.
gridpattern keeps widening its catalogue, and the newest patterns finally use the device's own line rendering.
See all n2kanalysis alternatives → · See all wasserportal alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. n2kanalysis 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. n2kanalysis 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 n2kanalysis alternatives in Analytics are ranked by recent ship velocity. Browse the "n2kanalysis alternatives" section above for the current picks, or visit /alternatives/n2kanalysis 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.