paleobuddy
paleobuddy can now simulate trait-dependent diversification, not just birth-death.
A side-by-side editorial comparison of epikit and geos — release velocity, themes, recent moves, and the top alternatives to consider.
epikit narrows to field-epidemiology helpers, handing proportions to a sibling package
epikit is a set of small helpers for applied epidemiology in R — age categorisation, date reconstruction from partial records, and related field-data chores, developed in the R4Epis orbit. Version 0.2.0 moved the proportion functions out to epitabulate, improved how find_date_cause(), find_start_date() and find_end_date() handle dates falling outside the period, and added a floor argument to age_categories() so the lowest band reads as under one rather than zero to zero.
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.
epikit is a set of small helpers for applied epidemiology in R — age categorisation, date reconstruction from partial records, and related field-data chores, developed in the R4Epis orbit. Version 0.2.0 moved the proportion functions out to epitabulate, improved how find_date_cause(), find_start_date() and find_end_date() handle dates falling outside the period, and added a floor argument to age_categories() so the lowest band reads as under one rather than zero to zero.
The package is being scoped down rather than built out. The 0.1.3 restructuring and the 0.2.0 handover of proportions to epitabulate are the same move made twice: push functionality into the package where it belongs and keep epikit to the toolkit that field epidemiologists reach for directly. The rest of the history is dependency compatibility work against dplyr and tibble.
With proportions gone and dependencies trimmed, the remaining functions cluster tightly around dates and age bands, so further refinement of the date-reconstruction helpers is more likely than new capability areas.
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.
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 epikit or geos.
paleobuddy can now simulate trait-dependent diversification, not just birth-death.
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.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. epikit and geos 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. epikit and geos 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 epikit alternatives in Analytics are ranked by recent ship velocity. Browse the "epikit alternatives" section above for the current picks, or visit /alternatives/epikit-r for the full list with editorial commentary on each.
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.