rjdqa
rjdqa keeps refining one screen: the seasonal adjustment quality dashboard
A side-by-side editorial comparison of lpjmlkit and rosm — release velocity, themes, recent moves, and the top alternatives to consider.
The LPJmL toolkit finally reads NetCDF, closing a gap against the format its field uses.
lpjmlkit is the R toolkit for running the LPJmL dynamic global vegetation model and reading its output. The 1.8.0 release adds direct NetCDF reading, either straight or via .nc.json metafiles, alongside the package's own binary formats. Before that, 1.7.3 sped up read_io(), reworked the LPJmLGridData implementation and added reservoir input support. Releases are infrequent, roughly one every 12 to 18 months.
rosm 0.3.0 silently deprecates its entire API and rebuilds on wk and curl
rosm downloads and stitches raster map tiles from OpenStreetMap and similar sources for use in R. After six years without a release, 0.3.0 deprecated the whole previous API, dropped the rgdal dependency, and introduced a replacement built on wk geometry and curl's multi-download interface. The follow-up 0.3.1 is documentation and CI work, plus test skips for Bing and Stamen URLs that no longer resolve.
lpjmlkit is the R toolkit for running the LPJmL dynamic global vegetation model and reading its output. The 1.8.0 release adds direct NetCDF reading, either straight or via .nc.json metafiles, alongside the package's own binary formats. Before that, 1.7.3 sped up read_io(), reworked the LPJmLGridData implementation and added reservoir input support. Releases are infrequent, roughly one every 12 to 18 months.
The work concentrates on the I/O layer rather than the modeling interface, and it is moving toward the formats the wider earth-system community already exchanges. The gap between 1.7.3 and 1.8.0 is over a year, so this is a research-group package released when the science requires it, not on a schedule. The changelog itself is thin — several entries are merge-commit text or CRAN resubmissions.
Further I/O breadth is the likeliest direction now that NetCDF is supported, though the entries give no schedule; the release cadence has not been regular enough to predict timing.
rosm downloads and stitches raster map tiles from OpenStreetMap and similar sources for use in R. After six years without a release, 0.3.0 deprecated the whole previous API, dropped the rgdal dependency, and introduced a replacement built on wk geometry and curl's multi-download interface. The follow-up 0.3.1 is documentation and CI work, plus test skips for Bing and Stamen URLs that no longer resolve.
The package is being brought back from dormancy on modern foundations rather than extended. rgdal's retirement forced the issue, and the maintainer used it to replace the download path with concurrent curl requests and to hand geometry handling to wk. What follows is consolidation: dead built-in tile sources are being tested around rather than replaced, which leaves the source registry as the obvious unfinished edge.
The dead Bing and Stamen endpoints are currently skipped rather than fixed, so the next release most likely prunes or re-points the built-in tile source list and continues retiring the silently deprecated functions.
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 lpjmlkit or rosm.
rjdqa keeps refining one screen: the seasonal adjustment quality dashboard
epikit narrows to field-epidemiology helpers, handing proportions to a sibling package
SimInf 10.0 turns an epidemic simulator into a tool that fits models to real time series
A young package porting Stata's egen row-wise helpers to the tidyverse, one function per release
A statistician's personal toolbox, growing one plotting utility at a time
R/qtl is in pure custodial mode: every recent release answers a compiler, not a user
See all lpjmlkit alternatives → · See all rosm alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. lpjmlkit and rosm 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. lpjmlkit and rosm 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 lpjmlkit alternatives in Analytics are ranked by recent ship velocity. Browse the "lpjmlkit alternatives" section above for the current picks, or visit /alternatives/lpjmlkit-r for the full list with editorial commentary on each.
Top rosm alternatives in Analytics are ranked by recent ship velocity. Browse the "rosm alternatives" section above for the current picks, or visit /alternatives/rosm for the full list with editorial commentary on each.