geodist
geodist stays dependency-free and fast, and warns you when 'cheap' distances stop being honest.
A side-by-side editorial comparison of geos and paleobuddy — release velocity, themes, recent moves, and the top alternatives to consider.
The thin GEOS binding for R adds terra interop after three years of compiler triage
geos is a low-overhead R binding to the GEOS geometry engine, exposing predicates, overlays and spatial indexes with minimal copying. Version 0.2.5 accepts terra SpatVector objects directly, alongside fixes for zero-length memcpy and plotting of invalid geometries. The releases between 0.2.0 and 0.2.5 contain almost no feature work — they are responses to compiler warnings, sanitiser findings and CRAN check failures.
paleobuddy can now simulate trait-dependent diversification, not just birth-death.
paleobuddy simulates diversification, fossil records and phylogenetic trees, with rates that can be arbitrary functions of time — its founding idea, implemented through rexp.var() generalizing exponential and Weibull draws. The 1.1.0 release adds state-dependent speciation and extinction simulation at roughly MuHiSSE generality, and lets simulations stop at a target number of extant species instead of conditioning on time.
geos is a low-overhead R binding to the GEOS geometry engine, exposing predicates, overlays and spatial indexes with minimal copying. Version 0.2.5 accepts terra SpatVector objects directly, alongside fixes for zero-length memcpy and plotting of invalid geometries. The releases between 0.2.0 and 0.2.5 contain almost no feature work — they are responses to compiler warnings, sanitiser findings and CRAN check failures.
Feature development stopped after 0.2.0 and the package has since been kept alive against a moving toolchain: strict-prototypes warnings, a clang sanitiser error, format string checks, an M1 test failure. The 0.2.5 terra support breaks that pattern and came from an outside contributor, which suggests the package's direction is now set by what neighbouring spatial packages need from it rather than by GEOS feature coverage.
GEOS has released new capabilities since the 3.11 features wired up in 0.2.0, and none have been exposed since; whether the next release closes that gap or continues as interop-and-maintenance is the open question the history does not yet answer.
paleobuddy simulates diversification, fossil records and phylogenetic trees, with rates that can be arbitrary functions of time — its founding idea, implemented through rexp.var() generalizing exponential and Weibull draws. The 1.1.0 release adds state-dependent speciation and extinction simulation at roughly MuHiSSE generality, and lets simulations stop at a target number of extant species instead of conditioning on time.
Releases track the maintainer's publications rather than a product cadence — 1.0.0 accompanied the MEE manuscript, 1.0.0.1 exists purely as a Zenodo citation anchor, and 1.1.0 is stated as going with a paper on SSE model accuracy for trees including fossil data. That framing sets the direction: the package grows whichever capability the next study needs to test. The stated SSE limits, no quantitative traits and no cladogenetic transitions, mark exactly where that boundary currently sits.
Quantitative traits and cladogenetic transitions are named as missing, which makes them the obvious next targets, though on this history the timing will follow a paper rather than a roadmap.
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 geos or paleobuddy.
geodist stays dependency-free and fast, and warns you when 'cheap' distances stop being honest.
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 geos alternatives → · See all paleobuddy alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. geos and paleobuddy 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. geos and paleobuddy 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 geos alternatives in Analytics are ranked by recent ship velocity. Browse the "geos alternatives" section above for the current picks, or visit /alternatives/geos-r for the full list with editorial commentary on each.
Top paleobuddy alternatives in Analytics are ranked by recent ship velocity. Browse the "paleobuddy alternatives" section above for the current picks, or visit /alternatives/paleobuddy for the full list with editorial commentary on each.