rjdqa
rjdqa keeps refining one screen: the seasonal adjustment quality dashboard
A side-by-side editorial comparison of geoarrow-r and oblicubes — 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 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.
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.
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 geoarrow-r or oblicubes.
rjdqa keeps refining one screen: the seasonal adjustment quality dashboard
epikit narrows to field-epidemiology helpers, handing proportions to a sibling package
SimInf 10.0 turns an epidemic simulator into a tool that fits models to real time series
A young package porting Stata's egen row-wise helpers to the tidyverse, one function per release
A statistician's personal toolbox, growing one plotting utility at a time
R/qtl is in pure custodial mode: every recent release answers a compiler, not a user
See all geoarrow-r alternatives → · See all oblicubes alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r — within Analytics. geoarrow-r 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. geoarrow-r 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 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 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.