EvoPhylo
EvoPhylo added BEAST2 alongside MrBayes, then went quiet for two years.
A side-by-side editorial comparison of geos and oblicubes — 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.
A tiny grid renderer for oblique-projection cubes, complete since its first release.
oblicubes draws 3D cubes and cuboids in oblique projection as grid grobs, with ggplot2 geom wrappers and a height-matrix helper for turning elevation data into coordinates. The entire feature set arrived in the initial 0.1.2 release, adapted from coolbutuseless's isocubes and cj-holmes's isocuboids. The two releases since have widened compatibility rather than added anything.
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.
oblicubes draws 3D cubes and cuboids in oblique projection as grid grobs, with ggplot2 geom wrappers and a height-matrix helper for turning elevation data into coordinates. The entire feature set arrived in the initial 0.1.2 release, adapted from coolbutuseless's isocubes and cj-holmes's isocuboids. The two releases since have widened compatibility rather than added anything.
The package is finished and its maintainer is treating it that way. 1.0.0 removed the R 4.1 native pipe from examples specifically so earlier R versions could use it — reaching backward, not forward — and added image alt text. The only change since is swapping a deprecated dplyr call in examples.
Expect nothing beyond occasional dependency deprecation fixes; the release pattern shows a small, deliberately complete package being kept installable.
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 oblicubes.
EvoPhylo added BEAST2 alongside MrBayes, then went quiet for two years.
treespace ships once every year or two, and only when CRAN or a user forces it.
Rpath 1.1.0 learns to read Ecopath's own files, easing migration off the desktop tool.
TAF keeps turning ICES stock assessments into reproducible, dependency-pinned projects.
parallelDist is in pure preservation mode — one build fix every few years.
Cairo finally catches R's graphics engine, all the way to GE API 16.
See all geos alternatives → · See all oblicubes 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 oblicubes 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 oblicubes 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 oblicubes alternatives in Analytics are ranked by recent ship velocity. Browse the "oblicubes alternatives" section above for the current picks, or visit /alternatives/oblicubes-r for the full list with editorial commentary on each.