mapSpain
mapSpain's 1.0.0 broke every user cache to get the package onto modern foundations.
A side-by-side editorial comparison of geoarrow-r and rncl — release velocity, themes, recent moves, and the top alternatives to consider.
geoarrow tracks the GeoArrow spec and otherwise just keeps compiling
geoarrow gives R zero-copy access to geospatial data in the Arrow columnar format, with conversions to and from sf and wk. The package is thin by design — most of the work lives in vendored copies of geoarrow-c and nanoarrow — and its release notes reflect that: the substantive one in the window implemented GeoArrow 0.2 specification features, and everything since has been compiler warnings and a test fixed for a new sf version.
A phylogenetics parser on life support, shipping only what CRAN's compilers demand.
rncl wraps the Nexus Class Library so R can read Newick and NEXUS tree files. Every release since 2016 has been custodial: 0.8.9 exists solely to pull upstream NCL changes so the bundled C++ compiles under the C++20 standard. No user-facing function has changed in close to a decade.
geoarrow gives R zero-copy access to geospatial data in the Arrow columnar format, with conversions to and from sf and wk. The package is thin by design — most of the work lives in vendored copies of geoarrow-c and nanoarrow — and its release notes reflect that: the substantive one in the window implemented GeoArrow 0.2 specification features, and everything since has been compiler warnings and a test fixed for a new sf version.
Development is downstream of two things the package does not control: the GeoArrow specification and the C libraries it vendors. When the spec added non-PROJJSON CRS types and spheroidal edge interpolations, the R package followed; when the geoarrow.box type appeared, it gained conversions to and from wk::rct(). Between those, releases exist to keep CRAN builds green. The type-selection work in 0.4.0 — letting callers force geoarrow.wkb output when converting from sf — is the only recent change driven by R-side ergonomics rather than upstream.
Given that every feature release so far has implemented a spec revision, the next one likely arrives when GeoArrow publishes its next set of extension types rather than on any schedule of its own.
rncl wraps the Nexus Class Library so R can read Newick and NEXUS tree files. Every release since 2016 has been custodial: 0.8.9 exists solely to pull upstream NCL changes so the bundled C++ compiles under the C++20 standard. No user-facing function has changed in close to a decade.
The release cadence tracks toolchain deprecations rather than user demand: gcc 12 removing binary_function in 2022, a deprecated Rcpp call in 2025, C++20 in 2026. The package is maintained as a stable parsing dependency for phylogenetics tooling, and the goal visible in these entries is keeping it installable, not extending it.
Expect the next release only when a compiler or CRAN policy change breaks the build again; nothing in these entries points to new parsing features.
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 geoarrow-r or rncl.
mapSpain's 1.0.0 broke every user cache to get the package onto modern foundations.
A Berlin groundwater scraper grew a full IoT publishing pipeline in two days.
cheapr turned multi-threaded, and its next stop is a C++20 public API.
RadialMR's 2026 release corrects degrees of freedom that had been wrong since documentation.
mrbayes spent 2026 auditing its own Bayesian MR estimators for coding errors.
lineup2 ships once every few years, and 2026's release is a logo and a core-count tweak.
See all geoarrow-r alternatives → · See all rncl alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. rncl is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. 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. rncl is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top geoarrow-r alternatives in Analytics are ranked by recent ship velocity. Browse the "geoarrow-r alternatives" section above for the current picks, or visit /alternatives/geoarrow-r for the full list with editorial commentary on each.
Top rncl alternatives in Analytics are ranked by recent ship velocity. Browse the "rncl alternatives" section above for the current picks, or visit /alternatives/rncl-r for the full list with editorial commentary on each.