paleobuddy
paleobuddy can now simulate trait-dependent diversification, not just birth-death.
A side-by-side editorial comparison of cairo and CatastRoNav — 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.
Navarre's cadastre client finally reaches feature parity with its bigger Spanish sibling.
CatastRoNav wraps the Cadastre of Navarre, a Spanish region that publishes its own cadastral services separately from the national system. Until 1.0.0 the package could only fetch cadastral parcels via ATOM; it now retrieves buildings and addresses through ATOM as well and adds WMS INSPIRE layer access through catrnav_wms_get_layer(). The same release relicenses to GPL-2, moves requests to httr2 with retries and switches messaging to cli.
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.
CatastRoNav wraps the Cadastre of Navarre, a Spanish region that publishes its own cadastral services separately from the national system. Until 1.0.0 the package could only fetch cadastral parcels via ATOM; it now retrieves buildings and addresses through ATOM as well and adds WMS INSPIRE layer access through catrnav_wms_get_layer(). The same release relicenses to GPL-2, moves requests to httr2 with retries and switches messaging to cli.
The package is being pulled into line with CatastRo, the maintainer's national-cadastre client: same transport, same UTF-8 normalization strategy, same option names falling back to the CatastRo equivalents. Coverage has been gated by what the Navarre Cadastre actually publishes — 0.1.0 said outright that further ATOM capabilities would arrive when the regional service made them available, and 1.0.0 is that promise landing.
Expect the next releases to track new Navarre service endpoints as they are published, and to inherit whatever maintenance pattern CatastRo adopts next.
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 CatastRoNav.
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 CatastRoNav 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 CatastRoNav 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 CatastRoNav 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 CatastRoNav alternatives in Analytics are ranked by recent ship velocity. Browse the "CatastRoNav alternatives" section above for the current picks, or visit /alternatives/catastronav for the full list with editorial commentary on each.