paleobuddy
paleobuddy can now simulate trait-dependent diversification, not just birth-death.
A side-by-side editorial comparison of geodist and rosm — release velocity, themes, recent moves, and the top alternatives to consider.
geodist stays dependency-free and fast, and warns you when 'cheap' distances stop being honest.
geodist computes geodesic distances between coordinate pairs in C with no dependencies, offering several measures that trade accuracy for speed — including a 'cheap' approximation used by default. The API is small and largely finished; 0.1.0 added geodist_min() for nearest-match lookups and 0.1.1 is a compiler warning fix.
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.
geodist computes geodesic distances between coordinate pairs in C with no dependencies, offering several measures that trade accuracy for speed — including a 'cheap' approximation used by default. The API is small and largely finished; 0.1.0 added geodist_min() for nearest-match lookups and 0.1.1 is a compiler warning fix.
Development has been about making the speed-accuracy trade visible rather than hiding it. The 0.0.6 release added messages telling users to pick a different measure once the default cheap approximation is applied beyond 100km, where its error stops being negligible. Around that, the work is input handling — tibble support, better lon/lat column matching, vector inputs — and hardening the C code. It is a package that treats being small and correct as the feature.
Expect continued low-frequency maintenance: compiler warnings and geodesic source updates account for three of the last six releases, and the function surface has grown by only two entries in five years.
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 geodist or rosm.
paleobuddy can now simulate trait-dependent diversification, not just birth-death.
errors keeps making uncertainty print the way each scientific field expects.
CMAQ went global in v5.5, and has been patching that surface ever since.
enpls has not changed its statistics since 2016 — only its website, twice.
grex is a lookup table with a version number — it ships when the annotation moves.
protr's feature set is finished; the work now is surviving Bioconductor's churn.
See all geodist alternatives → · See all rosm alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. geodist 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. geodist 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 geodist alternatives in Analytics are ranked by recent ship velocity. Browse the "geodist alternatives" section above for the current picks, or visit /alternatives/geodist-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.