paleobuddy
paleobuddy can now simulate trait-dependent diversification, not just birth-death.
A side-by-side editorial comparison of cairo and geomander — release velocity, themes, recent moves, and the top alternatives to consider.
Cairo finally catches R's graphics engine, all the way to GE API 16.
Cairo is the R device that renders plots through the cairo library, and until 1.7-0 it lagged R's own graphics engine by several API generations. That release closes the gap to GE API 16 (R 4.5.0), adding fill patterns, masks and groups. The releases before it were maintenance: a segfault shim for grid, a bashism removal in configure, and Windows font and build fixes.
A redistricting toolkit that grows mostly by wiring in new public data sources
geomander provides geographic tools for redistricting analysis in R — matching and aggregating across block, VTD and district geometries, spatial diagnostics, and download helpers for the datasets the field relies on. Recent work splits between data access, with fetchers added for Jeffrey B. Lewis's historical congressional districts and RPV Near Me, and performance, with 2.5.0 delivering large speed gains in geo_match().
Cairo is the R device that renders plots through the cairo library, and until 1.7-0 it lagged R's own graphics engine by several API generations. That release closes the gap to GE API 16 (R 4.5.0), adding fill patterns, masks and groups. The releases before it were maintenance: a segfault shim for grid, a bashism removal in configure, and Windows font and build fixes.
The arc is catch-up, executed one API generation at a time. Glyph rendering arrived in 1.6-3, GE 15 stubs in 1.6-5 existed only to stop grid from segfaulting, and 1.7-0 delivers the real GE 13/14/16 feature set rather than placeholders. Alongside that, dropping the CAIROGD_VER C API and the mkdist step means the package now builds with plain R CMD build, which reads as deliberate reduction of maintenance overhead.
Expect the next releases to be corrective rather than additive: the entries show every API adoption here has been followed by a fix release, and patterns, masks and groups are a much larger surface than glyphs were.
geomander provides geographic tools for redistricting analysis in R — matching and aggregating across block, VTD and district geometries, spatial diagnostics, and download helpers for the datasets the field relies on. Recent work splits between data access, with fetchers added for Jeffrey B. Lewis's historical congressional districts and RPV Near Me, and performance, with 2.5.0 delivering large speed gains in geo_match().
The package is consolidating as infrastructure rather than expanding its analytical surface. Each release either adds a source of redistricting data that users would otherwise download by hand, or makes the core geographic matching operations faster and more correct — the normalized global Moran's I correction and the block-level geometry mismatch fix both fall in the second category. geo_match() being the target of the most recent release confirms where the hot path is.
With geo_match() now optimised, the remaining friction is in the download helpers, several of which have needed repair after upstream changes; expect the next release to consolidate or harden those fetchers rather than add analysis 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 cairo or geomander.
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.
See all cairo alternatives → · See all geomander alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. cairo and geomander 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. cairo and geomander 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 cairo alternatives in Analytics are ranked by recent ship velocity. Browse the "cairo alternatives" section above for the current picks, or visit /alternatives/cairo-r for the full list with editorial commentary on each.
Top geomander alternatives in Analytics are ranked by recent ship velocity. Browse the "geomander alternatives" section above for the current picks, or visit /alternatives/geomander-r for the full list with editorial commentary on each.