tern.rbmi
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
A side-by-side editorial comparison of geoarrow-r and protr — 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.
protr's feature set is finished; the work now is surviving Bioconductor's churn.
protr generates numerical descriptors from protein sequences for machine learning, plus alignment-based similarity between sequences. The descriptor functions have been stable for years. Recent releases divide cleanly into two kinds: extending the similarity computations to work under memory constraints, and absorbing the Bioconductor split that moved pairwise alignment out of Biostrings into pwalign.
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.
protr generates numerical descriptors from protein sequences for machine learning, plus alignment-based similarity between sequences. The descriptor functions have been stable for years. Recent releases divide cleanly into two kinds: extending the similarity computations to work under memory constraints, and absorbing the Bioconductor split that moved pairwise alignment out of Biostrings into pwalign.
The similarity side is where the remaining engineering goes, and it follows a consistent pattern — whatever parSeqSim() gained, crossSetSim() eventually gets. Batching, verbose progress and a disk-backed variant all arrived for the single-set case first and were mirrored for the cross-set case in 1.7-1. That is a maintainer closing feature-parity gaps rather than opening new directions, and the two most recent releases contain no user-facing change at all.
Expect the next release to react to another Bioconductor or R CMD check change, which accounts for three of the last four. The similarity functions now have parity, so there is no obvious internal backlog left.
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 protr.
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
An MMRM tabulation package that has published nothing since its 2024 CRAN releases.
A single-purpose ggplot2 inset tool, refining the same three arguments.
An R symbolic-maths binding whose changelog is really the C++ core's release notes.
gtfstools stopped guarding its own object model and started accepting everyone else's.
The glue package that makes R carry units and uncertainty through the same calculation.
See all geoarrow-r alternatives → · See all protr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. geoarrow-r and protr 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. geoarrow-r and protr 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 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 protr alternatives in Analytics are ranked by recent ship velocity. Browse the "protr alternatives" section above for the current picks, or visit /alternatives/protr-r for the full list with editorial commentary on each.