HydroPortailStats
France's national flood statistics, ported out of Fortran and into R.
A side-by-side editorial comparison of ltertools and offsetreg — release velocity, themes, recent moves, and the top alternatives to consider.
A column-key toolkit for stitching decades of ecological field data into one table.
ltertools serves the Long Term Ecological Research network, where the same measurement carries a different column name at every site and in every era. Its core is a column key: begin_key drafts one, harmonize applies it, and the 2.0.0 release added check_key to validate a key and standardize to apply one to a single dataset. Harmonization of files above 5 MB now runs in roughly half the time.
The parsnip extension for exposure models grew from one algorithm to three
offsetreg supplies parsnip model specifications for regressions with offsets, the form actuarial and epidemiological work needs when modelling rates over exposure. It launched with a single specification, poisson_reg_offset(), backed by glm and glmnet engines. Version 1.1.0 added two more model types - boost_tree_offset() for boosted trees via xgboost and decision_tree_exposure() for weighted decision trees via rpart - and 1.2.0 has been consolidation: argument passthrough to the underlying glm and glmnet calls, an xgboost 3.0 minimum with API accommodation, and cli-formatted messages.
ltertools serves the Long Term Ecological Research network, where the same measurement carries a different column name at every site and in every era. Its core is a column key: begin_key drafts one, harmonize applies it, and the 2.0.0 release added check_key to validate a key and standardize to apply one to a single dataset. Harmonization of files above 5 MB now runs in roughly half the time.
Development has moved from breadth to depth. The first year added assorted utilities — temperature conversion, solar day length, a site timeline — while the last two releases have concentrated on the key workflow itself: incremental key expansion, validation, per-dataset application, and speed. A dependency archival forced the removal of the JSON helper, trimming the package back toward that core.
The key workflow now has draft, expand, check and apply steps, so the remaining gap is diagnostics on the harmonized output; the entries show no other thread in progress.
offsetreg supplies parsnip model specifications for regressions with offsets, the form actuarial and epidemiological work needs when modelling rates over exposure. It launched with a single specification, poisson_reg_offset(), backed by glm and glmnet engines. Version 1.1.0 added two more model types - boost_tree_offset() for boosted trees via xgboost and decision_tree_exposure() for weighted decision trees via rpart - and 1.2.0 has been consolidation: argument passthrough to the underlying glm and glmnet calls, an xgboost 3.0 minimum with API accommodation, and cli-formatted messages.
The package is following the tidymodels extension playbook: establish one model type, then add types rather than engines, and keep pace with parsnip's own releases. Each version has also tightened the guardrails around correct use - a vignette on when offsetreg should and should not be used, check_args() methods on the specifications - which suggests the maintainer is fielding misapplication rather than feature requests.
Expect additional engines under the existing model types, or a fourth specification, before any change to the offset handling itself, since the package's structure invites extension at the engine layer.
Other Infra & APIs 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 ltertools or offsetreg.
France's national flood statistics, ported out of Fortran and into R.
Sign, zero and narrative restrictions brought into the bsvars ecosystem.
Fast design-based estimators for experiments, coasting on CRAN patches.
The grammar of uncertainty visualization, now drawing the uncertainty in its own estimates.
IP address vectors for R that hit 1.0 and then went quiet.
Microsoft's automated forecasting framework, still mostly a one-maintainer effort.
See all ltertools alternatives → · See all offsetreg alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Infra & APIs. ltertools and offsetreg 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. ltertools and offsetreg 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 Infra & APIs products to evaluate alongside.
Top ltertools alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "ltertools alternatives" section above for the current picks, or visit /alternatives/ltertools for the full list with editorial commentary on each.
Top offsetreg alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "offsetreg alternatives" section above for the current picks, or visit /alternatives/offsetreg for the full list with editorial commentary on each.